---
title: "Configure incidents (pickup and delivery)"
description: "Configure incidents and set actions such as Block, Cancel, Don't replan, Retry, or Return, with a hub location."
url: https://help.qargo.com/us/articles/133792-configure-incidents-pickup-and-delivery
locale: us
updated: 2026-06-15
---

# Configure incidents (pickup and delivery)

Incidents, such as a failed delivery or pickup, can be configured for use on orders or loads. Each incident is recorded against a specific stop.

-   Navigate to **Rates > Order input**
-   Left-hand menu: **Stop options** – click **Incidents**
-   Click **New incidents** to add a new option and complete the details under **General info**.

    -   Select which stops the incident can be used on
    -   Set which customers can view incidents in the customer portal (all or selected customers only)
    -   Set the stop action when the incident is recorded. Options include:

        -   Block operations – can't be replanned and moves to Blocked status
        -   Don't replan – no further action, but available To plan
        -   Retry pickup/delivery – reschedules the stop.
    -   Set a question path (optional) if the Qargo mobile app is used and specific steps or information are required.
-   If charges apply, add a charge template that can be applied to specific rate cards

    -   Link the specific rate card to the transportation service as required.

Make sure the incident is set to **Active** against the transportation service in the configuration settings. This makes it visible in the dropdown menu when adding an incident.

![](https://help.qargo.com/media/25c7cab2f7c3-image.png)

-   Select the **Primary action** required once an incident is recorded. Options include:

    ![](https://help.qargo.com/media/f2625800c682-image.png)

    -   **Block operations:** The order is blocked and no further planning activity is available. The order moves to the **Blocked** tab in Orders.
    -   **Cancel shipment (Pickup):** The shipment is canceled. The order status updates based on the shipments on the order (Planned, In transit, Delivered).
    -   **Don't replan:** The order incident is recorded, but the order status does not update.
    -   **Retry pickup/delivery:** This option records the stop as an incident and creates a new _To plan_ status on the order. For deliveries, a default hub location must be specified for the redelivery. The freight on board is rescheduled to ship from this location on the next load.
    -   **Return to pickup location (Delivery):** The shipment is replanned. A default hub location must be specified for the redelivery. The freight on board is rescheduled to ship from this location on the next load.

![](https://help.qargo.com/media/0f3186bfc427-image.png)

![](https://help.qargo.com/media/e1b2542870ea-image.png)

:::callout{tone="note"}
If a **_Retry_ / _Return_** option is selected, the hub location shows when the incident is recorded. It can be changed to an alternative location if necessary.
:::

Once the configuration is saved, [these incidents can be selected](https://help.qargo.com/us/articles/133857-incidents) on orders and loads.

* * *

## Configuring and viewing incidents in the customer portal {#h_62b1912d7e}

Where enabled, customers can view stop incidents in the portal:

-   Viewing can be enabled for all customers or for specific customers only.
-   Each incident can be configured individually to show or hide it from the customer

![](https://help.qargo.com/media/b94756fb08b2-image.png)

### What changes in the customer portal {#h_26f88515f7}

When an incident is logged and visible to the customer, users see the same incident indicator icon, with a summary when hovering over the icon.

::video{src="/media/video/3d148a62b440-2026-06-15_16-54-12--1-.mp4"}

For a customer who is not allowed to see an incident type, it no longer appears anywhere in the portal:

-   The incident indicator next to the order name in the order list.
-   The incident indicator in the order detail header.
-   The **Incident** label in the operations section of the order detail.
-   The related incident columns available under **Customize**.

Internal recording is unchanged: incidents are still logged as before, and only the portal visibility changes.

## Troubleshooting {#h_c1ecb80af6}

| **Issue** | **Resolution** |
| --- | --- |
| An incident still shows in the portal | Confirm the customer is excluded from **Customers who can see this incident** on that incident type. |
| The setting cannot be edited | _Super Admin_ access is required to edit incident types. |
| Incidents need to be hidden in the carrier portal | This feature covers the customer portal only. Carrier portal visibility is tracked separately. |


## Related articles

- [Configure incidents (freight)](https://help.qargo.com/us/articles/133793-configure-incidents-freight.md)
- [Failed delivery for pallet network order](https://help.qargo.com/us/articles/144152-failed-delivery-for-pallet-network-order.md)
- [Qargo Mobile app – Cross-dock scanning: Question paths & incident registration](https://help.qargo.com/us/articles/690993-qargo-mobile-app-cross-dock-scanning-question-paths-incident-registration.md)
- [Planning: blocked orders / do not dispatch](https://help.qargo.com/us/articles/267831-planning-blocked-orders-do-not-dispatch.md)
- [Orders – Add or delete extra stops on an order](https://help.qargo.com/us/articles/133868-orders-add-or-delete-extra-stops-on-an-order.md)
