Implementation

Four stages, each with something you can hold.

Every warehouse is different, so we will not quote you a number of days before we have seen yours. What we commit to is this sequence — and to being on your floor rather than only in your meeting room.

Everything on this page describes behaviour running in live warehouses today. Where a capability is optional or per-warehouse, it says so.
The sequence

From walking your floor to running it.

01

A process map you sign off

We walk the building — goods in, locations, rotation rules, exceptions, and what actually happens on a peak day. You receive a written description of your own process and approve it before anything is configured.

02

A configured, integrated test environment

Your warehouse structure, locations, products, users and operating rules, connected to your ERP and running on your own data — in a test environment you can log into.

03

Operational validation by your own team

Your supervisors and operators run real scenarios on real handhelds: your SKUs, your barcodes, your awkward cases. Nothing reaches production until the people who will use it have signed it off.

04

Go-live and continuous improvement

Our people are in the warehouse for the first operating days and through the first peak. After that, changes keep coming — tracked, tested and documented.

You do not have to commit to everything at once. Start with one warehouse and one peak period, judge us on how the floor runs during it, and decide about the rest afterwards.

Straight answers

What decision-makers ask about go-live.

How long does implementation take?

We will tell you after we have walked your building — not before. What we commit to in advance is the sequence: a signed-off process map, a test environment on your data, validation by your own team, and our people on your floor at go-live.

What if it does not work for us?

Start with one warehouse and one peak period. Judge us on how the floor runs during it, and decide about the rest afterwards. We would rather earn the second warehouse than contract it.

What happens after go-live?

Changes keep coming — as tracked tickets, tested in your test environment, documented in release notes you can read. Your process will change; the system is built to change with it.

Start with the walk.

The first step costs you a morning: we walk your building and hand you a written map of your own process. Decide everything else after you have read it.

Book an operational demo →