Logistics database schemas
Stock, locations and movements. The recurring pattern is an append-only movement log with current quantities derived from it, so any variance can be explained rather than argued about. Every one opens in the free drawDB editor in a click, and is public domain.
6 schemas here, from 11 to 13 tables (73 tables and 746 columns in total), written for PostgreSQL, SQL Server. Each one ships an ER diagram you can open and edit, a column-by-column reference, design notes explaining the trade-offs, and SQL for all six dialects. Recurring themes across the set: delivery.
Vehicle fleet management database schema
How a vehicle fleet is modelled: vehicles and drivers, licence entitlements with expiry, assignment history, downsampled telematics and fault codes, maintenance due by mileage or date, work orders and parts, fuel, inspections and incidents.
International freight forwarding database schema
A SQL Server schema for international freight: bookings and incoterms, shipments and container consolidation, multi-leg sea, air and road journeys, carrier rate contracts, customs declarations, milestone events, documents, charges and invoicing.
Last-mile delivery & route planning database schema
Delivery operations modelled properly: depots, drivers and shifts, vehicle capacity constraints, orders with time windows, routes planned per day, stops in planned and actual sequence, geofenced arrivals, failed attempts, proof of delivery and re-sequencing history.
Parcel tracking and courier network schema
A courier network schema built on an append-only scan log: shipments and the packages inside them, hubs and planned routes, scan events as the only truth, derived status, delivery attempts, exceptions, proof of delivery, and promised versus actual delivery.
Returns & RMA (reverse logistics) database schema
How returns are actually modelled: RMA authorisations and eligibility windows, versioned policies, return reasons, inbound inspection and grading, dispositions from restock to scrap, refunds against exchanges and store credit, labels, restocking fees and return-abuse signals.
Warehouse & inventory management database schema
Bin-level inventory done properly: warehouses and storage locations, lot tracking for recalls, an append-only stock movement log with derived stock levels, purchase orders and outbound shipments.