Package Inputs
Data Model & Handoff Schema

Multiple Package Shipments

Data architecture for master tracking numbers and child packages in multi-piece shipments across enterprise workflows.

2026-09-08
•
Atlas Editorial Team
•
6 min read
Multiple package shipment data hierarchy and master tracking structure
Schema Unit #03 SCHEMA-PI-03-MPS

Parent-Child Data Relations in Multi-Piece Consignments

When an order requires more than one parcel, the integration pipeline must group discrete container records under a single master shipment identifier while preserving individual box dimensions and tracking IDs.

Core Structural Takeaways

  1. 01 Master Record Anchor: One parent shipment header binds all individual parcel objects together.
  2. 02 Child Tracking Uniqueness: Each discrete parcel receives its own sub-tracking number referenced to the master 1Z.
  3. 03 Weight Allocation Flow: Individual box weights must be supplied per line rather than averaged across the batch.
Read Technical Analysis All Package Inputs

Need Help Mapping Multi-Piece XML & ODBC Tables?

Review integration best practices and structural data schema requirements for multi-box dispatch.

Consult Architecture Specs
Technical Blueprint

Multi-Package Shipment Anatomy

Decoupling Single Parcels from Multi-Piece Consignments

In freight and express parcel logistics, handling multi-piece shipments (MPS) represents one of the most critical structural transitions for shipping software. An order comprising multiple boxes cannot simply be broadcast as multiple independent shipments without fracturing billing discounts, consolidated tracking, and receiver notifications.

The primary data challenge lies in maintaining the dual hierarchy: an overarching shipment entity that encapsulates shared destination, billing account, customs declaration, and service level, alongside an array of child package records detailing exact individual weights, box dimensions, and unique carrier sub-identifiers.

Systemic Dependencies

  • Header Synchronization: Any modification to recipient address or service code must cascade universally across all nested parcel records.
  • Package Indexing: Shipping applications require a zero- or one-indexed package counter (PackageCount and PackageIndex) to validate manifest completeness.
  • Label Generation Sequence: The master label (box 1 of N) establishes the lead tracking number used for shipment status aggregations and invoice reconciliation.

When systems like ERP or Warehouse Management Systems (WMS) prepare multi-package consignments for execution software like WorldShip, the payload must be structured strictly to avoid creating duplicate parent shipments or disassociated orphan parcels.

Relational Architecture: Master vs Child Entities

A relational schema for multi-piece shipments separates the transaction into two distinct tiers: the ShipmentHeader table and the ShipmentDetail (or Package) table. The header holds the primary transaction key, billing terms, carrier service code, and total aggregated shipment weight. The child table stores discrete dimensional weight properties and specific hazardous material or declared value flags per individual box.

In enterprise data architecture, treating multi-box consignments as isolated single shipments increases accessorial overhead and creates reconciliation gaps in downstream audit pipelines.

Atlas Editorial Team, Logistics Data Systems Architect

During ODBC or XML imports, shipping engines read the primary key from the header to open a transaction, and sequentially loop through the package table until the defined TotalPieces threshold is reached. Failure to match package row counts against the header count generates immediate validation rejections.

System Boundaries and Validation Specifications

Defining ownership boundaries prevents conflicting calculations between ERP, WMS, and terminal execution tools during multi-box packaging passes.

Parameter Attribute System Owner Validation Boundary
Master Tracking ID (1Z...) Shipping Execution Engine Generated on Box 1; bound to Shipment Header
Package Array & Dimensions Warehouse Management System (WMS) Explicit L x W x H per Child Record
Declared Value Distribution Enterprise Resource Planning (ERP) Per-box allocation or total shipment lump sum

Ensuring these boundary responsibilities are strictly maintained eliminates data truncation when exporting closed manifest results back to the corporate database.

Educational Inquiry

Ask About This Data Map

Share your question about package fields and the owners responsible for them.

Related Schemas

Related Documentation

View All