From Xero + spreadsheets to Xero + OpsUI: a NZ 3PL rollout
Most NZ 3PLs run on Xero + Excel + email.
Six weeks later, the spreadsheets are gone and Xero is untouched.
Most NZ 3PLs run on Xero + Excel + email.
Six weeks later, the spreadsheets are gone and Xero is untouched.
Here is the actual sequence we walk customers through.
The starting state
Pretty common shape for an NZ 3PL doing NZ$5–20M of throughput:
- Xero is the accounting system. Invoices, bills, GST, payroll all live there.
- Stock-on-hand lives in a shared Google Sheet that gets updated by the warehouse manager once a day.
- Picking happens off a printed pack list. The team marks lines as they go.
- Couriers are booked manually on the courier portal, one parcel at a time.
- Customers email orders. Someone types them into the spreadsheet.
- Once a week, someone tallies up what shipped and raises invoices in Xero.
It works. It is also fragile. Pick errors cost margin, the spreadsheet drifts from reality, and the team grows by adding people, not by adding leverage.
The ask
When operators ring us, the brief is usually: “Keep Xero. Replace the spreadsheets. Stop the pick errors. Do not give me a six-month ERP rollout.”
Fair. Here is how it actually runs.
Week 1: Scope and spreadsheet audit
We walk the existing operation. Watch a picker. Watch a packer. Read the spreadsheet.
Specifically:
- How many SKUs, how many locations, how many active customers
- Which carriers, which services, which dispatch cadence
- Which fields are actually used in the spreadsheet (most are not)
- Which Xero contacts and items are clean enough to import as-is
Output is a scope doc with the module set: Orders, Inventory, Receiving, Picking, Packing, Dispatch. Plus the NZ Couriers connector. Plus the Xero connector for accounting flow-through.
Week 2: Data migration
We pull customer and item data from Xero via the Xero API. The spreadsheet history is reconciled against it. Anything that exists in the spreadsheet but not in Xero gets reviewed, not auto-loaded.
Stock-on-hand is the truth-day exercise. We pick a date, the warehouse does a count, the count becomes the opening balance in OpsUI. Xero gets a one-off journal so the books match.
Locations get mapped (main DC, satellite store, returns area, hold area) with their own bin sequences.
Week 3: Couriers and Xero wired
NZ Couriers API connection goes live in the test environment. Service tiers, rate cards, label formats configured.
The Xero connector is wired against your tenant. Direction one: invoices created on dispatch in OpsUI flow to Xero. Direction two: payment events in Xero update order status in OpsUI. Master data (contacts, items) keeps syncing both ways.
At this point, nothing is live for customers yet. It is all running in parallel.
Week 4: Train pickers and packers
Pickers, packers, and dispatch get half-day sessions with the actual hardware they will be using.
The Bluetooth scanner pairs to a phone running the OpsUI picking screen. Pickers walk real pick paths against real orders. Packers print real labels against real parcels.
Issues that come up at this stage are the most valuable ones. They would have hit you on go-live week. Better to catch them now.
Week 5: Parallel run
For a week, the spreadsheet and OpsUI run side by side. Every order gets entered into both. Every shipment gets recorded in both. Stock movements happen in both.
The two diverge in detail at the line level (different exception handling) but not in totals. Both invoices flow to Xero: the OpsUI ones are flagged as live, the spreadsheet ones are the official record until cut-over.
By Friday of week 5, the team has confidence the OpsUI version is the cleaner picture.
Week 6: Cut over
Monday morning, the spreadsheet stops being the system of record. OpsUI takes over.
Xero is untouched. The accountant did not have to do anything different. GST returns run as usual. Invoices flow in. Payments reconcile.
The warehouse manager is on-call from us for the first two weeks. Most calls are about edge-case orders (returns, holds, partial dispatch). The actual flow runs.
By month two, the team forgets the spreadsheet existed.
What this gets you
Concretely:
- Pick errors drop because the picker is scanning, not reading
- Stock-on-hand is real-time, not yesterday’s update
- Couriers are booked automatically against orders, not retyped
- Invoices land in Xero on dispatch, not on Friday
- The accountant sees the same numbers they have always seen, just sooner and cleaner
Six weeks. Xero stays. Spreadsheets go. The warehouse runs.
Frequently asked
Six weeks sounds short. Is that real, or is that the brochure number?
It is the real cadence for a typical NZ 3PL of 5–10 staff with Xero already in place and a relatively clean spreadsheet to migrate. Bigger operations or messier data take longer. We will tell you that in the scoping call rather than slow-roll the timeline. The constraint is usually data quality and team availability, not the software.
What happens to the historical data in the spreadsheet?
It stays accessible. We do not delete it. The opening balance in OpsUI is the warehouse count from the truth-day exercise; historical movements live in the original spreadsheet for reference. If you want a longer history pulled into OpsUI, that is doable but usually not worth it. Reporting from a clean cut date is cleaner than reporting from messy historical data.
Does the accountant need to do anything different in Xero during the rollout?
No. The accountant continues to work in Xero exactly as before. The only one-off event is the opening-balance journal on truth day, which we prepare for them to review and approve. After cut-over, invoices and payments flow to Xero automatically via the connector.
What if our spreadsheet is a disaster and we cannot get clean data out of it?
We have rolled out customers whose source data was, frankly, an audit nightmare. The rollout still works. It just means more time on the truth-day exercise and a stricter cut-over discipline. The trade-off is honest: messier starting data means more manual reconciliation in week 2, but it does not block the rollout.
Can we run only part of OpsUI, or do we have to do the whole warehouse stack at once?
Modular. You can start with just Orders + Inventory if that is the bottleneck, and add Picking, Packing, Dispatch, and Receiving as separate modules later. Each module is priced individually on the pricing page. The Xero connector ships with the rollout regardless of which modules you start with.
See how OpsUI approaches this differently.
No hidden fees. No six-month implementations. Just warehouse software that works.
Book a Consultation