Data model

Explore the records behind warehouse work and plan a controlled data migration.

53 tables · 272 relationships

How the model is organised

Building and catalogs

Warehouses, Zones, Aisles, Racks, Bins, BinTypes, Locations and PackStations describe the floor. Items carries warehouse attributes for the upstream item master. Carriers, CarrierServices, PutawayRules and Users provide operating context.

Warehouses
Zones
Aisles
Racks
Bins
BinTypes
Locations
PackStations describe the floor

Stock and traceability

LicensePlates identifies containers; Inventory holds their current item, lot and serial position. ReceiptConfirmations preserves receiving evidence. StockEvents and StockMovements retain signed effects separately from current stock, while LPNMovements records container movements.

LicensePlates identifies containers; Inventory holds their current item
lot
serial position

Inbound work

Receipts and ReceiptLines describe expected deliveries. Receiving evidence records what arrived. PutawayTasks, MoveTasks and BinReplenishments direct controlled movements.

Receipts
ReceiptLines describe expected deliveries

Outbound work

Orders and OrderLines connect demand to InventoryReservations, Waves and WaveOrders. PickTasks, PickPaths and PickConfirmations lead into Cartonization and CartonizationLines, PackTasks, Cartons and CartonContents. Shipments, ShipmentOrders, ShippingLabels and ShipManifests retain shipping evidence.

Orders
OrderLines connect demand to InventoryReservations
Waves
WaveOrders

Checks and controls

CycleCounts, CycleCountTasks, CountResults, Adjustments, Exceptions and LaborTracking support accuracy and investigation. WarehousePolicies, AuthorityDelegations and LocationLocks retain the rules, authority and count boundaries used. CarrierRequests, WarehouseDeliveries and MigrationBatches preserve external request outcomes, delivery evidence and cutover approval.

CycleCounts
CycleCountTasks
CountResults
Adjustments
Exceptions
LaborTracking support accuracy
investigation

Keys and references

Keep stable source identifiers during imports, and resolve references by identifier rather than a label that may change. License-plate codes identify the physical container; inventory identity also includes item, location, lot and serial where required. Preserve the order-line assignment of picked stock through packing. Container nesting must not count the same contents twice.

Store stock effects in the item’s base unit and retain the original quantity, unit and conversion used. Operational timestamps need a defined warehouse timezone; expiry and other calendar dates retain their date-only meaning. Accepted event identities and revisions prevent a repeated import or scan from applying its stock effect again.

Migration order

Agree the source identifiers, cutoff, stock owner and destination posting rules. Inventory valuation remains with the financial system.
Load items and their base units, conversions, dimensions, control flags and usable costs for adjustment review. Resolve warehouse configuration references in stages where records depend on each other.
Load the building, locations, stations, rules, carrier accounts and services, then users and scoped authority. Verify device and connector configuration separately.
Reconcile opening stock by item, base-unit quantity, location, plate, lot, serial, expiry and hold status. Use a reviewed opening-balance mode that suppresses historical receiving and shipping notifications.
Cut over between completed waves. Import eligible unreleased orders and expected receipts after reconciling duplicate source keys. An in-flight status alone cannot restore picks, allocations, cartons or carrier commitments.
Activate the reviewed baseline once, reconcile totals with the source and financial owner, and test new receipts, movements, shipments and corrections across the cutoff. Retain the old system for history according to the agreed retention plan.

Tables

Find a table 53 tables

WarehousesPhysical distribution-center site. WMS may shadow themaster

Field	Type	Required	Details
`WarehouseCode`	text	yes
`Name`	text	yes
`Address`	text	yes	Street, city, state, ZIP
`State`	select	yes	US state code (AL, AK, AZ … WY)
`TimeZone`	text		Required IANA timezone before Active; persist operational instants in UTC and display/schedule in this timezone, including daylight-saving offsets
`ShipFromName`	text	yes	Return-address name on labels
`DefaultCarrier`	reference		→ Carriers
`Manager`	reference		→ Users (Warehouse Manager)
`Active`	toggle	yes
`Policy`	reference		→ WarehousePolicies (current effective approved control policy)
`StockRevision`	number	yes	Monotonic per-site posted stock-event sequence; positions and integration snapshots name this cutoff

UsersPeople who log into the system: managers, supervisors, leads, RFmaster

Field	Type	Required	Details
`UserCode`	text	yes	RF login / badge ID
`FullName`	text	yes
`Email`	text
`Role`	select	yes	Admin, WarehouseManager, ShiftSupervisor, ReceivingLead, WarehouseOperator, Packer, ShippingClerk, InventoryController, Viewer
`Warehouse`	reference		→ Warehouses; required for operational roles; empty means all sites only for explicitly granted Admin or Viewer scope
`Shift`	select		Day, Swing, Night
`ZoneAffinity`	reference		→ Zones (preferred zone for task assignment)
`Equipment`	select		OnFoot, PalletJack, Forklift, ReachTruck
`Active`	toggle	yes
`OnShift`	boolean	yes	Current verified shift availability, not inferred from a static Shift label
`EquipmentQualifiedUntil`	date		Required current qualification for powered-equipment tasks; local policy defines equipment evidence

ZonesFunctional zones inside a warehouse — Receiving, Bulk, Line item of Warehouses.line item

Field	Type	Required	Details
`Warehouse`	reference	yes	→ Warehouses
`ZoneCode`	text	yes
`Name`	text	yes
`ZoneType`	select	yes	Receiving, BulkReserve, ForwardPick, Pack, Ship, Quarantine, Returns, Hazmat
`HazmatPermitted`	toggle	yes
`Active`	toggle	yes

AislesAisles within a Zone — physical row of racks. Line item of Zones.line item

Field	Type	Required	Details
`Zone`	reference	yes	→ Zones
`AisleCode`	text	yes	e.g. A-01
`TraversalOrder`	number	yes	Sequence used by PickPaths
`Active`	toggle	yes

RacksVertical rack frames within an Aisle. Line item of Aisles.line item

Field	Type	Required	Details
`Aisle`	reference	yes	→ Aisles
`RackCode`	text	yes
`Side`	select		Left, Right
`Active`	toggle	yes

BinTypesCatalog of physical container specs — storage bins, totes, palletsmaster

Field	Type	Required	Details
`BinTypeCode`	text	yes
`Name`	text	yes
`LengthIn`	number	yes	Inches
`WidthIn`	number	yes	Inches
`HeightIn`	number	yes	Inches
`WeightCapacityLb`	number	yes	Pounds
`TareWeightLb`	number		Empty carton or tote weight, added to the cartonization plan
`HazmatPermitted`	toggle	yes
`UsageType`	select	yes	Storage, ShippingCarton, Tote, Pallet
`Active`	toggle	yes
`Revision`	number	yes	Version used by capacity and carton plans; existing approved work retains its snapshot
`ApprovedBy`	reference		→ Users (Warehouse Manager signs capacity/configuration changes; Admin maintains the record)
`ApprovedAt`	datetime		Required before changed capacity or geometry is activated

BinsPhysical storage bin coordinate. VelocityClass is the slot classmaster

Field	Type	Required	Details
`BinCode`	text	yes	e.g. A-01-03-B-04
`Aisle`	reference	yes	→ Aisles. Denormalized lookup from Rack.Aisle for query speed.
`Rack`	reference	yes	→ Racks
`Level`	number	yes	Vertical level 1 = floor
`Position`	number	yes	Position along the rack
`BinType`	reference	yes	→ BinTypes
`VelocityClass`	select		A, B, C (slot class; empty for doors and staging)
`IsForwardPick`	toggle	yes
`MinReplenishLevel`	number		Forward-pick faces only, in the item's base UOM
`ReplenishToLevel`	number		Forward-pick faces only
`Status`	select	yes	Active, Blocked, Maintenance
`ForwardPickItem`	reference		→ Items (required for IsForwardPick; MinReplenishLevel/ReplenishToLevel use this item BaseUOM)
`AllowMixedItems`	boolean	yes	False requires the same item across existing and pending stock
`AllowMixedLots`	boolean	yes	False requires one compatible lot, counting planned inbound capacity
`CapacityRevision`	number	yes	Changes when configuration, occupancy or reserved incoming capacity changes
`ApprovedBy`	reference		→ Users (Warehouse Manager approves configuration change; block/unblock retains its operational actor)
`ApprovedAt`	datetime		Required for active configuration changes

LocationsGeneric location join — a Bin, a ReceivingDock door, amaster

Field	Type	Required	Details
`LocationCode`	text	yes
`LocationType`	select	yes	Bin, ReceivingDock, ShippingDock, PackStation, StagingLane, ReturnsCage
`Bin`	reference		→ Bins (when LocationType = Bin)
`Warehouse`	reference	yes	→ Warehouses
`Active`	toggle	yes
`Zone`	reference		→ Zones (required for non-Bin operational locations; Bin locations derive the same warehouse/zone through the rack)
`TransitOnly`	boolean	yes	True for a transit/staging location that cannot supply fresh available-to-promise stock

ItemsThe warehouse's shadow of the upstream item master, keyed by SKU.master

Field	Type	Required	Details
`SKU`	text	yes	Item code from the ERP item master
`Description`	text	yes
`BaseUOM`	select	yes	EA, CS, LB, GAL, FT; stock and task quantities use this unit exactly once; SerialControlled requires EA
`CaseQty`	number		Base units per case
`PalletQty`	number		Base units per pallet (Ti × Hi)
`LengthIn`	number	yes	Dimensions of one base-unit handling package, in inches; unsuitable/missing package geometry holds automatic carton planning
`WidthIn`	number	yes
`HeightIn`	number	yes
`WeightLb`	number	yes	Weight per BaseUOM in pounds; must be positive for capacity/pack checks
`VelocityClass`	select	yes	A, B, C (owned here, reviewed from pick history)
`LotControlled`	toggle	yes
`SerialControlled`	toggle	yes
`ExpiryControlled`	toggle	yes
`MinShelfLifeDays`	number		Minimum remaining life at ship for allocation
`Hazmat`	toggle	yes
`HazmatClass`	text		DOT hazard class, e.g. 3, 8, 9
`FreightClass`	text		NMFC freight class for LTL bills of lading, e.g. 70, 100, 175
`UnitCost`	currency		USD per BaseUOM, used only to size adjustment approval; missing, stale or unsupported cost cannot qualify for controller confirmation
`Active`	toggle	yes
`UnitCostAsOf`	datetime		Required when UnitCost is used for threshold sizing
`UnitCostSource`	text		Upstream cost identifier and version; WMS does not own valuation
`DimensionBasis`	text		Reviewed base-unit package and allowed packing orientation; required for automatic cartonization

CarriersOutbound carrier catalog keyed by SCAC. Holds the account, the APImaster

Field	Type	Required	Details
`SCAC`	text	yes	Standard carrier alpha code, e.g. FDEG, UPSN, ODFL
`Name`	text	yes
`Mode`	select	yes	Parcel, LTL, FTL
`AccountNumber`	text		Shipper account used for labels and manifests
`APIProfile`	select		FedEx, UPS, USPSProvider, LTLTender, None; selector for a verified configured connector, not proof of connectivity
`DimDivisor`	number		Positive divisor from the configured account/service contract; no universal carrier rate constant is assumed
`PickupCutoffTime`	text		Warehouse-local HH:MM; dated cutoff instants are stored on Orders, Waves and carrier requests
`Active`	toggle	yes
`ConnectorStatus`	select	yes	Unconfigured, Testing, Active, Suspended
`ConnectorVersion`	text		Verified adapter/account version; adding an unsupported carrier requires integration work

CarrierServicesService levels a carrier offers — the ship method an order names. Line item of Carriers.line item

Field	Type	Required	Details
`Carrier`	reference	yes	→ Carriers
`ServiceCode`	text	yes	The carrier's own code, e.g. FEDEX_GROUND, 03
`Name`	text	yes	e.g. Ground, Home Delivery, 2Day, Next Day Air, Priority Mail, LTL Standard
`TransitDays`	number
`DailyCutoffTime`	text		Latest manifest close for same-day pickup on this service
`Active`	toggle	yes
`DimDivisorOverride`	decimal		Positive service/account-specific divisor, overriding carrier default
`SupportedPackageRules`	longtext		Verified service size, weight, label and tender requirements; unavailable rules block automatic release

PutawayRulesEffective directed-put-away rules. Lower numeric Priority is evaluated first; ties use RuleCode in ascending order. The first rule with a feasible compatible destination wins; a matching but infeasible fixed location never bypasses capacity or safety constraints.master

Field	Type	Required	Details
`RuleCode`	text	yes
`Name`	text	yes
`Priority`	number	yes	Lower number first; deterministic RuleCode tie-break, same order in planning and override validation
`ItemVelocityClass`	select		A, B, C, Any (matched from Items.VelocityClass to Bins.VelocityClass)
`MaxWeightLb`	number		Optional maximum loaded handling-unit weight to which this rule applies; destination capacity is independently enforced
`HazmatOnly`	toggle
`FixedItem`	reference		→ Items (route this SKU to a fixed location)
`FixedLocation`	reference		→ Locations
`TargetZoneType`	select		BulkReserve, ForwardPick, Hazmat, Quarantine
`Active`	toggle	yes
`Warehouse`	reference	yes	→ Warehouses
`Revision`	number	yes	Frozen version retained by each generated task
`ApprovedBy`	reference		→ Users (Admin)
`ApprovedAt`	datetime		Required before Active

PackStationsPack-station workstation — physical bench with a label printermaster

Field	Type	Required	Details
`StationCode`	text	yes
`Warehouse`	reference	yes	→ Warehouses
`Location`	reference	yes	→ Locations (LocationType = PackStation)
`ScalePresent`	toggle	yes
`LabelPrinterID`	text
`AssignedPacker`	reference		→ Users
`Status`	select	yes	Available, Occupied, Maintenance, Offline

LicensePlatesScannable pallet, tote, carton or cage. Its direct contents are Inventory rows; nested contents belong to child plates and are never copied onto the parent. Parent trees are acyclic, same-warehouse and physically co-located. Order-specific outbound totes/pallets retain ownership even when their pick path serves several orders.transaction

Field	Type	Required	Details
`LPN`	text	yes	Globally unique scan code
`SSCC`	text		GS1 serial shipping container code when the plate carries one (supplier pallet or outbound compliance)
`ContainerType`	select	yes	Pallet, Tote, Carton, Cage
`Warehouse`	reference	yes	→ Warehouses
`CurrentLocation`	reference		→ Locations
`ParentLPN`	reference		→ LicensePlates (self) for nesting
`Receipt`	reference		→ Receipts (the receipt an inbound plate was created under)
`Shipment`	reference		→ Shipments (the shipment an outbound tote or pallet is staged to)
`Status`	select	yes	Open, ReadyForPutaway, Stored, InTransit, Picked, Staged, Shipped, Voided
`CreatedFrom`	select	yes	Receipt, Production, Return, Repack, Outbound, System
`HoldReason`	select		Damage, QualityHold, Expired, Recall, ReturnPending
`Disposition`	select		ReleaseToStock, Rework, Scrap, ReturnToVendor
`DispositionedBy`	reference		→ Users
`CreatedAt`	datetime	yes
`ClosedAt`	datetime
`Order`	reference		→ Orders (required on outbound order-specific tote/carton/pallet; multi-order shipping parents hold child plates only)
`Revision`	number	yes	Changes with location, nesting, hold, contents or state
`LastEvent`	reference		→ StockEvents
`CreatedNumber`	text	yes	Human-readable creation identifier, distinct from scannable LPN

LPNMovementsImmutable container custody event: physical location, nesting, close and void. Item/quantity/serial transfers are separately recorded in StockMovements, linked through the same StockEvent. Nesting never duplicates child stock on the parent.transaction

Field	Type	Required	Details
`MovementNumber`	text	yes
`LicensePlate`	reference	yes	→ LicensePlates
`EventType`	select	yes	Created, Moved, Nested, Unnested, Picked, Staged, Closed, Voided, Shipped
`FromLocation`	reference		→ Locations
`ToLocation`	reference		→ Locations
`ParentLPN`	reference		→ LicensePlates (parent after a nesting change)
`TaskType`	select		Receiving, Putaway, Move, Pick, Pack, Ship, Replenishment, CycleCount, Adjustment
`TaskNumber`	text		The task that caused the movement
`Operator`	reference	yes	→ Users
`OccurredAt`	datetime	yes
`StockEvent`	reference	yes	→ StockEvents
`PreviousParentLPN`	reference		→ LicensePlates (parent before change)
`Status`	select	yes	Recorded; immutable custody evidence

InventoryCurrent stock position projected from signed posted StockMovements. A position key includes Warehouse, Item, Location, LicensePlate, LotNumber, SerialNumber, ReceiptConfirmation provenance, OrderLine ownership and Status. Existing identity fields are immutable; transfer creates or uses the destination identity and records paired movements. Zero-balance rows remain for traceability.transaction

Field	Type	Required	Details
`Item`	reference	yes	→ Items
`Warehouse`	reference	yes	→ Warehouses
`Location`	reference	yes	→ Locations
`LicensePlate`	reference		→ LicensePlates
`LotNumber`	text
`SerialNumber`	text
`ExpiryDate`	date
`QuantityOnHand`	number	yes	Sum of posted StockMovements.QuantityDelta for this exact position, in BaseUOM; never negative
`QuantityAllocated`	number	yes	Sum of signed InventoryReservations.QuantityDelta at Stage Hard for this exact position
`QuantityAvailable`	formula	yes	fx: eligible unowned QuantityOnHand − active Soft − active Hard reservation balances; 0 for order-owned, blocked/held/expired/damaged/quarantine, transit-only or count-locked stock. Never negative.
`Status`	select	yes	Available, Quarantine, Damaged, Expired, Held; status is part of exact stock identity and changes through a controlled transfer
`LastMovementAt`	datetime
`InventoryNumber`	text	yes	Stable position identity, retained after its balance reaches zero
`ReceiptConfirmation`	reference		→ ReceiptConfirmations (required for received stock; opening stock links its reviewed baseline confirmation)
`ReceiptLine`	reference		→ ReceiptLines (matches receipt confirmation origin)
`OrderLine`	reference		→ OrderLines (physical order ownership after pick; never fresh ATP)
`Version`	number	yes	Monotonic version of quantity/status/identity effects used by tasks and count snapshots
`QuantitySoftReserved`	decimal	yes	Sum of signed Soft reservation entries for this position
`QuantityPickedReserved`	decimal	yes	Sum of signed Picked claims on order-owned tote or unverified carton/pallet stock; these units remain unavailable to other orders
`QuantityPackedReserved`	decimal	yes	Sum of signed Packed reservation entries on the verified outbound position

ReceiptsInbound receipt header — one trailer, one ASN, one production runtransaction

Field	Type	Required	Details
`ReceiptNumber`	text	yes
`Warehouse`	reference	yes	→ Warehouses
`ReceiptType`	select	yes	PurchaseOrder, Production, CustomerReturn, Transfer, OpeningBalance; OpeningBalance is migration-only and never normal procurement receipt delivery
`Supplier`	text		Supplier name or code from the purchase order
`PONumber`	text		External PO from scm-procurement
`ASNNumber`	text		Inbound ASN ID
`RMANumber`	text		Return authorization for a CustomerReturn receipt
`CarrierSCAC`	text		Inbound carrier, e.g. FDEG, UPSN, ODFL
`TrailerNumber`	text
`TrailerType`	select		DryVan53, DryVan48, Container40, Container20, StraightTruck, Parcel
`SealNumber`	text		Checked against the ASN at arrival
`Door`	reference		→ Locations (LocationType = ReceivingDock)
`ScheduledArrivalAt`	datetime
`ActualArrivalAt`	datetime
`ReceivingLead`	reference		→ Users
`Status`	select	yes	ScheduledArrival, Arrived, Receiving, Closed, Cancelled
`ClosedAt`	datetime		UTC instant when Receiving Lead froze reviewed receipt totals; close does not wait for put-away
`ASNData`	attachment		Original ASN payload with stable external line identifiers; required for ASN import
`ASNRevision`	text		Source version used by the idempotent parser
`SourceSystem`	text	yes	Origin namespace
`SourceRecordID`	text	yes	Unique source receipt/ASN identity
`SourceRevision`	number	yes	Immutable input revision; same key with conflicting content is rejected
`ContentDigest`	text	yes	Canonical intake header and expected lines
`ClosedBy`	reference		→ Users (Receiving Lead)
`CloseEvent`	reference		→ StockEvents
`ImportMode`	select	yes	Live, HistoricalBaseline
`MigrationBatch`	reference		→ MigrationBatches (required for OpeningBalance/HistoricalBaseline)

ReceiptLinesStable expected line and immutable receiving evidence for a receipt. ReceivedQty sums signed posted ReceiptConfirmations.BaseQty for this exact line, independent of present LPN stock. AcceptedQty is separately tracked for the procurement handoff. Same-item lines remain distinct through source line identity, lot/serial and original confirmation. Line item of Receipts.line item

Field	Type	Required	Details
`Receipt`	reference	yes	→ Receipts
`Item`	reference	yes	→ Items
`UOM`	select	yes	EA, CS, PL; ordered display unit. ExpectedQty/ReceivedQty and all operational quantities are BaseUOM; BaseUnitsPerUOM is frozen once
`ExpectedQty`	number	yes	Expected base-unit quantity = ExpectedEnteredQty × BaseUnitsPerUOM; never convert again
`ReceivedQty`	number	yes	Sum of signed posted ReceiptConfirmations.BaseQty for this ReceiptLine; picking, moving, packing and shipping never change it
`VarianceQty`	formula	yes	fx: ReceivedQty − ExpectedQty
`LotNumber`	text
`ExpiryDate`	date
`Disposition`	select		ReturnToStock, Quarantine, Scrap, ReturnToVendor (returns and damaged lines)
`Status`	select	yes	Expected, Receiving, Received, Short, Over, Damaged
`LineNumber`	number	yes	Stable unique line within receipt
`SourceLineID`	text	yes	External expected line identity, or local generated identity
`ExpectedEnteredQty`	decimal	yes	Original amount in displayed UOM
`BaseUnitsPerUOM`	decimal	yes	Positive frozen conversion factor; 1 when UOM equals Item.BaseUOM
`AcceptedQty`	decimal	yes	Sum of posted StockMovements.AcceptanceDelta for this receipt line; receipt acceptance is separate from later inventory use
`AcceptanceEvidence`	attachment		Receiving Lead disposition/variance evidence at close

PutawayTasksOperator task to move a received LPN from a ReceivingDock to itstransaction

Field	Type	Required	Details
`TaskNumber`	text	yes
`Receipt`	reference		→ Receipts
`LicensePlate`	reference	yes	→ LicensePlates
`FromLocation`	reference	yes	→ Locations (typically ReceivingDock)
`ToLocation`	reference	yes	→ Locations (suggested Bin)
`ActualLocation`	reference		→ Locations (the bin confirmed when the operator overrode the suggestion)
`OverrideReason`	select		BinFull, BinBlocked, WrongBinType, OperatorChoice
`RuleApplied`	reference		→ PutawayRules
`AssignedTo`	reference		→ Users
`Status`	select	yes	Open, Released, InProgress, Completed, Cancelled
`StartedAt`	datetime
`CompletedAt`	datetime
`RuleRevision`	number	yes	Frozen PutawayRules version
`LPNRevision`	number	yes	Expected plate contents/location revision; changes invalidate the suggestion
`ReservedWeightLb`	decimal	yes	Incoming loaded weight reserved at ToLocation
`ReservedVolumeIn3`	decimal	yes	Incoming occupied volume reserved at ToLocation
`CapacityReservedUntil`	datetime	yes	Capacity claim expiry; expiry requires a fresh feasible suggestion
`CompletionEvent`	reference		→ StockEvents (one atomic move effect)
`OverrideCheckedBy`	reference		→ Users (operator; same full constraint checks as planning)
`OverrideCheckedAt`	datetime		Required with ActualLocation

MoveTasksInternal LPN or loose-quantity move — consolidation, reslotting,transaction

Field	Type	Required	Details
`TaskNumber`	text	yes
`LicensePlate`	reference		→ LicensePlates
`Item`	reference		→ Items (when moving a loose quantity without a plate)
`Quantity`	number
`FromLocation`	reference	yes	→ Locations
`ToLocation`	reference	yes	→ Locations
`Reason`	select	yes	Consolidation, Reslotting, PutawayCorrection, ExceptionFix, Other
`RequestedBy`	reference		→ Users
`AssignedTo`	reference		→ Users
`Status`	select	yes	Open, PendingApproval, Released, InProgress, Completed, Cancelled
`CompletedAt`	datetime
`SourceInventory`	reference		→ Inventory (required for loose-quantity move; exact lot/serial/provenance)
`SourceVersion`	number		Expected position version before moving
`SerialNumber`	text		Exact serial for a loose serialized move; quantity must equal 1
`StockLock`	reference		→ LocationLocks (exclusive source movement claim)
`ReservedWeightLb`	decimal		Target incoming weight reservation
`ReservedVolumeIn3`	decimal		Target incoming volume reservation
`CapacityReservedUntil`	datetime		Expired target claim must be recomputed
`ApprovedBy`	reference		→ Users (Warehouse Manager for Reslotting)
`ApprovedAt`	datetime		Required for a reslotting release
`CompletionEvent`	reference		→ StockEvents

BinReplenishmentsTask that brings stock from reserve to a forward-pick face:transaction

Field	Type	Required	Details
`ReplenishmentNumber`	text	yes
`Item`	reference	yes	→ Items
`UOM`	select	yes	EA, CS
`FromLocation`	reference	yes	→ Locations (reserve Bin)
`ToLocation`	reference	yes	→ Locations (forward-pick Bin)
`LicensePlate`	reference		→ LicensePlates (reserve plate drawn from)
`Wave`	reference		→ Waves (when TriggerEvent = WaveDemand)
`RequestedQty`	number	yes	Positive BaseUOM requested transfer, no more than movable source stock and compatible target capacity after existing tasks
`MovedQty`	number		BaseUOM quantity moved by posted completion events; retries do not add again
`AssignedTo`	reference		→ Users
`TriggerEvent`	select	yes	BelowMin, WaveDemand, ScheduledTopOff, Manual
`Status`	select	yes	Open, InProgress, Completed, Cancelled
`CompletedAt`	datetime
`SourceInventory`	reference	yes	→ Inventory (one exact source lot/serial/provenance per task)
`SourceVersion`	number	yes	Expected source version
`StockLock`	reference		→ LocationLocks (movement claim; Soft reservations follow the stock, Hard pick claims block relocation)
`DemandKey`	text	yes	Unique active warehouse + item + destination + demand source/revision; overlapping BelowMin and WaveDemand subtract already planned replenishments
`BaseUnitsPerUOM`	decimal	yes	Frozen display conversion; stored task quantities are already base units
`ReservedWeightLb`	decimal	yes	Incoming target weight reservation
`ReservedVolumeIn3`	decimal	yes	Incoming target volume reservation
`CapacityReservedUntil`	datetime	yes	Recheck expired claim
`CompletionEvent`	reference		→ StockEvents

OrdersOutbound order header. May shadow / sync from sales / CRM /transaction

Field	Type	Required	Details
`OrderNumber`	text	yes
`Customer`	text	yes	Account name (masked from floor roles)
`ShipToName`	text	yes	Consignee
`ShipToAddress`	text	yes
`ShipToState`	select	yes	US state code
`CarrierService`	reference	yes	→ CarrierServices (the ship method on the order)
`Carrier`	reference	yes	→ Carriers (derived from the service at intake; wave grouping key)
`ShipCutoffAt`	datetime	yes	Wave engine groups by this
`Priority`	select	yes	Standard, Expedite, NextDay
`Warehouse`	reference	yes	→ Warehouses
`Status`	select	yes	New, Hold, ReadyToWave, Waved, Picking, Packing, Shipped, Cancelled
`HoldReason`	select		CreditHold, AddressHold, CustomerRequest, Backorder
`OriginalShipCutoffAt`	datetime	yes	Immutable first accepted ship promise; operational rescheduling cannot erase lateness
`SourceSystem`	text	yes	Origin namespace
`SourceRecordID`	text	yes	Unique external order identity
`SourceRevision`	number	yes	Frozen fulfillment scope; changes after claim require reviewed cancel/replan of affected unshipped work
`ContentDigest`	text	yes	Canonical ordered quantities, addresses, carrier/service and cutoff
`ActiveWave`	reference		→ Waves (unique active Planning/Released/InProgress membership, claimed before planner emits work)
`PlanningClaimKey`	text		Stable order + source revision claim key; duplicate runs return the same membership
`FulfilledAt`	datetime		Actual latest tender instant when all non-cancelled quantities have shipped
`ImportMode`	select	yes	Live, HistoricalBaseline
`MigrationBatch`	reference		→ MigrationBatches
`CancellationEvidence`	attachment		Authorised upstream request and warehouse review of shipped, labelled and physically owned stock
`CancelledBy`	reference		→ Users (Warehouse Manager authorising local unwind after upstream cancellation)
`CancelledAt`	datetime		After local work/reservations and carrier requests reconcile

OrderLinesPer-item line on an outbound Order. Quantities are stored in the Line item of Orders.line item

Field	Type	Required	Details
`Order`	reference	yes	→ Orders
`LineNumber`	number	yes
`Item`	reference	yes	→ Items
`UOM`	select	yes	EA, CS, PL
`OrderedQty`	number	yes	Original accepted base-unit demand for this source revision
`AllocatedQty`	number	yes	Sum of active signed Soft + Hard + Picked + Packed reservations for this line; shipped quantity is separate
`PickedQty`	number	yes	Sum of active Picked + Packed reservation balances plus net ShippedQty; unpick reduces this without inventing another order
`ShippedQty`	number	yes	Net base units issued by evidenced ShipmentTender stock events for this line, less authorised tender reversal before an erroneous handover is corrected
`LotNumber`	text		If the customer restricts the lot
`Status`	select	yes	Open, Allocated, Picking, Picked, Shipped, Short, Cancelled
`EnteredQty`	decimal	yes	Original ordered amount in UOM
`BaseUnitsPerUOM`	decimal	yes	Frozen positive input conversion; operational quantities are base units once
`CancelledQty`	decimal	yes	Approved unshipped quantity cancelled after owned stock is safely unpacked/unpicked and reservations released
`UnreservedQty`	formula	yes	fx: OrderedQty − CancelledQty − ShippedQty − AllocatedQty; nonnegative
`PackedQty`	decimal	yes	Active Packed reservation balance plus ShippedQty
`SourceLineID`	text	yes	Stable source line identity

WavesPick wave header — a batch of outbound Orders released togethertransaction

Field	Type	Required	Details
`WaveNumber`	text	yes
`Warehouse`	reference	yes	→ Warehouses
`ShipCutoffAt`	datetime	yes
`Carrier`	reference		→ Carriers (wave grouping key)
`ZoneFilter`	select		ForwardPick, BulkReserve, Mixed
`ReleasedAt`	datetime
`ReleasedBy`	reference		→ Users
`OrderCount`	number	yes	Rollup
`LineCount`	number	yes	Rollup
`PickedLineCount`	number	yes	Rollup of PickTasks Completed
`OpenReplenishmentCount`	number	yes	Rollup of this wave demand replenishments still needed and not Completed; cancelled tasks require a replacement or reviewed feasible alternate route
`Status`	select	yes	Planning, Released, InProgress, Completed, Cancelled
`PlanRevision`	number	yes	Frozen reviewed membership, inventory claims and carton plan version
`PlanDigest`	text	yes	Exact release packet
`PlanningKey`	text	yes	Idempotent warehouse + scheduling window + batch identity
`Delegation`	reference		→ AuthorityDelegations (required for Shift Supervisor release)
`ReleaseEvent`	reference		→ StockEvents (atomic Soft→Hard conversion and task creation)
`ReplenishmentOverrideReason`	longtext		Required when releasing with open demand; feasible hard allocations must already exist
`CartonPlanOverrideEvidence`	attachment		Admin-supported manual plan evidence; cannot bypass contents, compatibility or capacity checks

WaveOrdersOrders included in a Wave. Line item of Waves.line item

Field	Type	Required	Details
`Wave`	reference	yes	→ Waves
`Order`	reference	yes	→ Orders
`AddedAt`	datetime	yes
`Status`	select	yes	Planned, Released, InProgress, Completed, RemovedFromWave
`ClaimKey`	text	yes	Unique active Order + SourceRevision; enforced before wave creation
`OrderRevision`	number	yes	Claimed immutable order scope
`RemovedAt`	datetime		Required on removal with reservation/task reconciliation
`RemovalReason`	text		Reason and affected unshipped work disposition

PickTasksPick assignment per exact source Inventory identity and OrderLine. One task identifies one lot/serial/provenance row; split demand creates additional tasks. An operator path may span orders, but each destination tote or outbound pallet belongs to one order.transaction

Field	Type	Required	Details
`TaskNumber`	text	yes
`Wave`	reference	yes	→ Waves
`OrderLine`	reference	yes	→ OrderLines
`FromLocation`	reference	yes	→ Locations
`LicensePlate`	reference		→ LicensePlates (source plate)
`ToLicensePlate`	reference		→ LicensePlates (the tote, carton or outbound pallet the pick is placed in)
`Item`	reference	yes	→ Items
`UOM`	select	yes	EA, CS, PL
`RequestedQty`	number	yes
`PickedQty`	number	yes
`LotNumber`	text
`AssignedTo`	reference		→ Users (Warehouse Operator)
`PickPath`	reference		→ PickPaths
`Sequence`	number		Position within the path
`Status`	select	yes	Open, Released, InProgress, Completed, Short, Hold, Cancelled
`CompletedAt`	datetime
`SourceInventory`	reference	yes	→ Inventory (matches item, location, source plate, lot and serial)
`SourceVersion`	number	yes	Version checked with the hard claim
`SerialNumber`	text		Required for serialized task; RequestedQty = 1
`ReservationKey`	text	yes	Stable hard-claim identity; reservation entries tie it to this task
`TaskKey`	text	yes	Unique wave release + order line + source identity + split sequence
`BaseUnitsPerUOM`	decimal	yes	Frozen display conversion; RequestedQty/PickedQty are base units
`StartedAt`	datetime		Start of assigned execution
`CompletionEvent`	reference		→ StockEvents

PickPathsGenerated walk-path per operator per Wave — sequence of PickTaskstransaction

Field	Type	Required	Details
`PathNumber`	text	yes
`Wave`	reference	yes	→ Waves
`Operator`	reference	yes	→ Users
`Strategy`	select	yes	SShape, ReturnPath, LargestGap, Manual
`TaskCount`	number	yes
`EstimatedSteps`	number		Heuristic walk length
`Status`	select	yes	Generated, InProgress, Completed

PickConfirmationsImmutable submitted scan evidence for a task, exact source position and order-owned destination. Wrong bin/item/serial or duplicate scan has no stock effect. Confirmed partial quantity is posted once and a final shortage releases only the unpicked hard balance.transaction

Field	Type	Required	Details
`ConfirmationNumber`	text	yes
`PickTask`	reference	yes	→ PickTasks
`ScannedLPN`	text		Source plate scanned
`ScannedToLPN`	text		The tote, carton or pallet the quantity was placed in
`ScannedBin`	text	yes
`ScannedItem`	text	yes
`ConfirmedQty`	number	yes
`Operator`	reference	yes	→ Users
`ScannedAt`	datetime	yes
`Outcome`	select	yes	Confirmed, Short, WrongBin, WrongItem
`SourceInventory`	reference	yes	→ Inventory
`DestinationInventory`	reference		→ Inventory (order-owned resulting position after a valid pick)
`SerialNumber`	text		Scanned serial, required when controlled
`EnteredQty`	decimal	yes	Scanned display quantity
`BaseUnitsPerUOM`	decimal	yes	Frozen conversion used once for ConfirmedQty
`StockEvent`	reference	yes	→ StockEvents (stable scanner/device event identity)
`ReversesConfirmation`	reference		→ PickConfirmations (controlled unpick/correction)
`Status`	select	yes	Recorded, Posted, Rejected; Posted is immutable

CartonizationVersioned per-order handling-unit plan, using a carton or full-pallet type and durable CartonizationLines. Automatic fit is a heuristic checked against permitted orientation, contents, dimensions, weight and compatibility; a reviewed manual plan can resolve missing automatic fit without bypassing physical constraints.transaction

Field	Type	Required	Details
`CartonizationNumber`	text	yes
`Order`	reference	yes	→ Orders
`BundleSeq`	number	yes	1 for single-carton; N for multi-carton
`SelectedCartonType`	reference	yes	→ BinTypes (ShippingCarton for PlanKind Carton; Pallet for PlanKind Pallet)
`TotalWeightLb`	number	yes	Base-unit content weight plus handling-unit tare; missing/unusable inputs hold planning
`DimensionalWeightLb`	number	yes	Configured dimensions divided by positive account/service divisor where applicable; freight uses its verified carrier weight rules
`BillableWeightLb`	formula	yes	fx: MAX(TotalWeightLb, DimensionalWeightLb)
`MultiCartonSplit`	toggle	yes
`Status`	select	yes	Planned, Confirmed, Voided
`PlanKind`	select	yes	Carton, Pallet
`PlanRevision`	number	yes	Frozen bundle contents version
`OrderRevision`	number	yes	Order source revision used
`PlanDigest`	text	yes	Exact quantities, dimensions, orientation, weights and carrier rules
`PlanningMethod`	select	yes	Automatic, ReviewedManual
`ReviewedBy`	reference		→ Users (Warehouse Manager; Admin supplies configuration override evidence where needed)
`ReviewedAt`	datetime		Required for ReviewedManual
`Evidence`	attachment		Manual arrangement and physical checks

CartonsPhysical carton produced — the unit that gets a tracking numbertransaction

Field	Type	Required	Details
`CartonNumber`	text	yes
`Order`	reference	yes	→ Orders
`Cartonization`	reference		→ Cartonization
`CartonType`	reference	yes	→ BinTypes
`LicensePlate`	reference		→ LicensePlates (carton LPN)
`Shipment`	reference		→ Shipments
`SSCC`	text		GS1-128 serial shipping container code for compliance labels
`ContentsWeightLb`	number	yes
`TrackingNumber`	text		Filled by shipping-label workflow
`ShipLabelURL`	text		PDF/ZPL URL
`Status`	select	yes	Open, Packed, LabelGenerated, Staged, Manifested, Shipped, Voided
`PackedAt`	datetime
`ShippedAt`	datetime
`Revision`	number	yes	Contents, dimensions, service or address change invalidates label request and pack verification
`PackedEvent`	reference		→ StockEvents
`TenderEvent`	reference		→ StockEvents
`ActiveLabelRequest`	reference		→ CarrierRequests (same exact carton revision)
`LabelStatus`	select	yes	NotRequested, Pending, Uncertain, Ready, Failed, VoidPending, Voided; separate from physical Carton.Status

CartonContentsImmutable per-confirmation content quantity for an exact order line, stock provenance and serial. Current packed contents sum posted transfer/reversal entries; scanning content and transferring the same stock are one event, not independent additions. Line item of Cartons.line item

Field	Type	Required	Details
`Carton`	reference	yes	→ Cartons
`OrderLine`	reference	yes	→ OrderLines
`Item`	reference	yes	→ Items
`Quantity`	number	yes	Signed BaseUOM packed amount; negative only on a linked authorised unpack/correction entry
`LotNumber`	text
`SerialNumber`	text
`Inventory`	reference	yes	→ Inventory (exact order-owned carton position)
`SourceInventory`	reference	yes	→ Inventory (tote source identity)
`ReceiptConfirmation`	reference		→ ReceiptConfirmations (origin)
`PlanLine`	reference	yes	→ CartonizationLines
`StockEvent`	reference	yes	→ StockEvents
`ReversesContent`	reference		→ CartonContents (unpack/correction; original retained)
`PackedAt`	datetime	yes	Actual scan instant
`Status`	select	yes	Posted; compensating entries retain original history

PackTasksPer-Carton task at a PackStation, opened when the picked tote fortransaction

Field	Type	Required	Details
`TaskNumber`	text	yes
`Order`	reference	yes	→ Orders
`FromLicensePlate`	reference		→ LicensePlates (the picked tote scanned to open the task)
`Carton`	reference		→ Cartons (required for carton plan; null for verified full-pallet plan)
`PackStation`	reference	yes	→ PackStations
`AssignedTo`	reference		→ Users (Packer)
`ScaleWeightLb`	number		Captured from scale
`WeightVarianceLb`	formula		fx: ScaleWeightLb − Cartonization.TotalWeightLb using this task Plan; policy compares absolute deviation
`HoldReason`	select		WeightVariance, WrongItem, MissingItem, DamagedGoods, CartonMissing, MissingScale, MissingDimensions, CarrierUncertain
`Status`	select	yes	Open, InProgress, Verified, LabelPrinted, Completed, Held, Cancelled
`StartedAt`	datetime
`CompletedAt`	datetime
`Plan`	reference	yes	→ Cartonization (exact order bundle and revision)
`OutputLicensePlate`	reference	yes	→ LicensePlates (carton or full-pallet output; same Order)
`Policy`	reference	yes	→ WarehousePolicies (frozen weight tolerance version)
`VerifiedAt`	datetime		Required on Verified, with complete contents and weight checks
`VerifiedBy`	reference		→ Users (assigned Packer)
`HoldReleasedBy`	reference		→ Users (Warehouse Manager)
`HoldReleasedAt`	datetime		Required for human hold release
`HoldReleaseEvidence`	attachment		Required reason and corrected re-verification; never waive missing/wrong stock
`VerificationEvent`	reference		→ StockEvents
`WeightEvidence`	attachment		Scale observation or independently reviewed external-scale evidence; missing weight never becomes a zero-variance pass

ShipmentsOutbound shipment — the freight unit handed to the carrier for onetransaction

Field	Type	Required	Details
`ShipmentNumber`	text	yes
`Warehouse`	reference	yes	→ Warehouses
`Carrier`	reference	yes	→ Carriers
`CarrierService`	reference	yes	→ CarrierServices
`Manifest`	reference		→ ShipManifests
`ShipToName`	text	yes	Consignee
`ShipToAddress`	text	yes
`TrackingNumber`	text		Lead carton's tracking number for parcel
`PRONumber`	text		Carrier's progressive number for LTL
`BOLNumber`	text		Bill of lading number for LTL and FTL
`FreightClass`	text		Reviewed applicable classification from commodity details and configured carrier/routing rules; never assume highest item class is universally correct
`OrderCount`	number	yes	Rollup of ShipmentOrders
`TotalCartons`	number	yes	Rollup of Cartons
`TotalPallets`	number	yes	Count of outermost pallet handling units tendered for the shipment; nested child inventory is not counted as additional parent stock
`TotalWeightLb`	number	yes
`ShipDate`	date		Warehouse-local calendar date derived from TenderedAt after actual handover; not used for within-day on-time tests
`Status`	select	yes	Pending, LabelsReady, Staged, Manifested, Shipped, Delivered, Voided
`Revision`	number	yes	Frozen shipment contents and carrier/account/address scope
`TenderedAt`	datetime		Actual evidenced carrier handover instant; receipt/transmission time stored separately
`TenderedBy`	reference		→ Users (Shipping Clerk)
`TenderEvidence`	attachment		Signed pickup, driver scan or reconciled carrier acknowledgement required before Shipped
`TenderEvent`	reference		→ StockEvents (one authoritative issue of exact verified contents)
`DeliveredAt`	datetime		Carrier delivery evidence; no second warehouse quantity issue
`ContentsDigest`	text		Frozen order-line/lot/serial/provenance and LPN tree at manifest close

ShipmentOrdersOrders carried by a Shipment. One row for a parcel shipment; several Line item of Shipments.line item

Field	Type	Required	Details
`Shipment`	reference	yes	→ Shipments
`Order`	reference	yes	→ Orders
`AddedAt`	datetime	yes
`Status`	select	yes	Planned, Packed, Shipped, Removed

ShippingLabelsEach generated carrier document — a parcel label per Carton, atransaction

Field	Type	Required	Details
`LabelNumber`	text	yes
`Carton`	reference		→ Cartons (parcel)
`Shipment`	reference		→ Shipments (LTL BOL)
`Carrier`	reference	yes	→ Carriers
`CarrierService`	reference	yes	→ CarrierServices
`LabelType`	select	yes	Parcel, BOL, Compliance
`TrackingNumber`	text		Required for Parcel; BOL/compliance documents use DocumentReference and need not invent a parcel tracking number
`LabelURL`	text	yes	PDF/ZPL location
`GeneratedAt`	datetime	yes
`Voided`	toggle	yes	True only after confirmed remote void or a supported reconciliation decision; timeout is not void success
`VoidReason`	text		Audit reason required to void
`VoidedAt`	datetime
`Request`	reference	yes	→ CarrierRequests (confirmed remote result for exact document revision)
`DocumentReference`	text	yes	Carrier label ID, BOL reference or compliance document identity
`Status`	select	yes	Generated, VoidPending, Voided, Superseded
`ReplacesLabel`	reference		→ ShippingLabels (confirmed prior void/supersession)

ShipManifestsDaily carrier manifest — closed at end-of-day per Warehouse, pertransaction

Field	Type	Required	Details
`ManifestNumber`	text	yes
`Warehouse`	reference	yes	→ Warehouses
`Carrier`	reference	yes	→ Carriers
`CarrierAccount`	text	yes	Shipper account or mode the close runs for, e.g. FedEx Express, FedEx Ground
`ManifestDate`	date	yes
`ShipmentCount`	number	yes	Rollup of Shipments
`TotalWeightLb`	number	yes	Rollup
`ClosedBy`	reference		→ Users (Shipping Clerk)
`ClosedAt`	datetime
`Status`	select	yes	Open, Closed, Transmitted; Transmitted requires a recorded accepted delivery, and none of these alone proves physical tender
`Revision`	number	yes	Membership and totals freeze at close; corrections require a new reviewed revision
`ContentsDigest`	text		Exact shipment revisions and LPN contents authorised at close
`TransmitRequest`	reference		→ CarrierRequests (manifest submission and acknowledgement)
`TransmittedAt`	datetime		Actual destination acknowledgement time
`TenderedShipmentCount`	number	yes	Shipments with independent evidenced TenderEvent, separate from ShipmentCount

CycleCountsCount cycle header — ABC cadence or exception-driven.transaction

Field	Type	Required	Details
`CycleNumber`	text	yes
`Warehouse`	reference	yes	→ Warehouses
`BinScope`	select	yes	SingleBin, ZoneSweep, AisleSweep, ABCAll, ExceptionDriven
`FrequencyABC`	select		A_Weekly, B_Monthly, C_Quarterly, OneOff
`ScheduledFor`	date	yes
`Coordinator`	reference	yes	→ Users (Inventory Controller)
`TaskCount`	number	yes	Rollup
`VarianceCount`	number		Rollup
`Status`	select	yes	Scheduled, InProgress, PendingReview, Adjusted, Closed, Cancelled
`Policy`	reference	yes	→ WarehousePolicies (effective count cadence, tolerance and threshold)
`CreatedAt`	datetime	yes	Scheduling event instant
`ScheduleKey`	text	yes	Unique site + scope + scheduled occurrence; repeated scheduler does not duplicate active counts

CycleCountTasksPer-Bin count assignment within a CycleCount. Line item of CycleCounts.line item

Field	Type	Required	Details
`CycleCount`	reference	yes	→ CycleCounts
`Location`	reference	yes	→ Locations
`Item`	reference		→ Items (optional restriction to one SKU)
`LotNumber`	text
`AssignedTo`	reference		→ Users
`Status`	select	yes	Assigned, Counting, Counted, Recount, Adjusted, Closed, Cancelled
`CountedAt`	datetime
`Lock`	reference		→ LocationLocks (Count lock for this entire location before physical count)
`SnapshotAt`	datetime		Physical-count snapshot instant
`SnapshotRevision`	number		Warehouse stock revision retained for audit only; unrelated-bin increments do not invalidate unchanged counted positions
`StartedAt`	datetime		Actual physical count start
`ClosedAt`	datetime		Completion after correction/review and lock release
`SnapshotPositions`	attachment		Frozen complete position-ID/version set for the locked location, including expected zero/count identities
`SnapshotDigest`	text		Digest of the locked-location identity/version set; new/missing identities invalidate this count

CountResultsExact-position physical count evidence at a locked location, including serial and origin. Every expected positive stock identity is counted, including explicit zeros; discovered stock has a documented new identity. Recounts are independent immutable results under a valid lock and version snapshot.transaction

Field	Type	Required	Details
`ResultNumber`	text	yes
`CycleCountTask`	reference	yes	→ CycleCountTasks
`Item`	reference	yes	→ Items
`LicensePlate`	reference		→ LicensePlates
`LotNumber`	text
`CountSequence`	number	yes	1 = first count, 2 = recount
`ExpectedQty`	number	yes	Base-unit on-hand snapshot while the task lock is valid; never a later live balance
`CountedQty`	number	yes	Nonnegative physical BaseUOM quantity; serialized identity is exactly 0 or 1
`VarianceQty`	formula	yes	fx: CountedQty − ExpectedQty
`VariancePercent`	formula		fx: VarianceQty / ExpectedQty × 100 when ExpectedQty > 0; 0 when both quantities are 0; otherwise null and Discovery flag forces review
`CountedBy`	reference	yes	→ Users
`CountedAt`	datetime	yes
`Status`	select	yes	Recorded, RecountRequired, Confirmed, Superseded
`Inventory`	reference		→ Inventory (required for an existing position; null only for discovered identity before approved creation)
`SerialNumber`	text		Required for serial-controlled stock
`ExpiryDate`	date		Required for expiry-controlled discovered stock
`ReceiptConfirmation`	reference		→ ReceiptConfirmations (existing origin; discovered stock requires reviewed provenance before available release)
`InventoryVersion`	number		Version at SnapshotAt; stale or expired lock requires recount
`SnapshotAt`	datetime	yes	Count snapshot instant
`Discovery`	boolean	yes	ExpectedQty = 0 and CountedQty > 0; never treated as within-percent tolerance
`Supersedes`	reference		→ CountResults (recount retains first result)
`ConfirmedBy`	reference		→ Users (Inventory Controller)
`ConfirmedAt`	datetime		Required for Confirmed

AdjustmentsInventory adjustments from cycle count, damage, or exceptiontransaction

Field	Type	Required	Details
`AdjustmentNumber`	text	yes
`Warehouse`	reference	yes	→ Warehouses
`Location`	reference	yes	→ Locations
`Item`	reference	yes	→ Items
`LicensePlate`	reference		→ LicensePlates
`LotNumber`	text
`QuantityBefore`	number	yes	Exact versioned on-hand quantity at approved correction snapshot
`QuantityAfter`	number	yes	Nonnegative corrected BaseUOM balance under the same valid count/position lock
`QuantityDelta`	formula	yes	fx: QuantityAfter − QuantityBefore
`ValueDelta`	formula		fx: ABS(QuantityDelta) × CostSnapshotUSD per BaseUOM; unusable cost blocks posting pending reviewed cost evidence, never defaults to 0
`Source`	select	yes	CycleCount, Damage, ExceptionResolution, ManualCorrection, ReturnsDisposition
`CountResult`	reference		→ CountResults
`Exception`	reference		→ Exceptions
`Reason`	text
`RequestedBy`	reference	yes	→ Users
`ApprovedBy`	reference		→ Users (Warehouse Manager for above threshold, discovered/identity-changing, reserved/order-owned stock, or exceptional cost review; independent of requester and counter)
`ApprovedAt`	datetime
`PostedAt`	datetime
`Status`	select	yes	Draft, PendingApproval, Approved, Posted, Rejected
`Inventory`	reference		→ Inventory (exact existing identity; new discovered identity is created only in approved posting)
`SerialNumber`	text		Exact serial; positive final position unique and quantity 1
`ExpiryDate`	date		Required controlled expiry for discovered stock
`ReceiptConfirmation`	reference		→ ReceiptConfirmations (provenance where known)
`InventoryVersion`	number		Expected version; mismatch blocks posting and requires recount/reapproval
`StockLock`	reference	yes	→ LocationLocks (valid correction lock)
`Policy`	reference	yes	→ WarehousePolicies (frozen thresholds)
`CostSnapshotUSD`	decimal		Usable nonnegative USD cost per BaseUOM; required before posting
`CostAsOf`	datetime		Cost effective instant
`CostEvidence`	attachment		Required for missing/stale upstream cost or a reviewed alternative
`ConfirmedBy`	reference		→ Users (Inventory Controller for eligible below-threshold confirmation)
`ConfirmedAt`	datetime		Actual confirmation time
`ApprovalBasis`	select	yes	ControllerConfirmation, ManagerApproval
`ApprovalDigest`	text		Exact identity, quantity, version, cost and policy reviewed; edits invalidate decision
`PostingEvent`	reference		→ StockEvents (one signed correction, with affected reservations resolved atomically)

ExceptionsOperator-flagged issues — short pick, damage, wrong item, nottransaction

Field	Type	Required	Details
`ExceptionNumber`	text	yes
`ExceptionType`	select	yes	ShortPick, Damage, WrongItem, NotFound, Overage, BinBlocked, EquipmentDown
`Warehouse`	reference	yes	→ Warehouses
`Location`	reference		→ Locations
`LicensePlate`	reference		→ LicensePlates
`Item`	reference		→ Items
`QuantityImpacted`	number
`RelatedPickTask`	reference		→ PickTasks
`RelatedReceipt`	reference		→ Receipts
`Photo`	attachment		Taken on the scanner at the moment of raising
`RaisedBy`	reference	yes	→ Users
`RaisedAt`	datetime	yes
`Severity`	select	yes	Low, Medium, High, Critical
`Resolution`	select		Recount, Adjustment, Reroute, ReturnToVendor, EscalatedQuality, NoActionRequired
`ResolvedBy`	reference		→ Users
`ResolvedAt`	datetime
`Status`	select	yes	Open, Routed, InTriage, Resolved, Cancelled
`Inventory`	reference		→ Inventory (exact affected position)
`RelatedPackTask`	reference		→ PackTasks
`Owner`	reference		→ Users (scope-eligible triage owner)
`ResolutionEvidence`	attachment		Required before Resolved; authority decisions/postings remain in their linked records
`RoutingEvent`	reference		→ StockEvents (idempotent follow-up creation; cannot create duplicate reallocation/count work)

LaborTrackingOperator on-task time per task type, linked to the task by type andtransaction

Field	Type	Required	Details
`EntryNumber`	text	yes
`Operator`	reference	yes	→ Users
`Warehouse`	reference	yes	→ Warehouses
`TaskType`	select	yes	Receiving, Putaway, Move, Pick, Pack, Ship, CycleCount, Replenishment, Exception, Idle
`TaskNumber`	text		The task of that type the time was booked to
`StartedAt`	datetime	yes
`EndedAt`	datetime
`DurationMinutes`	formula		fx: (EndedAt − StartedAt) in minutes using UTC instants; negative/zero durations excluded from rate calculations
`UnitsHandled`	number		Confirmed base-unit operational effects only; task retries/voids excluded; unlike units are not silently summed
`Status`	select	yes	Open, Closed
`SourceEvent`	reference		→ StockEvents (unique relevant handling event)
`TimeSource`	select	yes	TaskClock, ReviewedManual
`CorrectionReason`	text		Required for reviewed manual corrections; original timing retained

ReceiptConfirmationsImmutable receiving scan and correction evidence per exact expected line and physical identity. Posted quantities record what arrived; later storage, allocation and shipment never rewrite them. A correction is a signed linked confirmation and stock event against still-correctable stock, not an edit.transaction

Field	Type	Required	Details
`ConfirmationNumber`	text	yes	Unique receiving confirmation
`ReceiptLine`	reference	yes	→ ReceiptLines
`LicensePlate`	reference	yes	→ LicensePlates
`Item`	reference	yes	→ Items (matches expected line)
`LotNumber`	text		Required when controlled
`SerialNumber`	text		Required when controlled; each positive receipt confirmation represents one base unit
`ExpiryDate`	date		Required when controlled
`EnteredQty`	decimal	yes	Signed original quantity in UOM; negative only for approved correction
`UOM`	text	yes	Captured display unit
`BaseUnitsPerUOM`	decimal	yes	Frozen positive factor from the receipt line; serial scans use base unit factor 1
`BaseQty`	decimal	yes	EnteredQty × BaseUnitsPerUOM, applied once; negative correction no greater than unreversed source amount
`AcceptedBaseQty`	decimal	yes	Signed accepted quantity in this initial/correction event, bounded by its received magnitude
`StockStatus`	select	yes	Available, Quarantine, Damaged, Expired, Held; unaccepted quantity cannot become Available
`ReceivedBy`	reference	yes	→ Users (Receiving Lead or assigned Warehouse Operator)
`ScannedAt`	datetime	yes	Actual event time
`StockEvent`	reference	yes	→ StockEvents
`ReversesConfirmation`	reference		→ ReceiptConfirmations (required for correction)
`Status`	select	yes	Draft, Posted, Rejected; Posted payload immutable
`Evidence`	attachment		Damage, serial, receipt variance or authorised correction support
`ApprovedBy`	reference		→ Users (Receiving Lead approves variance/correction and acceptance decision before posting)
`ApprovedAt`	datetime		Required when acceptance or correction needs lead review

StockEventsAuthoritative immutable business event packet. The source key/digest detects replay and conflict. Committing Applied is atomic with every stock movement, reservation leg, task state and document effect; external deliveries are independently acknowledged. Event immutability is an implementation requirement, not an observed runtime guarantee.transaction

Field	Type	Required	Details
`EventNumber`	text	yes	Human-readable event identifier
`EventKey`	text	yes	Unique SourceSystem + SourceEventID + SourceRevision + EventType
`SourceSystem`	text	yes	Origin namespace, including scanner device or upstream source
`SourceEventID`	text	yes	Stable original action identity, reused on retry
`SourceRevision`	number	yes	Frozen source revision
`EventType`	select	yes	Receipt, ReceiptCorrection, Putaway, Move, Replenishment, WaveClaim, WaveRelease, Pick, Unpick, Pack, Unpack, PackVerify, PalletVerify, Adjustment, Disposition, ShipmentTender, TenderReversal, ReceiptClose, ManifestClose, ExceptionRoute, OpeningBalance, OrderCancel, ReservationChange
`Warehouse`	reference	yes	→ Warehouses
`OccurredAt`	datetime	yes	Actual effective UTC business instant
`RecordedAt`	datetime	yes	When evidence reached WMS
`Actor`	reference	yes	→ Users (scoped person or configured restricted integration identity)
`PayloadDigest`	text	yes	Same key/same digest returns prior result; different digest is a conflict
`Payload`	attachment	yes	Frozen exact identities, expected versions, signed legs and resulting revision IDs
`ReversesEvent`	reference		→ StockEvents (authorised compensating event; original stays Applied)
`Status`	select	yes	Staged, Applied, Rejected
`AppliedAt`	datetime		After successful atomic local effects
`StockRevision`	number		Resulting Warehouses.StockRevision
`ImportMode`	select	yes	Live, HistoricalBaseline
`MigrationBatch`	reference		→ MigrationBatches
`Evidence`	attachment		Required release, correction or actual handover support

StockMovementsImmutable signed stock posting leg against an exact Inventory identity. Internal transfers have equal opposite base-unit legs for the same item/lot/serial/origin; receipts, approved adjustments and tender are explicit external quantity changes. AcceptanceDelta tracks receiving acceptance separately from current warehouse on-hand. Line item of StockEvents.line item

Field	Type	Required	Details
`MovementNumber`	text	yes	Unique event + line identity
`StockEvent`	reference	yes	→ StockEvents
`Inventory`	reference	yes	→ Inventory (immutable identity)
`QuantityDelta`	decimal	yes	Signed BaseUOM stock effect; inbound positive, outbound negative, zero only for acceptance/verification without physical change
`AcceptanceDelta`	decimal	yes	Signed accepted-receipt quantity for ReceiptLine; only receipt/correction or authorised receiving disposition can change it
`ReceiptLine`	reference		→ ReceiptLines
`ReceiptConfirmation`	reference		→ ReceiptConfirmations (origin preserved through all movement)
`OrderLine`	reference		→ OrderLines (required for pick/pack/tender ownership)
`PickTask`	reference		→ PickTasks
`PackTask`	reference		→ PackTasks
`Adjustment`	reference		→ Adjustments
`Shipment`	reference		→ Shipments
`FromInventory`	reference		→ Inventory (paired source for destination transfer leg)
`ReversesMovement`	reference		→ StockMovements (compensating effect, bounded by original remaining effect)
`BalanceBefore`	decimal	yes	Version-checked original stock balance
`BalanceAfter`	decimal	yes	BalanceBefore + QuantityDelta; nonnegative
`PostedAt`	datetime	yes	Atomic effective posting time
`Status`	select	yes	Posted; original and compensating legs are both retained

InventoryReservationsOne immutable signed reservation ledger for order stock. Soft, Hard, Picked and Packed are mutually exclusive stages for the same units, not additive claims on their transition. Current stage balances are sums of posted entries by order line, exact position and reservation key; a transfer releases the old stage/position and claims the new in one event.transaction

Field	Type	Required	Details
`ReservationNumber`	text	yes	Unique event + leg identifier
`ReservationKey`	text	yes	Stable order-line claim or split identity, recorded in event payload
`StockEvent`	reference	yes	→ StockEvents
`OrderLine`	reference	yes	→ OrderLines
`Inventory`	reference	yes	→ Inventory (eligible source for Soft/Hard; order-owned tote/unverified output for Picked, verified output for Packed)
`Stage`	select	yes	Soft, Hard, Picked, Packed
`QuantityDelta`	decimal	yes	Signed BaseUOM claim or release; each aggregated stage/key balance stays nonnegative
`Wave`	reference		→ Waves
`PickTask`	reference		→ PickTasks
`PackTask`	reference		→ PackTasks
`ReversesReservation`	reference		→ InventoryReservations (linked release/correction)
`PostedAt`	datetime	yes	Atomic claim instant
`Status`	select	yes	Posted; releases are negative entries, not deletion or status changes

CartonizationLinesDurable planned order-line contents for one carton or pallet bundle. Active bundle quantities exactly cover the order quantity chosen for this fulfillment revision. A pack scan must match both its bundle and the picked stock owner; an undifferentiated multi-order tote is never inferred to belong to one order. Line item of Cartonization.line item

Field	Type	Required	Details
`PlanLineNumber`	text	yes	Stable line identifier within bundle revision
`Cartonization`	reference	yes	→ Cartonization
`OrderLine`	reference	yes	→ OrderLines (same order as plan)
`Item`	reference	yes	→ Items
`PlannedQty`	decimal	yes	Positive BaseUOM quantity; no conversion at pack
`RequiredLot`	text		Customer lot condition inherited from order
`Orientation`	text	yes	Reviewed orientation/packing instruction
`ContentWeightLb`	decimal	yes	PlannedQty × valid base-unit item weight
`Status`	select	yes	Planned, Confirmed, Voided
`CreatedAt`	datetime	yes	Plan generation instant

WarehousePoliciesVersioned site control policy prepared by Admin and approved by Warehouse Manager. Counts, adjustment value and pack tolerances have explicit units and defaults; a missing policy blocks the governed action instead of granting an unlimited allowance.master

Field	Type	Required	Details
`PolicyNumber`	text	yes	Unique site/version
`Warehouse`	reference	yes	→ Warehouses
`Revision`	number	yes	Immutable effective policy revision
`EffectiveFrom`	datetime	yes	UTC instant
`EffectiveTo`	datetime		Optional end instant
`CountToleranceQty`	decimal	yes	Nonnegative absolute BaseUOM units, applied per item/position; both quantity and percent tests must pass
`CountTolerancePct`	decimal	yes	Nonnegative absolute percentage when expected quantity is positive
`AdjustmentApprovalUSD`	decimal	yes	Nonnegative absolute value ceiling for eligible controller confirmation; equality is within threshold
`CostMaxAgeDays`	number	yes	Nonnegative allowed age of cost snapshot; stale/missing cost requires independently reviewed usable cost
`PackWeightToleranceLb`	decimal	yes	Nonnegative absolute scale deviation allowed
`PackWeightTolerancePct`	decimal	yes	Nonnegative percent of positive planned gross weight; permitted deviation is max(absolute, percentage allowance)
`CountLockMinutes`	number	yes	Positive maximum renewable count lock duration; lapse invalidates count snapshot
`CapacityClaimMinutes`	number	yes	Positive planned destination reservation duration
`PreparedBy`	reference	yes	→ Users (Admin)
`ApprovedBy`	reference		→ Users (Warehouse Manager other than PreparedBy)
`ApprovedAt`	datetime		Required before Active
`Status`	select	yes	Draft, Active, Superseded, Expired

AuthorityDelegationsTime-limited Warehouse Manager authority for a named Shift Supervisor to release defined waves at one site. Delegation cannot expand stock, count, adjustment or manifest permissions. The actual release retains actor, grant and exact reviewed plan.master

Field	Type	Required	Details
`DelegationNumber`	text	yes	Unique authority grant
`Warehouse`	reference	yes	→ Warehouses
`Delegator`	reference	yes	→ Users (Warehouse Manager)
`Delegate`	reference	yes	→ Users (Shift Supervisor, different from Delegator)
`Action`	select	yes	WaveRelease
`EffectiveFrom`	datetime	yes	UTC beginning
`EffectiveTo`	datetime	yes	UTC exclusive end; required and later than start
`Scope`	longtext	yes	Allowed shift, carrier/zone and any wave limits
`GrantedAt`	datetime	yes	Actual grant instant
`RevokedAt`	datetime		Stops later releases without rewriting earlier valid evidence
`Status`	select	yes	Active, Expired, Revoked

LocationLocksExplicit physical-count or source-movement claim. Count locks cover the location, block stock movements and new allocation there, and remain valid through correction/release. Movement locks can cover a source position; Soft reservations may follow an authorised transfer but Hard pick claims must be released/replanned first.transaction

Field	Type	Required	Details
`LockNumber`	text	yes	Unique location/scope claim
`Warehouse`	reference	yes	→ Warehouses
`Location`	reference	yes	→ Locations
`Inventory`	reference		→ Inventory (Movement lock; null means entire location)
`Purpose`	select	yes	Count, Movement, Correction
`CycleCountTask`	reference		→ CycleCountTasks
`MoveTask`	reference		→ MoveTasks
`Replenishment`	reference		→ BinReplenishments
`Owner`	reference	yes	→ Users (eligible task owner)
`AcquiredAt`	datetime	yes	Atomic claim time
`ExpiresAt`	datetime	yes	Lease expiry; expired work cannot post without revalidation/recount
`ReleasedAt`	datetime		After reviewed work completion or cancellation
`Status`	select	yes	Active, Released, Expired
`SnapshotRevision`	number	yes	Warehouse revision at claim for audit; commit checks this locked scope and its position versions, not unrelated warehouse activity

CarrierRequestsStable carrier operation request and reconciliation state. A lost or timed-out response is Uncertain, not a confirmed failure. The original request identity is reused only when the verified connector supports idempotency; otherwise query/reconcile before another potentially billable creation.transaction

Field	Type	Required	Details
`RequestNumber`	text	yes	Human-readable operation identity
`RequestKey`	text	yes	Unique account + operation + carton/shipment/manifest identity + revision
`Operation`	select	yes	LabelCreate, LabelVoid, ManifestSubmit, TenderRegister, BOLCreate
`Carrier`	reference	yes	→ Carriers
`CarrierService`	reference		→ CarrierServices
`Carton`	reference		→ Cartons
`Shipment`	reference		→ Shipments
`Manifest`	reference		→ ShipManifests
`SourceRevision`	number	yes	Frozen content revision
`RequestDigest`	text	yes	Exact account, ship-from/to, service, dimensions, weight and contents
`RequestedBy`	reference	yes	→ Users
`RequestedAt`	datetime	yes	Original request instant
`LastAttemptAt`	datetime		Most recent transport attempt
`RemoteRequestID`	text		Carrier lookup/idempotency identity
`RemoteDocumentID`	text		Confirmed returned label/BOL/manifest identifier
`Status`	select	yes	Prepared, Sent, Uncertain, Succeeded, Failed, VoidPending, Voided
`ReconciledBy`	reference		→ Users (Shipping Clerk for uncertain create/void result)
`ReconciledAt`	datetime		Required for manual reconciliation decision
`Evidence`	attachment		Carrier response, lookup, confirmed rejection/void or support evidence
`ReplacesRequest`	reference		→ CarrierRequests (new request only after prior outcome/void resolved)
`Attempts`	number	yes	Transport attempt count; printing is not another carrier request

WarehouseDeliveriesPer-event destination delivery and acknowledgement. Quantity effects and destination reporting are separate: event-mode inventory consumers post each signed event once, while position snapshots replace their read-only operational mirror at a declared revision and never create an additional movement.transaction

Field	Type	Required	Details
`DeliveryNumber`	text	yes	Unique delivery identity
`StockEvent`	reference		→ StockEvents (required for Event mode)
`Warehouse`	reference	yes	→ Warehouses
`Destination`	select	yes	Procurement, Production, OrderSystem, FinancialInventory, Quality, Carrier, Notification
`Mode`	select	yes	Event, PositionSnapshot, Document
`DeliveryKey`	text	yes	Unique destination + mode + event key or snapshot revision
`PositionRevision`	number		Required for position snapshot; receiver rejects stale cutoffs
`PayloadDigest`	text	yes	Frozen signed effects or full authoritative snapshot
`Status`	select	yes	Pending, Sending, Acknowledged, Failed, Uncertain, Suppressed
`Attempts`	number	yes	Transport retries, never local reposting
`AcknowledgedAt`	datetime		Required for Acknowledged
`ExternalReference`	text		Destination receipt/cutoff reference
`LastError`	longtext		Failure or uncertainty detail
`ReconciledBy`	reference		→ Users (Admin with operational owner review)

MigrationBatchesReviewed between-waves cutover. Stock is reconciled by base unit, location, plate, lot, serial and provenance; historical operations are nonposting evidence. Only eligible unreleased orders are activated and re-reserved. In-flight work must be completed or explicitly unwound/reconciled before this baseline, never recreated from a status alone.transaction

Field	Type	Required	Details
`BatchNumber`	text	yes	Unique source cutover batch
`Warehouse`	reference	yes	→ Warehouses
`SourceSystem`	text	yes	Origin namespace
`CutoffAt`	datetime	yes	UTC boundary agreed with procurement, inventory, order and carrier systems
`SourceDigest`	text	yes	Frozen inventory/order extract identity
`PreparedBy`	reference	yes	→ Users (Admin)
`ReviewedBy`	reference		→ Users (Inventory Controller other than PreparedBy)
`ApprovedBy`	reference		→ Users (Warehouse Manager)
`ApprovedAt`	datetime		Required before activation
`OpeningReceipt`	reference		→ Receipts (ReceiptType OpeningBalance, HistoricalBaseline)
`OpeningEvent`	reference		→ StockEvents (one signed baseline posting)
`ReconciliationEvidence`	attachment	yes	Per-item/UOM, plate, lot, serial, hold and zero-negative checks; original source IDs; open-order and carrier reconciliation
`StockRevision`	number		Final activated baseline cutoff
`Status`	select	yes	Staged, Validated, Approved, Activated, Rejected
`ActivatedAt`	datetime		Set once with OpeningEvent

ERP•AI workspace

Start now Warehouse Management

Create your ERP.AI account and get started with Proto.

Start now Download agent

Previous · reference 2 of 6Reports and dashboards Next · reference 4 of 6Integrations

Warehouse Management

Modules

Warehouse Management

Processes

Warehouse Management

Industries

Warehouse Management

Reference

Warehouse Management

Data model

How the model is organised

Building and catalogs

Stock and traceability

Inbound work

Outbound work

Checks and controls

Keys and references

Migration order

Tables

Start now Warehouse Management

Warehouse Management

Modules

Warehouse Management

Processes

Warehouse Management

Industries

Warehouse Management

Reference

Data model

How the model is organised

Building and catalogs

Stock and traceability

Inbound work

Outbound work

Checks and controls

Keys and references

Migration order

Tables

Start now Warehouse Management

Your Privacy, Your Choice

Manage Your Cookie Preferences