Your stock already knows how much. This knows where — down to the zone, aisle or bin — so nothing is hunted for again and every move is recorded rather than remembered. And the month's storage invoice builds itself from what actually happened.
B2-3 has no capacity set, so it is shown as not measured — never as empty, and never counted toward the free space above.
Most warehouse software tracks quantities and leaves the invoice to a spreadsheet somebody rebuilds every month. BackOffice measures occupancy every night, prices it against the rate card you agreed with that customer, and assembles the document.
Reserved space, space actually occupied, goods in and out, stickering and strapping — each line says which rate priced it, so a year later the document can still explain its own numbers.
Preview the whole run before you commit it. Nothing is written until you say so, and re-running a closed period can't invoice anyone twice.
Warehouse software is full of confident numbers built on missing data. Every figure here would rather say "unknown, and here's why" than quietly round to zero — because a zero you trust is worse than a blank you can act on.
Shown as empty — go ahead, promise the space.
Shown as not measured, and excluded from "where will this fit". You can't promise room that may not exist.
Invoiced as if the month were complete.
The shortfall is printed on the customer's own copy, and the operator sees it before sending.
"About 12,000." Built on three days of history.
What's contractually certain, separately from what depends on usage — and no forecast at all until there's enough history to earn one.
Averaged over what's still on the shelf — so the fast movers, already gone, never count.
Measured at departure, where both ends of the interval are known. The median leads, because one forgotten pallet ruins a mean.
Every pallet can carry an owner. A retail chain leaves it empty and gets zones, capacity and put-away over its own inventory. A 3PL or bonded warehouse sets it, and the same zones now hold six customers' goods with each one's stock, contract and invoice kept apart.
Customer-held goods are not your asset. They're bailment, and the module reports exactly how much of your inventory valuation isn't yours to count — a figure that can otherwise dwarf a 3PL's real balance sheet.
Contracts carry the terms that matter: space-only or full custody, how deep you count, whether FIFO is an obligation rather than a preference.
One module for the whole cycle — not three tools taped together.
Model buildings, zones, racks and bins to whatever depth you actually work at, each with real capacity in your own unit.
See what's arrived but has no spot yet, get a suggested location, and split one delivery across several zones.
Every shift of stock is recorded with who, when and why. This is what answers "where has this pallet been" during a dispute.
Pick lists follow the same order your stock is valued in — oldest first, or earliest-expiring for lot-tracked goods — so the ledger and the floor never disagree.
Count one location at a time without showing the expected number. It's the only kind worth trusting in a custody dispute.
Space, handling and services priced per customer, effective-dated so a mid-term price change never rewrites last month's invoice.
Issue and send the document, take payments against it, and watch the ageing buckets — one transfer can settle several invoices.
Draw the site once and see it coloured by how full it is, next to what each unit of space actually earned.
Choose the unit you measure space in, set each warehouse's usable area, then divide it into zones. A run of doors like C5-1 to C5-3 generates in one go, and you can drag the whole thing into a floor plan afterwards.
Anything already in stock but without a spot shows up as a put-away queue — including deliveries taken before you switched this on. Assign it, and every later move is recorded automatically.
For each customer: what's reserved, what's counted, what it costs per square metre, per pallet handled, per sticker applied. The rate card is entered once and read by every invoice after it.
Preview what every customer will be billed, see any charge that couldn't be priced before you send rather than after, then issue and email the document. Payments and ageing follow in the same place.
| What you'd otherwise pay for | Typical price | BackOffice |
|---|---|---|
| Warehouse management system | $150+/mo | ✓ |
| 3PL storage-billing add-on | $100+/mo | ✓ |
| Inventory app it has to sync with | $99+/location | ✓ |
| The monthly storage-invoice spreadsheet | Somebody's week | ✓ |
| All of it, one workspace | $349+/mo | One bill · per user |
Typical entry pricing for comparable tools — not a like-for-like sum. The point: it's one bill, and the invoice stops being a spreadsheet. See the full comparisons →
No. This sits on the stock BackOffice already tracks — your catalogue, quantities, costing and movement ledger stay exactly where they are. It adds the one thing they never had: where each unit physically sits. A quantity and its location are checked against each other daily, and anything that drifts is reported rather than quietly corrected.
Yes — that's a first-class mode, not an edge case. Every pallet can carry an owner, so your own stock and six customers' stock share the same zones without mixing. Customer-held goods are reported separately from your inventory valuation because they're bailment, not an asset. Per-customer rate cards price space, handling and services, and the monthly run turns what actually happened into a document you can send.
Whichever one you actually use — square metres, pallet positions, cubic metres, tonnes, containers, or one you invent this morning. Units are an editable list, because the unit is what you price against. Physical units convert between each other; countable ones like pallets deliberately don't, since how much floor a pallet takes depends on your racking — that ratio belongs to the building, and it's set per warehouse.
It shows as not measured, never as empty, and it's left out of "where will this fit". Calling it empty would let somebody promise space that may not exist; calling it full would stop them using space they have. The same rule runs through the module — anything that can't be computed honestly is shown as unknown, with the reason.
Yes, and as an obligation rather than a preference. If a customer's contract requires it, picking out of order is refused, not warned about — and the required order is the same one your stock is valued in, so the ledger can't end up saying a cheap old batch shipped while an expensive new one actually left.
It is. Warehouse Management lives alongside your CRM, helpdesk, POS, projects and books — same records, same roles and permissions, same audit log, same typed API and webhooks. A member who can't see a customer's record can't see that customer's stock, invoices or balances either; the permission you already set is the one that applies.
It's part of the BackOffice workspace and billed per user like everything else — not a separate WMS subscription on top. One bill replaces a warehouse system, a 3PL billing add-on, the inventory app they'd sync with, and the spreadsheet somebody rebuilds every month. See current plans →
Add a zone, put a delivery away, and watch the floor plan fill in. No credit card to get started.
Start free