Spike · Restaurant ordering

Online ordering, embedded in your own site

A working harness for the Phase-1 offering: a white-label CloudWaitress storefront embedded under the client’s brand — pickup, self-delivery, and on-demand couriers, no commissions.

The embed

Ordering embed harness

Wired and ready. Drop a real CloudWaitress store URL into storefrontUrl and flip storefrontLive in lib/ordering.ts — this becomes a live ordering iframe, no component changes.

Preview storefront URL

provider: cloudwaitress · method: iframe · live: false — single swap point in lib/ordering.ts

Three delivery modes, one storefront

A client mixes all three — switch per delivery zone.

Pickup

DriverThe diner

Cost to restaurant$0

Diner seesReady-for-pickup notification

Self-delivery

DriverRestaurant’s own staff

Cost to restaurant$0 per trip (they pay wages)

Diner seesStatus: preparing → out for delivery → delivered

On-demand

DriverDoorDash Drive / Uber Direct

Cost to restaurant~$6.99 per delivery, no commission

Diner seesLive courier map + photo on delivery (carrier-hosted URL)

How this is wired

01
CloudWaitress hosts the storefront (menu, cart, checkout, payments) — we resell it white-label at $39/store/mo and mark it up.
02
We embed that storefront into the client’s Inyeon-built site via iframe (this page), or point order.client.com at it with a custom domain.
03
Delivery is a toggle inside CloudWaitress: the restaurant’s own drivers for close zones, DoorDash Drive / Uber Direct for the rest.
04
On dispatch, the carrier returns a hosted live-tracking link — the diner gets a courier map and a photo on delivery. Zero code from us.
05
Going live for a new client = edit one config object (lib/ordering.ts). No component changes, no redeploy of shared code.

Live courier tracking is carrier-hosted — DoorDash Drive / Uber Direct return a per-order tracking URL on dispatch. We never build the map. See docs/ordering-spike.md for the go-live checklist.