Including the questions where our answer is “not today”. You should not have to book a call to find these out — but when you do call, you will find we answer the same way in person.
Configurable per warehouse. One live site allocates what is available and flags the shortfall as a visible exception; another holds the line until stock is resolved.
No. Allocated stock is held against its order until the allocation resolves.
Yes, where that rule is enabled: expiry-first allocation can look across a product’s alternative barcodes. This runs today in one live warehouse.
No. Quantities can be adjusted after an order is confirmed and released — used hundreds of thousands of times across both live countries.
The order stops. The exception is held and stays visible until a responsible person resolves it.
Per warehouse: one live site rejects any overage, another accepts a defined tolerance.
Honestly: offline task execution is not currently supported. The handheld needs a live connection. We treat coverage as a site-survey problem and walk the building with you before go-live.
Every scan is confirmed centrally against the live server. There is no stale local picture to conflict.
A visible record with the failure reason in plain language, and for supported message types a replay action an operator can use — not a silent gap discovered three weeks later.
Your ERP stays the system of record. The warehouse enforces its operating rules on top and reports stock and dispatch reality back.
No. Corrections are recorded operations with a reason, carrying before-and-after quantities, the reference and the operator.
No — and we say so on the homepage. If your ERP’s warehouse module covers your rules, stay with it. If you need one template rolled out identically across many countries with robotics ecosystems, a global platform may fit better. Talk to us when your rules are more complex than your ERP can express and they differ by site, customer or product.
Yes. Cut-offs, rotation strategy, scan mandates, short-pick behaviour, case handling and more are configured per warehouse — on the same release and the same database.
We quote after walking your building, not before. Committed in advance: a signed-off process map, a test environment on your own data, validation by your own team on real handhelds, and our people on your floor at go-live.
No. Start with one warehouse and one peak period, judge us on how the floor runs, and decide about the rest afterwards.
Ask it in the demo — and bring your hardest scenario while you are at it. A warehouse specialist answers within one working day.