There is a moment in most Shopify projects where somebody says the word integrations, everyone in the room nods, and the word goes into the minutes without a definition attached to it. Six weeks later the store is close to launch and a question arrives that nobody can answer: when an order comes in, what happens in Xero, and who told it to happen?
A Shopify store is the visible front of a stack that includes freight, accounting, inventory, payments and marketing, and every one of those connections is a decision somebody has to own.
This is a map of what a New Zealand business actually needs, in the order it becomes necessary, with the tools that serve this market rather than the American ones the app store surfaces first.
The five categories
Almost every connection falls into one of five groups, and it helps to name them before naming products.
Payments set what it costs you to take money. Freight sets what shipping costs the customer against what it costs you to send, which on New Zealand rural addresses is a wider gap than most stores realise. Accounting decides whether your books reconcile without somebody doing detective work on a Tuesday. Inventory decides whether the number on the website is true, and marketing decides whether you can talk to the people who bought.
A store can launch with two of those and survive. It cannot scale on two.
Freight, the one New Zealand gets wrong
Freight is where the local specifics bite hardest, because rural delivery in this country is expensive and the boundaries are not intuitive.
Three tools cover most of the market. GoSweetSpot is free to use, connects across the New Zealand carrier network, and validates delivery addresses at checkout so rural and residential surcharges are charged rather than absorbed. Starshipit connects to more than twenty-five domestic and international carriers, offers live rates at checkout, and is the only one that manages fulfilment from inside the Shopify dashboard, on tiered pricing starting around $40 a month. NZ Post eShip is free, works only with NZ Post carriers, and does not currently offer live rates at checkout.
Domestic only and cost-sensitive, GoSweetSpot. If you are shipping to Australia or running several carriers across more than one market, Starshipit. Committed to NZ Post and pricing freight by hand, eShip.
What decides success is not the tool. It is whether your product weights and dimensions are accurate, because live rates are calculated from what the catalogue says a product weighs. A catalogue where half the SKUs carry a guessed default will produce confident, wrong numbers all day.
Accounting, and the payout problem
This is the integration most often done badly, and the failure is subtle enough that a business can run for two years without realising.
Shopify does not pay you per order. It pays you in batched payouts, net of fees, on a schedule. Your bank shows a single deposit of $8,412.66 covering forty-three orders, three refunds, and Shopify's processing fees deducted somewhere in the middle. Reconciling that against individual sales invoices is the detective work that eats a bookkeeper's Tuesday.
There are three approaches and they produce materially different outcomes.
Xero's own Shopify integration syncs sales, refunds and fees into Xero directly. It is free, it is quick to set up, and for a store with straightforward volume it is adequate.
A2X summarises Shopify transaction data and posts it as a journal entry per payout, with revenue, fees, taxes and returns broken out so the entry matches the bank deposit exactly. Reconciliation becomes one click. It is purpose-built for the payout problem and it is what most accountants ask for once volume is real.
Amaka occupies similar ground with a different interface and strong support, and is worth comparing if your accountant has a preference.
If your bank reconciliation currently takes hours rather than minutes, the integration is wrong and no amount of discipline downstream will fix it.
Get GST right at this layer too. Whether your Shopify tax settings, your accounting integration and your actual filing agree is a question worth answering before it is asked by somebody else.
Inventory, and when you actually need it
Most stores do not need an inventory system. Shopify handles stock across up to ten locations on a standard plan, which covers a shop, a warehouse and a few marketplaces without help.
You need a dedicated system when one of four things is true: you manufacture or assemble, so raw materials and finished goods need separate tracking. You sell wholesale alongside retail with different pricing and stock pools. You carry serialised or batch-tracked stock. Or you are running purchase orders and supplier lead times that Shopify has no concept of.
Three options dominate in New Zealand, and all three appear in the Xero marketplace, which is not a coincidence given how much of this market runs on Xero.
Cin7 Core originated in New Zealand and suits businesses with complex inventory or light manufacturing, particularly those already on Xero. Entry pricing sits around US$349 a month on the Standard plan.
Unleashed came out of Australia and has a broad following among SME manufacturers and wholesalers. Strong on production and supplier management.
Katana is the lighter option, with a free tier and a Core plan around US$299 a month with unlimited users, and covers Shopify, Xero and QuickBooks natively.
The mistake here is buying one early. An inventory system installed before the business needs it adds a synchronisation surface, a subscription and a second version of the truth, and it will introduce more errors than it prevents.
Payments, briefly
Shopify Payments handles most of it, and the number that matters is the surcharge on everything else. Processing through a third-party gateway adds 2% on the Basic plan, 1% on Grow, 0.6% on Advanced and 0.2% on Plus, on top of what your provider already charges. On $3M of online revenue at Advanced, that is $18,000 a year for the privilege of keeping your existing arrangement.
For stores with a physical counter, Shopify POS in New Zealand covers the in-person side and the Eftpos question that goes with it, which is its own integration problem entirely.
The order to do them in
Payments first, because they affect margin on every transaction and they are painful to change later.
Freight second, because inaccurate freight costs money from the first order and the fix is not difficult.
Accounting third, before volume makes the backlog painful. Doing this at launch is an afternoon. Doing it at eighteen months means someone reconciling a year and a half of payouts.
Inventory fourth, and only when the four triggers above are actually true.
Marketing last, because a customer list is worth building from day one but the sophistication can wait.
Who owns each connection
This is where the four o'clock phone call comes from.
Every integration involves at least three parties: Shopify, the other system, and whoever configured the link between them. When an order fails to sync, the question of who investigates should have been answered in writing months earlier.
Our own position is worth stating plainly, because it differs from how some studios present it. Skyrocket scopes, maps and manages integrations. We do not build the connections themselves, because the technical link sits with the platform vendor, the app developer or the existing system, and those parties maintain it properly in a way a web studio patching around the edges never will. What we own is the mapping: exactly how each chosen system behaves inside the site, what happens when a sync fails, and who picks up the phone.
Most businesses already know their accounting system and their freight partner before a project starts. The work is not choosing them. It is deciding precisely how they will function once live orders start flowing, which is why integration mapping belongs in the strategy phase rather than being discovered during the build. Complex Shopify integrations goes deeper on the ERP end of this.
What goes wrong
Apps accumulate. Each one solves a ticket, adds a subscription, adds load time, and adds a party to call. A store running fifteen apps is running fifteen dependencies, a cost we have set out in how too many Shopify apps cost your store revenue.
Two systems both think they own stock, and they disagree. That resolves into overselling on your best trading day.
And nobody tests the failure cases. What happens when the accounting system is down, when an address fails validation, when a refund is issued from the wrong end. Integrations are judged on what they do when something breaks rather than on the day they are installed.
When we migrated Advintage off Magento, the job carried more than 5,000 SKUs with layered discount and stock management, wholesale pricing and an ERP integration, and it went live with zero customer downtime. That came from mapping every one of those connections before anything was switched over.
Common questions
What integrations does a new Shopify store need at launch?
Payments, freight and accounting come first. Inventory and marketing can follow once the store is trading, and adding them early creates more surface area than value.
Do I need a developer for Shopify integrations?
For standard app connections, no. Shopify integration specialists in NZ earn their place on the mapping rather than the installing: deciding how systems interact, what happens when a sync fails, and how freight, stock and accounting stay consistent with each other.
What is the best Shopify accounting integration for New Zealand?
Xero's own integration is adequate at lower volume. A2X is the common answer once payouts are frequent, because it posts a journal per payout that matches the bank deposit exactly. Ask your accountant, who will have a firm view.
How much do Shopify integrations cost to run?
Freight can be free with GoSweetSpot or around $40 a month with Starshipit. Accounting sits between free and roughly $50 a month. Inventory is the expensive one at US$299 to US$349 a month, which is why the timing of that purchase matters.
Skyrocket builds Shopify websites for established New Zealand and Australian businesses and maps the integration stack that runs underneath them. If nobody can currently answer what happens in your accounting system when an order comes in, get in touch.
