These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Cross-dock Management
- Data model
The tables behind Cross-dock Management
Cross-dock Management ships with 16 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 16
- Features
- 7, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Load coordination
Loads carries load number, Carrier, dock door, seal number, arrived at and Status. Load stops references Loads and storage locations with Sequence, appointment at and Status.
Staging and custody
Cross dock matches references stock items through Item and storage locations through Location. License plate, Quantity, custody owner and Status identify the physical unit and its current context.
Stock requests
Stock requests references Organizations, team members through Owner, stock items through Item, and storage locations through both Location and Counterparty. Requested units, base unit and Revision define the reviewed quantity scope.
Lots and reservations
Stock lots references Item and storage location. Stock reservations links Lot to Request and carries Quantity, Status, expires at and Revision.
Allocation policies
Allocation policies belongs to Organizations. Channel, Priority, safety stock units, allocation rule and effective from provide policy context with the Active setting.
Stock movements
Stock movements references its parent request, organization, owner, item, location and optional lot. Signed quantity and source effect key identify the stock effect; Reverses links a compensating movement to the original.
Evidence and reconciliation
Review decisions, operation receipts and record attachments link to stock requests through Parent. Review decisions retains source revision and Reason; receipts retain operation key and failure reason.
Every table, by feature
- Load coordination3
- Staging and custody3
- Stock requests7
- Lots and reservations5
- Allocation policies5
- Stock movements6
- Evidence and reconciliation6
- Shared and settings1
- Loads
Inbound and outbound loads with carrier, dock door and seal.
- Load stops
Sequenced stops and dock appointments for a load.
Linked to Loads, Storage locations - Storage locations
Warehouses, bins, yards and cold rooms where stock is held.
Linked to Organizations
- Cross dock matches
Pallets, totes and license-plate handling units with custody.
Linked to Storage locations, Stock items - Storage locations
Warehouses, bins, yards and cold rooms where stock is held.
Linked to Organizations - Stock items
Stock keeping units with base unit, tracking mode and reorder settings.
- Stock requests
Requests to receive, move, reserve or issue stock.
Linked to Organizations, Team members, Storage locations, Stock items - Stock items
Stock keeping units with base unit, tracking mode and reorder settings.
- Storage locations
Warehouses, bins, yards and cold rooms where stock is held.
Linked to Organizations - Team members
Warehouse staff and reviewers linked to an organization and platform user.
Linked to Organizations, Users - Review decisions
Approved, rejected, returned or escalated decisions on source records.
Linked to Organizations, Team members, Stock requests - Record attachments
Documents and links attached to operational records.
Linked to Stock requests, Organizations - Operation receipts
Recorded, verified, failed or corrected operation evidence.
Linked to Organizations, Team members, Stock requests
- Stock lots
Lot or serial level inventory held at a storage location.
Linked to Stock items, Storage locations - Stock items
Stock keeping units with base unit, tracking mode and reorder settings.
- Stock reservations
Held, released or consumed reservations against eligible stock lots.
Linked to Stock lots, Stock requests - Stock requests
Requests to receive, move, reserve or issue stock.
Linked to Organizations, Team members, Storage locations, Stock items - Operation receipts
Recorded, verified, failed or corrected operation evidence.
Linked to Organizations, Team members, Stock requests
- Allocation policies
Channel allocation rules with priority and safety stock.
Linked to Organizations - Organizations
Operating organizations that own warehouses, stock and team members.
- Stock requests
Requests to receive, move, reserve or issue stock.
Linked to Organizations, Team members, Storage locations, Stock items - Review decisions
Approved, rejected, returned or escalated decisions on source records.
Linked to Organizations, Team members, Stock requests - Stock reservations
Held, released or consumed reservations against eligible stock lots.
Linked to Stock lots, Stock requests
- Stock movements
Posted signed-quantity movements that change on-hand inventory.
Linked to Organizations, Team members, Storage locations, Stock items - Stock requests
Requests to receive, move, reserve or issue stock.
Linked to Organizations, Team members, Storage locations, Stock items - Stock lots
Lot or serial level inventory held at a storage location.
Linked to Stock items, Storage locations - Stock items
Stock keeping units with base unit, tracking mode and reorder settings.
- Storage locations
Warehouses, bins, yards and cold rooms where stock is held.
Linked to Organizations - Operation receipts
Recorded, verified, failed or corrected operation evidence.
Linked to Organizations, Team members, Stock requests
- Operation receipts
Recorded, verified, failed or corrected operation evidence.
Linked to Organizations, Team members, Stock requests - Review decisions
Approved, rejected, returned or escalated decisions on source records.
Linked to Organizations, Team members, Stock requests - Record attachments
Documents and links attached to operational records.
Linked to Stock requests, Organizations - Stock requests
Requests to receive, move, reserve or issue stock.
Linked to Organizations, Team members, Storage locations, Stock items - Stock movements
Posted signed-quantity movements that change on-hand inventory.
Linked to Organizations, Team members, Storage locations, Stock items - Stock reservations
Held, released or consumed reservations against eligible stock lots.
Linked to Stock lots, Stock requests
Keys and references
Preserve Id values and relationships when migrating. Human identifiers include load, request, movement, reservation and receipt numbers, along with item SKU and location Code. A familiar display name does not replace a valid reference to the intended record.
Resolve the signed-in user through team members.User and the organization’s membership policy. Stock lots and cross dock matches carry scope through their related locations and items; confirm the access policy for every read and action. Users.User is a reference to Users and needs deliberate platform identity mapping.
Keep stock requests.Revision and review decisions.source revision aligned with the workflow’s actual decision semantics. Source effect key identifies repeatable posting effects, while operation key identifies the recorded operation. Preserve reversal references and original quantities when importing history.
Migration order
- Organization and identity. Establish Organizations and Users, then team members with valid platform mappings.
- Locations and items. Create storage locations and stock items with recognizable codes, eligibility context and consistent base units.
- Opening stock and policy. Reconcile stock lots and prepare allocation policies before creating new commitments.
- Dock context. Load Loads and load stops, then cross dock matches with valid item and location references.
- Authorized requests. Load stock requests and stock reservations with preserved quantities, states and revisions.
- Historical evidence. Preserve stock movements, reversal links, review decisions, operation receipts and record attachments without re-executing their recorded effects.
Set up Cross-dock Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.