Before you begin
- Packaging in Forge MES
How the workflow connects
This journey connects the following stages. Complete the required checks at each stage before moving forward.
- 01Conditional
Configure leaf and parent types
In Packing Configuration, create the leaf first, then create each parent with its allowed Child Container Type; selecting a child makes Max child count required.
Provides the controlled input for the next stage. - 02Conditional
Set UID and physical limits
Choose a container-specific UID Template and sequence reset scope, then configure dimensions, weight range, and tolerance.
Provides the controlled input for the next stage. - 03Conditional
Create the parent container
Create the parent from the Packaging Dashboard by selecting the Product, parent Container Type, and completed Work Order.
Provides the controlled input for the next stage. - 04Conditional
Pack an eligible identity
In Pack by UID, scan a finished serial, device UID, child UID, identifier, or task ID; a valid unit automatically creates the configured leaf and packs it into the parent.
Provides the controlled input for the next stage. - 05Conditional
Print and audit the label
Print the carton label and verify carton UID, model, quantity, unit serial, QR codes, History, and the Reprint path.
Step-by-step in Forge MES
- In Packing Configuration, create the leaf first, then create each parent with its allowed Child Container Type; selecting a child makes Max child count required.
- Choose a container-specific UID Template and sequence reset scope, then configure dimensions, weight range, and tolerance.
- Create the parent from the Packaging Dashboard by selecting the Product, parent Container Type, and completed Work Order.
- In Pack by UID, scan a finished serial, device UID, child UID, identifier, or task ID; a valid unit automatically creates the configured leaf and packs it into the parent.
- Print the carton label and verify carton UID, model, quantity, unit serial, QR codes, History, and the Reprint path.
Rules to remember
- Use a container-specific UID pattern so generated container identities do not collide with unit serials.
- A parent accepts only its configured child type, and its maximum child count is enforced.
- Only eligible production identities can be packed; source values unavailable to the label remain blank.
Configure for the client
- Match packaging hierarchy, label templates, container rules, shipment gates, ASN needs, and genealogy retention to the client's logistics and compliance requirements.
- Validate the configured behaviour with approved test data in the target environment before production use.
Ready when
- Leaf and parent types mirror the physical hierarchy.
- UID template, capacity, dimensions, weight, and tolerance are correct.
- Packing, printed label content, History, and Reprint have been checked.