How a WMS works: one carton, dock to truck

The two documents

Everything that happens in a warehouse starts from a document that came from outside. Goods come in against a purchase order. Goods go out against a sales order. The warehouse does not invent either one. A WMS takes those two documents and turns them into physical work, and turns the physical work back into records the rest of the business can trust.

Inbound: purchase order to shelf

Receive. A truck arrives with cartons against purchase order 4471. The receiver scans the product and confirms the count. The WMS writes a receive movement into a bucket called received-on-dock. The stock now exists, but it is not sellable: it has no location and it has not been put away.

Inspect and label. If the product tracks lots or expiry, the receiver records the lot and the date here, not later. If the goods carry a marketplace barcode instead of yours, the WMS resolves it to your SKU and records the real SKU, never the alias.

Putaway. An operator scans the carton and then scans the bay. The WMS moves the quantity from the dock bucket to that location. Now it is on hand, and now it is available to promise. This is the moment the store may see it.

Three steps, three movement rows. If the receiver counted twelve and the putaway operator moved eleven, the dock still holds one, and the ledger says so.

Outbound: order to truck

Allocate. A customer order for two units arrives from the store. The WMS checks what is available to promise, reserves exactly two units for this order, and writes an allocation row. Available to promise drops by two on every channel. Nothing has physically moved yet.

Pick. A picker is sent to the location. They scan the bin, scan the product, and confirm the quantity. The WMS writes a pick row and the units leave the shelf on record. If the picker scans the wrong product, the scan is refused; a lookalike cannot be picked by accident.

Pack. At the bench, the packer scans each unit again before the box can close. The WMS records the packaging used and, if you track packaging as stock, consumes a box from inventory.

Ship. A label is bought or scanned, the carrier and tracking are recorded, and the WMS writes the ship row. The order is now out of the building on record, and the store is told the shipment and its tracking.

Four steps, four movement rows, one traceable story from the store’s order to the carrier’s truck.

Counting: the loop that keeps it honest

A WMS also directs counting. Instead of shutting the building once a year, it asks an operator to count a few locations each day. Where the count differs from the record, the difference becomes a variance line that cannot be approved without a reason, and approval writes an adjustment row. The correction is on the ledger with everything else.

What the order of steps buys you

Every number on every screen is the sum of these rows. On hand is receives minus picks plus adjustments. Available is on hand minus allocated, and it never includes the dock, damaged stock or quarantine. When a number looks wrong, the rows that produced it are there to read, and one of them is the answer.

How DockingWare runs this loop

DockingWare runs the inbound and outbound loops on a handheld and on a desktop station console, and both write the same rows through the same services. Available to promise is computed on the server and published to each connected channel after each movement. A nightly job replays every movement row and compares the result with the stored balance, so if the record and the cache ever disagree, the record wins and the run says so.