> For the complete documentation index, see [llms.txt](https://docs.commercelayer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.commercelayer.io/core-api-reference/2026-05/parcels.md).

# Parcels

The parcel object and the allowed CRUD operations on the related resource endpoint

A parcel represents one of the physical boxes a [shipment](/core-api-reference/2026-05/shipments.md) is split into for delivery — each packed in its own [package](/core-api-reference/2026-05/packages.md) and tracked individually through the assigned [shipping carrier](/core-api-reference/2026-05/carrier_accounts.md). A shipment is split into two or more parcels when its contents don't fit into a single package.

## Tracking

Once a parcel is created, Commerce Layer requests a shipping label and tracking number from the carrier on your behalf. The `tracking_status`, `tracking_status_detail`, and `tracking_details` attributes are automatically kept up to date in real time by the carrier, so you and your customers can monitor the parcel through to delivery.

## Cross-border shipments

For international shipments, you can fill in a customs form using the `eel_pfc`, `contents_type`, `customs_certify`, and related attributes — the completed form is automatically generated and attached to the parcel alongside its shipping label.


---

# 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://docs.commercelayer.io/core-api-reference/2026-05/parcels.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.