> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to manage an order pipeline from payment to dispatch
- URL: https://blog.jestor.com/manage-an-order-pipeline-end-to-end/
- Published: 2026-09-16T18:53:45.000Z
- Updated: 2026-09-16T18:53:45.000Z
- Author: Bruno Bannach

To **manage an order pipeline** properly, each stage has to correspond to something that physically happened. In **Jestor**, orders move across a board where the stage is the source of truth for both the warehouse and the customer, so nobody has to ask where an order is.

## Why order status becomes unreliable

Status is usually updated as a courtesy, after the work, by whoever remembers. The physical reality and the record drift apart within days.

Then customer service answers questions by walking to the warehouse, and the system becomes something people work around rather than with.

What a reliable pipeline fixes:

- Customers told a status that is no longer true
- The warehouse working from a printed list
- No way to tell which orders are actually late
- Stock committed to orders that were already cancelled
- No measure of how long fulfilment really takes

## Stages that reflect physical reality

| Stage             | Physical meaning              | Customer visible   |
| ----------------- | ----------------------------- | ------------------ |
| Payment confirmed | Funds cleared                 | Yes                |
| Reserved          | Stock allocated to this order | No                 |
| Picking           | Items being collected         | Yes, as preparing  |
| Packed            | Ready to leave                | Yes                |
| Dispatched        | Handed to the carrier         | Yes, with tracking |
| Delivered         | Received by the customer      | Yes                |

## Step by step to build it

1. **Define stages by physical events**, not by internal handoffs.
2. **Update the stage where the work happens**, on a phone in the warehouse if needed.
3. **Reserve stock at the reservation stage**, not at dispatch.
4. **Show different fields per stage**, so pickers see items and dispatch sees the address.
5. **Trigger customer notifications** on the stages that matter to them.
6. **Track time per stage**, which is where fulfilment delays actually live.
7. **Handle cancellation explicitly**, releasing reserved stock.

## Why cancellation deserves as much design as fulfilment

Most order processes are designed for the happy path. Cancellation is handled manually, which means reserved stock stays committed and inventory drifts. Designing the cancellation path releases the stock automatically and keeps the numbers honest.

## Why choose Jestor

In **Jestor**, orders and their items are connected records, so reservation and cancellation can act on stock through automation. Boards show different fields per stage, the mobile layout is built separately for warehouse use, **SLA** per stage reveals fulfilment delays, and customer updates can go out through native **WhatsApp** automations.

## Frequently Asked Questions

### When should stock be reserved?

At the reservation stage, so availability reflects commitments rather than dispatches. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Can warehouse staff update status from a phone?

Yes. The mobile layout is designed separately for field use.

### What is most often forgotten in order design?

Cancellation, which must release reserved stock or inventory drifts.

## Video Tutorial: Step by Step

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by **AI**. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.