The store already takes orders. Xero already holds the invoices. The gap is the hand-off — contacts, invoices, payments, and which system is allowed to post. We will tell you what to connect, and what to leave alone.
Australian ecommerce team. We look at the store and the Xero organisation before anyone talks about a connector.
01
What you have
02
What is safe to keep
03
Connect or leave
The store still takes orders. Xero still does the books. That is why the two have been left talking through spreadsheets, or through a plugin nobody wants to touch.
Xero is cloud accounting — invoices, contacts, bank, payroll, connected apps. It was founded in Wellington in 2006, is NZ-incorporated, and listed on the ASX. Its FY24 annual report claims 4.2 million global subscribers across Australia, the UK, the US and more than 180 other countries. That is Xero’s global figure, not an Australian store count, and we will not dress it up as one.
You might recognise one of these:
You do not need a new storefront, or a rebuild pitch. You need a clear read on the Xero organisation you already have, and the store that has to talk to it.
Xero is a real accounting product with a public Accounting API. The stall is rarely “Xero has no API”. It is the gap between a working store and a Xero org that already has rules, apps, and a chart of accounts.
The Accounting API is REST over HTTPS (https://api.xero.com/api.xro/2.0/). Auth is OAuth 2.0 — client id and secret. There is no basic API-key auth. Custom Connections (client-credentials) are available for AU, NZ, UK and US organisations. Apps created on or after 2 March 2026 use granular scopes. Older apps must migrate by 13 September 2027. A connector that still assumes the old scope model will fail on a new app, and will have a deadline on an old one.
Ecommerce jobs that belong in Xero are invoices, credit notes, contacts, items as accounting items, payments, and optional repeating invoices. Live warehouse quantity usually lives in Cin7, Unleashed, or an ERP. Xero taking financials while another system holds stock is a normal AU/NZ pattern — Unleashed documents its own Xero integration on its site; that is Unleashed’s product, not ours. Pushing “stock on hand” into Xero as if it were a WMS is how you get a ledger that lies.
If Cin7, Unleashed, or Peach already syncs sales into Xero, the store must not post the same invoice again. The first design question is who is allowed to create the Xero Invoice. Get that wrong and the BAS is the thing that breaks, not the plugin.
Contacts, Items, Invoices, Payments, Credit Notes and Purchase Orders are the entities that matter. Mapping a SKU to a Xero Item, a guest checkout to a Contact, and a refund to a Credit Note is the work. A generic “Xero plugin” that only dumps a sales invoice and ignores credit notes, payments, or tax codes is how these jobs come back six months later.
None of that makes the store or the Xero file worthless. It does mean “turn on the Xero app on Monday” is usually the wrong first move.
We start with the store and the Xero organisation, not with a connector name.
Store platform (nopCommerce, AbleCommerce, Shopify, or another CMS), how orders and refunds work today, which Xero organisation and which apps already have access, and whether inventory or ERP already posts invoices. We will tell you who should own the Invoice, and who should not.
There are three honest outcomes. We recommend one, not all three.
Contacts and items first, then invoices, then payments and credit notes. Staging against a Xero demo or a spare org beats a Friday post into the live file. Unused Xero apps and dead plugins do not come across.
Source, the Xero app and scope list, and a short record of what posts where. Someone else should be able to see why an invoice appeared.
We will not tell you Xero is a warehouse. We will not tell you every store needs a first-party Xero plugin. If you already know you want a Xero-certified app-store product and nothing custom, that marketplace may be a better fit. If you want an honest fork in the road, talk to us.
A store URL and which Xero organisation is enough to start.
The first call is 30 minutes. You leave with a recommendation you can take to a manager, not a connector estimate pulled from thin air.
Windsor Truck Bits is a published Australian nopCommerce store on the Peach inventory API, with Peach syncing accounting to Xero. Real-time stock and pricing sat in Peach; online orders created API invoices through that path. That is Peach-mediated Xero, not a first-party nopCommerce↔Xero connector we have published, and not a reason to assume every store should go through Peach. A direct Xero connection still starts with its own assessment. We will not pretend we have shipped a named standalone Xero plugin for every platform.
CoSource is a Sydney software firm and a nopCommerce Gold Partner. Ecommerce work includes custom development and CRM & ERP integration on nopCommerce, AbleCommerce, and Shopify. That is a capability, not a Xero case study.
Thirty minutes. Bring a store URL and which Xero organisation. We will tell you whether to connect, fix the connector, or leave Xero posting to the system that already owns it.
Book a free 30-minute discovery call