Fizook Scenarios.

Process overview

This is the cold-start journey for a brand-new restaurant. The vendor lands on the consumer marketing page, gets pulled in by the bright vendor invite ribbon, signs up, signs in, fills in the restaurant info that powers their vendor profile, and walks through the seven-section offer builder one card at a time. The walkthrough pays extra attention to the Availability section — days of the week, hours of the day, date ranges, and blackout dates — because those settings decide whether an offer ever appears in a live auction. It finishes with how the vendor manages a running roster: editing, pausing without deleting, and deleting outright.

Flow shown to the new vendor

Each step below corresponds to one stop on the flow above. Follow them in order to reproduce the full walkthrough.

Steps for a new vendor to register, build a profile, and manage offers

1. Discover Fizook on the consumer landing page

   The restaurant owner lands on index.html — the consumer-facing entry page. As they scroll past the diner-focused hero and live bidder demo, they hit the big animated ribbon labelled "Want diners coming to YOU?" sitting between the audience picker and the final CTA. The ribbon is built specifically to catch the eye of a restaurant owner who showed up looking for the diner experience.

   Entry point Marketing page

2. Click the vendor invite ribbon

   Clicking the ribbon (or the "I run a restaurant" audience picker card) routes the user to fizook-vendor-login.html. The vendor login page is themed in green and amber so it visually distinguishes itself from the consumer surface, and the call to action is unambiguous: existing vendors sign in, new vendors create an account.

   Vendor doorway

3. Open the vendor sign-up page

   From the vendor login page the new vendor clicks the "Create a vendor account" link in the form footer, the audience picker, or the final CTA button. All three route to fizook-vendor-register.html, the vendor registration form.

   Sign up entry

4. Fill out the vendor registration form

   The registration form asks for everything Fizook needs to onboard the restaurant: legal restaurant name, owner first and last name, vendor email (with live validation), a vendor username, a password and a confirmation (with strength meter and match check), the restaurant phone, the full street address with city, state, ZIP, the cuisine type, and an optional Tax ID / EIN. Two required checkboxes confirm the Terms of Service and the user’s authority to register the restaurant. Submit lands them on the offer builder.

   Registration 13 fields

5. Sign in as a vendor

   For return visits, the vendor signs in from fizook-vendor-login.html using the email or username and password they just registered. The login page’s glassmorphic card mirrors the consumer login on the index page but is themed for restaurant owners and lands them directly on the offer builder rather than the diner auction setup.

   Authentication

6. Land on the offer builder

   The vendor arrives on fizook-vendor.html — the seven-section offer builder. A sticky section navigator runs across the top so the vendor can jump between Restaurant Info, Meal Details, Pricing & Auction, Card Display, Fulfillment, Availability, and Notifications. A saved-offers panel on the right rail will hold every offer they publish from this page forward.

   Offer builder 7 sections

7. Configure the Restaurant Info (vendor profile)

   Section 1 doubles as the vendor profile. Upload a square restaurant logo (shown on every offer card), then fill in the legal restaurant name, the brand display name that appears to diners, the restaurant phone, the vendor email, the manager on shift, the optional business license, and the full address. Everything entered here flows through to every offer the vendor publishes, so it only needs to be filled in once.

   Section 1 Profile

8. Add the Meal Details for the first offer

   Section 2 captures the meal itself: a square meal photo (at least 400 by 400), the meal name, a description, the meal type (breakfast / lunch / dinner / snack / late night), the cuisine, the portion size, an optional calorie count, a spice slider, what the meal includes (sides, drinks, sauces), the dietary tags, and the allergens. A toggle at the bottom decides whether diners can request modifications via a short note.

   Section 2 Meal info

9. Set pricing and auction limits

   In Section 3 the vendor enters the retail price, the starting auction price (usually 10–20 percent below retail), the floor price they refuse to drop below, and the maximum discount percentage. The auction-limit fields cap how many of this meal can sell per hour and per day, and three auto-decline toggles let Fizook bail out automatically when an auction hits the floor, when capacity is full, or when the offer is outside scheduled hours.

   Section 3 Pricing

10. Tune Card Display, Fulfillment, and Notifications

    Sections 4 through 7 cover the diner-facing polish and the kitchen-facing wiring. Toggle which adornments appear on the offer card (on-fire badge, strength bars, vendor stats). Pick the service modes (dine-in, pickup, delivery), the average prep time, and the accepted payment methods. Finally, choose where alerts land — KDS, email, SMS, or all three — and what triggers them (every accepted offer, only sub-floor deals, or end-of-auction summaries).

    Sections 4 – 5 – 7

11. Schedule the offer (days, hours, dates, blackouts)

    Section 6, Availability, is the heart of an offer’s lifecycle. Activate the days of the week the offer should run by tapping the day pills. Activate the hours of the day on the 24-hour grid — each hour button opens a popup so the vendor can pin a precise start minute (:00, :15, :30, :45) or turn the hour off entirely. Set an active-from date and an optional end date if the offer is a limited-time campaign. Add any blackout dates — holidays, private events, or known closures — as a comma-separated list.

    Scheduling controls auction eligibility

    An offer is only invited to a live auction when the current day-of-week AND hour both fall inside its schedule, the date sits inside the active-from / end date window, and today is not in the blackout list. Skip this section and the offer keeps the form defaults — which means Monday through Friday only. A Saturday or Sunday auction will never see it.

    Section 6 Schedule gate

12. Publish the offer

    At the bottom of the form the vendor clicks Publish offer. The page calls publishOffer(), which gathers every field across all seven sections into a single offer object, writes it to localStorage['fz-offers'], and refreshes the saved-offers panel. The page scrolls the panel into view so the vendor sees their newly published offer drop in as the top row.

    Persistence

13. Manage offers from the saved-offers panel

    The saved-offers panel becomes the vendor’s command center. Every row shows a thumbnail, the meal name, the current price, the schedule summary, and a pair of icon buttons. The pencil Edit button loads the offer back into the form so the vendor can change anything — the meal photo, the price, the schedule, the allergens — and re-publish to save the update. The trash Delete button drops the offer entirely after a confirmation prompt.

    Edit + delete Lifecycle

14. Pause an offer to take it out of auctions without deleting it

    When the vendor wants to take an offer offline temporarily — a sold-out ingredient, a slow shift, a holiday week — they edit the offer and tap the Pause this offer button inside the Availability section. The button flips to red and the saved-offers row picks up a Paused badge.

    Pause keeps the offer; only auctions ignore it

    Pausing flips one boolean on the offer (availability.paused: true). The offer stays in storage with all its settings intact — pricing, schedule, allergens, photo — but the auction’s eligibility check on fzk-new.html skips it, so diners never see it. Edit the offer again and tap This offer is paused to resume.

    Pause vs delete Reversible

15. Run an auction to see the offer compete

    From the saved-offers panel the vendor clicks Run auction with these offers. The auction page fzk-new.html reads every offer from localStorage['fz-offers'], filters them by current eligibility (schedule, dates, blackouts, paused state), groups by vendor so each restaurant becomes a single bidder card, surfaces the cheapest current offer per vendor, and starts the live price drop loop. Watching the page is the final confirmation that the offer is live, scheduled correctly, and ready for diners.

    Auction Smoke test

Outcome