Skip to main content
The Pass · Ownership audit

Marketplace or branded ordering: what does your restaurant actually control?

Your logo at checkout is not the same as a venue-controlled direct journey. Follow one guest from discovery to their third order and the difference becomes obvious.

Distinctive restaurant connected directly to a customer beside an anonymous row of ordering windows
Original conceptual illustration—not a customer result or depiction of a named marketplace.
The short answer: marketplaces are valuable demand and logistics channels; a branded ordering experience is the restaurant’s direct commercial home. The resilient setup is often both—but with the venue’s brand, customer relationship and operational workflow designed deliberately rather than left inside somebody else’s listing.
Publisher disclosure: Zwift provides branded ordering and connected hospitality products. This guide compares operating models, not just vendors. Marketplace facts come from current first-party sources.

In 30 seconds

  • Use marketplaces for reach when the economics and audience make sense.
  • Build a direct channel for repeat ordering, venue storytelling, bookings, loyalty and permissioned customer relationships.
  • Do not call any channel “commission-free” without reading processing, delivery, service and activation terms.
  • Test whether a direct order reaches POS, kitchen and delivery without re-keying.
  • A platform can be branded without giving the venue meaningful control of the whole journey.

One customer, three orders

Order one: discovery

A customer wants dinner but has no venue in mind. A marketplace can be excellent here: location, filters, menus, reviews and logistics compress discovery into a familiar interface. The restaurant pays for access to that demand under the marketplace’s current commercial terms.

Order two: recognition

The same customer remembers the meal and searches for the restaurant by name. This is the moment a venue-owned web presence should earn its keep: clear identity, locations, food, opening details, ordering, booking and loyalty paths that feel like the restaurant—not a duplicated listing.

Order three: relationship

The restaurant now has a chance to turn satisfaction into a repeat habit. That may involve permissioned email or SMS, loyalty, a voucher, a review response or simply a mobile ordering experience the customer trusts. The important question is who can continue that relationship, under what consent, and through which channels.

The third order is where Zwift earns its place. The first order proves that a channel can process a transaction. The third proves whether the customer remembers the restaurant, whether the venue can recognise the relationship with permission, and whether ordering, loyalty, feedback and the next invitation still feel like one business.
The ownership test: can the customer recognise the venue without seeing its name? If every layout, interaction and follow-up feels like the platform, the logo may be present while the restaurant remains secondary.

The 12-point restaurant ordering ownership audit

Check the experience, relationship and operating control separately
QuestionWhat strong control looks likeWhy it matters
1. DomainThe customer can reach ordering from a venue-controlled domain or clearly connected subdomain.Branded discovery and return visits remain coherent.
2. Visual identityLayout, imagery, colour, menu storytelling and navigation can reflect the venue.Recognition is bigger than a logo.
3. Venue contentFood, atmosphere, locations, bookings, trading details and ordering coexist.The site can convert more than immediate hunger.
4. Ordering modesPickup, delivery, table and future orders are configured around actual service.The channel fits operations instead of forcing one pattern.
5. Menu expressionModifiers, half-half products, allergens, dietary details and pricing changes remain clear.Complex food should not become a support ticket.
6. Customer accessThe venue can use permissioned customer context under documented controls.Repeat relationships should not require another paid impression.
7. LoyaltyEarning and redemption live in the same customer experience.Recognition continues across visits.
8. ReviewsFeedback can return to an accountable venue workflow.Service recovery becomes possible.
9. POS and kitchenDirect orders reach the operational system with full context.Brand control is hollow if staff re-key the order.
10. Delivery choiceThe venue can understand delivery zones, partners, fees and responsibilities.Logistics remain a decision, not an assumption.
11. Export and exitData access, portability and contract exit are explained in writing.Real control includes the ability to change.
12. MeasurementOrders, customers, campaigns and settlements can be reconciled.The venue can improve what it can see.

What marketplaces do well

DoorDash and Uber Eats can create demand, provide familiar consumer experiences and supply delivery logistics. Both also offer products beyond their core marketplaces: DoorDash has Online Ordering and Drive On-Demand; Uber has Webshop and Uber Direct. A fair comparison must separate marketplace pricing from those direct and logistics products because they solve different jobs under different terms.

The strategic risk is not “using a marketplace”. It is allowing any single external channel to become the only discoverable menu, customer path or delivery workflow. Australia received a sharp reminder when Menulog stopped accepting Australian orders. Operators did nothing wrong by using Menulog; the lesson is that rented distribution and an owned commercial home serve different resilience roles.

Current-language caution: “commission-free” can still coexist with payment, delivery, software, activation or other fees. Compare the final scenario—marketplace delivery, self-delivery, pickup or direct web ordering—not the largest or smallest percentage on the page.

What restaurant control looks like in a Zwift journey

Zwift does not begin with a standard marketplace listing. It begins with the venue: its domain, visual identity, locations, food, service modes and reasons to return. Live examples show multi-location routing, complex product choices, mobile ordering, table bookings and loyalty expressed differently for different restaurants. Behind that experience, the order can continue into the venue’s configured operational setup.

This does not make every integration native or every service automatically included. Payments, delivery partners, hardware, marketing, Gem and implementation scope are confirmed for each venue. The advantage is an accountable connected product family and Australian team that can consider the web experience and the service workflow in the same conversation.

The brand should survive every hand-off

A customer finds the restaurant, chooses a location, schedules delivery, customises an item, pays, receives status updates, earns loyalty and later sees a relevant campaign. The venue should be recognisable throughout—and staff should not reconstruct the order behind the scenes.

A balanced channel plan

  1. Give every channel one job. Discovery, repeat ordering, logistics, table service and loyalty do not have to live in one consumer app.
  2. Make the direct path worth choosing. It should be fast, mobile, trustworthy and visibly connected to the venue.
  3. Keep menus and service rules governable. Trading hours, sold-out items, surcharges, zones and modifiers need an owner.
  4. Measure channel economics honestly. Include marketing, processing, delivery, labour, support and repeat behaviour—not only commission.
  5. Practice the exit. Know how customers find you and how service continues if one external channel changes.

Inspect the evidence

Compare six live Zwift-powered venue journeys.

Explore visibly different experiences across brand-led websites, multi-location routing, ordering, bookings and loyalty.

Sources and review notes

Commercial terms vary by product and can change.

Correction or updated evidence? Email marketing@zwift.com.au.