Discovery versions of the FoodBridge Store Builder modules. Each stands on its own: no server, no real API call, invented data. In the product they share one database, and the team reads builds through Store Builder's published contract, never its tables.
The owner lands on the platform's dashboard. Activating the store — two steps, products and customers — happens in one large modal: drop an XLSX or CSV file, review it like a sheet (problems marked in their cells, one-tap fixes, dropdowns, search-select-add, a map for a customer's address), submit; customers open once products are in. Product Master and Customer Management fill as it goes; their Import menu offers Smart import.
Share this link: start as a new owner · products already added · the discovery hub. Open it on a computer (under 1024 px it asks to). Progress is kept in this browser; an XLSX file is not read (a sample stands in), a CSV is; the address map uses OpenStreetMap.
A new owner's Getting started page: six steps from an empty store to a running business — items (on the Products page: Import, four ways in — upload any file, a photoshoot, speak them, search products — then your rate list to check, and the assistant brings you back), customers from phone contacts, the first order, deliver it, get paid, and the daily plan on WhatsApp — a setup guide towards the first sale, in three stages on a milestone track (Ready to sell → First sale → Daily plan), the current step opened with one short line and a named button. The floating FoodBridge assistant only points to the page; it never runs a step in the chat.
Share this link: start fresh · the platform's dashboard (avatar ring, profile menu, Getting started card) · the discovery hub. The customer's invoice and the driver's link open from the order. Progress is kept in this browser; an uploaded file is not read (a sample rate list stands in) and nothing is sent on WhatsApp.
v7, plus a comment on every question: never a forced choice. Type or say anything instead of picking — it is kept with the question for the team ("📝 Noted.") and the next question comes. 🎤 in the message bar: speech to text where the browser has it, else a voice note.
Share this link: the Assistant. Give feedback sends a rating and a comment to the FoodBridge team — the one thing here that leaves the browser (and, if you use 🎤, your browser's own speech service).
v6, plus what happens after the store request. After the mobile, the Assistant also asks the FoodBridge Digital Assistant for an existing account; when the team marks the store Ready to use, his chat switches on his store's options — Open my store, Create an order, Collection request, Add customers… — each a login link. The Digital Assistant is not connected yet, so the chat says so and shows a sample link.
Try it: the Assistant — create a store, open
FoodBridge Team, and use the dashed Demo · team row to mark it Ready to use. The team's side:
ticketing-workspace-v3 (key fb-team-demo).
The owner's second round: mobile first, then the shop's name (no owner's name); business, returns and mornings take as many answers as apply; "anything else?" after contacts, products and papers; every message cut to one line. It stops at the store request: "Done! We'll set up your store and send you a login link."
Share this link: the Assistant · also inside the Control Tower · the discovery hub. Give feedback (bottom of the chat list on a computer, or ⋯ on a phone) sends a rating and a comment to the FoodBridge team — the one thing here that leaves the browser.
Store Builder as a WhatsApp-style chat: say hi, and the Assistant sets up the store one question at a time — name, mobile, contacts, who is who, the business, how the day runs, products read from a rate list — then sums it up, creates the store, and offers what to do next. On a computer it looks like WhatsApp Web; on a phone, like WhatsApp.
Share this link: the Assistant · also inside the Control Tower · the discovery hub (the question tree and decisions). Give feedback (bottom of the chat list on a computer, or ⋯ on a phone) sends a rating and a comment to the FoodBridge team — the one thing here that leaves the browser. Everything else is invented data in this browser; a real phone scanning the QR code is not part of this demo (use the link beside the code).
Both versions side by side: build a store on the left, and it arrives on the right as a New ticket — read through Store Builder's contract, never its storage.
Team key: fb-team-demo. On a phone: Owner and Team tabs.
The owner builds his store on a computer or a phone: Shop · Contacts · Who is who · Daily work · Files · Send. Each screen follows the screen it is opened on: on a phone, the phone layout. The phone QR, Build my store and “What reached FoodBridge” all work in this browser.
The FoodBridge online / down switch in each top bar shows what happens when FoodBridge can't be reached. On a computer, “Add from phone” and the QR phone page pick six invented contacts; an iPhone shows Safari's one-time setting, as the real page does. On the desktop Contacts and Files screens, use “Open the phone page for this QR”. Each browser keeps its own builds, so a real phone scanning the QR is not part of this demo.
Earlier: store-builder-v3 (hid the iPhone setting; no “down” state) · store-builder-v2 (no stand-in picker on the phone layout) · store-builder-v1 (its step screens held the desktop layout on a phone).
The customer success team: every store built, its files, and a ticket per store — New → In review → Set up.
Team key: fb-team-demo. Three sample stores, every file real and downloadable.
Earlier: ticketing-workspace-v1 (placeholder downloads).
Source: exagon-ai/foodbridge-module-store-builder (private),
modules/*/discovery/versions/. Store Builder and the team panel frozen 2026-10-01; the Assistant (modules/assistant) published 2026-10-05; Store Activation from exagon-ai/foodbridge-module-digital-assistant (private), modules/store-activation/discovery/versions/, published 2026-10-10. Do not edit here.