Understand the products. Plan the right next step.

Branded Storefront presents the customer ordering journey. Arena and POS support live venue operations. The Business Portal provides wider browser-based management, Gem adds review-led analysis inside the portal, and marketing tools help teams act on approved plans. The exact combination depends on the agreed configuration.

The Zwift Branded Storefront is the customer-facing website, menu and checkout journey shaped around the venue's identity, service modes, catalogue and enabled customer tools.

See the Branded Storefront experience.

Pickup, delivery, table ordering and ordering for later can be presented when they are configured for the venue. Available times, areas, payment methods, fees, promotions and post-order features can differ by order type and setup.

POS focuses on taking and settling transactions. Arena is the broader in-venue operations workspace that can connect POS with production, kitchen displays, delivery dispatch, payments, menu controls, reporting and supported hardware.

Explore Arena and POS for the two perspectives.

The Business Portal is the browser workspace for owners, managers and growth teams. Depending on permissions and configuration, it can bring together orders, customers, menus, storefront management, marketing, delivery, reporting, finance and support views.

Explore the Business Portal.

Gem currently provides three focused workflows inside the Business Portal: Menu Improvement, Order Analysis and Campaign Planner. They prepare evidence and direction for retailer review; they do not make changes automatically.

The flexible conversational Gem Assistant is identified as coming soon. See Gem's current boundaries and workflows.

Marketing scope can involve search visibility, listings, customer databases, email, text messaging, loyalty, reviews, promotions and campaign support. The selected services, channels, approval process and any third-party spend are confirmed in writing.

Explore marketing capabilities.

An online ordering journey may be connected to an existing website or delivered as a wider Zwift-managed storefront. The appropriate domain, branding and navigation arrangement is confirmed during discovery.

Discuss your current website.

Existing hardware and provider arrangements can be reviewed. Compatibility, security, reliability, supported devices and any new equipment or integration work are confirmed for the specific venue configuration.

Hardware may include terminals, tablets, printers, cash drawers, kitchen displays, customer displays and network equipment. Payment and delivery arrangements can introduce separate provider requirements and commercial terms.

A reliable business connection is important for connected ordering, synchronisation, payments and cloud services. Arena includes a local operational data layer for workflows that need data close to the venue, but that does not make every workflow available without connectivity. Resilience and network requirements should be reviewed during scoping.

Implementation can include discovery, workflow mapping, configuration, menu or data preparation, integration and hardware checks, training, launch planning and agreed support. The final plan depends on readiness and complexity.

Multi-location needs can be mapped across storefronts, venue configurations, users, permissions, catalogues, reporting and rollout stages. The Business Portal can provide wider oversight, while each venue's live-service setup is scoped around its operating requirements.

Bring examples of current menus or catalogues, modifiers, prices, imagery, customer or order data requirements, location structures and required integrations. Zwift can then confirm suitable formats, access, quality checks, responsibilities and what can be migrated.

No, unless a page explicitly says otherwise. Product pages identify demonstration fixtures, illustrative or privacy-redacted data, and actual interface captures. Visible names and figures should not be read as customer results.

Each focused workflow uses the relevant business context available to it. Order Analysis is designed around aggregate order context and does not need customer identities or individual order records to prepare its hypotheses. Access and availability remain subject to the portal configuration and permissions.

Do not assume Gem is included with every Business Portal setup. The written proposal confirms Gem availability, enabled workflows, permissions and any applicable fees for the venue.

No. The current Gem tools prepare review-ready priorities, hypotheses and campaign direction. The retailer reviews the evidence and decides whether, when and how to act. Gem is positioned as direction, not autopilot.

Ask for a walkthrough and share your service model, locations, current systems and the decisions you want to explore. Zwift can focus the conversation on the relevant product areas; demonstration environments may use illustrative data.

Request a contextual demonstration.

Zwift scopes the products, locations, workflows, hardware, integrations, implementation and support required, then records applicable inclusions, fees and commercial terms in a written proposal.

See the plans and pricing guide.

Do not assume that a channel, service or third-party spend is included. The written proposal should identify the selected marketing scope, approval responsibilities, messaging arrangements, campaign management and any relevant platform or media costs.

The venue should confirm valid consent, identify the business, make unsubscribe easy, respect opt-outs and approve the audience, offer, timing and message. For branded SMS in Australia, the sender ID must be registered through the relevant telco or message provider or it may be shown as “Unverified”.

See current ACMA guidance for commercial email and SMS and the SMS Sender ID Register. This is general information, not legal advice.

Contract length, notice periods, renewal, cancellation and any minimum term depend on the selected services and commercial arrangement. Confirm them in the written proposal and agreement before proceeding.

Review the selected products and capabilities, locations, implementation work, hardware arrangements, provider dependencies, customer responsibilities, support scope, applicable charges, exclusions, acceptance and governing terms.

This website is a product and scope guide; it is not a quote or commercial offer.

Use the Request Support action where it is available in your Zwift workspace, or contact support@zwift.com.au with the venue, order or issue reference and a clear description. Account and ownership changes should be sent to accounts@zwift.com.au.

Where the relevant refund action is available, open the order in the in-store workspace and follow the displayed prompts. If the action is unavailable or the transaction needs review, contact support@zwift.com.au with the order number (or customer name and order date), the requested amount and the reason.

Do not send full payment-card credentials by email. Processing and bank display times can vary.

Contact accounts@zwift.com.au from an authorised business contact. The accounts team will confirm the required verification, effective date and secure information path. Do not send passwords or full card credentials.

Contact accounts@zwift.com.au as early as practical with the current venue details, authorised contacts for both parties and the proposed effective date. The team will confirm the transfer process, required documents and any changes to services, settlement or domain administration.

Processing and settlement timing can be affected by the payment arrangement, provider and receiving bank. Check the relevant portal or statement first, then contact support or accounts with the transaction or settlement reference if a payment needs investigation.

Email domains@zwift.com.au. Domain ownership, registrant details, renewals, security certificates and administration should follow the applicable registration records, agreement and auDA requirements.