From spreadsheets to a real 3PL WMS: a migration guide for Australian warehouses

Plenty of Australian third-party logistics operators are still run on a stack of spreadsheets, a shared inbox and a whiteboard. It works, right up until it doesn't. The day a single client adds 300 SKUs, or you sign a second site, or a customer asks for a live stock-on-hand feed, the cracks show fast.

This is a practical guide to moving from spreadsheets to a real 3PL warehouse management system in Australia: how to know you've outgrown the sheets, what a sensible migration actually looks like, and how to wire up activity-based billing, AU carriers and your finance system without a multi-month rebuild.

Signs your spreadsheet 3PL is breaking

Spreadsheets are brilliant for a single client and a few hundred orders a month. The problem is they don't enforce anything. Every quantity, every rate, every pick is only as accurate as the last person who typed it. Here's what that costs you as you scale.

• Pick and pack errors creep up. With no scan verification, the wrong SKU goes in the box and you wear the return, the re-ship and the angry client email.
• Billing leakage is the silent killer. Storage days, receipt lines, pick lines, special handling and freight recovery all get under-counted when someone is reconstructing a month of activity from memory and a movement log.
• No real-time client visibility. Your customers want to see their own stock-on-hand and order status. A weekly emailed spreadsheet is not a portal, and it makes you look small.
• Stocktake is a guess. Without perpetual inventory and cycle counting, your on-hand numbers drift, and you only find out during a painful full stocktake.
• Key-person risk. The whole operation lives in one analyst's head and one fragile workbook with 40 tabs and a broken VLOOKUP.
• You can't take on complex clients. Batch/lot tracking, expiry, serial numbers, kitting and multi-warehouse all break a spreadsheet model immediately.

If two or three of these sound familiar, you're not short of effort, you're short of a system. The good news is the move from spreadsheet to 3PL WMS in Australia is far less painful than it was even a few years ago.

What a real 3PL WMS gives you that a sheet never will

Before the roadmap, it's worth being clear about what you're actually buying. A 3PL-focused WMS does three things a spreadsheet structurally cannot.

• Multi-client separation. Every client's inventory, rate card, orders and reporting are isolated, so you can run twenty brands out of one building without cross-contaminating data.
• Directed, verified work. Scan-driven receiving, putaway, picking and despatch enforce accuracy instead of hoping for it. See /modules/order-management and /modules/inventory-management.
• Activity capture for billing. Every billable event (a receipt, a pick line, a storage day, a special pack) is logged as it happens, so your invoice builds itself.

That last point is the one that pays for the whole project, so we'll come back to it.

The migration roadmap: clients, SKUs, rate cards, integrations

A 3PL migration is not one big-bang switch. The operators who do it well break it into four data domains and stage them. Do them in this order.

1. Clients and contracts

Start with your client list, because everything else hangs off it. For each client, capture the legal entity, billing contact, contracted services and any SLAs. This becomes the top-level structure the WMS organises inventory and billing around.

• List every active client and the modules of service they actually use (storage only, pick-pack, returns, kitting).
• Decide who gets portal access and what they should see.
• Flag the clients with special requirements (batch/expiry, serial, dangerous goods, temperature) early, because they shape your SKU data.

2. SKUs and inventory

This is the heaviest lift and where spreadsheet data is usually dirtiest. Clean it before you import it, not after.

• Standardise SKU codes and descriptions per client; kill the duplicates and the free-text variants.
• Capture GTIN/barcode, unit of measure, carton and pallet quantities, and weight/dimensions for cartonisation and freight.
• Record current on-hand by location so you can reconcile against a physical count at go-live. See /glossary for GTIN, SSCC and ASN definitions.
• Decide your location/bin naming scheme now; retrofitting it later is miserable.

3. Rate cards

Your rate cards are the bridge between operations and revenue. Translate every line of your current billing spreadsheet into structured charges the WMS can apply automatically.

• Map each billable activity: inbound per receipt or per line, storage per pallet/shelf/cubic metre per period, outbound per order and per pick line, plus value-adds like labelling, kitting and returns processing.
• Capture freight recovery rules so carrier cost plus your margin flows onto the invoice.
• Note client-specific exceptions and minimums, because they're exactly what gets forgotten in a manual invoice.

4. Integrations

Last, connect the WMS to the systems either side of it: the sales channels feeding orders in, the carriers shipping orders out, and the finance system that gets paid.

• Ecommerce and marketplaces: Shopify, WooCommerce and BigCommerce stores, plus Amazon.com.au, eBay AU, Catch and The Iconic for clients who sell there.
• Carriers: see the AU carrier section below.
• Finance: Xero, MYOB or NetSuite, covered further down.

Activity-based billing: the single biggest payoff

Once your activity is captured on the floor, billing assembles itself: every receipt, pick line, storage day and value-add task is rated against the client's card automatically, so invoices go out on day one of the month and stop leaking the storage and pick lines a manual run forgets. That is the whole argument for moving off spreadsheets, and it is worth getting right.

Because it is the deciding factor for most operators, we have written it up in full separately: rate-card structure, tiered pricing, minimums, freight recovery and how leakage actually happens. Read the deep-dive at /blog/3pl-billing-software-au before you finalise your rate cards.

Wiring up Australian carriers

A 3PL lives and dies on despatch. The WMS needs to produce compliant labels and book consignments across whatever carrier mix your clients use, and recover the freight cost into billing.

• Lead with the honest status: NZ Couriers is the one live carrier API today. Every Australian carrier runs through the Shipping/Outbound module workflow, with the connection method (direct API, aggregator, or file-based) confirmed during scoping so you know exactly what go-live looks like.
• The AU carriers covered that way are Australia Post, StarTrack, Sendle, Toll, DHL, Aramex (formerly Fastway) and CouriersPlease, plus the Shippit aggregator for clients who want carrier choice at the point of despatch.
• Cartonisation uses the SKU dimensions you captured during migration to pick the right box and feed accurate freight to the carrier.
• For grocery and big-box clients, the system supports GS1-128 and SSCC pallet labels and ASN/Despatch Advice so you can meet retailer compliance. See /modules/shipping-outbound.

Be wary of any vendor who tells you every carrier is "live" out of the box. Honest scoping up front beats a surprise integration bill after you've signed.

Xero and MYOB sync (keep your finance system)

Here's the part that derails a lot of WMS projects: the assumption that a new operations system means migrating your ledger. It doesn't, and it shouldn't. The OpsUI model is to keep your finance system and add the WMS as the operations layer on top.

• Bidirectional NetSuite sync is live in production today.
• Bidirectional Xero and MYOB sync is wired during rollout via the /modules/finance-accounting module, so your activity-based invoices flow into the ledger you already run.
• No ledger migration means a dramatically smaller, lower-risk project, and your accountant keeps the system they know.

See /integrations/xero and /integrations/myob for how the sync is set up, or /integrations/netsuite if you're on NetSuite.

Your go-live checklist

When you're ready to switch, run this sequence. The goal is a clean cutover with a verified opening stock position and no billing gap.

• Freeze the spreadsheet: pick a cutover date and stop new entries in the old system.
• Reconcile inventory: run a full count (or targeted cycle counts via /modules/cycle-counting) and load verified opening on-hand.
• Validate rate cards: run a parallel invoice for one prior period and check the WMS figure against your manual number.
• Test the carrier workflow: book and label a real consignment per carrier before you depend on it.
• Confirm finance sync: push a test invoice through to Xero, MYOB or NetSuite and check it lands correctly.
• Train on the floor: scan-driven receiving and picking are quick to learn but need a hands-on run-through.
• Switch on client portals: give your customers live stock and order visibility from day one; it's an immediate selling point.
• Keep the spreadsheet read-only for one billing cycle as a safety net, then retire it.

How OpsUI fits

A spreadsheet-to-WMS migration is exactly the jump OpsUI is designed for: you stage the move client by client instead of betting the operation on a big-bang cutover. You buy the modules you need a la carte rather than a monolithic suite, so most 3PLs start with order management, inventory, receiving and shipping, then add cycle counting, returns and a CRM as they grow.

• Flat modular pricing from A$399/module/mo — full breakdown at /pricing. The point is your bill scales with the modules you switch on, not with every casual you put on the floor.
• Keep your ledger: add OpsUI as the operations layer over Xero, MYOB or NetSuite instead of migrating finance.
• AU carrier integrations are wired during rollout (NZ Couriers is the one live API today); see /integrations for the current state and what go-live involves.
• Purpose-built for multi-client 3PL: see /solutions/3pl for the full picture, and /compare/opsui-vs-cartoncloud if you're weighing alternatives.

If you're outgrowing the spreadsheets, the fastest way to see whether OpsUI fits your operation is to walk through your own clients and rate cards with us. Book a demo at /book-demo and we'll map your migration before you commit to anything.