> ## Documentation Index
> Fetch the complete documentation index at: https://help.owlery.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Respond to Load Changes

> Review and accept or reject a shipper's changes on the existing load without creating a duplicate.

**Where to find it:** `Dashboard → Operations → Shipments (Loads)`

When a shipper changes an accepted load, Owlery keeps the current load in place and adds a proposed revision for your review.

<Warning>
  Work from the existing load. Do not create another load or assign a new load number for the proposed change.
</Warning>

## Review the Changes

<Steps>
  <Step title="Open the Existing Load">
    Find the load by its current **Load Number** and open it. A banner says that a load change is waiting for your confirmation.
  </Step>

  <Step title="Open Proposed">
    Click **See Proposed Changes** in the banner or open the **Proposed** tab.

    Owlery shows the previous and proposed values side by side. Only changed fields are emphasized.
  </Step>

  <Step title="Check the Affected Details">
    Review any changes to:

    * Reference numbers, equipment, items, price, or temperature requirements.
    * Pickup and delivery locations.
    * Requested or scheduled dates.
    * Stop requirements and notes.
    * Added or removed stops.
  </Step>

  <Step title="Accept or Reject">
    Click **Accept** to apply the revision to the existing load. Click **Reject** to keep the previous load details.
  </Step>
</Steps>

After you accept, the banner clears and Owlery keeps the same load record and Load Number. After you reject, the **Proposed** tab records that the last edit was rejected and the previous details remain active.

## If You Respond Through an Integration

Use the same channel that received the change.

<Tabs>
  <Tab title="EDI">
    Treat the update as a revision to the existing load. Do not import it as a new load in your TMS.

    Follow the [EDI Guidelines](https://owlery.ai/open/edi-guidelines) for the transaction and response requirements.
  </Tab>

  <Tab title="API">
    Respond to the new revision for the existing load number. The original tender is revision `0`; each accepted load change uses the revision identified by the API.

    A stale revision is rejected so an older response cannot overwrite the current proposed change.
  </Tab>
</Tabs>

<Note>
  If the Portal does not show **Accept** or **Reject**, your connection may require the response in your TMS or by EDI. Follow the message shown on the tender instead of responding through both systems.
</Note>

## If the Change Is Missing or Incorrect

* Confirm that you opened the existing Load Number rather than a second record in your TMS.
* Check the **History** tab for the latest tender activity.
* For EDI, confirm that your system received and processed the revision according to the [EDI Guidelines](https://owlery.ai/open/edi-guidelines).
* Ask the shipper to confirm the exact Load Number, what changed, and when they sent it.
* If the comparison is unavailable, email [support@owlery.ai](mailto:support@owlery.ai) with the Load Number, shipper, timestamp, and a screenshot.