Sample market — a Market OS demo. Nothing here is real. Directory generated .

Demonstration build — Riverside Commons Market is fictional: every vendor, date, document and payment here is sample data, and these pages collect nothing.Sample market — a Market OS demo. Nothing here is real. Start the tour →
Riverside CommonsMarket

This is a sample market running on Market OS.

Riverside Commons is fictional. Everything below is what your market's site, your vendors' portal and your staff portal look like with your vendors in them. Two minutes, eight stops.

What changes for you

  1. Keep the application form you already use. How vendors apply does not have to change.
  2. On Thursday, paste who is coming. That one list is the week's line-up.
  3. The site, its Spanish twin, the map, the directory and the calendar feed follow from it. It takes the place of the page you edit by hand and the line-up you post every week.

A market that would rather take applications, documents and stall payments in one place sees that side at stops 6 to 8.

The eight stops

The vendor directory

Only vendors the market has cleared appear: at this sample market that means a paid stall and verified documents for an upcoming date. Search a product in either language.

Open it — The vendor directory →

Who's here this Saturday

One address for the next market date, made to be texted and pinned. In the live product the list changes when a booking changes; nobody edits a web page on Friday night.

Open it — Who's here this Saturday →

A vendor's page

Products, stall, next dates, SNAP, and the market liaison for that vendor.

Open it — A vendor's page →

The map

Stall by stall for the next date, and the same information as a list for screen readers and for printing.

Open it — The map →

The whole site in Spanish

Not a translation widget: a second site built from the same data. Every page has its twin, one tap away.

Open it — The whole site in Spanish →

How a vendor applies

Five steps, made for a phone, by email or by text, with no password. In the demo it sends nothing.

Open it — How a vendor applies →

What a vendor sees

Five accounts, five states. It opens on Brasa y Humo BBQ: a paid stall that is held, and hidden from the public site, until a document is back in order.

Open it — What a vendor sees →

What your staff sees

It opens on this week's line-up: paste who is coming, preview the public cards, publish. In the other sections, review an application, cancel a date for weather, check vendors in on market day and add a vendor by hand. Buttons show what would happen; nothing is sent.

Open it — What your staff sees →

Rules built into the pages

  • The directory lists a vendor only while the market has cleared it for an upcoming date. A vendor with no such date is not listed: that is the rule, not an outage.
  • The email list belongs to the market, not to a platform.
  • No report identifies a shopper who paid with SNAP. That is a design rule, not a courtesy.
  • The two portals are optional. They are for markets that run applications by hand: a vendor side where a confirmed date publishes a stall, and a staff side that runs the week. Markets that keep their own application tool use the public site alone.

There is no sign-in in this demo. The real portals require one.

Market OS is a product of The Finessed Hub. To see it with your own market's vendors in it, ask the person who sent you this link.