WAREHOUSES
Your count is not wrong.
It is just in four systems.
Two buildings, a client running their own WMS, a dropship vendor and a spreadsheet that arrives by email on Tuesdays. Every one of them is telling the truth about its own corner. None of them can tell you what you have.
Scan the zone. See what is in it.
Inventory View starts empty on purpose. Scan a zone name and it resolves what is physically in that location, whichever system owns the count.
The live screen, waiting.
Zone UNJ-A-14-C
Union NJ · rack A, level 14, position C · last counted 26 Jul
Items
4
| SKU | UPC | On hand | ATS | Count source |
|---|---|---|---|---|
| NL-TEE-BLK-M | 889432104772 | 312 | 288 | OMNI |
| NL-TEE-WHT-L | 889432104789 | 140 | 140 | OMNI |
| HG-MUG-12OZ | 712398445021 | 864 | 720 | Camelot WMS |
| CB-CANDLE-VN | 604215889013 | 96 | 60 | Camelot WMS |
One zone. Two count sources. One list.
The count can be yours, theirs, or ours
This is the part that decides whether an inventory layer is worth having. OMNI does not need to own the count to be useful, and it says on every row where the number came from.
Ours
Run OMNI inventory directly. Scan receiving, put away to a zone, move, count. The record is created where the work happens rather than typed in afterwards.
Theirs
Your client runs their own WMS and has no intention of stopping. Aggregator ingests their feed, whether that is an API, an FTP drop, a portal or a spreadsheet in an inbox.
Both, on the same screen
Mixed sources in one zone is the normal case, not the exception. The count source column means nobody has to remember which building trusts which system.
On hand is not available to sell
Three of the four rows above show a lower ATS than on hand, and that gap is where oversells come from. ATS subtracts what is already committed, so the number you publish is the number you can actually ship.
312 on hand, 288 available
Twenty four units are spoken for. Publishing 312 sells stock that is already leaving the building, and the apology lands on your client rather than on the channel.
864 on hand, 720 available
A vendor owned count with commitments against it. Set a floor and Balancer will publish zero rather than risk the last few units, which is usually cheaper than a cancelled order.
Built for the floor, not the office
Inventory Management is four working screens, and the tools that surround them exist because someone on a warehouse floor needed them at seven in the morning.
Inventory View
Scan a zone, see what is there, drill into any SKU.
Inventory Move
Relocate stock between zones with the movement recorded as it happens.
Picking
Work the pick, with the order line and the location on the same screen.
Inventory Creator
Bring new stock into the system without waiting on a back office import.
Pick Ticket Generator
Paperwork for the floor, generated from the live order line.
Inventory Label Generator
Location and stock labels printed from the same record.
UPC Label Generator
UPC labels off the catalog, so the barcode matches the item record.
Bulk Mark Ship
Close out a batch in one action instead of one order at a time.
All eight are live screens in OMNI today.
Situations this gets built for
Not testimonials. These are shapes of operation we work in, with names removed.
Four WMS platforms, twenty two sites
A prep and fulfillment operator where four systems disagreed and most of the resulting exception volume turned out to be noise rather than real problems.
The counts were not the issue. Reconciling them was.
Two million square feet, three regions
Freight landing on one coast and shipping from another, with stock moving between buildings mid order.
Port to door visibility, without replacing what ran the buildings.
Client keeps their own WMS
An operator whose largest account runs proprietary systems and will not migrate, ever.
Addition rather than migration was the only workable answer.
Start with your messiest zone
Not the tidy one. Pick the location your team argues about, the one where the count and the shelf part company most often. Connect what already runs it, scan it, and compare what comes back against what your current system says. If it does not hold up, nothing changed and nobody outside your building saw it.