Handle incidents: failed deliveries and what happens next
Record what went wrong at a stop, such as a refused delivery or damaged goods, and choose the follow-up: a new attempt, a return, a hold or a cancellation.
Updated 13 October 2026
An incident records why a stop did not go as planned: the consignee refused the goods, the address was closed, goods were damaged. Each incident has a type, the consignments it concerns and a follow-up that decides what happens next. Transportial then creates the new work for you, such as a new delivery attempt in the planning pool.
How incidents are created
- By the driver. When a driver marks a stop in OpenMove as Partly done or Not able to do, the app asks What went wrong? and shows the incident types. Some types require a photo or a remark before the driver can complete the stop. See Execute a stop.
- Automatically from a failed stop. When Create an incident when a stop fails is on (the default), a failed stop always becomes an incident. If the driver did not pick a type, Transportial chooses one from the words in the reason, or uses the fallback type.
- By a planner, as described below. Subcontractors in the carrier portal report incidents the same way when they record a failed stop.
Report an incident yourself
- Open the transport order.
- Open the options menu (⋮) and click Report incident.
- Under What happened, choose the Incident type, the Consignments and optionally the Stop (optional). Add a Remark and Photos or files when the type requires them.
- Under Follow-up, choose what should happen, or No follow-up to decide later.
- Click Report incident. The Incidents tab of the order opens.
Choose the follow-up
Open incidents appear in the Incidents tab of the order and, with the exceptions feature, as an Incident in the exceptions list with each follow-up as an alternative. The type's default follow-up is listed first.
- Click Choose follow-up on the incident.
- Choose the follow-up. For a hub or depot, pick the Location (leave it empty for the default from the settings). For a new attempt, optionally set New attempt from (optional) and Add to trip (optional).
- Click Apply follow-up.
In the exceptions list, Accept on an alternative applies that follow-up with the default settings. See Handle planning exceptions.
| Follow-up | What Transportial does |
|---|---|
| New delivery attempt | Creates the failed stop again at the same address, moved to the date you choose or by the number of days in the settings (1 by default). |
| Return to the pickup address | Adds an unloading stop at the address where the goods were picked up. |
| Via a hub, then deliver | Unloads at a hub, loads again there and delivers onward to the original address. |
| Park at a depot, then deliver | The same, via a depot. |
| Cancel the consignment | Cancels the consignment. With dead freight on (the default) the order stays invoiceable; otherwise an order without active consignments is cancelled too. |
| Put on hold | Puts the consignment on hold with the incident as the reason. See Put an order or consignment on hold. |
| No replanning (accept the failure) | Accepts the failed attempt, so the consignment no longer needs replanning. |
New stops land unplanned in the planning pool, or at the end of the trip you chose. Applying a follow-up resolves the incident: its status changes from Open to Resolved. If a follow-up fails, the incident stays open with the error.
Incidents that affect the whole stop
Some types, such as Closed or Address not found, apply to the whole stop. When such an incident is reported, every consignment that was still to be loaded or unloaded at that stop is marked as failed and added to the same incident, so you handle them all in one go.
Set up incident types
- Open Settings, click the Environment tab and open the section Incidents.
- Set the general options: Create an incident when a stop fails, Apply the type's default follow-up immediately (off by default), Keep a cancelled consignment invoiceable (dead freight), Days to shift a new delivery attempt, Type when nothing matches, Default hub (via a hub) and Default depot (park at a depot).
- Under Incident types, change the built-in types or click Add incident type. Each type has a Name, a Default follow-up, the words in a driver's reason that pick it, and the switches Active, Visible to the customer, Photo required, Remark required and Applies to the whole stop.
- Click Save.
The built-in types are Refused by consignee, Address not found, Closed, Damaged goods, Shortage, Wrong goods, Waiting too long and Other.
Customers see incidents of types that are Visible to the customer on their order in the customer portal, with the follow-up and when it was resolved. To notify someone, use the trigger events After an incident is reported and After an incident is resolved in message automations.