> For the complete documentation index, see [llms.txt](https://developer.esw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.esw.com/customs-catalog-api/fulfillment-api/core-concepts/advanced-shipping-notice-asn.md).

# Advanced Shipping Notice (ASN)

The ASN closes the fulfillment loop. It is submitted when the parcel physically leaves the fulfillment centre — typically when the carrier's driver scans it at collection or when the 3PL hands it off at the dock. It carries the tracking reference, physical measurements, and per-item dispatch quantities.

### When to submit the ASN

**On carrier scan**

Ideal trigger: when the carrier's handheld scanner records the waybill/tracking barcode at the dock. The `shipmentDateTime` should be the scan timestamp.

**On batch handover**

If your dock uses batch handover without individual scans, submit the ASN after the batch manifest is signed by the driver. Set `shipmentDateTime` to the manifest signing time.

**Not before dispatch**

Do not submit an ASN before the parcel is confirmed collected. An ASN triggers customer tracking notifications and customs pre-clearance — submitting prematurely causes support issues.

### `shipmentStatus` 

| Value              |                                                                     |
| ------------------ | ------------------------------------------------------------------- |
| `Shipped`          | All items in the pack were dispatched to the carrier                |
| `PartiallyShipped` | Only some items were dispatched (others failed at PickPack/Confirm) |
| `Unshipped`        | Package created at 3PL but not yet dispatched                       |

### Physical measurement fields

The `packageWeight` and `packageDimensions` fields should reflect the actual measured values from the dock scale and volumetric scanner — not the declared values from the Package API. Carriers use these for billing reconciliation. A significant difference between declared and actual weight can trigger carrier surcharges and customs queries.

{% hint style="warning" %}

#### **`carrierReference` is the customer's tracking number**

The `carrierReference` field is the carrier-assigned tracking number (e.g. DHL waybill number, FedEx tracking ID). ESW uses this to build the tracking URL and send it to the customer. An incorrect or missing `carrierReference` means the customer cannot track their parcel.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.esw.com/customs-catalog-api/fulfillment-api/core-concepts/advanced-shipping-notice-asn.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.