CounterFire Documentation

CounterFire is a single-restaurant, zero-commission online ordering platform. A restaurant owner runs their own branded ordering page, their own kitchen display, and their own menu, and pays a flat fee instead of handing 15 to 30 percent of every order to a marketplace.

These docs are split into three audiences.

Owner onboarding

Set up the restaurant the same day you sign up. Walk through the menu wizard, configure opening hours, and learn the signature 86 toggle that pulls a sold-out dish off the customer portal within seconds.

• Menu wizard
• Opening hours and the kill switch
• How to 86 a dish

KDS operation

Run the line, not a dashboard. Read the live ticket board, watch the age timers, advance tickets through Accept, Start, Ready, and Complete, and trust that a network drop never loses a ticket.

• Reading the board
• Age timers
• Advancing tickets
• Reconnect behavior

Developer docs

The technical contract behind the unbroken loop: the canonical order event schema, the REST surface grouped by area, realtime reconnect and snapshot semantics, and the latency budgets the platform is held to.

• Order event schema
• REST API reference
• Realtime: reconnect and snapshots
• Latency budgets

The signature loop

Everything in CounterFire serves one unbroken loop, end to end:

1. The owner marks a dish sold out (the 86 toggle) on the console.
2. The dish disappears from the customer ordering portal within a few seconds.
3. A customer places an order in under 60 seconds.
4. The ticket appears on the KDS in under 2 seconds, with an audible chime.
5. The kitchen advances the ticket: Accept, Start, Ready, Complete.
6. The customer’s shareable tracker reflects Received, In Kitchen, Ready in real time.

If that loop is fast, correct, and reliable, the product works.