LPN nesting & container hierarchies
Model nested containers, pallets, and kits with recursive location resolution and audit-ready lineage.
Feature profile
Primary API
LPN / Containers
Primary engines
Spatial Asset Management + Provenance Ledger
Artifacts
LpnLifecycleEventLog + LocationHierarchy
Problem
Container hierarchies break the moment systems lose parent-child context.
Traditional WMS and ERP workflows flatten containers into single locations, losing lineage when items move or are re-packed. LPN nesting preserves every parent-child relationship so inventory movement, audits, and compliance checks stay accurate.
Operational impact
- Lost traceability when pallets are broken into kits
- Manual reconciliation after rework or inspection
- Inconsistent location resolution across systems
Engine
Spatial Asset Management + Provenance Ledger
Nested containers are modeled as a spatial graph with immutable lineage events, so every LPN inherits location and custody without duplicating records.
- Recursive parent-child resolution for location and custody
- Immutable ledger events for nest, move, and unnest actions
- Policy-driven validation to prevent orphaned containers
- Cross-location rollups for audits and cycle counts
Engine promise
This engine anchors the feature with reusable operational logic, ensuring every workflow stays aligned with tenant-owned data models.
Workflow
How the workflow moves from signal to action.
Step 1
Create LPNs with parent context
Issue LPNs for pallets, totes, or kits and optionally attach them to a parent container.
Step 2
Nest and unnest containers
Move child LPNs into or out of parent containers while preserving lineage history.
Step 3
Move nested hierarchies
Relocate a parent LPN and automatically resolve the location of all children.
Step 4
Audit and reconcile
Export lineage events and reconcile location hierarchies during cycle counts or inspections.
Data artifacts
Tenant-owned artifacts that power downstream systems.
Every workflow produces structured records that stay in the customer domain.
LpnLifecycleEventLog
Immutable events tracking nest, move, status, and custody changes.
LocationHierarchy
Recursive resolution of parent locations and nested container paths.
LpnHierarchy
Parent-child relationships for totes, pallets, kits, and case carts.
InventoryMovementLedger
Stock movement history tied to LPN lineage for audit trails.
LpnStatusTransitions
Allowed status changes enforced by policy and logged per tenant.
API preview
The endpoints teams integrate first.
The API surface remains consistent across industries, with schema-stable event hooks.
/api/lpns Create an LPN (optionally with parent LPN).
/api/lpns/{sqid}/nest Nest a child LPN into a parent container.
/api/lpns/{sqid}/move Move an LPN to a new location with hierarchy resolution.
/api/lpns/{child_sqid}/unnest Unnest a child LPN from its parent container.
Cross-industry examples
One engine, many instantiations.
The same operational logic adapts across manufacturing, healthcare, logistics, and regulated industries.
Healthcare
Case carts nest trays, instruments, and disposables with full custody history.
Retail
Totes roll up SKU movement while keeping store-level location accuracy.
Logistics
Pallet hierarchies track cross-dock transfers without losing lineage.
Manufacturing
Kitted subassemblies remain traceable across work orders and rework flows.
Construction
Tool kits and job-site containers roll up to project-level locations.
Field services
Truck stock totes stay linked to technician load-outs and returns.
FAQ
Answers for security, data, and rollout teams.
How do nested LPNs resolve location?
Child LPNs inherit the current location of their parent, and the hierarchy is recalculated whenever a parent moves or a child is re-nested.
Are lineage events tenant-owned?
Yes. LPN lifecycle events, hierarchy records, and audit exports remain tenant-owned and are fully exportable for compliance.
Can we prevent invalid nesting?
Policy-driven validation blocks cycles, status conflicts, and orphaned containers before they are committed.
Does unnesting preserve history?
Yes. Unnest actions append a lifecycle event, preserving the full chain of custody over time.
Explore more