Overview

The Aggregated Packages feature enables the grouping of multiple smaller packages into a single larger package for shipment. This approach allows print houses to optimize shipping costs by reducing the number of shipments required, resulting in cost savings and improved operational efficiency.

On a technical level, smaller packages are shipped using a special GCW External Aggregated Package Label shipment method, which produces labels that only contain basic information (name; address; order and package id - example below) and are not fit for shipping on their own. This ‘label’ uses the regular process and can be downloaded in MPJ, under EDIs. After that they need to be grouped and shipped together using Aggregated Packaging feature described in this document.

How It Works

Using the Aggregated Packages feature, smaller packages are shipped under the GCW External Aggregated Package Label shipment method, which can be easily identified in the Manage Print Jobs page. These labels include essential shipping details such as the recipient's name, address, order, and package ID. However, they are not valid for standalone shipping and must be grouped together following the steps below.

Step-by-Step Guide for the Set Up of a Larger Package

Step 1: Select the Recipient

Go to the ‘Aggregated package’ section of the app.
The first step is to select the recipient. You cannot proceed to the subsequent sections without completing this step.
The list will be automatically populated with packages with the GCW External Aggregated Package Label shipment method.

Step 2: Scan the Packages

In this section, you will scan the individual packages. A verification check is performed to ensure the scanned packages are associated with the selected recipient.
There are three possible scan statuses:
- Invalid Barcode: The scanned barcode is not registered in our system.
- Invalid Recipient: The scanned package does not belong to the selected recipient.
- OK: The scanned package has a valid barcode and is correctly assigned to the selected recipient.

Step 3: Enter Package Dimensions & Select Shipping Options

Input the dimensions of the aggregated package (length, width, height in millimeters) and weight (in grams). In phase 2 we will add US metrics as well.
Once the dimensions are entered, shipping options specific to the recipient and packages will be provided.
After selecting a shipping option, you can generate the necessary packaging documents, which will be immediately ready for printing.

Step 4: Ship the Aggregated Package

At this stage, the aggregated package is considered shipped.

Step 5: Add Another Aggregated Package (If Needed)

If you need to send another aggregated package, simply reset the process and follow the flow again.

Advanced Capabilities & Rules

Requirements & Solutions

1. Retain Original Shipping Method

Requirement: The original shipping method on the order must not be overwritten when added to an aggregated package.
Solution: The system now retains the original shipping method of each package, ensuring correct routing and logistics compliance.

2. Customer-Level Aggregated Package Control

Requirement: Ability to configure whether a customer accepts aggregated packages (e.g., 2 of 50 funeral homes do not).
Solution: A new configuration page allows Print Partners to enable or disable aggregated packages per customer.
- Customers enabled for aggregation appear in the recipient list.
- Customers disabled are excluded from selection during aggregation.

3. Express Shipping Handling

Requirement: If any package within an aggregated group is marked as express, the entire box must be sent express.
Solution: Aggregated shipment logic now auto-escalates to express if any package within it requires express handling.

4. Box Dimension Configuration

Requirement: Ability to define the default box dimensions used for aggregation.
Solution: The new UI allows users to predefine width, height, length, and weight for aggregated boxes. These defaults can be adjusted manually per use case.

5. Manual Box Packing Control

Requirement: The packaging operator should be able to manually assign packages to boxes, optimizing express vs non-express shipping.
Solution: Manual control is maintained—operators can decide box assignments, allowing cost and speed optimization based on shipping class.

Outcome

This feature update allows greater flexibility, accuracy, and efficiency in handling Aggregated Packages. Print Partners now have:

Full control over which customers support aggregation,
Reliable express routing rules,
Configurable package sizing,
And a clear way to exclude ineligible recipients.

Enabling Aggregated Packaging in Order Intake

To enable this feature during order intake via the GelatoAPI, use the following Liquid template:

{% set payload = context.payload %}

{# Check if aggregatedPackaging exists and is true #}
{% if payload.aggregatedPackaging is defined and payload.aggregatedPackaging %}

{# Clone the metadata and append the new entry #}
{% set metadata = payload.metadata if payload.metadata is defined else [] %}
{% set new_metadata = metadata + [{"key": "tenant-shipping-method-uid", "value": payload.shipmentMethodUid}] %}

{# Replace shipmentMethodUid and update metadata #}
{% set payload = payload.copy() %}
{% set _ = payload.update({"shipmentMethodUid": "gcw_external_aggregated_package_label", "metadata": new_metadata}) %}

{% endif %}

{{ payload | tojson(indent=2) }}

This logic can be applied to the Order Submit endpoint and works only with the GelatoAPI payload structure.

Example Payload

{% set payload = context.payload %}

{# Check if aggregatedPackaging exists and is true #}
{% if payload.aggregatedPackaging is defined and payload.aggregatedPackaging %}

{# Clone the metadata and append the new entry #}
{% set metadata = payload.metadata if payload.metadata is defined else [] %}
{% set new_metadata = metadata + [{"key": "tenant-shipping-method-uid", "value": payload.shipmentMethodUid}] %}

{# Replace shipmentMethodUid and update metadata #}
{% set payload = payload.copy() %}
{% set _ = payload.update({"shipmentMethodUid": "gcw_external_aggregated_package_label", "metadata": new_metadata}) %}

{% endif %}

{{ payload | tojson(indent=2) }}

Note: The shipment method gcw_external_aggregated_package_label must be enabled by the Logistics team.