> 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/parcel_line_items.md).

# Parcel line items

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

A parcel line item represents a [SKU](/core-api-reference/2026-05/skus.md) (or [bundle](/core-api-reference/2026-05/bundles.md)) packed into a specific [parcel](/core-api-reference/2026-05/parcels.md), tracking exactly which items — and how many of each — ended up in that parcel.

## Splitting logic

Each parcel line item mirrors a [stock line item](/core-api-reference/2026-05/stock_line_items.md):

* If a stock line item isn't split across multiple parcels, its parcel line item carries over the full SKU code, bundle code, and quantity.
* If a stock line item is split — because its items ended up in more than one parcel — it generates a corresponding parcel line item in each parcel, each carrying only the quantity that parcel actually contains.


---

# 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/parcel_line_items.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.