> 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/data-model/shipping/parcels-packages-and-pickups.md).
# Parcels, packages, and pickups
Organizing shipment contents into parcels and packages, with parcel line items and carrier pickup scheduling
{% hint style="info" icon="lightbulb" %}
The physical side of fulfillment: splitting shipments into parcels, packing them into sized boxes, and scheduling carrier pickups.
{% endhint %}
## Parcels
[Parcels](/core-api-reference/parcels.md) are shipping line items that represent how a shipment is split for delivery. A shipment can be split into two or more parcels, each tracked individually through the carrier integration. Each parcel includes a shipping label and tracking information that customers can use to monitor their shipment.
## Parcel line items
[Parcel line items](/core-api-reference/parcel_line_items.md) are the individual SKUs within a parcel. If a stock line item is not split, the parcel line items correspond directly to its SKUs. If a stock line item is split, it is distributed across more than one parcel line item.
## Packages
[Packages](/core-api-reference/packages.md) are physical boxes or packs stored at a stock location, with predefined dimensions (length, width, height) and weight. Each stock location can have its own set of packages. Shipping carriers use these dimensions to calculate shipping rates.
## Pickups
[Pickups](/core-api-reference/pickups.md) are associated with eligible shipments and defined by a time window — an earliest and latest time at which the package is available for collection. Once created, the carrier's available pickup rates are returned automatically. A rate must then be selected and purchased to schedule the pickup.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.commercelayer.io/data-model/shipping/parcels-packages-and-pickups.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
