🚀 Cognit is live — our all-in-one ERP you run your whole company on. Take a look →
← All insights

Xero integration for NZ food distributors and wholesalers: what actually syncs

18 June 2026 · 7 min read · Zeabyte

Xero is the most widely used accounting platform among New Zealand businesses, and food distributors and wholesalers are no exception. But accounting is only one layer of what a food distributor runs. B2B ordering, customer pricing, inventory, picking, despatch — none of that lives in Xero. When order volume or customer count grows, distributors need Xero connected to the systems that handle the rest.

This post explains how Xero integration works in practice for NZ food distributors and wholesalers: what data syncs, how the Xero API handles the technical side, and where the edge cases bite.

Why food distributors need Xero integration

Xero was built for accounting. It handles invoicing, accounts receivable, bank reconciliation, GST returns and financial reporting very well. What it doesn't do at distribution scale is:

  • Per-customer pricing — Xero can store a contact's default account code but has no native price-book system for complex, customer-specific pricing across hundreds of SKUs.
  • Real-time stock visibility — Xero's tracked inventory works for simple catalogues but breaks down when you have multiple locations, catch-weight products, or batch/lot requirements.
  • High-volume B2B ordering — a trade portal where accounts log in, browse their prices and place orders at any hour is outside Xero's scope entirely.

The pattern that works for NZ distributors: keep Xero for the accounts, and connect it — in real time — to an ordering portal, an inventory layer and your warehouse.

What syncs between Xero and your ordering platform

Customers ↔ Xero contacts

Every customer account in your trade portal maps to a Xero contact. When a new account is approved, it's created in Xero — with the correct credit terms, account codes and tax treatment. If a contact is updated in either system, the integration keeps them aligned so your books always match your portal.

Orders → Xero invoices

When a trade customer places an order and it's confirmed or despatched, the integration writes it to Xero as a sales invoice — against the right contact, with the correct line items, tax codes (standard-rated, zero-rated for exports) and due date. No re-keying, no transcription errors.

Payments ← Xero

As invoices are paid — by direct debit, bank transfer or credit card — the payment records in Xero and the portal updates the account balance. Your team can extend or hold credit based on live AR data rather than checking Xero manually before each order.

Products and pricing

This is where the integration design matters most. Xero holds items, but NZ food distributors typically have complex pricing: quantity breaks, customer-group rates, promotional pricing per SKU or category. The ordering platform is usually the system of record for this — it holds the price books and shows each customer their correct price — while Xero receives the final invoiced price as a line item. Pricing logic runs in your platform, not inside Xero, which is where it belongs for anything beyond simple retail pricing.

Inventory

For simpler catalogues, Xero's tracked inventory can feed stock-on-hand to the ordering portal. At distribution scale — multiple warehouse locations, batch and lot tracking, date-controlled products — a dedicated inventory layer manages stock and posts the financial entries (cost of goods sold, stock adjustments, landed costs) to Xero automatically. The accounting stays clean without Xero having to understand your warehouse operations in detail.

How the Xero API works in practice

Xero provides a well-documented REST API with OAuth 2.0 authentication, supporting contacts, invoices, payments, credit notes, accounts, tax rates and tracked inventory. A real-time integration typically runs as a persistent service:

  1. When an order is confirmed in the portal, the service calls the Xero API to create or update an invoice.
  2. Xero webhooks notify the service when a payment is received, so AR balances stay current without constant polling.
  3. A reconciliation job runs daily to catch any discrepancy — duplicate checks, failed writes — and alerts the team if anything drifted out of step.

Two things deserve attention in production. First, Xero's API rate limits are strict at higher volumes (60 calls per minute per tenant on the standard tier), so a well-designed integration batches and throttles rather than firing a call on every individual event. Second, multi-currency needs care when your customer base spans NZ and Australia — the integration must pass the correct currency code and exchange rate on each transaction, and your Xero plan must have multi-currency enabled.

What good looks like — and what to avoid

A well-integrated Xero connection means your accounts team never logs into the ordering portal to check what happened, and your operations team never logs into Xero to check if something got invoiced. Each system does its job and the data flows automatically.

The common failure modes: treating the integration as an afterthought (built last, tested least), batch syncing nightly when real-time is possible, or skipping monitoring so the first sign of a broken sync is a customer with a wrong balance. In production, an integration without alerting is an integration waiting to cause a problem.

When Xero integration is the right call — and when to go further

If your team is happy with Xero for the books, there is often no reason to change it. Connecting it to a proper trade ordering and inventory system is straightforward and leaves your accountant working in the tool they know. That is the right call for most growing NZ distributors — it removes the re-keying, eliminates errors, and lets the accounts run clean while the business focuses on distribution operations.

The calculus shifts when per-user fees climb steeply with headcount, when financial workflows no longer fit Xero's model, or when the ongoing cost of maintaining several bolted-on integrations tips past the cost of a single owned platform. At that point, bringing accounting into a custom ERP is worth the conversation — but that's a separate question from whether Xero integration is the right starting point.

Whether you want to integrate Xero tightly with an existing ordering platform, or build the whole stack — ordering, inventory, accounting — on one owned system, the Zeabyte platform supports both paths. Xero is one of 25+ systems we connect in production. If you want to see exactly how it would work for your setup, talk to us.

Talk to the team that does this every day

30 minutes, no obligation — we'll look at your systems and tell you exactly what's possible.

Talk to us