> ## 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 calculate the real fulfilment cost per order
- URL: https://blog.jestor.com/calculate-fulfilment-cost-per-order/
- Published: 2026-09-16T18:54:03.000Z
- Updated: 2026-09-16T18:54:03.000Z
- Author: Bruno Bannach

Calculating **fulfilment cost per order** means counting everything between payment and delivery, not just the carrier invoice. In **Jestor**, those costs can accumulate on the order record, so the figure is available per order, per channel and per product.

## Why shipping cost is not fulfilment cost

Most companies know what the carrier charged. That number excludes packaging, the labour to pick and pack, the failed attempts, the returns and the support contacts the order generated.

For low value orders, the excluded portion frequently exceeds the carrier fee, which is how a product can be sold profitably and fulfilled at a loss.

What the full figure reveals:

- Products whose margin disappears in fulfilment
- Channels that look profitable and are not
- The real cost of a failed delivery attempt
- Whether a free shipping threshold is set correctly
- Which order profiles are worth optimizing

## Components of the real cost

| Component                  | Where it comes from         | Often ignored |
| -------------------------- | --------------------------- | ------------- |
| Carrier charge             | Shipping invoice            | No            |
| Packaging                  | Consumables consumed        | Yes           |
| Picking and packing labour | Time per order              | Yes           |
| Failed attempts            | Delivery records            | Almost always |
| Returns processing         | Return records              | Yes           |
| Support contacts           | Tickets linked to the order | Almost always |

## Step by step to measure it

1. **Record packaging consumption** per order at packing.
2. **Measure average handling time** per order profile, rather than per individual order.
3. **Link delivery attempts** to the order, including failures.
4. **Link returns** to the original order.
5. **Link support tickets** to the order they concern.
6. **Build the cost formula** across those connected records.
7. **Analyse by product and channel**, not only by individual order.

## Why analysing by profile beats analysing by order

Costing each order individually is precise and unusable. Grouping by profile, such as small single item orders to a given region, produces a number you can act on, because the action is a policy change rather than a decision about one customer.

## Why choose Jestor

In **Jestor**, deliveries, returns and support tickets can all connect to the order as related records, which is what makes a cost formula across them possible. Dashboards read the same data with no export, and grouping by product, channel or region is a filter rather than a report build.

## Frequently Asked Questions

### What is most often left out of fulfilment cost?

Failed delivery attempts and support contacts, which rarely get linked to the order. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Should I cost every order individually?

No. Group by order profile, since that is the level where you can act.

### How do I link a support ticket to an order?

As a connected record, so its cost can be included in the calculation.

## 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.