Identifiers
Your SKUs, barcodes and partner codes all point to one shared product record.
Identity
Resolve the right product before moving it
Attributes
Dimensions, weight, material, shelf life, lot, serial and constraints describe what execution must know.
Client scope
Client-specific mappings remain separate from the shared product.
Logistics hierarchy
From each to pallet
- Each
The consumer unit carries the sold and scanned identity.
- Inner pack
Record the quantity, barcode, dimensions and weight for this level.
- Case
The case links quantity, dimensions, weight and contained units.
- Pallet
Record units per pallet, gross weight, dimensions and stacking limits.
Handling requirements
Handling requirements your teams can check
Define requirements for
- receiving, inspection and putaway
- allocation, picking and cartonisation
- labelling, transport and compliance
Before changing an item
- check the client scope and required dimensions
- review units per packaging level and barcodes
- check the effects on packing and carrier calculations
Catalog checks
Preview, check, then import
Create products from a CSV
Preview the file, map columns to recognised fields and inspect row-level errors. The file preview does not create products.
This import creates new products. Duplicate SKUs within the file and SKUs already in the accessible catalogue are flagged, rather than overwritten.
Import checks the rows again before creating products. An invalid row blocks the batch; a failure during creation rolls back the transaction. Check the final result and imported product count.
Test a real packaging hierarchy
Bring one item, its codes, packaging levels, constraints and source systems.