- 1
60 minutes
We map how your business actually runs today, agree a go-live date, and walk you through the import wizards you will use next. Always take the CSV templates from inside your account rather than from an email or an old copy: Qoblex generates them fresh, so they carry whatever columns the current release expects. This is also where we ask the questions that size the rest of the program, so it is the session to raise anything unusual in.
Who to bring: Your project owner, and whoever is allowed to decide that a process will change.
- 2
Your work, no call
You download each template from its import wizard in Qoblex and fill it in: products, customers, suppliers, and opening stock as a stocktake. The switch guide in the support centre walks the whole sequence, and the project tracker on it is the checklist we work from together. We review what you send back and return a list of what will fail, so you fix it once rather than three times.
Who to bring: Whoever knows your product list well enough to say which of two similar SKUs is the real one.
- 3
60 minutes
Company settings, locations, units of measure, tax rates, product and variant structure, and the costing method you will run on. This is the session that is expensive to change later, which is why it happens before anything is imported.
Who to bring: Your project owner, plus anyone who owns how products are named and grouped.
- 4
45 minutes
We go through your completed templates before anything is imported and tell you exactly what will fail: duplicate SKUs, missing units of measure, invalid characters, opening stock that does not reconcile. When it is clean we give you the go-ahead and you run the import yourself from the wizard, with us on the call while you do it. Nothing moves forward until the stock figures are ones you recognize.
Who to bring: Whoever can confirm the opening stock is right.
- 5
60 minutes
You make the connections, not us: Xero, Shopify and the rest are authorized with your own login, and we never ask for credentials to a system we do not own. Connect each one with every sync option set to Do Not Sync, and we then go through the settings together so nothing posts anywhere until the mapping is agreed. On Full, the accounting side gets its own session instead of sharing this one.
Who to bring: Someone with admin access to each system. If accounting is in scope, bring your accountant or bookkeeper.
- 6
60 minutes
The whole order lifecycle against your own data rather than a demo set. Inbound: supplier terms, purchase orders, partial receipts, landed cost, and what happens when a shipment arrives short. Outbound: sale orders, allocation, backorders, picking and packing, shipments, and the point at which stock and the ledger both move.
Who to bring: The people who actually raise, receive, pick and ship — not only their manager.
- 7
60 minutes
A dry run of cutover day against a staging store, in the order it will actually happen: count and authorize opening stock, bring in open purchase orders and stock in transit, bring in open sale orders, then turn sync on. Whatever surprises us here is a thing that does not surprise us on the day. We finish with the readiness checklist, the cutover date confirmed, and an agreed list of what is frozen in the old system from that point.
Who to bring: Your project owner, and one person from each team that has been trained.
- 8
On call, not a booked session
Your specialist is available while you work through the runbook: stocktake, open purchase orders, open sale orders, sync on, then reconcile against your accounting system. The support centre has each of those steps written out, so the day is a rehearsed sequence rather than a call where we work it out together.
Who to bring: Whoever is on the floor on the day.
- 9
30 minutes
Two weeks after go-live, a review of anything that surprised you: what people are working around, what is being entered twice, and anything in the data that has drifted since cutover. Full gets a second one of these at around sixty days, which is when the problems that only show up over a full cycle have shown up.
Who to bring: Whoever is on the floor, not only their manager.
- 10
45 minutes
At your first month end, a walk through the close itself: reconciling stock on hand, checking what posted where, and the reports you will run every month from then on.
Who to bring: Finance, and whoever signs off the numbers.
- 11
Only if you need them
Included, and deliberately unallocated. Rollouts run over — every vendor we looked at quotes four to six weeks and none of them hits it every time — so rather than pretend otherwise, two sessions are already paid for and waiting. Use them for a re-import after a bad data day, a second pass at training for a team that did not get it first time, an integration that behaved differently to the rehearsal, or an extra week of hand-holding after go-live. Unused, they simply expire with the program.
Who to bring: Whoever needs them on the day.