Restaurant control plane for Bai-Tee · Poolside Bar, 1401 Atlantic Ave, Ocean City MD · Sept 13, 2026
North star: We do not replace Toast. We use Toast and extend what it can't do. Toast stays the POS system of record; Fusion owns the digital work around the gaps.
What already works — authorized READ only
Authenticated read-only Toast integration → normalizes 328 items / 6 menus / 57 modifier groups into a provider-neutral graph (Toast GUIDs kept as provider identity, never overwritten).
Live sold-out sync (86'd items hide on the site, from Toast stock read).
Staff→manager portal + governed API: bartender submits a drink photo → manager approves → one canonical live image → website updates. Proven end-to-end.
We claim no write we haven't been granted. Toast Menus API is understood as retrieval-only today.
The bartender story (why it's new value, not a second POS)
Fusion knows a drink has no photo→bartender's already making it→tap → shoot → submit→manager: CURRENT vs CANDIDATE → approve→one canonical live image→site/app/agent get better→task closes · audit
86'ing an item stays in Toast — the terminal's already in front of the bartender. Fusion never duplicates a POS button.
The ask to Toast — scope questions (custom integration)
Bai-Tee (Peter / Krystle) routes these to the Bai-Tee Toast account rep. Fusion handles all technical work once scopes are confirmed. Nothing about the live Toast setup changes.
Which read scopes can Bai-Tee authorize? (confirm: menus, stock, restaurants)
Which write scopes can Bai-Tee authorize?
Is stock:write available for this custom integration? (capability only — 86 stays POS-native)
Which order write scopes are available, if useful later?
Supported interface to write item images / photos?
Item descriptions?
Item prices?
Modifier / menu configuration?
Menu publishing / synchronization?
If Menus API stays retrieval-only, is there another supported custom/partner interface for authoring?
What sandbox / certification requirements apply?
Can Bai-Tee be an alpha / reference customer for a future Fusion Toast partner integration?
We do not assume answers to #5–#10. No fabricated endpoints. If Toast grants an interface, we wire that exact scope; if not, Fusion stays canonical and the website updates from Fusion.
Blocked-external · pending ToastMenus API retrieval-only
Two lanes
Lane A — now Bai-Tee custom integration. Peter/Krystle → Bai-Tee's Toast rep with the 12 questions. Confirm read + any write scopes for this one restaurant.
Lane B — scale Fusion Toast Integration Partner: application → discovery → compliance/legal → agreement → sandbox → certification → alpha (Bai-Tee) → beta 3–5 → GA → Partner Directory.
Why Toast should care
Fusion extends Toast — doesn't compete; makes Toast data more useful.
Helps mutual customers keep richer digital experiences.
Ships with roles, approval, audit and human-review gates.
A real mutual customer (Bai-Tee) is asking for the capability, with a working prototype already live.