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.
- Logistics ERP
- Data model
The tables behind Logistics ERP
Logistics ERP ships with 15 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
- 15
- Features
- 6
- Change it
- Add fields and tables in Proto
How the model is organised
Freight Intake
Freight orders references Parties through Customer and carries Origin, Destination, Weight, weight unit and promised at. Freight charges references its Order and stores charge type, Amount and invoice reference.
Fleet and Dispatch
Trips references Customer, Vehicle and Driver. Vehicles stores Capacity and capacity unit; People links staff to Users through User. Trips carries planned start, planned end, actual start and actual end.
Trip Execution and Evidence
Trip stops, delivery evidence and transport documents each reference Trip. Stops retain Sequence and arrival timing; documents identify verified by through People; delivery evidence carries Status and Proof.
Freight and Trip Charges
Trip charges references Trip and records charge type, Amount and Status. Keep this parent separate from freight charges.Order when importing or reconciling amounts.
Inventory and Warehouses
Inventory items carries SKU, Unit, reorder point and Active. Warehouses identifies facilities with Name, Code, City and Active.
Warehouse Transfers
Stock transfers references from warehouse, to warehouse and Item. Stock movements references Transfer, Item and Warehouse with Direction, Quantity and posted at.
Every table, by feature
- Freight Intake4
- Fleet and Dispatch6
- Trip Execution and Evidence5
- Freight and Trip Charges6
- Inventory and Warehouses4
- Warehouse Transfers4
- Freight orders
Customer freight orders awaiting movement
Linked to Parties - Parties
Customers, carriers and service providers
- Trips
Planned and executed transport trips
Linked to Parties, Vehicles, People - Freight charges
Linehaul, fuel and accessorial charges
Linked to Freight orders
- Vehicles
Fleet vehicles and capacity
- People
Staff and drivers linked to platform users
Linked to Users - Users
Users
Linked to Users - Trips
Planned and executed transport trips
Linked to Parties, Vehicles, People - Trip stops
Ordered stops on a trip
Linked to Trips - Parties
Customers, carriers and service providers
- Trips
Planned and executed transport trips
Linked to Parties, Vehicles, People - Trip stops
Ordered stops on a trip
Linked to Trips - Delivery evidence
Proof of delivery captured at completion
Linked to Trips - Transport documents
Trip paperwork and verification
Linked to Trips, People - People
Staff and drivers linked to platform users
Linked to Users
- Freight charges
Linehaul, fuel and accessorial charges
Linked to Freight orders - Freight orders
Customer freight orders awaiting movement
Linked to Parties - Trip charges
Charges billed against a trip
Linked to Trips - Trips
Planned and executed transport trips
Linked to Parties, Vehicles, People - Delivery evidence
Proof of delivery captured at completion
Linked to Trips - Parties
Customers, carriers and service providers
- Inventory items
Stock-keeping units available for freight and warehouse operations.
- Warehouses
Facilities that hold logistics inventory.
- Stock transfers
Approved warehouse-to-warehouse inventory movements.
Linked to Warehouses, Inventory items - Stock movements
Posted inbound and outbound stock effects created from transfers.
Linked to Stock transfers, Inventory items, Warehouses
- Stock transfers
Approved warehouse-to-warehouse inventory movements.
Linked to Warehouses, Inventory items - Stock movements
Posted inbound and outbound stock effects created from transfers.
Linked to Stock transfers, Inventory items, Warehouses - Inventory items
Stock-keeping units available for freight and warehouse operations.
- Warehouses
Facilities that hold logistics inventory.
Keys and references
Use stored reference identifiers to connect records. Resolve Trips.Driver through People.User for the personal assignment view. Preserve the Users.User self-reference and establish its platform identity behavior during user setup.
Freight orders.Customer and Trips.Customer both reference Parties. Identify the trip returned by the capture operation before relating it to the intended order; a shared customer and lane must not identify unrelated repeated work. Charge reconciliation must respect freight charges.Order and trip charges.Trip as separate parents.
Preserve identifier casing: the inventory records use ID, while the transport records use Id. A posted stock movement must reference the intended Transfer and Item. Its Warehouse and Direction must match the source or destination side of that transfer.
Migration order
- Users and staff. Establish platform Users and People, resolving identity references and active staff context.
- Customers and fleet. Import Parties and Vehicles, preserving party types and capacity units.
- Freight and trips. Import freight orders and establish the intended Trips with Customer, Vehicle and Driver resolved. Keep generated-trip correlation available from the capture process.
- Operating evidence. Attach trip stops, transport documents and delivery evidence to the correct trip and verifier identity.
- Charges. Import freight charges under orders and trip charges under trips, using the agreed currency convention and preserving invoice references.
- Inventory work. Establish inventory items and Warehouses before stock transfers. Preserve genuine historical stock movements under their transfer without replaying them as new postings.
Set up Logistics ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.