Skip to content
Back to rollout overview
Rollout · §02 Configure

The middle weeks of the rollout. We do the data migration and the integration wiring so your team walks into a system that already knows their warehouse, their customers, and their carriers.

2-3 weeks

Data we migrate in

We pull data from the systems you already run today, clean it up, and load it into the agreed module set:

  • SKUs / items, including supplier + cost data where available
  • Locations, bins, and any zone configurations from a previous WMS or spreadsheet
  • Customers and contact records (from your CRM, Xero, NetSuite, or wherever they live)
  • Vendor / supplier records
  • Open POs and open sales orders, so cut-over does not lose work in flight
  • A short window of historical orders for trend / dashboard context (usually 12 months)

Integrations we wire

Each integration is wired against your actual production tenant, not a sandbox:

  • NZ Couriers (live in production for NZ rollouts today)
  • Australian carriers, configured against your existing carrier accounts
  • Xero or MYOB accounting connector, built per rollout, bidirectional sync of invoices / customers / items
  • NetSuite extension, bidirectional event-driven sync, see /integrations for the full record
  • Existing internal APIs / webhooks if the operation has them

Roles & permissions

We map roles to the actual humans on your team: pickers, packers, dispatch supervisors, ops manager, finance. Each role only sees the modules and the workflows they need. Pickers do not see invoicing, finance does not see the picking floor.

This part is opinionated. We have run enough warehouses to have a default role model that works, and we propose it to you rather than asking you to design one from scratch.

Stage 02 · Common questions

What operators actually ask about this stage

How clean does our existing data need to be?

+
Cleaner is faster, but we have done rollouts where the source data was, frankly, an audit nightmare. The configure stage just stretches longer in that case, extra reconciliation work on the truth-day exercise. The rollout itself does not block on bad data.

Can we keep running the old system in parallel during this stage?

+
Yes, and we recommend it. Configure happens against the new OpsUI instance while your old system keeps running production. The cut-over only happens in stage 4 (Go live), after week 5's parallel run. Configure is a no-business-impact stage.

What if a connector we need is not built yet (e.g. MYOB)?

+
It gets built during your rollout. That is the "Built on rollout" tier on /integrations. The Xero and MYOB connectors are not shipping as off-the-shelf marketplace apps yet; they are wired against your specific tenant during this stage. Same bidirectional event-driven shape as the NetSuite connector.
Previous stage · §01
Scope
Discovery & module selection
Next stage · §03
Train
Hands-on team training

Ready to start your rollout?

The scoping call is the first stage. Bring one of your own orders. In 30 minutes we walk through claim → pick → pack → ship on live OpsUI.

Book a consultationSee all four stages