6 Integration Layers Every NZ Restaurant POS Must Cover

NZ POS Integration Framework at a Glance

The POS system that serves NZ hospitality operators most effectively won't be the one with the slickest UI or the cheapest monthly fee — it will be the one that connects most cleanly and completely to the tools Kiwi operators already depend on. Use the six-layer framework and the operational checklist above to evaluate any POS vendor you're considering, and make integration ecosystem breadth and depth — not just feature list — the centre of your decision.

Layer 1: NZ Payment Rails — eftpos, Paywave & Surcharge Compliance

A POS system operating in New Zealand must natively support eftpos NZ (the domestic debit network), Visa and Mastercard Paywave (contactless credit), and comply with the Commerce Commission's merchant surcharge guidance, which requires that any surcharge passed to customers must not exceed the actual cost of accepting that payment method.

What to Look for in NZ Payment Integration

NZ Payment Processors Worth Evaluating

• Windcave (formerly Payment Express): One of New Zealand's most widely deployed payment gateway providers, with strong POS integration support and eftpos NZ certification.

• Tyro NZ / Smartpay: Growing presence in the NZ hospitality market with integrated terminal options.

• Stripe Terminal: Increasingly used by NZ tech-forward operators, though eftpos NZ support should be confirmed per POS integration.

NZ Operator Notes

For a standalone café, the priority is fast tap-to-pay throughput with minimal declined transaction friction during peak service. For a bar or pub, split-bill capability and tab management tied to the payment terminal are non-negotiable. For a multi-site restaurant group, centralised surcharge configuration across all terminals — so no site accidentally overcharges on surcharges — is a compliance requirement, not a nice-to-have.

Eats365 POS has certified integrations with Windcave (eftpos NZ), Smartpay/Tyro NZ, and Stripe Terminal for New Zealand operators. Terminal configuration supports Paywave and eftpos debit with compliant surcharge enforcement built into the system level. For current certified payment processor status and specific terminal models supported, contact the Eats365 NZ team or consult the official NZ payment integration documentation.

Layer 2: Xero Accounting Integration — the NZ SMB Standard

Xero is headquartered in Wellington and commands an exceptionally high share of the New Zealand SMB accounting market. For NZ hospitality operators, the practical question is not whether to use Xero — most already do — but how cleanly their POS system pushes sales data, GST, and COGS into Xero without manual entry.

What a Strong Xero–POS Integration Delivers

Depth of Integration Varies Significantly

Not all POS-to-Xero integrations are equal. Some POS systems export only a daily revenue lump sum — one line item per day — which gives Xero almost nothing useful for reconciliation. A high-quality integration exports itemised revenue by category (food, beverage, surcharge, tip), payment method breakdown, and tax mapping aligned with NZ GST requirements.

For NZ café operators in particular, where owner-operators are often doing their own Xero reconciliation, the difference between a clean automated sync and a daily manual import is 30–60 minutes of admin time every single day of the year.

Eats365 POS supports automatic submission of the Daily Closing Report to Xero after End of Day, covering transactions and sales processed across POS terminals, modules, and third-party integrations. In addition, a new Xero export type allows merchants to send sales information as invoice only or as invoice and credit note, with refunds and voided payments separated into credit notes for cleaner reconciliation and more accurate bookkeeping.

Layer 3: Online Delivery Platforms — Uber Eats NZ & DoorDash NZ

Uber Eats and DoorDash are the two dominant third-party delivery platforms operating in New Zealand. Without a direct POS integration, orders from these platforms arrive on a separate tablet, require manual re-entry into the POS, and create a parallel order stream that breaks kitchen workflow, inflates error rates, and makes end-of-day reconciliation painful.

Why Delivery Platform Integration Is Non-Negotiable for NZ Operators

NZ Delivery Platform Integration Options

• Uber Eats NZ: Supports POS integration via its Uber Eats Manager API. Quality of integration depends on the POS vendor's certification level — some offer full menu sync and order injection into the POS kitchen display; others only offer basic order forwarding.

• DoorDash NZ: Similarly supports POS integration through its merchant platform, with comparable requirements for certified POS connectivity.

• Aggregator middleware (e.g., Deliverect, Ordermark): NZ operators running both Uber Eats and DoorDash simultaneously sometimes use a middleware aggregator to funnel all delivery orders into a single POS integration point — reducing the number of direct API connections the POS must maintain.

Use-Case Notes by Operator Type

• Standalone café: Delivery volume is typically lower; the priority is reducing the distraction of a separate delivery tablet during service rather than maximising throughput.

• Multi-site NZ restaurant group: Centralised menu management pushed simultaneously to all delivery platforms and all POS terminals is the key operational win — one menu change in the POS propagates everywhere.

• Bar or pub: Delivery integration is less common but increasingly relevant for NZ bars adding a food delivery revenue stream.

Eats365 POS supports direct integration with major delivery platforms, allowing NZ operators to receive Uber Eats and DoorDash orders directly into the POS order flow and kitchen display system — eliminating the standalone tablet and the manual re-entry that goes with it.

Layer 4: Reservation & Table Management — ResDiary, SevenRooms & OpenTable in NZ

Reservation systems do more than hold a guest's name and time — when integrated with a POS, they carry booking data, pre-order information, dietary flags, and spend history directly into the service workflow, enabling front-of-house teams to deliver personalised experiences without paper notes or verbal briefings.

What POS–Reservation Integration Should Deliver:

Real-time table status sync ensures that when a table is seated or cleared in the POS, the reservation system updates automatically — removing the need for floor staff to manually update two systems. Reservation cover data flows into POS reporting, giving operators accurate covers-per-session metrics for menu planning and staffing. Pre-orders taken at booking time arrive in the POS kitchen system before guests walk in the door. Post-meal, POS transaction data pushes back to the reservation platform to build individual guest spend profiles over time.

NZ Operator Considerations:

For a fine dining or mid-scale NZ restaurant, the reservation–POS link is where hospitality personalisation is either enabled or blocked. Without it, the front-of-house team is manually briefing the kitchen on pre-orders and manually noting dietary requirements in a way that doesn't survive a busy Friday service. For a café, reservation integration is typically lower priority — most café trade is walk-in — but table management and waitlist functionality still matter during weekend brunch peaks.

Eats365 POS's open API architecture supports connectivity with reservation platforms used in the NZ market, allowing operators to build the reservation-to-table-to-payment loop without switching systems mid-service.

Layer 5: Loyalty, CRM & Repeat-Visit Tools for NZ Hospitality

Customer retention is one of the highest-leverage levers available to NZ hospitality operators facing rising food costs and compressed margins. A POS-connected loyalty system turns anonymous transactions into identified customer relationships — enabling personalised offers, visit-frequency rewards, and CRM campaigns that bring guests back without discounting broadly. Customer retention through sophisticated loyalty is where operational leverage meets margin protection — and the integration of loyalty data into your POS workflow is what makes it actually work operationally.

Loyalty & CRM Options Relevant to NZ Operators

Effective loyalty integration works when every POS transaction is tied to a loyalty member ID automatically — not just a table number — enabling individual spend tracking and personalised reward triggers. Automated campaign engines should engage guests who haven't visited in 30 days without manual CRM report runs. Tiered rewards recognise high-frequency regulars with escalating benefits, which matters in cafés where the same customers visit daily. Redemption must happen directly in the POS transaction flow, not on a separate screen that slows service.

Built-in POS loyalty modules work well for standalone NZ cafés with strong regular customer bases — the priority is recognising repeat customers quickly at point of sale without adding operational friction. Larger NZ multi-site restaurant groups benefit from a more robust CRM layer (SevenRooms or similar) that aggregates guest data across all locations and gives management a cross-site view of their most valuable customers. Eats365 POS includes native loyalty and member management functionality, and its open API supports connections to third-party CRM tools for operators who need advanced segmentation and campaign capabilities.

Layer 6: Inventory, Food Cost & Reporting Tools

Food cost pressure is among the most acute operational challenges facing NZ hospitality operators right now — driven by supply chain volatility, import costs, and the rising price of staple ingredients. A POS system that integrates with inventory management tools allows operators to see exactly where food cost is leaking, which menu items are underperforming on margin, and when stock levels require purchasing action.

What POS–Inventory Integration Should Deliver for NZ Operators

Inventory Platforms Worth Evaluating in NZ

• MarketMan: Cloud-based inventory and purchasing management with POS integration capability, used by NZ operators managing multi-supplier purchasing.

• Cooking the Books / MAPAL: Used in some NZ hospitality groups for recipe costing and waste management.

• Built-in POS inventory modules: Some POS systems — including Eats365 — include native inventory tracking modules that remove the need for a separate inventory platform for operators with simpler stock management needs.

NZ Operator Notes

For a standalone NZ café, a basic POS-integrated inventory module tracking top-cost ingredients (milk, coffee, avocado) is often sufficient and avoids the overhead of a dedicated inventory platform. For a NZ restaurant group running multiple kitchens, a dedicated inventory platform integrated with both the POS and Xero becomes essential — the cost variance data from multiple sites needs to be aggregated and acted on centrally.

Eats365's modular ecosystem includes inventory management capabilities and supports connections to third-party inventory platforms via its open API, giving NZ operators the choice to use the built-in module or connect a specialist tool depending on operational complexity.

How to Evaluate a NZ POS System's Integration Ecosystem

Before selecting a POS vendor, work through this operational checklist against each candidate platform. Answer each question with reference to the vendor's official integration documentation — not their sales pitch — and use your answers to score breadth and depth of support for your specific tech stack.

Use this checklist as your decision filter:

• [ ] Payment rails – eftpos NZ certified? Confirm the POS has eftpos NZ certification (Windcave, Tyro, or equivalent) and supports compliant surcharge configuration per Commerce Commission merchant surcharge guidance.
  
  Example check: Surcharge rates can be set globally and per-terminal, enforcing the rule that surcharge ≤ actual cost of payment acceptance.

   

• [ ] Xero integration – itemised with GST mapping? Verify that daily Xero exports show revenue broken into food/beverage/surcharge/tips as separate line items, each tagged with NZ 15% GST mapping.
  
  Example:Xero sees individual lines like 'Food Revenue – 15% GST' and 'Beverage Revenue – 15% GST', not one daily lump sum.

  Request sample daily export to verify structure.

   

• [ ] Uber Eats NZ & DoorDash NZ – direct order injection? Confirm the POS receives orders directly from the delivery platforms and pushes them live to the kitchen display system — not via middleware workaround.
  
  Example: Orders from Uber Eats NZ appear in POS KDS within 30 seconds of customer placing order; menu updates in POS sync to Uber platform within 5 minutes.

  Verify integration status with official Uber Eats NZ and DoorDash partner documentation.

   

• [ ] Reservation system compatibility – which platforms natively integrate? Check which NZ-active reservation systems (ResDiary, SevenRooms, OpenTable) the POS natively supports. Confirm whether integration is plug-and-play (native), requires a middleware partner, or needs custom API development.
  
  Example: ResDiary table status syncs automatically; SevenRooms requires a middleware partner; OpenTable requires custom API work.

  Request current partner integration list.

   

• [ ] Loyalty and CRM – built-in or third-party connectable? Determine whether the POS includes a built-in loyalty module, and whether its API supports connections to third-party CRM tools like Mr Yum or SevenRooms.
  Example: Built-in loyalty allows transaction-level member ID and real-time point accrual at POS; open API supports Mr Yum integration for advanced segmentation.

  Test member identification workflow at a demo terminal.

   

• [ ] Inventory and COGS – native module or third-party integration? Confirm the POS includes a native inventory module for recipe-level COGS tracking and automated stock deduction, or integrates with platforms like MarketMan. Verify that inventory cost data flows to Xero automatically.
  
  Example: Every POS order deducts recipe ingredients in real time; weekly variance reports show theoretical vs. actual stock; COGS accounts update in Xero daily.

  Request inventory sample report.

   

• [ ] Open API – documented and available? Request the vendor's API documentation. Confirm that custom integrations are supported for your specific tech stack (e.g., a local NZ supplier system or a custom reporting tool).
  
  Example: Vendor provides OpenAPI 3.0 documentation; sandbox environment available for testing; support team available for custom integration projects.

  Check for published API reference and integration partner marketplace.

   

Why Eats365 POS Is Built for the NZ Integration Stack

Eats365's open API and 100+ modular extensions allow NZ operators to connect the tools they already use — or plan to use — without being forced into a closed POS ecosystem that restricts integration options.

Whether you're a standalone Wellington café running Xero and Uber Eats, or an Auckland multi-site restaurant group needing centralised Xero reporting, delivery platform sync, ResDiary connectivity, and an inventory tool talking to your POS, Eats365's architecture supports that stack without requiring a separate middleware layer for every connection.

NZ hospitality operators can book a free Eats365 POS demo to see how the integration ecosystem maps to their specific tech stack — including a walkthrough of Xero sync, delivery platform order injection, and payment compliance configuration for the New Zealand market.