Fish costs do not leave room for a 25% commission. Keep the omakase at the counter and the roll business on your own channel.

A sushi order is a stack of precise decisions: soy paper or nori, white rice or brown, cucumber wrap instead of rice, spicy mayo in or on the side, no masago, extra tempura flakes, sauce drizzled or bottled. Generic platforms flatten all of it into a free-text notes box, the itamae never sees half of it, and the roll comes back wrong. Zay-OS models wrap, rice, sauce placement, and add-ins as structured modifiers so every roll fires exactly as the diner built it.

A sushi restaurant usually runs two businesses under one roof. The omakase and nigiri counter is a dine-in experience no app can touch — and on Zay-OS, dine-in QR orders carry a $0 diner fee. The takeout-roll business is the opposite: high volume, mid-size tickets, and the exact P&L a percentage commission lands on hardest. Zay-OS separates the two cleanly, so the counter stays a counter and the roll business runs commission-free on your own channel.

Sushi-grade fish is some of the most expensive protein in the industry — bluefin, uni, hamachi, and ikura push food cost far above the fast-casual norm. When a marketplace takes its 15-30% base commission (a 25-35% blended real cost once fees stack), it is not shaving your margin, it is deleting it: on many premium rolls the commission exceeds the entire profit in the item. A flat diner-paid fee ($0.99 pickup, $2.99 delivery) instead of a percentage is a structural fix, not a discount.

Sushi is the cuisine diners are most nervous to order online — nobody wants a $60 platter that arrives warm and shuffled. A marketplace listing gives you zero room to earn that trust. Your branded Zay-OS storefront does: pickup-forward ordering flow, packaging notes on every platter (wasabi and ginger packed separately, sauce always on the side), and item descriptions that tell the diner exactly how their order travels. Setting expectations is how sushi wins the direct channel.

The weekday sushi lunch — two rolls plus miso and salad, or three rolls for the bigger appetite — is a fixed-format order that generic platforms turn into a confusing pile of line items. Zay-OS ships it as a single lunch SKU with pick-two / pick-three roll choices as modifiers, so the office crowd checks out in two taps. Reorder-from-history turns the Tuesday spicy-tuna regular into a one-tap habit on your channel, not a marketplace's.

The platter is where sushi margin scales: chef's-choice boats feeding 6-10, build-your-own platters by roll count, sashimi trays by the piece. Zay-OS sells them with real sizing (feeds 4 / feeds 8 / feeds 12), lead-time windows so the sushi bar can plan the fish order, and priced add-ons — extra wasabi, side salads, miso for the table — instead of scribbled requests. Platter-scale catering bills at a flat 10%, a fraction of a marketplace cut on a big-ticket order.

Uni, toro, live scallop, seasonal fish — the best items in the case are the first to run out. With Zay-OS, 86ing an item once removes it everywhere at the same moment: your direct storefront and every Otter-ingested marketplace channel. No more selling o-toro on three apps an hour after the case emptied, and no more refund-and-apologize cycles that burn a first-time diner.

Sushi menus carry hard constraints: diners who need cooked-only options, shellfish allergies, gluten-free diners who need the tamari swap called out, vegetarians hunting the avocado-and-inari section. Zay-OS carries raw / cooked / shellfish / gluten-free / vegetarian flags at the item and modifier level so a cooked-only diner filters the menu to what they can actually order — instead of interrogating a marketplace listing that says nothing.

DoorDash, Uber Eats, and Grubhub orders ingest into the same kitchen tablet as your direct Zay-OS orders. One menu is the single source of truth across every channel — no double-entry at the sushi bar, no tablet wall between the rice station and the fish case, and no 86ing the toro in four different apps on a busy Friday night.

The Zay-OS schema carries Japanese and romanized alternateName variants so diners searching the way they actually type — "sushi near me," "omakase near me," "japanese restaurant near me," "寿司" — find your storefront. The visible storefront stays in your brand language, but the discovery layer reaches searches generic platforms never index for.