# Forcing a delivery

> **You need:** *Hub — force delivery*. Typically `hub_manager` only. This is the most consequential action in the Hub — read the whole page before using it.

Force delivery closes an order as delivered when the normal flow could not close it — most often because the driver's device failed to register the delivery, or an external carrier never reported completion.

## What it actually does

It records the order as delivered, with a driver and a distance that **you** supply rather than ones the system observed.

That is the whole point, and the whole risk: you are asserting something the system could not confirm. Everything downstream — delivery counts, driver figures, distance-based reporting — takes your word for it.

## Use it only when the delivery really happened

Force delivery is for correcting a **recording** failure, not an operational one.

| Situation | Force delivery? |
|---|---|
| Customer received the order; the app never registered it | ✅ Yes — that is exactly this |
| Carrier delivered but never reported back | ✅ Yes |
| Order is very late and you want it off the board | ❌ No — it is still in progress |
| Order was never delivered | ❌ No — cancel it instead |
| You are not sure whether it was delivered | ❌ No — find out first |

> Forcing an order that was never delivered puts a false delivery into your records permanently. There is no clean undo. When in doubt, confirm with the driver or the customer before acting.

## Doing it

1. Open the order — see [Order details and pickup code](/books/console-yF7/page/order-details-and-pickup-code).
2. Choose force delivery.
3. Enter **who delivered it**: your own driver, or the carrier. For an own driver you name the specific person; for a carrier the company is enough, since the courier is theirs.
4. Enter the **estimated distance** for the delivery.
5. Confirm.

## The distance matters

The distance you enter is used as the delivery's distance. It feeds driver figures and any distance-based reporting or settlement.

Estimate it honestly from the store to the delivery address. A placeholder — zero, or a round number entered to get past the field — quietly corrupts whatever is calculated from it, and nobody will notice until the numbers are questioned months later.

## Always log an incident too

A forced delivery with no incident is the hardest thing to reconstruct later: the record shows a normal delivery, with nothing explaining why a person had to close it by hand.

Log an incident describing why the force was needed — device failure, carrier silence, whatever it was. See [Logging an incident](/books/console-yF7/page/logging-an-incident).

## If you are unsure

Do something reversible instead. Change the promised time, log an incident, or leave the order alone and escalate. Every other Hub action can be worked around afterwards; this one cannot.