Why 'in stock and in date' is not 'shippable' in a food warehouse, and how release state and per-customer life rules decide which orders each batch can fill.

Location tracking says where a tool is. Assigning work needs custody and fitness for the whole job window. Three questions to test any asset tracking system.

A forecast is one input to the weekly buy. See how the inventory position, the buffer, pallet rounding and shelf life set the order, and why position errors cost as much as forecast error.

A client instruction is enforced only when it becomes a step on the right orders, and provable only when completion records the version followed. How to judge any fulfilment system.

Why an approved supplier list did not stop a bad order, what an approval must record to be checked at the order line, and three tests to run on any system.

Why a line board survives beside the ERP: it holds working state, the operation's rules and each person's view. Sort your columns into three kinds and judge every replacement by what it holds.

After a pick is released, a commercial order change is a request the warehouse accepts or refuses. How to draw the ERP and WMS boundary so both systems agree on what shipped.

Why a timed-out carrier booking is neither retried nor assumed done: three states per handoff, evidence the partner owns, and a named owner while it is pending.

Why a gap on the calendar is not capacity, what changeovers and material do to a plan, and what an urgent job displaces when it is put first.

When an order cannot ship whole, four quantities on each line keep the warehouse, customer service and finance agreeing on what is still owed. One twelve-case example and a buying test.

Faster stock sync narrows the window in which two channels sell the same units. Only one reservation authority, or a deliberate split of stock, closes it.

A purchase runs through four facts that must stay connected and never merge: ordered, received, accepted and invoiced. One illustrative order shows why.