> 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

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

<div align="left"><figure><img src="/files/onT5nupoaCSGV3oC9wB4" alt="Multi-parcel order diagram" width="149"><figcaption></figcaption></figure></div>

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

<div align="left"><figure><img src="/files/w2aOUPT2gpR3IyHqleys" alt="Specific email content for a split shipment" width="375"><figcaption></figcaption></figure></div>

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
<p>You can expect {{numberOfTrackingsInOrder/system}} parcels!</p>
```

{% 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}}
<p>I'm only shown if there are multiple parcels in the order.</p>
{{/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}}
<p>I'm only displayed if there's just one single parcel in the order.</p>
{{/isOnlyTrackingInOrder/system}}
```

{% endcode %}

### Display Split Shipments on the Order Status Page

You can use the <code class="expression">space.vars.Product\_OrderStatus</code> 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 <code class="expression">space.vars.Product\_OrderStatus</code> 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](/docs/developers/v2/status-updates/configuration.md#usage-with-orders).

<div align="left"><figure><img src="/files/SJeM0fXXKiD32SqjQikz" alt="Tabs on the Order Status page for each delivery in a split shipment" width="563"><figcaption></figcaption></figure></div>


---

# 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.parcellab.com/docs/engage/messages-and-journeys/configuration/split-shipments.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.
