Tracking Partial Deliveries Without Closing the Whole Order

Imagine a plumbing supplies distributor handling this situation. The warehouse ships the fittings it has, but the remaining valve disappears from the dispatch list when the order is marked sent.

For a plumbing supplies distributor, this is an illustrative situation, but the difficulty is familiar: the team can see individual pieces of work without a dependable explanation of what should happen next. It deserves a closer look before another tool is added. The aim is to make the next action clear without adding unnecessary administration.

A single order status cannot represent quantities requested, allocated, dispatched and still outstanding for each line.

The balance belongs to each line, not merely to the order as a whole. This lets staff fulfil what remains without treating earlier dispatches as missing or repeating them.

Each line needs a balance that reflects dispatches, cancellations and approved changes. Staff can then distinguish remaining demand from work already fulfilled. The order-level view should summarise that position without forcing every line into a single state that hides meaningful differences. This creates two kinds of work: handling the original request and checking whether the information describing it is usable. The second task is easy to overlook because it takes place between systems rather than appearing as a formal item on the work list.

Track fulfilment against order lines and retain a visible balance. Use an existing backorder feature if suitable before commissioning a separate tool.

If a small custom component is justified, define what it owns and what remains maintained elsewhere. The proposed tool should make its current state understandable rather than hide important uncertainty behind a simple button. Use realistic records to check that staff can complete the whole task, including correcting a mistake. Describe the required relationship between records before discussing a new screen. An existing application may already provide the needed structure through configuration or a supported extension. Keep the scope narrow enough that users can evaluate one complete workflow before more features are added. Permissions, recovery and operational support belong in the design from the beginning.

Stock allocation and invoicing may follow different rules and should not be inferred from one dispatch button.

For background relevant to partial order fulfilment, see The Spreadsheet That Became Your Entire Business. The issue here is the narrower workflow described in this example.

Dispatch part of one line, cancel another balance and inspect what remains available to fulfil. Treat the first implementation as a limited operational trial. Keep the scope clear and nominate a person to collect problems from the people using it. Assess exceptions alongside ordinary work before deciding whether the change is ready for wider use.

For partial order fulfilment, review the proposed outcome with the staff responsible. Check what an authorised user can see, change and recover in the proposed tool. The result should remain understandable to a colleague who did not create the record, including when the task is corrected or handed over. Check that the proposed improvement does not create a second private list for unresolved cases. Relevant staff should be able to see the next action in the agreed place.

At Software Logic, we help businesses examine practical improvements to small internal tools, starting with the work their existing tools need to support. Which undelivered items disappear when your team marks an order sent?