Give each order
a clear next step.

An order received is not necessarily an order accepted for fulfillment. Likewise, an item picked is not always an item ready for customer collection. Agree on what a status means and which event can change it.

For a collection order, staff may need to distinguish waiting for stock, ready to pick, ready for collection, and collected. The exact states should reflect the actual operation.

A handoff needs more than a notification. Explain who receives it, what information they need, and how completion is acknowledged. An unresolved item should remain visible to the appropriate person.

Consider changes after the first instruction, such as a missing item or a customer changing a collection arrangement. The software needs an understandable path for the exception, not just the normal sequence.

Staff investigating an order benefit from knowing when a meaningful change occurred and which source supplied it. A readable account can support a conversation without exposing unnecessary customer information.

Before discussing a tool, outline one typical order and one difficult exception. These examples help establish the required actions, information boundaries, and points where a person needs to make a decision.