Warehouse management that never loses a lot.
Acrocargo WMS runs third-party logistics operations end to end — inbound forecasting, receiving, putaway, allocation, picking and shipping — on an inventory model that identifies every unit by seven dimensions, so batch traceability survives every move, split and transfer.
web.acrocargowms.me
The core idea
A stock unit is seven things at once
Most systems treat inventory as a number attached to a SKU. Acrocargo treats it as a position: quantities merge only when all seven dimensions match, and differ in any one of them and they stay separate rows. That is what makes lot-level recall, customer-specific handling and true FIFO possible.
Client
Whose goods these are
SKU
Which product
ULN
Which logical lot — drives FIFO
Container
Which physical carrier
Location
Which rack or floor position
UOM
Cartons or pieces
Warehouse
Which physical site
Capabilities
Built for contract logistics
The platform assumes the hard case: many clients, shared space, mixed B2B and B2C flows, and auditors who will ask where a specific lot went.
Inbound with real traceability
ASNs carry PO, container and lot data from forecast through receipt. Every receipt mints a ULN so a batch can be traced back to its purchase order and forward to every order it shipped on.
Two client models, one warehouse
B2B clients get strict lot separation, pallet-by-pallet declaration and mandatory PO or container references. B2C clients get a lighter path optimised for speed. Both run in the same building on the same stock.
Handheld scanning on the floor
An Android companion app puts receiving, putaway, moves, counts and picking on a rugged scanner, so floor staff confirm work against barcodes instead of transcribing it later.
Directed putaway and moves
Stock moves as whole units carrying their lot and container identity. Partial putaway or transfer splits the record rather than blurring it, so traceability is never lost to a partial move.
Client self-service
Clients log in to submit inbound forecasts, watch stock by lot and expiry, place and track outbound orders, and pull their own documents and labels without emailing the warehouse.
Usage-based billing
Storage, handling and value-added charges are computed from the operational record by scheduled jobs, using pluggable fee strategies rather than hardcoded rates.
Lifecycle
From forecast to invoice
- Step 1
Forecast
A client or coordinator raises an ASN naming the goods, quantities, PO and container expected to arrive.
- Step 2
Receive
The truck arrives. Staff record what actually landed, capture condition evidence, and stock enters the building.
- Step 3
Put away
Goods move from the receiving area to their storage position, carrying their lot identity with them.
- Step 4
Hold & count
Stock is queryable by any dimension, can be moved, frozen or adjusted, and is reconciled by stocktake.
- Step 5
Allocate & pick
An outbound order reserves specific lots by FIFO, and pickers are directed to the exact positions to pull from.
- Step 6
Ship & bill
Dispatch closes the order, releases the reservation, and feeds the usage record that billing runs against.
Each step has its own preconditions, validations and state transitions.
Surfaces
Four ways in
Web console
Coordinators, supervisors, managersThe full operational surface — ASNs, inventory, orders, master data, billing and reporting.
Handheld scanner
Receivers, stockers, pickersBarcode-driven execution of the physical tasks: receive, put away, move, count and pick.
Client portal
External client usersA scoped view of one client's own stock, inbound forecasts, outbound orders and documents.
Integration API
Partner systemsA versioned REST surface plus webhooks for partners who push orders and pull status programmatically.