The numbers disagree, and nobody knows whether the problem is a sale, a transfer, a return or a physical count.
First workflow from A$4,900 ex GST, with 12 months of support for the agreed implementation. Scope and pricing →
Treat transfers as a state change, not new stock. Preserve raw events. Reconcile by variant and location; authorised adjustments require reason and evidence.
Unrecorded walk-in sale; damage; wrong item shipped; count errors; missing receipts; in-transit goods.
Uncertain inputs go to an assigned owner with the source, reason and next decision. Failed writes are reconciled before retrying, so a recovered connection does not create a duplicate order, payment or stock movement.
Investigation minutes; unexplained units/value; repeat discrepancy rate; aged unresolved adjustments.
Sample representative work before the build, including difficult cases. Compare the same task mix after launch; include review, exception handling and system upkeep in the time used.
Map the first input, the final accepted result and who can approve it. Agree source systems, read/write access, rules, exception ownership and acceptance checks. Run representative normal, failure and recovery cases before expanding across teams.
Role-based access, separation of preparation and approval, versioned rules, an action history, duplicate protection, reconciliation, alerts and a named recovery owner. Private deployment or customer-controlled infrastructure can be scoped where needed. These are design requirements to validate, not an unsupported promise of perfect source data or regulatory compliance.
Specific answers to help you judge the fit, the information needed and the decisions your team keeps.
We align the product variant, location and cut-off time before comparing POS, warehouse or store balances. Sales, reservations, returns and transfers need compatible definitions. A supplier availability figure or stock currently travelling between sites should not be compared directly with local physical stock.
The investigation view can gather the relevant sales, transfers, returns, receipts and count records around a difference. It suggests an evidence-supported category and identifies missing events. Where the records do not explain the gap, the case remains unresolved for a count or operational review.
An investigation and a stock adjustment are separate steps. Agreed low-risk corrections may be eligible for a controlled path, but unexplained losses need authorised review. Record the reason, before-and-after quantity and source evidence, then verify that the intended system accepted the adjustment.
A transfer keeps one identity through dispatch, transit and receipt, so the same units are not added twice. Returns remain separate until their destination and condition are confirmed. Missing receipts, damaged returns and incomplete transfers become owned cases instead of silently changing the available balance.
Use a representative set of discrepancy cases and preserve the original evidence. Compare investigation time, unexplained units or value, repeat causes and aged adjustments. A faster report alone is insufficient; check whether staff can close cases and whether later counts support the recorded resolution.
Automate supplier stock updates across your POS and ecommerce store. Separate local stock, supplier availability and reservations before publishing a fulfilment promise.
Retail owner / operations managerWorkflow designSee pipeline, exceptions & controls →Update ecommerce prices from supplier price lists and promotion sheets. Check campaign dates, eligible variants and approved margin rules, then verify the live price and its expiry.
Merchandising / purchasing managerWorkflow designSee pipeline, exceptions & controls →Turn emailed customer purchase orders into validated SKU orders, stock allocations and warehouse instructions. Keep payment checks, partial shipments and dispatch status aligned.
Wholesale operations / warehouse leadWorkflow designSee pipeline, exceptions & controls →