Vendors / Regional & international
Zonal
The deepest UK pub-estate stack there is — Aztec EPoS plus Kitchen iQ, handhelds, bookings, PMS, purchase-to-pay and Zonal Pay under one roof — now owned by Volaris, with nothing at all published about pricing or APIs.
scored live legacy rubric
- Claims in scope
- 312
- Scored
- 45
- Assessed
- 35
- Unknown
- 277
- Not applicable
- 2
- Cells challenged
- 17
unknown, never as no.Identity
- Owner
- Volaris Group (part of Constellation Software) — Zonal joined Volaris in 2026; previously independent, founded 1979 by Ralph McLean, trading as Zonal Retail Data Systems Limited, Edinburgh (SC069596). Joel Chapman became CEO in July 2026.
- Who it is for
- UK pub groups, restaurant chains, hotels, stadia, leisure venues and holiday parks — large, complex, multi-site estates; UK-only
- Site
- https://www.zonal.co.uk/
Pricing
transparency: unknown · unit: Quote only (scaled by estate size/complexity) · processor lock-in: unknown
- Software
- No figures published. Described as tailored to estate size and complexity with no hidden fees and all features included as standard.
Capabilities
Every claim is binary and checkable. Grades: A primary documentation · B product documentation · C pricing or feature page · D marketing claim · E third-party reporting · F inference with no source. A yes on a differentiator claim requires A or B.
Order capture & FOH workflow
order-capture-floor-plan-editor
Not scored by this record.
order-capture-seat-level
Not scored by this record.
order-capture-coursing-hold-fire
Not scored by this record.
order-capture-split-merge
Aztec is a mature full-service EPoS so this is very likely present, but no feature-level documentation is public.
order-capture-bar-tab-preauth differentiator
Not scored by this record.
order-capture-transfer-audit
Not scored by this record.
order-capture-native-handheld
Not scored by this record.
order-capture-offline-order-entry
Aztec publishes its offline scope. Standalone Mode lets a terminal trade with the server down: orders can be created, choices and instructions applied, and cash tendered, and stored transactions reconcile to the account when the terminal rejoins. Shortfalls, all stated by Zonal: "operating a terminal in Standalone Mode means that it will trade entirely independently to all other terminals in the business inclusive of all remote printing capabilities (IE Kitchen Printers will NOT work)", so the send-to-kitchen half of the claim fails outright; the mode is not automatic failover but a manually pressed button requiring Dallas-key or PIN authorisation (override code 1901), taken after the terminal shows a countdown and reboots on losing the server; there is "a limited amount of space on a terminal for storing transactions during periods of being offline" with no figure published; and "it is recommended that only one terminal per trading area ever have Standalone Mode enabled", so this is not estate-wide degraded trading. Handheld (iServe) offline behaviour is not covered by this page or any other public Zonal page found. https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/PoS/How%20To%27s/Standalone%20Mode.htm · retrieved 2026-08-04
order-capture-qr-same-check differentiator
Not scored by this record.
order-capture-kiosk-first-party differentiator
Not scored by this record.
order-capture-drive-thru
Not scored by this record.
order-capture-drive-thru-timers
Not scored by this record.
order-capture-voice-ai differentiator
Not scored by this record.
order-capture-throttling differentiator
Not scored by this record.
order-capture-scheduled-orders
Kitchen iQ documents future-dated preparation: "When an order is rung up on the POS, the user has the opportunity to delay the time by which an order needs to be prepared", and Cook Times computes a fire order - a per-product cook time means "the next item will be displayed in 'waiting to start' X minutes after the first item ... all items arrive for serving at the same time", with a station able to have "visibility of the items [only] when they are due to be prepared, using the cook time view". Click & Collect takes orders "for collection at a specific location and time" and states it "will only display orders to your kitchen team when they're needed". Shortfall: the documented POS behaviour is the opposite of injection at fire time - a delayed order "is displayed on the kitchen screen display with both the delayed order time and the time the order was sent to the kitchen", i.e. it lands in the queue on receipt annotated with its due time; and a configurable per-channel lead time is documented only as per-provider prep times in Zonal Delivery, not for the first-party channels. https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Kitchen%20iQ/How%20To/Delayed%20Orders.htm · retrieved 2026-08-08
order-capture-catering
Not scored by this record.
order-capture-order-ready-signal differentiator
Not scored by this record.
order-capture-void-comp-controls
Not scored by this record.
Menu, modifiers & pricing engine
menu-pricing-nested-modifiers
Aztec's multi-level conversational ordering release notes state that before it, conversational ordering was restricted to one menu depth - only top-level choices could have min/max enabled and nested choices could only run sequentially without min/max restrictions - and that nested choices (choices within choices) now carry min/max controls at multiple levels, with a nested min/max choice respecting the min/max limits defined by the parent choice. A minimum of 1 is the forced-selection mechanism; there is no separate required flag. On the terminal a nested choice opens "an additional choice selection dialog that opens on top of the previous existing dialog". The Product Modelling Nested Choices help guide documents both nesting forms with no stated depth cap: a choice inside a recipe (Deluxe Burger, British Beef triggers a cooking-temperature choice) and a choice directly inside another choice (House Burger, an Extra Toppings choice containing a Cheese choice of seven options). Caveats: the feature must first be switched on in Aztec Base Data and "this new setting cannot be undone", and "choices with defaults cannot be included as a choice within a choice". https://knowledge.zonal.co.uk/archive/Content/Point%20of%20Sale/Aztec/Releases/Aztec%203.08.4.htm · retrieved 2026-08-04
menu-pricing-modifier-price-by-parent-size
Modifier pricing is carried by portions, not by a parent x size matrix. Instructions & Choices: "Products can have a portion added that will then be used in a choice or use the Standard Portion... In this example a new Portion was created - 'Inclusive' - and the Inclusive Portion was added to a choice. This gives you the option to change pricing on the choice, e.g. free choice or cheaper", so one choice item can price differently against different parents by attaching a different portion of it. Portion Types documents a per-product Price Matrix across portions plus a Price Factor. Shortfall: the per-parent price is set by choosing which portion of the choice item is appended to each parent recipe, one recipe at a time; no single parent-item x size price matrix for modifiers is documented, and where a parent has multiple portions each portion's ingredient row must be edited separately or "the choice will not activate when that portion has been selected on the terminal". https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Product%20Modelling/How%20To%27s/Instructions%20%26%20Choices.htm · retrieved 2026-08-03
menu-pricing-fractional-placement differentiator
Not scored by this record.
menu-pricing-half-and-half-rule differentiator
Not scored by this record.
menu-pricing-topping-quantity-tiers
Portion Types: each product can carry up to 20 portions, each with a "Price Factor" - "can be used in conjunction with percentage / factor options to allow different prices to be applied depending on the portion... Double Portion is '2' and Half is '0.5'" - set against a Price Matrix. Instructions & Choices confirms portions apply to choice (modifier) items, including a zero-charge "Inclusive" portion for free or cheaper options. Enterprise Recipes confirms "The available Dispense Sizes for Choices will always be their portions (e.g.: Standard, Double, etc)". That is a tiered price multiplier per modifier, distinct from ordering the modifier twice. https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Base%20Data/How%20To%27s/Portion%20Types.htm · retrieved 2026-08-03
menu-pricing-size-style-matrix differentiator
Not scored by this record.
menu-pricing-included-allowance differentiator
Not scored by this record.
menu-pricing-combos
Not scored by this record.
menu-pricing-upsell-prompts differentiator
Not scored by this record.
menu-pricing-86-propagation
Not scored by this record.
menu-pricing-countdown-auto-86 differentiator
Not scored by this record.
menu-pricing-dayparting
Not scored by this record.
menu-pricing-channel-price-books
Not scored by this record.
menu-pricing-dual-pricing differentiator
Not scored by this record.
menu-pricing-versioning-effective-dates differentiator
Not scored by this record.
menu-pricing-franchise-hierarchy differentiator
Not scored by this record.
menu-pricing-allergen-nutrition
Not scored by this record.
menu-pricing-recipe-linkage differentiator
Not scored by this record.
menu-pricing-3p-menu-push
Not scored by this record.
menu-pricing-dynamic-pricing
Not scored by this record.
Payments & money movement
payments-processor-choice differentiator
Not scored by this record.
payments-published-rates differentiator
Not scored by this record.
payments-dual-pricing differentiator
Not scored by this record.
payments-surcharge-guardrails differentiator
Not scored by this record.
payments-emv-nfc
Aztec PoS Payments documents EMV at the terminal: "If your venue is configured with integrated EFT, then the Chip & PIN device will prompt if configured the customer to leave a tip", with credit card taken through the integrated device rather than keyed. The Zonal integrated payment system page enumerates the wallets - "Supports digital payment - In addition to processing card payments, both Apple and Google Pay are supported" - alongside "end-to-end encryption and is fully PCI compliant" and tableside payment on the handheld. Chip and PIN plus Apple/Google Pay (which are NFC-only) covers the claim; contactless card is not separately named. https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/PoS/How%20To%27s/Payments.htm · retrieved 2026-08-08
payments-softpos-tap-to-pay differentiator
Not scored by this record.
payments-pay-at-table
Not scored by this record.
payments-qr-guest-pay differentiator
Not scored by this record.
payments-tip-adjust
Not scored by this record.
payments-tip-pooling differentiator
Not scored by this record.
payments-offline-store-and-forward differentiator
Not scored by this record.
payments-offline-decline-liability differentiator
Not scored by this record.
payments-gift-cards
First-party gift cards are documented: the Loyalty & Gift Card Production guide covers "cards for use with iZone Loyalty or Gift platform", recommends "the loyalty / gift platform generates all card numbers" with prefix, number range and check digit, and specifies mag-stripe encoding plus a QR of the full card number "futureproofed for use during iServe or QR code scanners at the point of sale". The Loyalty product page states "Integration with your other Zonal technology facilitates automatic redemption and balance checking at any point-of-sale", which covers real-time balance and redemption anywhere in the estate; Toggle sells branded physical and digital cards with "easy redemption at any point-of-sale". Shortfall: redemption through the first-party online-ordering channel is not documented - Order & Pay and Click & Collect both list only "vouchers, promotional offers, and loyalty rewards" as redeemable in the guest journey - and Zonal "does not produce cards" itself. https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Loyalty%20%26%20Voucher%20Manager/Loyalty/How%20Tos/Loyalty%20%26%20Gift%20Card%20Production.htm · retrieved 2026-08-08
payments-house-accounts
Not scored by this record.
payments-split-tender
Not scored by this record.
payments-refund-void-controls
A fully configurable finance environment with real-time transaction visibility is claimed; approver-level authorization and immutable audit are not described.
payments-chargeback-tooling differentiator
Not scored by this record.
payments-card-on-file differentiator
Not scored by this record.
payments-payout-timing differentiator
Not scored by this record.
payments-multi-entity-routing differentiator
Not scored by this record.
payments-p2pe-pci4
Not scored by this record.
Kitchen & production
kitchen-station-routing
Kitchen iQ is a first-party kitchen management product but its routing model is not documented publicly.
kitchen-expo-consolidation
Kitchen iQ Channels: "Excluded Stations set to 'Prep1, Prep2, Assembly'... View will not show the account if any of the lines are at not at 'Server'. Account will become visible when all the lines are bumped to 'Server'" - a pass/expo view that resolves only once every contributing station has bumped. Routing Rules adds a "Recombine Station" for items sent to two or more stations and states "When items have been sent to 2 or more stations each operator of that station needs to individually bump the item". Stations defines an Assembly order stage: "product items have been cooked / made and have come together at the assembly / pass area for final plating". https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Kitchen%20iQ/How%20To/Channels.htm · retrieved 2026-08-03
kitchen-course-firing differentiator
Not scored by this record.
kitchen-prep-time-pacing differentiator
Not scored by this record.
kitchen-order-throttling differentiator
Not scored by this record.
kitchen-channel-pause-propagation differentiator
Not scored by this record.
kitchen-order-ready-callback differentiator
Not scored by this record.
kitchen-bump-bar-hardware
Intro to Bump Bar documents a physical Kitchen iQ bump bar with a full button map (bump 1-6, unbump, hold, drill-down, order and item navigation, menu) and two shortcut sets depending on whether the screen is configured for a "vertical bump bar" or a keyboard, with a keyboard usable as fallback "if a kitchen screen is configured to use a vertical bump bar but for some reason it is not working". Shortfall: no supported bump-bar model or part number is published - the customer portal Hardware Catalogue's Kitchen Systems section lists exactly one item, "KIQ Kitchen Screen Controller / ZKMS-CONTRLR-IOT", and no bump bar or programmable keypad SKU appears anywhere in the catalogue. https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Kitchen%20iQ/How%20To/Intro%20to%20Bump%20Bar.htm · retrieved 2026-08-03
kitchen-all-day-counts
Not scored by this record.
kitchen-sla-alerts
Not scored by this record.
kitchen-printer-fallback differentiator
Not scored by this record.
kitchen-offline-operation differentiator
Not scored by this record.
kitchen-item-build-screens differentiator
Not scored by this record.
kitchen-pizza-fractional-display differentiator
Not scored by this record.
kitchen-recall-refire
Not scored by this record.
kitchen-order-modification-alerts differentiator
Not scored by this record.
kitchen-guest-ready-notification differentiator
Not scored by this record.
kitchen-waste-logging
Not scored by this record.
kitchen-speed-of-service-reporting
Not scored by this record.
kitchen-prep-forecasting
Not scored by this record.
Delivery, dispatch & third-party channels
delivery-driver-roster
Zonal states what its delivery product is: "Zonal Delivery is our cost-effective, user-friendly platform for managing delivery service providers, offering seamless integrations with the three major online ordering and delivery services", and the FAQ defines the category as managing "Deliveroo, Just Eat, and Uber Eats in one location". The enumerated feature set is Direct order integration, Centralised management, Easily publish changes, Flexible item pricing and Control order volumes - no driver entity, assignment state or run history. Corroborated by the Zonal Delivery help guide already held in this record, whose complete Setup section list is Login & Navigation, Permissions, Menu Management, Pricing, Orders & History, Prep Times & Availability, Overriding Product Names, Dietary Tags, Removing Sites and Deliveroo. In-house delivery is a third-party handoff, not a native driver module. https://www.zonal.co.uk/products/online-ordering-systems/delivery/ · retrieved 2026-08-08
delivery-dispatch-board
Zonal's delivery offering is documented as third-party aggregation only, with no dispatch of own drivers anywhere in it. The Zonal Delivery user manual scopes the product as 'manage all of your Delivery Service Providers (DSPs) from one place' and enumerates its entire feature set - menu schedules by DSP, publishing a menu, reviewing and adjusting prices across DSPs, pausing a menu, prep time, item availability, active orders and order history - with no dispatch or expo screen, no driver-availability view, no elapsed-time-per-order display and no multi-order run batching; dispatch and drivers belong to the DSP (Deliveroo, Uber Eats). The Delivery help-guide navigation on knowledge.zonal.co.uk shows the same DSP-only section list (Integrations, Setup, Menu Management, Pricing, Orders & History, Prep Times & Availability, Deliveroo), and the EPoS product page describes delivery solely as 'Orders from major delivery partners are received straight into the EPoS'. Knowledgebase searches for driver or dispatch screens surface nothing outside DSP integration. https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/iOrder/Zonal%20Delivery/User%20Manuals/Zonal%20Delivery%20User%20Manual.htm · retrieved 2026-08-04
delivery-route-map differentiator
Not scored by this record.
delivery-driver-tracking differentiator
Not scored by this record.
delivery-zones-polygon differentiator
Not scored by this record.
delivery-zone-pricing
Zonal Delivery is a DSP aggregation layer, not first-party delivery: "Zonal Delivery allows you to manage all of your Delivery Service Providers (DSPs) from one place", with setup guides only for Deliveroo and Uber Eats. Its user manual states it "will outline everything that you need to do to get the best from your Zonal Delivery platform" and enumerates the whole feature set - login, menu schedules by DSP, publishing a menu, per-DSP price adjustment, pausing a menu, prep time, order review, permissions. There is no delivery zone, delivery fee, order minimum, address validation or quoted promise time in it; fee and promise time belong to the DSP. Prep time is the only timing control and exists to tell the DSP when a courier should collect. https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/iOrder/Zonal%20Delivery/User%20Manuals/Zonal%20Delivery%20User%20Manual.htm · retrieved 2026-08-03
delivery-address-validation
Not scored by this record.
delivery-driver-comp differentiator
Not scored by this record.
delivery-cash-reconcile
Not scored by this record.
delivery-daas-dispatch
Not scored by this record.
delivery-daas-fallback differentiator
Not scored by this record.
delivery-3p-direct-integration differentiator
Not scored by this record.
delivery-3p-injection
Not scored by this record.
delivery-menu-push
Not scored by this record.
delivery-86-sync
Not scored by this record.
delivery-store-pause
Not scored by this record.
delivery-3p-reconciliation differentiator
Not scored by this record.
delivery-injection-error-visibility differentiator
Not scored by this record.
delivery-tracking-page
Not scored by this record.
delivery-promise-time differentiator
Not scored by this record.
delivery-offline-behavior
Not scored by this record.
Digital ordering & guest-facing channels
digital-first-party-web
"Zonal's Click & Collect platform is white-labelled, enabling you to fully customise it with your branding and logos. This gives your customers a simple, easy-to-follow user experience with no confusing third-party logos or messaging", delivered as a "Responsive web application" and "fully EPoS-integrated, meaning all orders placed through the platform are automatically passed through to your kitchen to be actioned as with in-venue orders". Order & Pay is the same construction: "Available as both a fully branded app and web platform", white-labelled, orders "automatically sent through to the kitchen or bar". These are first-party ordering channels sold by Zonal, not a marketplace, so no per-order marketplace commission arises; note that Zonal uses the explicit phrase "commission-free" only of Zonal Bookings, and hosting on the operator's own domain is not stated. https://www.zonal.co.uk/products/online-ordering-systems/click-and-collect/ · retrieved 2026-08-08
digital-menu-single-source
Propagation is stated outright: "Natively integrated with our EPoS and wider suite of hospitality technology, any changes made in our menu management platform will be automatically pushed out across all your other Zonal tech, providing massive time savings and ensuring accuracy across the board." The EPoS page names the targets - "changes can be published across all of your other Zonal tech, whether it's your handheld POS devices, digital ordering platforms, or even pre-order menus" - and Order & Pay confirms from the channel side that "any changes to menus or products can be automatically published across all channels" with "real-time product availability, including stock levels ... shared between the EPoS and Order & Pay". The iOrder Product Manager guide already in this record corroborates that the digital channel reads the POS record: a nested choice "is set up in Aztec exactly as a normal product". https://www.zonal.co.uk/products/operations/menu-management-system/ · retrieved 2026-08-08
digital-native-app differentiator
Not scored by this record.
digital-account-saved-payment
Re-verified verbatim at the current Order & Pay page: "Repeat orders - Another round? Guests can see and repeat previous orders at the push of a button", "Secure payment - All payments are processed securely by PayPal Braintree, with Apple Pay and Google Pay also supported", and "QR codes - After scanning a QR code, information such as table number and venue are pre-populated". A guest identity exists: the Loyalty knowledge base Data Flows guide documents White Label App auto-enrolment, a Loyalty widget web sign-up and head-office enrolment. Shortfall: no saved delivery or collection address (the nearest documented feature is "Deliver to Location - Add a room number, caravan plot or other fixed location") and no account-stored tokenised card - the named payment methods are device-held wallets. Further, the app account and the loyalty record are separate registrations: "If a guest signs up via the Loyalty Widget this will not create an App account." https://www.zonal.co.uk/products/online-ordering-systems/order-and-pay/ · retrieved 2026-08-08
digital-upsell-engine differentiator
Not scored by this record.
digital-scheduled-pacing
Not scored by this record.
digital-fulfillment-modes
Not scored by this record.
digital-qr-table
Not scored by this record.
digital-kiosk differentiator
Not scored by this record.
digital-group-ordering
Not scored by this record.
digital-catering-portal differentiator
Not scored by this record.
digital-voice-ai-phone differentiator
Not scored by this record.
digital-drivethru-ai
Not scored by this record.
digital-sms-ordering
Not scored by this record.
digital-google-order differentiator
Not scored by this record.
digital-apple-business-connect
Not scored by this record.
digital-loyalty-attach
Not scored by this record.
digital-subscriptions
Not scored by this record.
digital-promo-parity
Not scored by this record.
digital-guest-data-ownership differentiator
Not scored by this record.
digital-checkout-pci-sca
Not scored by this record.
digital-surcharge-transparency differentiator
Not scored by this record.
Guest data, loyalty & marketing
guest-loyalty-unified-profile
A single guest identity does exist and it is first-party: the Loyalty Data Flows guide documents sign-up via White Label App auto-enrolment, a Loyalty widget on the operator's website, or head office in the Loyalty Platform, and the Loyalty product page states "Integration with your other Zonal technology facilitates automatic redemption and balance checking at any point-of-sale". Shortfall, and it is positively documented rather than merely absent: the channels do not dedup or merge. "If a guest signs up via the Loyalty Widget this will not create an App account. To use the App the user will need to create an app account and add their Loyalty Card"; head-office edits "will not update within the App"; and changing an email means the guest "should create a new account within the White Label App and add their existing card". Reconciliation is manual - head office performs "Card Swaps, i.e., transferring a member to a different Loyalty Card". No phone- or email-match merge behaviour is described. https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Loyalty%20%26%20Voucher%20Manager/Loyalty/How%20Tos/Data%20Flows.htm · retrieved 2026-08-08
guest-loyalty-thirdparty-identity-attach differentiator
Not scored by this record.
guest-loyalty-accrual-models
Loyalty Program Basics documents four configurable program types: currency program ("customers get direct currency for the amount they spend... £1 spend = 0.05p reward (5% return)"), spend-to-points-to-rewards ("£1 spend = 1pt, 200pts = free starter, 500pts = free main"), stamp card programs, and "Tiered card action (Normal members 5pts per £1, VIP members 10pts per £1)", plus rate variation by product division, site and time period and configurable points expiry with a transaction log. Actions & Rewards adds "Item for visits - a reward can be created so that once a loyalty card has been created with a certain number of visits then a free drink or meal is provided". Points-per-pound, visit/punch and spend-tier accrual are all configuration, no bolt-on vendor. https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Loyalty%20%26%20Voucher%20Manager/Loyalty/How%20Tos/Loyalty%20Program%20Basics.htm · retrieved 2026-08-03
guest-loyalty-tiers differentiator
Not scored by this record.
guest-loyalty-offline-behavior differentiator
Not scored by this record.
guest-loyalty-offer-stacking-rules differentiator
Not scored by this record.
guest-loyalty-targeted-offers differentiator
Not scored by this record.
guest-loyalty-rfm-segmentation differentiator
Not scored by this record.
guest-loyalty-lifecycle-automation
Actions & Rewards documents always-on triggered rewards: "Item for birthday - you can choose to give items for birthdays such as a free glass of champagne; this reward can also be set so that it can only be redeemed one week prior and one week after a birthday date", "Item for registration - an item given away for free on registration", a "Registration action" crediting points or cash, and "Recurring item - for example, all loyalty card holders get one free beer every month". Loyalty Program Basics adds a registration bonus that "can be delayed applying on the day after registration". Shortfall: no lapsed or win-back trigger appears anywhere in the Loyalty or Voucher Manager documentation - Voucher Manager Campaigns is a code-batch and distribution tool - and outbound lifecycle messaging is positioned in Zonal's own product navigation as a separate product, Airship CRM, which has no knowledge base section at all. https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Loyalty%20%26%20Voucher%20Manager/Loyalty/How%20Tos/Actions%20%26%20Rewards.htm · retrieved 2026-08-03
guest-loyalty-native-email-sms differentiator
Not scored by this record.
guest-loyalty-consent-management
Not scored by this record.
guest-loyalty-10dlc-registration
Not scored by this record.
guest-loyalty-campaign-attribution differentiator
Not scored by this record.
guest-loyalty-data-export-portability differentiator
Not scored by this record.
guest-loyalty-cdp-event-api differentiator
Not scored by this record.
guest-loyalty-review-capture-routing differentiator
Not scored by this record.
guest-loyalty-referral-program
Not scored by this record.
guest-loyalty-wallet-pass differentiator
Not scored by this record.
guest-loyalty-privacy-rights-tooling
Not scored by this record.
guest-loyalty-redemption-fraud-controls
Not scored by this record.
guest-loyalty-ai-offer-recommendation differentiator
Not scored by this record.
guest-loyalty-stored-value-gift
Not scored by this record.
Labor & workforce
labor-clock-in-at-pos
"The Time & Attendance module is used in conjunction with the clock in and out function on the PoS terminal. Within the module, rotas can be scheduled, worked hours are confirmed and the payroll week is signed off", and "After every day, when employees have clocked in and out on the PoS terminal, the clock times should be confirmed and verified"; breaks "taken on the PoS" flow into the Break time box, and unscheduled staff who clocked in on the PoS still appear. The credential is documented in Staff & Security > Adding Front of House Users: "The Dallas key or 4-digit PIN code are assigned in this screen" - an iButton badge or a PIN at the terminal itself. No separate time-clock hardware appears anywhere in the module. https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Time%20and%20Attendance/How%20To/Verifying%20Clock%20Times.htm · retrieved 2026-08-08
labor-photo-punch-verification differentiator
Not scored by this record.
labor-geofenced-mobile-punch
Not scored by this record.
labor-offline-time-punch differentiator
Not scored by this record.
labor-granular-rbac
Enterprise User Management documents role-plus-location permissioning: "Under Users, click on User Groups. These are the permissions that can be assigned to the user" and "Under Users, click on User Access Groups. These are the active restaurants that can be assigned to a user", so permission sets and site scope are assigned independently rather than as fixed tiers. Zonal Delivery Custom User Permissions goes further - operators "Add a role", name it and compose it from a named action list (Catalogue Ingest, Publish DSP, Remove integration, Update location, Bind DSP location, Create org and others) with per-location member assignment. Shortfall: the Aztec till permission model is not published. Staff and Security documents only assigning users a Job Role and its permissions material is a video with no text, so the grantable till actions (void, comp, discount, refund, drawer open, price change, report access) are never enumerated. Per-action authority demonstrably exists - "depending on the security settings managers authority maybe required to use some correction method" and "Should site users not have permissions to enable Standalone Mode..." - but the list itself is undocumented. https://product.zonal.co.uk/customer/Content/Order%20Inventory%20and%20Menu%20Management/Enterprise/How%20To/Enterprise%20Admin/User%20Management.htm · retrieved 2026-08-03
labor-manager-override-audit
Overrides are authenticated to an individual: the Standalone Mode approval screen requires that "An authorised user must then approve the action of putting the terminal into Standalone Mode with either their Dallas key or PIN", front-of-house users are issued a personal Dallas key or 4-digit PIN, and correction methods support "up to 16 correction reasons which can be used for reporting". User-attributed audit reporting exists in the Enterprise report catalogue - "Wastage Details, showing wastage entered by item, reason and user includes date waste was entered" and "Price Change Tracker - shows how many times the price was changed and who changed the price when". Shortfall: Zonal documents a shared bypass code for that same approval - "Should site users not have permissions to enable Standalone Mode, the code 1901 should be used to enable the functionality" - which defeats individual attribution, and no immutable or tamper-evident override log is described; the override trail is reached through ordinary reports rather than an append-only audit store. https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/PoS/How%20To%27s/Standalone%20Mode.htm · retrieved 2026-08-03
labor-native-scheduling differentiator
Not scored by this record.
labor-demand-labor-forecast differentiator
Not scored by this record.
labor-realtime-labor-percent differentiator
Not scored by this record.
labor-overtime-prevention differentiator
Not scored by this record.
labor-break-compliance-by-state differentiator
Not scored by this record.
labor-fair-workweek-support
Not scored by this record.
labor-minor-labor-rules
Not scored by this record.
labor-tip-pooling-rules
Not scored by this record.
labor-tip-distribution-audit-trail
Not scored by this record.
labor-qualified-tips-w2-reporting differentiator
Not scored by this record.
labor-native-payroll differentiator
Not scored by this record.
labor-payroll-export-formats
Not scored by this record.
labor-shift-swap-workflow differentiator
Not scored by this record.
labor-digital-onboarding-i9
Not scored by this record.
labor-server-performance-metrics differentiator
Not scored by this record.
Inventory, purchasing & cost control
inventory-recipe-bom-costing
Multi-level BOM is documented. Food Recipe Costings states "It is also possible that a recipe can contain a choice, another recipe or a prepared item", and the prepared-items guide walks through building a batch sub-recipe from purchase lines with a "preparation batch field, for example 1kg" and a storage count unit, then inserting it into the dish: "Any number of prepared items can be added to a recipe, and as they are added the cost of that proportion of the batch will be displayed." Shortfall: nothing states that plate cost recalculates automatically when a component purchase line's cost changes - the guides describe cost being displayed at build time and purchase lines feeding the stock system, but no recosting trigger or cascade is documented. https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Product%20Modelling/How%20To%27s/Full%20Recipe%20Costing%20(with%20prepared%20items).htm · retrieved 2026-08-08
inventory-unit-conversion-yields
Three distinct units with explicit conversion factors are documented. Enterprise Stock Items: a generic "Stock Size" as the count unit ("such as Each or Kg"), "Size Multiples" for the purchase pack size ("there are 5 (250g) in one (5x250g)"), and "Enter the Dispense Size which is the unit of measurement that will be used when adding ingredients to recipes", plus a separate reporting size. Aztec Base Data Units: "Units are used when setting up products to determine the sizes that they are purchased in, counted in or used within recipes", with base amounts in ml, g or single items and the warning "It is very important to get the Base Amount Correct as this will affect both product depletion and stock takes". Shortfall: no yield or waste percentage is applied to the raw-to-usable conversion - Enterprise recipe ingredient rows carry only Ingredient, Dispense size, Unit Cost, Qty and Ext Cost, and wastage is captured as separate front-of-house or back-of-house wastage transactions reported as "raw and finished waste by item", not as a per-ingredient yield factor. https://product.zonal.co.uk/customer/Content/Order%20Inventory%20and%20Menu%20Management/Enterprise/How%20To/Stock%20Admin/Stock%20Items.htm · retrieved 2026-08-03
inventory-theoretical-vs-actual differentiator
Not scored by this record.
inventory-realtime-depletion differentiator
Not scored by this record.
inventory-86-auto-sync differentiator
Not scored by this record.
inventory-count-modes
Two of the three modes are documented, each retaining its own history. Full physical: Adding a New Stock opens a stock audit against a division and thread for a chosen stock period end date, prints count sheets and records Open Stk, Purch Stk, Th. Reduct, Th. Close Stk and Wastage per item with a Multi Unit pack-to-single entry aid; prior audits stay retrievable and feed Loss & Gain, Closing Stock Variance and Stock Result Summary reports. Ad-hoc subset: Completing a Spot Check runs from PoS Manager Functions against selected products - "The spot check report will display the expected, actual and variance figures for each product" - and separate Line Check Daily Variance and Line Check Weekly Variance reports exist. Shortfall: no scheduled recurring cycle count of a defined subset is documented. The only scheduling primitive found is a company-wide Default Stock Period Length in Enterprise Admin, and Stock Count Methods offers only a choice of count ordering (Supplier Items by Suppliers, Supplier Items by Categories, Stock Items by Categories) that "will be applied to all" restaurants and "will be handled by Zonal during the initial setup process". https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Stocks/How%20To/Adding%20a%20New%20Stock.htm · retrieved 2026-08-03
inventory-mobile-count-offline
Not scored by this record.
inventory-vendor-catalogs-edi differentiator
Not scored by this record.
inventory-invoice-ocr differentiator
Not scored by this record.
inventory-price-change-alerts differentiator
Not scored by this record.
inventory-par-auto-suggest differentiator
Not scored by this record.
inventory-waste-logging
Not scored by this record.
inventory-transfers
Not scored by this record.
inventory-commissary
Not scored by this record.
inventory-lot-traceability
Not scored by this record.
inventory-shelf-life-expiry
Not scored by this record.
inventory-bar-partial-bottle
Not scored by this record.
inventory-cogs-gl-export
Not scored by this record.
inventory-native-not-partner differentiator
Not scored by this record.
inventory-menu-margin-linkage differentiator
Not scored by this record.
Reporting, BI & data access
reporting-realtime-dashboard
The EPoS page claims "140+ reports, real-time transaction visibility" per site or across the estate. Off-premise dashboards are Dimensions+: "Our suite of additional reporting tools are fully integrated with our EPoS and wider suite of technology, meaning all data is shared seamlessly and in real time", with "Simple dashboards", "Unlimited users" and "Accessible anywhere - Dimensions+ can be accessed on PC, tablet, mobile or via a free Power BI app". Shortfall: this is not a first-party dashboard app included with the EPoS - Zonal describes Dimensions+ as "our Microsoft Power BI integrated suite of additional reporting tools, for when you need to go above and beyond the standard reporting functionality available in our EPoS", and its own FAQ states "Dimensions+ requires a Microsoft Power BI Pro license". No refresh latency for the dashboard is stated anywhere. https://www.zonal.co.uk/products/operations/reporting/ · retrieved 2026-08-08
reporting-eod-closeout
The 7 Day Statement of Trade is described as "the most frequently used report within Aztec" and reconciles a trading day in one document: Gross Sales by reporting division, Promotions, Discounts, "Sales after Promo and Disc", Tips, Service Charge, Deferred Income, Declared Payments broken out by tender and by card scheme, Walkout, Uplift, Increased Float, Auto Banking, Declaration Variances, bookings and sales-ledger movements, Opening Cash on Site, "Cash/Cheques banked" and closing Cash on Site. Daily Sign Off then closes the trading date, gated on no open sessions, all closed sessions declared, all safes counted and banking performed, and "cannot be undone once completed without administrator permissions". Shortfall: VAT/tax and refunds are not lines on this document - VAT appears only in separate Enterprise reports (Financial Detail, Daily Sales Summary) and refunds must be chased through the Detailed Transaction report - so tax and refunds are not reconciled in the same packet. https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Reporting/How%20To/7%20Day%20Statement%20of%20Trade.htm · retrieved 2026-08-03
reporting-pmix-modifier-level
Item-level PMIX with the required filters is documented in the Enterprise report catalogue: "Detailed Sales Mix - Lists all menu items sold within a given date range, for one or all profit centres. Shows average FIFO cost of each item if run for all profit centres. This report can also be run by revenue centre and sales type"; "Sales Category Analysis - Profit centre breakdown of Menu items within a given sales category. Shows net and gross sales, discounts, VAT and cost details"; "Sales Mix by Time Period - Shows menu items sales by day, breakdown can be viewed hourly or by day part". Shortfall: no report in the catalogue is documented as breaking sales out at modifier level. Zonal models modifiers as Choices and Instructions, and Instructions are explicitly non-revenue - "Instructions are not priced and have no effect on stocks or sales" - so item-level sales mix cannot be assumed to carry modifier quantity and net sales. https://product.zonal.co.uk/customer/Content/Order%20Inventory%20and%20Menu%20Management/Enterprise/How%20To/Reports/Report%20Names%20And%20Descriptions.htm · retrieved 2026-08-03
reporting-comps-voids-audit
Not scored by this record.
reporting-cash-over-short
Not scored by this record.
reporting-labor-productivity
Not scored by this record.
reporting-server-scorecards differentiator
Not scored by this record.
reporting-channel-profitability differentiator
Not scored by this record.
reporting-multiloc-drilldown differentiator
Not scored by this record.
reporting-custom-report-builder differentiator
Not scored by this record.
reporting-scheduled-delivery
Not scored by this record.
reporting-raw-warehouse-export differentiator
Not scored by this record.
reporting-public-api differentiator
Not scored by this record.
reporting-webhooks differentiator
Not scored by this record.
reporting-api-not-upcharged differentiator
Not scored by this record.
reporting-tier-paywall differentiator
Not scored by this record.
reporting-history-retention differentiator
Not scored by this record.
reporting-anomaly-alerts differentiator
Not scored by this record.
reporting-nl-query
Not scored by this record.
reporting-guest-cohorts differentiator
Not scored by this record.
reporting-sales-forecast differentiator
Not scored by this record.
reporting-tip-tax-compliance
Not scored by this record.
Multi-location, franchise & enterprise governance
multi-location-org-hierarchy
Aztec Base Data holds a named five-level estate structure as first-class objects: "When the company details are defined, an option box will allow you to add a new company or add an area to the company you just created", and "You will be presented with a variation of the below page every time you complete your new company, area, site, sales area, or POS. By the time that you define a sales area or a POS, the option box will allow you to modify any part of the estate structure". Grouping and reporting scope on top of it are documented in Site Tags: tags "create virtual groups of sites that are not dependent on corporate structure", e.g. a Beer Garden tag "so that you can search for, and report on, sites that have a beer garden", with a Site Tag filter in the Estate Structure Advanced Select. A parallel five-level Product Structure (Division > Sub Division > Super Category > Category > Sub Category) exists for the catalogue. https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Base%20Data/How%20To%27s/Estate%20Structure.htm · retrieved 2026-08-08
multi-location-central-menu-publish
One-action publish is documented: "The Send to PoS function allows any updates to be sent across your terminals; in addition, you can run a PoS preview prior to sending" - click "Send All" and "if all terminals update successfully, a green tick will be displayed. For any that do not update a red cross will be displayed", with "Preview Selected" to see the theme first. The same Send to PoS quick link publishes Staff & Security changes. Central authoring is covered by the menu management platform, whose changes "will be automatically pushed out across all your other Zonal tech". Shortfall: no publish/version history is documented - the screen shows current success or failure per terminal, not a record of what was pushed, when and by whom - and the publish target is the terminal list rather than a chosen set of locations. https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Theme%20Modelling/How%20To/Sending%20to%20PoS.htm · retrieved 2026-08-08
multi-location-local-override-policy differentiator
Not scored by this record.
multi-location-price-zones
Location-group pricing is documented: site tags "create virtual groups of sites that are not dependent on corporate structure", and "Tags can be used for a Site Location or a specific Price Band, as well as for Products, to identify products in a specific menu or for a specific site(s)" - a price band applied to a tagged group of sites, not a duplicated item record. Per-channel pricing exists on the delivery channel: Zonal Delivery offers "Flexible item pricing - Manage menu item prices per delivery provider", corroborated by the Zonal Delivery user manual's per-DSP price adjustment already held in this record. Shortfall: no daypart or time-of-day price tier is documented - the per-product Price Matrix in Base Data varies price by portion (Price Factor, e.g. Double 2, Half 0.5), not by time, and no first-party channel price tier is described for Order & Pay or Click & Collect. https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Base%20Data/How%20To%27s/Site%20Tags.htm · retrieved 2026-08-08
multi-location-scheduled-publish differentiator
Not scored by this record.
multi-location-new-store-template differentiator
Not scored by this record.
multi-location-corp-vs-franchisee-roles differentiator
Not scored by this record.
multi-location-royalty-calculation differentiator
Not scored by this record.
multi-location-royalty-collection
Not scored by this record.
multi-location-consolidated-reporting
Not scored by this record.
multi-location-normalized-item-rollup differentiator
Not scored by this record.
multi-location-cross-location-giftcard
Not scored by this record.
multi-location-cross-location-loyalty
Not scored by this record.
multi-location-multi-brand differentiator
Not scored by this record.
multi-location-multi-tax-jurisdiction
Not scored by this record.
multi-location-config-audit-log differentiator
Not scored by this record.
multi-location-enterprise-api differentiator
Not scored by this record.
multi-location-central-labor-policy
Not scored by this record.
Hardware & physical footprint
hardware-commodity-devices differentiator
Not scored by this record.
hardware-os-platforms
Zonal supplies its own terminals and handhelds with UK field engineers, but no OS versions or device specs are published.
hardware-handheld-purpose-built
Not scored by this record.
hardware-handheld-battery-swap differentiator
Not scored by this record.
hardware-handheld-lte
Not scored by this record.
hardware-offline-mode
Zonal documents offline continuity and names what degrades, but the documented offline mode fails the print-to-kitchen leg of the claim. Aztec Standalone Mode lets a disconnected till keep taking orders and recording cash sales, with stored accounts reconciled (Keep Account / Delete Account) when the server returns, and the degradations are stated by Zonal: 'all remote printing capabilities (IE Kitchen Printers will NOT work)', accounts created on the terminal 'will not be available on other terminals', there is 'a limited amount of space on a terminal for storing transactions', and only one terminal per trading area should have the mode enabled. It is a manually pressed, Dallas-key/PIN-authorised button after a countdown and reboot, not automatic failover. iServe handhelds offline can keep ringing items but 'will not be able to' sync accounts with Aztec, get prices and promotions, 'Send items to the bar/ kitchen' or 'Pay'. Shortfalls: kitchen printing is explicitly lost in the documented offline mode; the documented triggers are loss of the on-site server or Wi-Fi, and behaviour during a pure internet outage with the site server still up - including card authorisation and loyalty lookup - is not documented anywhere public. https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/PoS/How%20To%27s/Standalone%20Mode.htm · retrieved 2026-08-04
hardware-kds
Kitchen iQ is Zonal's own KDS and every element of the claim is documented. Bump bar: "The Kitchen iQ bump bar is equipped with a large number of buttons, allowing the kitchen screen system to be optimised for both large and small organisations", with a published shortcut table for the vertical bump bar and a keyboard alternative, plus touch-screen bumping. Station routing: "Routing rules control where all product items are sent on their journey through the preparation journey, from the entry point to the exit point and each stage between. Items are routed to stations and can be routed on any number of steps", filtered on Course, Order Destination, Prep Stream, Terminal Group, Serving Area or Station Dish Allocation, with a Recombine station for multi-station items. Course/fire timing: Cook Times holds a per-product cook time so "the next item will be displayed in 'waiting to start' X minutes after the first item ... all items arrive for serving at the same time", with percentage modifiers keyed to modifier text (a well-done steak fires before a rare one). Scales 1 to 25 screens. https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Kitchen%20iQ/How%20To/Routing%20Rules.htm · retrieved 2026-08-08
hardware-kiosk differentiator
Not scored by this record.
hardware-drive-thru
Not scored by this record.
hardware-printer-compatibility
Not scored by this record.
hardware-peripherals
Not scored by this record.
hardware-p2pe-terminal
Not scored by this record.
hardware-tap-to-phone differentiator
Not scored by this record.
hardware-pricing-transparency differentiator
Not scored by this record.
hardware-ownership-vs-lease differentiator
Not scored by this record.
hardware-usable-after-churn differentiator
Not scored by this record.
hardware-rma-sla differentiator
Not scored by this record.
hardware-byod
Not scored by this record.
hardware-remote-device-management differentiator
Not scored by this record.
hardware-selfpour-scales
Not scored by this record.
hardware-callerid-integration
Not scored by this record.
Integrations, API & extensibility
extensibility-public-api-docs
No public developer portal or API reference found.
extensibility-api-access-cost differentiator
Not scored by this record.
extensibility-partner-revshare
Not scored by this record.
extensibility-free-sandbox differentiator
Not scored by this record.
extensibility-oauth-partner-apps
Checked https://www.zonal.co.uk/integrations/ (HTTP 200), which lists 200+ named integration partners but publishes no technical detail; its only statement about access is "Integration and API access will be available for shared customer projects only. Please leave your details below highlighting the Zonal customer". Checked both public MadCap Flare documentation sites end to end via their table-of-contents indexes - product.zonal.co.uk/knowledgebase (Data/Tocs/Knowledgebase.js, 489 topics across Acquire, Aztec, Kitchen iQ, Bookings, Loyalty, Voucher Manager, iOrder, Zonal Delivery and Payment Devices) and product.zonal.co.uk/customer (Data/Tocs/Master.js, hardware catalogue plus Enterprise stock, reports and admin). Neither contains a developer, API, authentication, token or app-authorisation topic. Unresolved rather than no, because a gated partner programme is not evidence of the authentication mechanism used inside it: nothing published states whether partners use OAuth 2.0 scoped grants or shared static keys, and no operator-facing app-authorisation or revocation screen is documented in any admin module.
extensibility-webhooks-push
No public API reference exists to check. The integrations page (HTTP 200) states "Integration and API access will be available for shared customer projects only" and offers only a partnership contact form. Searched both public documentation sites' full topic indexes (product.zonal.co.uk/knowledgebase Data/Tocs/Knowledgebase.js and product.zonal.co.uk/customer Data/Tocs/Master.js) - no webhook, callback, event-subscription or polling topic exists. The only event-adjacent wording found is operational rather than architectural: Zonal Delivery role permissions include "Create location events provider" and "Update location events provider", and Kitchen iQ exports average times "to a JSON file in the installation path of the Kitchen iQ site server PC", which is a file drop, not a push. Real-time order flow to Kitchen iQ and to DSPs is internal to Zonal's own stack; whether third parties can subscribe to order lifecycle events is not published either way.
extensibility-webhook-reliability differentiator
Not scored by this record.
extensibility-order-injection-api
Not scored by this record.
extensibility-menu-write-api differentiator
Not scored by this record.
extensibility-data-symmetry differentiator
Not scored by this record.
extensibility-published-rate-limits
Not scored by this record.
extensibility-doordash-preferred differentiator
Not scored by this record.
extensibility-first-party-delivery-integrations differentiator
Not scored by this record.
extensibility-middleware-compatibility
Not scored by this record.
extensibility-accounting-connectors
Not scored by this record.
extensibility-payroll-export
Not scored by this record.
extensibility-bi-data-warehouse differentiator
Not scored by this record.
extensibility-app-marketplace
Not scored by this record.
extensibility-custom-fields-scripting
Not scored by this record.
extensibility-headless-embedded
Not scored by this record.
extensibility-api-versioning-deprecation
Not scored by this record.
extensibility-data-portability-exit differentiator
Not scored by this record.
Reliability, offline & operations
reliability-offline-order-entry
Aztec is an on-premise-anchored estate architecture, which implies local resilience, but no vendor statement of offline behavior was found.
reliability-offline-card-auth differentiator
Not scored by this record.
reliability-offline-decline-liability differentiator
Not scored by this record.
reliability-lan-degraded-multi-terminal differentiator
Not scored by this record.
reliability-local-transaction-engine differentiator
Not scored by this record.
reliability-offline-kds-printing
Zonal's own Standalone Mode guide states the limitation directly: "It is important to understand that operating a terminal in Standalone Mode means that it will trade entirely independently to all other terminals in the business inclusive of all remote printing capabilities (IE Kitchen Printers will NOT work)." The same page tells operators to plan around it - "Our customers are strongly advised to have an emergency process for manual activities in place should they experience outages... alongside operational processes such as getting orders to the Kitchen or Dispense bars" - and warns "there is a limited amount of space on a terminal for storing transactions during periods of being offline". Kitchen iQ screens depend on the kitchen server: Channels configures an "Offline Background Colour" for "if the screen looses connection to the kitchen server", which is a status indication, not continued routing. https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/PoS/How%20To%27s/Standalone%20Mode.htm · retrieved 2026-08-03
reliability-printer-fallback
Read Kitchen iQ Adding & Configuring Printers, which enumerates every per-printer field - Name, Type (only Orient BTP-R580II and Epson TM-U220; "Only IP Printer are available for use within Kitchen iQ printing"), IP Address, Last Job, Last Status - with no backup printer, failover target or alert setting among them. Also read Kitchen iQ Routing Rules and Load Balancing (round-robin distribution between a Primary Station and Secondary Stations, which is station workload balancing and explicitly not printer redundancy), Printing Selected Tickets, Notifications, Header Warnings & Alerts, System Warnings (a stub page whose warning examples are images only, so the warning texts could not be read), and Aztec Base Data Print Streams (which links physical printers to streams but documents only name creation). Unresolved: the per-printer "Last Status" field shows printer health is tracked, but nothing published says whether an unreachable printer triggers an automatic reroute to a backup printer or KDS station, or an alert to staff.
reliability-sync-conflict-handling
Not scored by this record.
reliability-offline-feature-matrix
Not scored by this record.
reliability-public-status-page
Not scored by this record.
reliability-contractual-uptime-sla differentiator
Not scored by this record.
reliability-incident-postmortems
Not scored by this record.
reliability-247-live-support
Not scored by this record.
reliability-onsite-install differentiator
Not scored by this record.
reliability-menu-build-service differentiator
Not scored by this record.
reliability-hardware-replacement-sla
Not scored by this record.
reliability-backup-restore
Not scored by this record.
reliability-pci-dss-4-attestation
Not scored by this record.
reliability-mfa-role-based-access
Not scored by this record.
reliability-self-serve-training
Not scored by this record.
reliability-failover-terminal-role differentiator
Not scored by this record.
reliability-cellular-backup
Not scored by this record.
Commercial, compliance & data ownership
commercial-month-to-month-contract differentiator
Not scored by this record.
commercial-no-early-termination-fee differentiator
Not scored by this record.
commercial-autorenew-terms-published
The only contract-terms document Zonal publishes is https://www.zonal.co.uk/terms-and-conditions/, and it governs use of the website rather than the product - its substantive clauses are that Zonal may "Change or remove (temporarily or permanently) the Website or any part of it without notice" and "Change these Terms and Conditions at any time". It contains no minimum term, no auto-renewal clause and no cancellation notice window. No master service agreement, terms of business or SLA is linked anywhere on the site, and pricing is quote-only with prospects routed to a sales telephone number. The renewal term and notice window therefore cannot be diligenced before signing. https://www.zonal.co.uk/terms-and-conditions/ · retrieved 2026-08-03
commercial-processing-not-bundled differentiator
Not scored by this record.
commercial-interchange-plus-published differentiator
Not scored by this record.
commercial-rate-increase-clause differentiator
Not scored by this record.
commercial-pricing-published
The EPoS page FAQ answers the question directly and without a figure: "How much does a hospitality EPoS system cost? Pricing is tailored to your estate's size and complexity. Our consultative team will work with you to build a package that fits your operation with no hidden fees and everything included as standard." No sterling or dollar figure appears anywhere on the page, per-site or per-terminal. The site's own Rental Packages links (/products/rental-packages/ and /products/rental-packages/pos-essentials/) return 404, and the Akru panel for independents promises only that a demo will "tell you exactly what it costs". https://www.zonal.co.uk/products/epos/ · retrieved 2026-08-08
commercial-module-unbundling differentiator
Not scored by this record.
commercial-hardware-purchase-outright
Established that no hardware price is published anywhere: https://www.zonal.co.uk/products/epos/hardware/ (HTTP 200) lists no prices and routes to sales; https://www.zonal.co.uk/order/ (HTTP 200) covers consumables only ("till rolls, ink ribbons and dallas keys"), publishes no prices and notes only that "carriage will be added depending on the order quantity"; and the customer portal Hardware Catalogue (product.zonal.co.uk/customer/Content/Hardware/) lists part numbers, specifications and release status for terminals, printers, PEDs, tablets and the KIQ screen controller with no prices at all. Unresolved on the substantive half of the claim: Zonal's own product navigation markets "POS Rental Packages", but the package page https://www.zonal.co.uk/products/rental-packages/all-in-one-pos/ returned HTTP 404 on every attempt (WebFetch and curl with a browser user-agent) despite being search-indexed, so the rental term, the monthly figure and whether an outright-purchase alternative exists could not be read first-hand. Not scored from the search-engine snippet.
commercial-hardware-not-locked differentiator
Not scored by this record.
commercial-implementation-fee-published
Not scored by this record.
commercial-data-export-self-serve
Not scored by this record.
commercial-export-customer-and-loyalty differentiator
Not scored by this record.
commercial-post-termination-export-window differentiator
Not scored by this record.
commercial-data-ownership-clause differentiator
Not scored by this record.
commercial-source-available-selfhost
Not scored by this record.
commercial-pci-p2pe-tokenization
Not scored by this record.
commercial-pci-dss-4-controls
Not scored by this record.
commercial-soc2-attestation
Not scored by this record.
commercial-privacy-dsar-tooling
Not scored by this record.
commercial-wcag-kiosk-accessibility differentiator
Not scored by this record.
commercial-dual-pricing-compliant differentiator
Not scored by this record.
Adversarial verification
An independent pass was instructed to refute this record, defaulting to downgrade when uncertain. It challenged 37 values — 13 upheld, 0 downgraded, 4 upgraded. This is published in full because a reader who can see which values were contested, on what evidence, and which way they moved has something no affiliate-funded comparison offers.
Capability claims
| Claim | As first scored | Verdict | What the verifier found |
|---|---|---|---|
| menu-pricing-modifier-price-by-parent-size | unknown (grade F placeholder: "No public documentation located during the 2026-08-01 research pass") | resolve-to-partial | Placeholder rationale meant the cell was never examined. Read Aztec Product Modelling Instructions & Choices and Base Data Portion Types. Per-parent modifier pricing is achieved by attaching a different portion of the choice item to each parent recipe, and a per-product Price Matrix exists across portions. Resolved to partial because the mechanism exists but is not the parent x size matrix the claim describes and must be maintained per parent recipe. source |
| menu-pricing-topping-quantity-tiers | unknown (grade F placeholder: "No public documentation located during the 2026-08-01 research pass") | resolve-to-yes | Placeholder rationale meant the cell was never examined. Portion Types documents a configurable Price Factor per portion (Double 2, Half 0.5) inside a Price Matrix; Instructions & Choices confirms portions apply to choice items including a zero-charge 'Inclusive' portion, and Enterprise Recipes confirms choice dispense sizes are the choice's portions. Grade B documentation, so yes. source |
| kitchen-expo-consolidation | unknown (grade F placeholder: "No public documentation located during the 2026-08-01 research pass") | resolve-to-yes | Placeholder rationale meant the cell was never examined. Kitchen iQ Channels documents an excluded-stations view that shows the account only once every line has been bumped to the serving station, Routing Rules documents a Recombine Station with per-station bumping, and Stations documents an Assembly/pass stage. Grade B. source |
| kitchen-bump-bar-hardware | unknown (grade F placeholder: "No public documentation located during the 2026-08-01 research pass") | resolve-to-partial | Placeholder rationale meant the cell was never examined. A physical bump bar with a fully documented button map exists, but the claim also requires documented supported models and the customer-portal Hardware Catalogue's Kitchen Systems section lists only the KIQ screen controller (ZKMS-CONTRLR-IOT), with no bump-bar SKU anywhere in the catalogue. source |
| delivery-zone-pricing | unknown (grade F placeholder: "No public documentation located during the 2026-08-01 research pass") | resolve-to-no | Placeholder rationale meant the cell was never examined. Resolved to no on positive absence rather than on failure to find: the Zonal Delivery user manual states it covers everything the platform does, enumerates the full feature set, and contains no zone, fee, minimum or address-based promise time - delivery is executed by Deliveroo and Uber Eats, who own those settings. source |
| digital-account-saved-payment | unknown (grade F placeholder: "No public documentation located during the 2026-08-01 research pass") | resolve-to-partial | Placeholder rationale meant the cell was never examined. The Order & Pay product page claims repeat-previous-order and wallet payment, and the Loyalty knowledge base documents an iOrder sign-up journey, but saved addresses and stored tokenised cards are undocumented. Partial at grade C because the reorder evidence is a product page, not documentation. source |
| guest-loyalty-accrual-models | unknown (grade F placeholder: "No public documentation located during the 2026-08-01 research pass") | resolve-to-yes | Placeholder rationale meant the cell was never examined. Loyalty Program Basics documents currency, points, stamp-card and tiered programs as configuration and Actions & Rewards adds item-for-visits, clearing the two-of-three bar at grade B with no bolt-on loyalty vendor. source |
| guest-loyalty-lifecycle-automation | unknown (grade F placeholder: "No public documentation located during the 2026-08-01 research pass") | resolve-to-partial | Placeholder rationale meant the cell was never examined. Birthday, registration and recurring rewards are documented as always-on triggers; no lapsed or win-back trigger exists in the Loyalty or Voucher Manager documentation, and outbound campaign messaging sits in the separately branded Airship CRM product with no knowledge base section. source |
| labor-granular-rbac | unknown (grade F placeholder: "No public documentation located during the 2026-08-01 research pass") | resolve-to-partial | Placeholder rationale meant the cell was never examined. Enterprise separates permission groups from per-restaurant access groups and Zonal Delivery lets operators compose custom roles from a named action list, but the Aztec till permission list is never enumerated publicly - Staff and Security covers only Job Role assignment and its permissions material is a text-free video. source |
| labor-manager-override-audit | unknown (grade F placeholder: "No public documentation located during the 2026-08-01 research pass") | resolve-to-partial | Placeholder rationale meant the cell was never examined. Approvals are taken by individual Dallas key or PIN and user-attributed audit reports exist (Wastage Details, Price Change Tracker), but Zonal documents a shared bypass code (1901) for the same approval and describes no immutable audit store. source |
| inventory-unit-conversion-yields | unknown (grade F placeholder: "No public documentation located during the 2026-08-01 research pass") | resolve-to-partial | Placeholder rationale meant the cell was never examined. Purchase pack size, dispense (recipe) size and stock count size are stored per item with explicit multiples, but no yield or waste percentage is applied to the raw-to-usable conversion - wastage is a separate transaction type, not a per-ingredient factor. source |
| inventory-count-modes | unknown (grade F placeholder: "No public documentation located during the 2026-08-01 research pass") | resolve-to-partial | Placeholder rationale meant the cell was never examined. Full stock audits and ad-hoc PoS spot checks are both documented with their own variance history, but no scheduled recurring cycle count of a subset is documented; the only scheduling primitive is a company-wide default stock period length. source |
| reporting-eod-closeout | unknown (grade F placeholder: "No public documentation located during the 2026-08-01 research pass") | resolve-to-partial | Placeholder rationale meant the cell was never examined. The 7 Day Statement of Trade reconciles gross and post-discount sales, tips, service charge, tender-level declared payments, banking and cash on site per trading day, and Daily Sign Off gates the close, but VAT and refunds are not lines on it, so the claim's single-document requirement is not fully met. source |
| reporting-pmix-modifier-level | unknown (grade F placeholder: "No public documentation located during the 2026-08-01 research pass") | resolve-to-partial | Placeholder rationale meant the cell was never examined. The Enterprise report catalogue documents item-level sales mix filterable by revenue centre, sales type and day part, but no report is documented at modifier level, and Zonal's Instructions are explicitly unpriced and excluded from sales. source |
| reliability-offline-kds-printing | unknown (grade F placeholder: "No public documentation located during the 2026-08-01 research pass") | resolve-to-no | Placeholder rationale meant the cell was never examined. Resolved to no on the vendor's own explicit statement of the limitation: in Standalone Mode remote printing including kitchen printers does not work, and Zonal advises operators to run a manual process to get orders to the kitchen during outages. source |
| commercial-autorenew-terms-published | unknown (grade F placeholder: "No public documentation located during the 2026-08-01 research pass") | resolve-to-no | Placeholder rationale meant the cell was never examined. Resolved to no on positive absence: the only terms document Zonal publishes governs website use and contains no term, renewal or notice clause, and no master service agreement is linked anywhere on the site. The claim is specifically about public availability, which is directly verifiable. source |
| order-capture-offline-order-entry | unknown (grade F placeholder: "No public documentation located during the 2026-08-01 research pass") | resolve-to-partial | Placeholder rationale meant the cell was never examined. Aztec PoS Standalone Mode is the vendor's published offline scope: orders, choices and cash tender work on a disconnected terminal and reconcile on rejoin. Partial, not yes, because Zonal states remote printing is excluded - 'Kitchen Printers will NOT work' - so orders cannot be sent to the kitchen; the mode is a manually pressed, PIN-authorised button rather than automatic failover after the terminal counts down and reboots; local transaction storage is 'limited' with no published figure; and Zonal recommends enabling it on only one terminal per trading area. Handheld offline behaviour is not documented anywhere public. source |
| menu-pricing-nested-modifiers | unknown (grade F placeholder: "No public documentation located during the 2026-08-01 research pass") | resolve-to-yes | Placeholder rationale meant the cell was never examined. The Aztec 3.7.3-3.8.4 release notes for multi-level conversational ordering state the prior one-menu-depth limit is removed and that nested choices carry min/max controls at multiple levels, a nested choice respecting its parent's min/max; min>=1 is the forced-selection mechanism. The Nested Choices help guide documents both a choice inside a recipe and a choice directly inside another choice, with no stated depth cap, and iOrder Managing Products independently confirms choice-within-choice modelling with a multi-select setting. Grade B vendor documentation on a table-stakes claim, so yes; the Base Data enablement being irreversible and defaults being un-nestable are recorded as caveats in the note rather than as a downgrade. source |
| delivery-dispatch-board | unknown (grade F placeholder: "No public documentation located during the 2026-08-01 research pass") | resolve-to-no | Placeholder rationale meant the cell was never examined. Resolved to no on positive absence: Zonal's delivery product (Zonal Delivery) is scoped by its own user manual as managing Delivery Service Providers from one place, and the manual enumerates the entire feature set - menu schedules, publishing, per-DSP pricing, pause, prep time, availability, active orders, order history - with no dispatch/expo screen, driver availability, elapsed-time view or run batching among them; drivers and dispatch belong to the DSPs (Deliveroo, Uber Eats). The knowledge.zonal.co.uk Delivery help-guide navigation shows the same DSP-only sections, and the EPoS page describes delivery solely as receiving orders from delivery partners. This is the docs-enumerate-the-alternatives form of absence evidence, not a failed search. source |
| hardware-offline-mode | unknown (grade F placeholder: "No public documentation located during the 2026-08-01 research pass") | resolve-to-partial | Placeholder rationale meant the cell was never examined. Zonal does publish an explicit offline scope, satisfying the documents-what-degrades half of the claim: Aztec Standalone Mode keeps a disconnected till taking orders and recording cash sales with reconciliation on rejoin, and iServe offline mode lists exactly what a handheld loses. Partial, not yes, because Zonal states kitchen printers will NOT work in Standalone Mode - the print-to-kitchen leg of the claim - the mode is a manually authorised button rather than automatic failover, and the documented triggers are on-site server or Wi-Fi loss; behaviour during a pure internet outage with the site server up, including card auth and loyalty lookup, is undocumented. Consistent with the resolve-to-partial already recorded for order-capture-offline-order-entry on the same evidence. source |
| commercial-pricing-published | no, grade B - Pricing is explicitly tailored to estate size and complexity | upheld | Grade only, value untouched. Corpus-wide mechanical pass (workflows/regrade-marketing-pages.mjs): the cited page is a first-party pricing/feature/product page, which atlas-evidence-rules grades C ("vendor pricing page or feature page - first-party, but written to sell"), not B ("vendor product documentation - the manual, the help centre, the admin guide"). No claim was re-researched in this pass and no evidence was re-read; only the grade was brought into line with the source type. source |
| digital-account-saved-payment | partial, grade C - "The Order & Pay product page claims reorder - 'Guests can see and repeat previous orde" | upheld | The cited URL was a dead citation wearing a 200 - it 301s to /products/online-ordering-systems/order-and-pay/. I fetched the destination and matched all three quoted strings character for character, so nothing was conflated. Saved addresses and stored tokenised cards are still absent from the feature list; the Loyalty Data Flows guide additionally shows app account and loyalty card are separately created. Partial stands on the destination page. source |
| order-capture-scheduled-orders | partial, grade D - "Click & Collect and advance-booking deposit traceability through the POS are docume" | upheld | The cited /solutions/epos/ URL redirects to /products/epos/. Rather than re-point to another marketing page I walked the Aztec knowledge base and found the mechanism the researcher said was undocumented: Kitchen iQ Delayed Orders and Cook Times. That withdraws the original shortfall but does not carry the cell to yes, because the same doc shows the delayed order is displayed on receipt with its due time rather than withheld, and no per-channel lead time is configurable for Order & Pay or Click & Collect. Partial retained, re-evidenced at grade B. source |
| payments-emv-nfc | partial, grade D - "Zonal Pay unifies in-person and digital payments and handhelds ship with integrated " | upgrade-to-yes | The cited /solutions/epos/ URL is a redirect. Chasing the capability instead of the page: the Aztec knowledge base PoS Payments guide names the Chip & PIN device driven by integrated EFT, and https://www.zonal.co.uk/products/epos/integrated-payment-system/ states plainly that Apple Pay and Google Pay are supported in addition to card payments. Both legs the researcher called unenumerated are now enumerated, one of them in product documentation, so the partial no longer holds. source |
| payments-gift-cards | partial, grade D - "Gift cards and vouchers are listed within the loyalty and CRM ecosystem (alongside A" | upheld | The cited URL redirects. I replaced it with the iZone gift-card production guide in the Aztec/Loyalty knowledge base, which establishes a first-party gift platform issuing its own numbered cards, plus the Loyalty product page for balance checking and redemption at any point of sale. That kills the researcher's 'listed alongside Airship' framing and the estate-wide half of their shortfall. Partial still stands because no source shows a gift card being redeemed inside Order & Pay or Click & Collect, whose enumerated redemption journeys name only vouchers, offers and loyalty rewards. source |
| delivery-driver-roster | no, grade D - "Delivery is offered as an online-ordering channel; no in-house driver module with cl" | upheld | This is a conclusion-flipping cell held at `no` on a citation that now 301s, with a note that was pure absence-of-mention. I re-retrieved the dedicated Zonal Delivery product page, which positively frames the product as a delivery-service-provider management platform integrating Deliveroo, Just Eat and Uber Eats, and cross-checked the Zonal Delivery help guide's section inventory in this record's own sources - neither contains a driver, dispatch board or run history. That is positive evidence of a DaaS handoff rather than a native roster, so `no` now meets the bar it previously did not. source |
| digital-first-party-web | yes, grade D - "First-party Order & Pay, Click & Collect and Delivery ordering channels sold as part o" | upheld | The sole citation redirected, so the yes was standing on nothing. I retrieved the Click & Collect and Order & Pay product pages, which independently document white-labelled, operator-branded web ordering writing straight into the EPoS with no third-party branding. I also checked whether Zonal claims commission-free ordering and it does not - it applies that phrase to Bookings only - so I have recorded that limit in the note rather than borrowing it. The yes carries on first-party white-label ordering. source |
| digital-menu-single-source | partial, grade D - "Marketed as one connected platform where products and pricing are managed centrally ac" | upgrade-to-yes | The cell was held at partial only because the redirected overview page spoke of central management without naming propagation. The dedicated menu management page does name it, and the Order & Pay page confirms it from the receiving end; the iOrder Product Manager documentation shows digital products are the Aztec product records themselves rather than a parallel build. Three independent first-party sources, one of them documentation, so the named shortfall no longer exists. source |
| guest-loyalty-unified-profile | partial, grade D - "Loyalty and CRM are delivered largely via Airship, a sibling/partner brand rather than" | upheld | Withdrawing the researcher's reasoning as well as their dead citation. Zonal Loyalty is a first-party product with its own knowledge base, and Airship is a Zonal-group CRM, so 'delivered via a partner brand' was not the reason to hold this at partial. The actual reason is in the Loyalty Data Flows and Guest Management guides, which state that a widget sign-up does not create an app account, that platform edits do not propagate to the app, and that card association and card swaps are manual head-office operations. That is documented absence of dedup/merge, which is a stronger basis for partial than the one it replaces. source |
| labor-clock-in-at-pos | partial, grade D - "Staff management with payroll, rotas, targets and scheduling is built into the EPoS; c" | upgrade-to-yes | Held at partial because a marketing page (now a redirect) did not spell out the clock-in method. The Aztec knowledge base does: Verifying Clock Times repeatedly describes employees clocking in and out on the PoS terminal, including break capture, and Adding Front of House Users shows each employee is issued a Dallas key and/or a 4-digit PIN read at that terminal. Both halves of the claim are in grade B documentation, so partial is not defensible. source |
| inventory-recipe-bom-costing | partial, grade D - "Inventory covers purchase-to-pay and menu management with stock control across multipl" | upheld | The redirected citation gave no view of recipe structure at all. In Aztec Product Modelling I found the sub-recipe layer the researcher said was undocumented: prepared items are batch sub-recipes built from purchase lines and priced pro-rata into the parent dish, and a recipe may contain another recipe. That withdraws the stated shortfall, but the claim also requires automatic recalculation when a component cost moves, and no guide in Product Modelling or Stocks says so. Partial retained on the remaining leg, at grade B instead of D. source |
| reporting-realtime-dashboard | partial, grade D - "140+ reports per site or across the estate, with real-time transaction visibility clai" | upheld | The citation redirected, so I retrieved the dedicated reporting product page. It does name a mobile off-premise route, refuting the researcher's stated gap, but it also shows that route is Dimensions+, a Power BI-based add-on gated behind a Microsoft Power BI Pro licence and explicitly positioned as beyond standard EPoS reporting. That is a paid add-on dependency, which is exactly what partial is for; the value is unchanged but the shortfall recorded against it is now the right one. source |
| multi-location-org-hierarchy | partial, grade D - "Reporting works per site or across the estate and pricing is controllable at enterprise" | upgrade-to-yes | The researcher inferred 'at least two levels' from a marketing page that now redirects. The Base Data Estate Structure guide documents five named levels created and editable as objects - company, area, site, sales area, POS - which is well past the three the claim asks for, and Site Tags documents reporting and search scoped to groupings over that structure. Grade B documentation, so the partial does not survive. source |
| multi-location-central-menu-publish | partial, grade D - "Products can be managed centrally across the entire business; publish/version history s" | upheld | The citation redirected. I found the actual publish mechanism in Theme Modelling > Sending to PoS, which supplies the single-action push with preview and per-terminal success indicators that the marketing page only gestured at. It does not supply an audit history: nothing in Theme Modelling records the content or author of a past send, and the selection unit is terminals. Partial stands for the same stated reason, but now on documentation that shows what does exist. source |
| multi-location-price-zones | partial, grade D - "Claims complete control over pricing at enterprise or individual site level; per-chann" | upheld | The redirected page said only 'enterprise or individual site level'. Base Data Site Tags shows the actual object - a Price Band bound to a virtual group of sites - and Zonal Delivery documents per-provider item pricing, so two of the three legs the researcher called unstated are in fact documented. The daypart leg is not: I checked Base Data, Product Modelling, Portion Types and Promotions and found time-based promotions but no time-based price tier on the item. Partial retained, evidence replaced and grade raised to B. source |
| hardware-kds | yes, grade D - "Kitchen iQ is a first-party kitchen management/display product within the Zonal platfo" | upheld | A yes standing on a dead marketing citation is worth re-testing, so I went looking for the mechanism rather than the brand. The Aztec Kitchen iQ knowledge base carries a bump-bar guide with a full button/shortcut table, a routing-rules guide describing multi-step station routing with recombine, and a cook-times guide describing computed staggered firing with per-modifier percentage adjustment. First-party, documented, and covering bump bar, routing and course timing - the yes is better supported than the record claimed. source |
| commercial-pricing-published | no, grade C - "Pricing is explicitly tailored to estate size and complexity; no dollar or sterling fig" | upheld | The 2026-08-06 regrade left this cell pointing at /solutions/epos/, which now 301s to /products/epos/. I fetched the destination and the tailored-pricing sentence is present verbatim in the FAQ, so the positive statement supporting `no` carries over intact. I also tested the two Rental Packages URLs linked from the navigation, in case a published price list had appeared for the independents range; both 404. Value and grade unchanged, citation re-pointed. source |
Sources
Every URL this record cites. 65 in total.
- https://www.zonal.co.uk/solutions/epos/
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Product%20Modelling/How%20To%27s/Instructions%20%26%20Choices.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Base%20Data/How%20To%27s/Portion%20Types.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Product%20Modelling/How%20To%27s/Full%20Recipe%20Costing%20%28with%20choices%29.htm
- https://product.zonal.co.uk/customer/Content/Order%20Inventory%20and%20Menu%20Management/Enterprise/How%20To/Stock%20Admin/Recipes.htm
- https://product.zonal.co.uk/customer/Content/Order%20Inventory%20and%20Menu%20Management/Enterprise/How%20To/Stock%20Admin/Stock%20Items.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Base%20Data/How%20To%27s/Units.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Stocks/How%20To/Adding%20a%20New%20Stock.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Stocks/How%20To/Completing%20a%20Spot%20Check%20How%20To.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Kitchen%20iQ/How%20To/Channels.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Kitchen%20iQ/How%20To/Routing%20Rules.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Kitchen%20iQ/How%20To/Stations%20%26%20Station%20Dish%20Allocation%20Groups.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Kitchen%20iQ/How%20To/Intro%20to%20Bump%20Bar.htm
- https://product.zonal.co.uk/customer/Content/Hardware/Kitchen%20Systems/Kitchen%20Systems%20Home.htm
- https://product.zonal.co.uk/customer/Content/Hardware/Hardware%20Catalogue.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Kitchen%20iQ/How%20To/Adding%20%26%20Configuring%20Printers.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Kitchen%20iQ/How%20To/Load%20Balancing.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/PoS/How%20To%27s/Standalone%20Mode.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Theme%20Modelling/How%20To/Correction%20Methods.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Staff%20and%20Security/How%20To/Adding%20Front%20of%20House%20Users.htm
- https://product.zonal.co.uk/customer/Content/Order%20Inventory%20and%20Menu%20Management/Enterprise/How%20To/Enterprise%20Admin/User%20Management.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/iOrder/Zonal%20Delivery/How%20To%27s/Custom%20User%20Permissions.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/iOrder/Zonal%20Delivery/User%20Manuals/Zonal%20Delivery%20User%20Manual.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Reporting/How%20To/7%20Day%20Statement%20of%20Trade.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Finance/How%20To/Daily%20Sign%20Off.htm
- https://product.zonal.co.uk/customer/Content/Order%20Inventory%20and%20Menu%20Management/Enterprise/How%20To/Reports/Report%20Names%20And%20Descriptions.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Loyalty%20%26%20Voucher%20Manager/Loyalty/How%20Tos/Loyalty%20Program%20Basics.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Loyalty%20%26%20Voucher%20Manager/Loyalty/How%20Tos/Actions%20%26%20Rewards.htm
- https://www.zonal.co.uk/integrations/
- https://www.zonal.co.uk/products/order-and-pay/
- https://www.zonal.co.uk/terms-and-conditions/
- https://www.zonal.co.uk/products/epos/hardware/
- https://www.zonal.co.uk/order/
- https://www.zonal.co.uk/products/rental-packages/all-in-one-pos/
- https://knowledge.zonal.co.uk/archive/Content/Point%20of%20Sale/Aztec/Releases/Aztec%203.08.4.htm
- https://knowledge.zonal.co.uk/pos/Content/Aztec/Help-Guides/Product-Modelling/Choices/Nested-Choices.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/iOrder/Product%20Manager/How%20To%27s/Managing%20Products.htm
- https://knowledge.zonal.co.uk/pos/Content/Aztec/Help-Guides/Product-Modelling/General-Information.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/iServe/How%20To/Using%20iServe%20in%20Offline%20Mode.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/PoS/How%20To%27s/Using%20Aztec%20POS%20Terminals%20in%20Standalone%20Mode.htm
- https://knowledge.zonal.co.uk/ordering/Content/Zonal-Delivery/Help-Guides/Setup/Login.htm
- https://www.zonal.co.uk/products/epos/
- https://www.zonal.co.uk/products/online-ordering-systems/order-and-pay/
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Kitchen%20iQ/How%20To/Delayed%20Orders.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Kitchen%20iQ/How%20To/Cook%20Times.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/PoS/How%20To%27s/Payments.htm
- https://www.zonal.co.uk/products/epos/integrated-payment-system/
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Loyalty%20%26%20Voucher%20Manager/Loyalty/How%20Tos/Loyalty%20%26%20Gift%20Card%20Production.htm
- https://www.zonal.co.uk/products/marketing/loyalty-programmes/
- https://www.zonal.co.uk/products/marketing/toggle-ecommerce-and-gift-cards/
- https://www.zonal.co.uk/products/online-ordering-systems/delivery/
- https://www.zonal.co.uk/products/online-ordering-systems/click-and-collect/
- https://www.zonal.co.uk/products/operations/menu-management-system/
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Loyalty%20%26%20Voucher%20Manager/Loyalty/How%20Tos/Data%20Flows.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Loyalty%20%26%20Voucher%20Manager/Loyalty/How%20Tos/Loyalty%20Guest%20Management%20(Head%20Office).htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Time%20and%20Attendance/How%20To/Verifying%20Clock%20Times.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Product%20Modelling/How%20To%27s/Food%20Recipe%20Costings.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Product%20Modelling/How%20To%27s/Full%20Recipe%20Costing%20(with%20prepared%20items).htm
- https://www.zonal.co.uk/products/operations/reporting/
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Base%20Data/How%20To%27s/Estate%20Structure.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Base%20Data/How%20To%27s/Product%20Structure.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Theme%20Modelling/How%20To/Sending%20to%20PoS.htm
- https://product.zonal.co.uk/knowledgebase/Content/Knowledge%20Base/Aztec/Back%20Office/Base%20Data/How%20To%27s/Site%20Tags.htm
- https://www.zonal.co.uk/products/operations/kitchen-management-system/
- https://www.zonal.co.uk/products/rental-packages/