> For the complete documentation index, see [llms.txt](https://docs.parcellab.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parcellab.com/docs/engage/messages-and-journeys/configuration/split-shipments.md).
# Split Shipments
Use special placeholders for split shipments to let customers know how many packages they can expect to receive in a delivery.
## Overview
Sending out multiple packages for one order is a common practice in e-commerce. Where there are multiple packages in a single order, it is easy to keep customers informed by adding placeholders in email communications.
## Configuring Split Shipments
The following sections describe the configuration required for split shipments.
### Requirements
The only requirement for split shipment communication is that each tracking in parcelLab is assigned to an order number.
### Display Split Shipments in Emails
You can easily display split shipments in your customer emails by adding the relevant placeholder.
To begin, you can show the number of parcels for an order by using the `{{numberOfTrackingsInOrder/system}}` placeholder.
{% code title="number-of-parcels.html" %}
```markup
You can expect {{numberOfTrackingsInOrder/system}} parcels!
```
{% endcode %}
You can use a conditional placeholder to show special text/content for the cases of multiple parcels or a single parcel per order.
{% hint style="info" %}
This needs additional settings to be configured by parcelLab. For further assistance, please contact your parcelLab representative.
{% endhint %}
To include content for multiple parcels, the `{{#hasMultipleTrackingsInOrder/system}}` `{{/hasMultipleTrackingsInOrder/system}}` placeholder is used with the relevant text included.
{% code title="multiple-parcels-in-order.html" %}
```markup
{{#hasMultipleTrackingsInOrder/system}}
I'm only shown if there are multiple parcels in the order.
{{/hasMultipleTrackingsInOrder/system}}
```
{% endcode %}
To include content for a single parcel, the `{{#isOnlyTrackingInOrder/system}}` `{{/isOnlyTrackingInOrder/system}}` placeholder is used with the relevant text included.
{% code title="just-one-parcel-in-order.html" %}
```markup
{{#isOnlyTrackingInOrder/system}}
I'm only displayed if there's just one single parcel in the order.
{{/isOnlyTrackingInOrder/system}}
```
{% endcode %}
### Display Split Shipments on the Order Status Page
You can use the space.vars.Product\_OrderStatus to view each package in a split shipment, which is tracked in one simple screen for your customer to make it easy to understand.
The space.vars.Product\_OrderStatus should be set to multi-parcel view based on orders before switching the emails. For further information, see [how split shipments are configured for the Order Status page](https://github.com/parcelLab/gitbook-documentation/tree/main/developers/status-updates/configuration/README.md#usage-with-orders).
---
# 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.parcellab.com/docs/engage/messages-and-journeys/configuration/split-shipments.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.
