Cross-Dock TMS: License Plate Number (LPN) Barcode Pallet Routing Solvers

Core Architecture of a Cross-Dock TMS with LPN Routing

A purpose-built cross-dock TMS must manage both the physical movement of freight and the parallel information flow. The system begins at the inbound unload door and maintains custody of each logistics unit until it is loaded on its outbound trailer.

GS1-128 License Plate Number (LPN) Generation

Upon receipt at the inbound door, each pallet receives a unique GS1-128 label containing a Serial Shipping Container Code (SSCC). The SSCC follows the GS1 standard (Application Identifier 00) and provides a globally unique identifier for the logistics unit. The label also includes human-readable fields for shipment number, destination, and contents summary.

In the TMS database, the LPN becomes the primary key for all subsequent transactions. A typical normalized schema includes:

CREATE TABLE lpn_master (
    lpn_id BIGINT PRIMARY KEY,
    sscc VARCHAR(20) UNIQUE NOT NULL,
    inbound_shipment_id BIGINT REFERENCES shipments(shipment_id),
    pallet_type VARCHAR(20),
    weight_lbs NUMERIC(8,2),
    height_inches NUMERIC(6,2),
    status VARCHAR(20) CHECK (status IN ('RECEIVED','STAGED','LOADED','DAMAGED','RETURNED')),
    create_ts TIMESTAMPTZ DEFAULT CURRENT_TIMESTAMP,
    last_scan_ts TIMESTAMPTZ
);

CREATE TABLE lpn_routing (
    routing_id BIGINT PRIMARY KEY,
    lpn_id BIGINT REFERENCES lpn_master(lpn_id),
    assigned_door VARCHAR(10),
    assigned_lane INTEGER,
    priority_score NUMERIC(6,3),
    assigned_ts TIMESTAMPTZ,
    forklift_operator_id INTEGER,
    route_sequence INTEGER
);

This structure supports rapid lookup by SSCC while maintaining full audit history through related movement transaction tables.