Process flows
Current and future state for every area, reviewed and signed off by your team.
Implementation
How DOSS gets you live
One DOSS team takes you from signed contract to running in production. We learn how you work today, design how you will work in DOSS, build and test it with your team, and stay with you after go-live.
How every implementation runs
Master data comes first
Products, suppliers, and customers are set up and migrated before anything else, because every workflow depends on them.
Built on your real numbers
We configure the actual values, like approval thresholds and the named approvers in order, not just the shape of a process.
Tested before you see it
Our team tests every build first. Then your team runs its own processes on it and tries to break it.
One team, start to finish
The people who run your discovery stay with you through go-live, and support never takes over while build work is still open.
The path to go-live
Seven phases, each with a clear exit before the next one starts.
- 01
Kickoff
We meet your team, open a shared channel, and walk through the plan, the data we need, and system access.
- 02
Discovery
Six working sessions on how you run today: master data, procurement and inbound, inventory, orders, finance and accounting, then a closing session on reporting and access.
- 03
Design
We map current and future process flows area by area. You choose between options, and we finish the design workbooks together.
- 04
Build and test
We build in loops, master data first. Each loop is tested by our team, then accepted by yours, before the next one starts.
- 05
Train
Training lives inside your own DOSS instance: general training, your own processes, and troubleshooting in one searchable hub. Train a champion or each team by function.
- 06
Go-live
We confirm the date a month out, follow the cutover plan on the day, and introduce your customer success manager and support engineer before launch.
- 07
Hypercare
For at least two weeks after launch, a support engineer triages issues daily and your implementation lead stays on hand. Then Customer Success takes over.
Accepted in loops, not all at once
Each area moves through the same loop: built, tested by DOSS, accepted by your team, then added to your training hub. Master data comes first, then orders, procurement, inventory, finance, and reporting, and the order can change when getting one area live early matters more to you.
What you'll have along the way
Design workbooks
Every configuration decision written down, from approval thresholds to lot rules.
Document mockups
Purchase orders, packing slips, and invoices exactly as they will go out.
Cutover plan
A source-of-truth matrix and a step-by-step plan for go-live day.
Training hub
General DOSS training, your process track, and troubleshooting answers in one place.
Launch tracker
Priorities, the bug log, and fast follows in one view your team shares with ours.
See how your implementation would run
Bring your SKUs, channels, and 3PLs, and we'll walk you through the plan.
Frequently asked questions
It depends on the modules and systems in scope. Before you sign, we agree the scope line by line and set the plan in your statement of work, and we confirm your go-live date a month ahead.
An owner for each area in discovery, such as buying, receiving, inventory, orders, and finance. Time to review process flows and workbooks. And your team running acceptance tests. We ask for your master data at least five days before discovery starts.
An implementation lead runs your project from kickoff through hypercare. You meet your customer success manager early, and a support engineer joins during testing and becomes your first line of support after launch.
At least two weeks of hypercare, with daily issue triage and your implementation lead still on hand. Then your customer success manager becomes your main contact, with support through the portal and a regular check-in.
No. DOSS posts to the GL you already use, including QuickBooks Online, Xero, and NetSuite.