Outlets

Onboard F&B outlets onto the platform, configure their commercial terms, and manage menus and readers.

Connected outlets

Outlet	Onboarding	Connected account	Status	Terms
Loading…

Add an outlet

Name Type Cuisine Icon

Creates the platform record only. No Stripe account exists until you onboard it.

Terminal readers

Label	Reader ID	Device	Type	Status

Register a reader

Registration code Label

Physical S710: Settings → generate pairing code (three words). No hardware: use simulated-s710. Readers belong to a Terminal Location, created automatically per outlet.

Commercial & statutory terms

Platform fee (bps) Service charge (bps) GST (bps)

Country Currency Brand colour

The 70/30 split

Everything on this screen is the 30% — configured per client at deployment. Everything behind it is the 70%: Connect onboarding, direct-charge fund flow, Checkout, server-driven Terminal, pre-auth tabs, refund clawback and reconciliation, all shipped unchanged.

Also per-client but set at onboarding time: dashboard mode (Stripe-hosted vs API-based), payout cadence, and enabled payment methods per market.

Platform revenue

By outlet

Outlet	Orders	Gross	Platform fee	Net to outlet	Payouts

By channel

Channel	Orders	Gross	Platform fee	Flows through Stripe

Not everything flows through Stripe. Delivery aggregators and OTAs collect payment themselves and remit net proceeds separately — those orders carry no PaymentIntent and no platform fee, and need their own reconciliation path against the aggregator's settlement file. Assuming all revenue moves through Stripe is the most common scoping error in an F&B platform engagement.