In 30 seconds
- Native means one provider documents and operates the capability.
- Integrated means products exchange supported data across a defined boundary.
- Managed means one accountable relationship helps design and support the working combination.
- Ask what happens to one order identifier, menu change, refund and incident across every layer.
- Fewer vendors can simplify accountability; specialist products can offer deeper functions. Architecture is a trade-off, not a slogan.
“All-in-one” has four meanings—and only three help an operator
Products developed and operated under one platform umbrella, often sharing identity, data and support.
Specialist products connected through supported APIs, middleware or certified output paths.
A provider scopes the combination, coordinates setup and offers an accountable operating relationship.
A broad catalogue that may still require several logins, contracts, integrations and support teams.
Most serious restaurant platforms blend the first three. Toast, Oolio, Lightspeed and Square all market broad suites while also relying on integrations and optional products. me&u openly presents a large integration ecosystem around its ordering layer. SevenRooms connects deep guest and reservation capability to external POS and payment systems.
Zwift’s public product story is also a blend: branded storefront, Arena, POS, Business Portal, Gem and marketing workflows are connected, while supported payments, delivery services, hardware and integrations depend on the venue configuration. “Connected operating workflow” is more useful—and more honest—than pretending external dependencies disappear.
The Friday-night test
Friday, 7:32 pm
A delivery order includes a future time, a half-half pizza, removed ingredients, a voucher and a new address near a delivery-zone edge. The customer pays. The venue is busy. Now trace:
- Which system validates the menu, modifiers and price?
- Which identifier follows the order into POS and kitchen?
- Where do staff see the promised fulfilment time?
- Who assigns delivery and communicates status?
- Where is the refund controlled if the address cannot be served?
- Which report explains payment, fees and settlement?
- Which support team takes the first call if one step stops?
Every manual copy, duplicate menu, polling delay and “please call your other provider” is a hand-off. Some are entirely reasonable. The risk appears when they are invisible during the sales process and ownerless during service.
How the main platform models differ
| Platform | Centre of gravity | Strength to inspect | Boundary to inspect |
|---|---|---|---|
| Our leading managed fit Zwift | Branded customer journey connected to venue operations and growth | Custom web presence, ordering depth, Arena/POS, Portal, Gem and Australian implementation | Which payments, delivery, hardware and modules are connected or optional for the venue |
| Oolio / OrderMate | Hospitality POS ecosystem | POS depth, payments, online ordering, reporting, loyalty, training and local support | Partner roles, custom website depth and which products sit across Oolio brands |
| me&u | Guest ordering and payment layer | QR, mobile, group ordering, loyalty and large integration network | Fault ownership between ordering and the underlying POS |
| Lightspeed | Modular POS and payments | Mature restaurant functions, offline mode, reporting, AI and published plan ladder | Add-ons, transaction arrangements and the configured total stack |
| Square | Payments-led business ecosystem | Accessible entry, POS, KDS, ordering and optional growth products | Plan-specific support plus separate loyalty, marketing and inventory costs |
| Toast | Restaurant-specific all-in-one platform | Hardware, POS, KDS, ordering, payments, growth tools, offline mode and AI | Australian rollout fit, implementation and contracted commercial scope |
| SevenRooms | Guest experience, reservations and CRM | Deep guest profiles, table operations, marketing, feedback and Voice AI | External POS/payment architecture where broader venue operations are required |
Where “all-in-one” earns its keep—and where it does not
Specialist depth versus shared context
A best-of-breed reservations or inventory product may be deeper than a suite module. The cost is another boundary. Decide where specialist depth produces real value and where shared order, menu, customer or settlement context is worth more.
Vendor count versus vendor accountability
One contract does not guarantee one answer, and several vendors do not guarantee chaos. What matters is a documented first-response and escalation model. me&u’s public guidance about when to call me&u or the POS provider is a good example of making the boundary visible.
Standardisation versus venue identity
Highly standardised systems can be fast to deploy. A brand-led restaurant group may instead value distinct landing pages, location stories, ordering logic and campaign work. Compare the live customer output, not only the back-office module list.
Cloud convenience versus local continuity
“Offline” is not one binary feature. A system may retain local order entry while cloud synchronisation, external payments, maps or delivery services remain unavailable. Zwift describes Arena as having an offline-capable local operational data layer with exactly those connectivity caveats. Ask every provider for the same precision.
Build your one-page architecture blueprint
Tick the parts your venue uses, then take the map into every product conversation. For each selection, record the provider, whether it is Native, Connected or Optional, and who owns the first response.
The blueprint does not need to be technical. If a restaurant manager cannot explain it, the architecture is unlikely to become clearer at 7:32 pm.
Make the stack visible
Map your service day with Zwift.
Bring your current systems and one troublesome order journey. We will help identify where a connected Zwift setup could reduce hand-offs, with scope confirmed before you proceed.
Sources and review notes
Product architecture claims are drawn from first-party pages and should be reconfirmed for the proposed configuration.
- Zwift: Connected Solutions, Arena, Business Portal and implementation and continuity FAQs.
- Oolio: solution suite; OrderMate: POS system architecture and support.
- me&u: Serve products and support boundary.
- Lightspeed Restaurant, Square for Restaurants, Toast Australia and SevenRooms.
Correction or updated evidence? Email marketing@zwift.com.au.