Logistics and distribution
Data inventory template for logistics and distribution (WMS, TMS, ERP, EDI)
By SourceX Editorial · Updated
Short answer
A logistics data inventory template needs one row per record type and seven columns: system, record type, years of history, volume, owner, rights notes and a personal data flag. Fill it from system reports and admin screens rather than memory, and mark unknowns as unknown. A finished sheet answers most fit-check questions without moving any files.
Key takeaways
- Use one row per record type, not per system; a WMS alone may hold receipts, orders, adjustments and billing events.
- Years and volume come from reports and admin screens, and estimates are labeled as estimates.
- Rights notes name the governing document, such as a warehouse services agreement or an EDI trading partner agreement.
- The personal data flag shows where drivers, consumers or employees appear, so preparation can be planned early.
- Retired systems and EDI archives get their own rows, because they often hold the deepest history.
What columns does the template need?#
The logistics data inventory template needs seven core columns: system, record type, years of history, volume, owner, rights notes and personal data flag. Two optional columns, export route and linking keys, help once a review moves past the first pass.
| Column | What to enter | Example entry |
|---|---|---|
| System | Product name and whether it is live, retired or archived | WMS (live); prior WMS (retired, read-only) |
| Record type | One business record family per row | Outbound orders with lines and ship confirmations |
| Years of history | First and last year still accessible | Current system since go-live; earlier years in an archive |
| Volume | Rough count from a system report, labeled if estimated | Order lines per year from the WMS activity report |
| Owner | Person who can answer questions and approve access | Director of warehouse operations |
| Rights notes | Contracts or terms that govern use | Client warehouse agreements; data clause varies by client |
| Personal data flag | Yes, no or unknown, plus who appears | Yes: consumer ship-to names and addresses |
| Export route (optional) | How the records can be extracted | Saved report to CSV, or the vendor's API |
| Linking keys (optional) | IDs shared with other rows | Order number, client code, PRO number |
Which systems belong on the list?#
Every system that holds operational history belongs on the list, including retired ones and the inboxes where exceptions get handled. Logistics companies tend to under-list, because the WMS and TMS feel like the whole story when they are only the transaction layer.
- WMS: receipts, orders, picks, adjustments, cycle counts, returns and billing events.
- TMS or brokerage platform: load records, carrier selection, rate confirmations, tracking updates and accessorial charges.
- ERP and accounting, such as NetSuite, Epicor, Infor, SAP Business One or Acumatica: quotes, orders, invoices, credits and payments.
- EDI translator and VAN archives: purchase orders, ship notices, load tenders, status messages and invoices.
- Telematics, such as Samsara: trips, hours of service and safety events.
- CRM and help desk: customer cases, escalations and account notes.
- Shared inboxes, claims files and document imaging for bills of lading and proofs of delivery.
- Retired systems, exports and backups still held on servers or in cloud storage.
Example rows for a 3PL and a distributor#
Example rows show how one system splits into several record types, each with its own rights and privacy answers. The entries below are illustrative placeholders; real rows carry your own system names and report figures.
Notice that the same WMS appears twice with different answers. Client order data and the 3PL's own adjustment notes sit in one system but can fall under different rules.
| System | Record type | Years | Volume | Owner | Rights notes | Personal data |
|---|---|---|---|---|---|---|
| WMS | Outbound orders and ship confirmations | Since go-live | Order lines per year, activity report | Warehouse operations director | Client agreements govern; check each client | Yes: consumer ship-to details |
| WMS | Inventory adjustments with reason codes | Since go-live | Adjustments per year, audit report | Inventory control manager | Client inventory data; internal notes are yours | Low: user IDs only |
| TMS | Loads with exception notes and claims | Current TMS plus retired archive | Loads per year, load report | Brokerage operations lead | Shipper and carrier confidentiality terms | Yes: driver and contact names in notes |
| ERP | Credit memos with reason codes | Since last ERP migration | Credits per year, AR report | Controller | Customer pricing confidentiality | Low: buyer contacts |
| EDI archive | Purchase orders, ship notices, invoices | As retained by the provider | Documents per year, provider portal | IT manager | Trading partner agreements | Low |
| Shared inbox | Customer escalations | Mailbox retention setting | Threads per year, mail admin | Customer service manager | Customer contracts; employee notices | Yes: names and contact details |
How do you fill in years and volume without exporting anything?#
Years and volume can be filled in from system reports, admin screens and vendor portals, so no records leave the system at this stage. Most WMS, TMS and ERP platforms have activity or audit reports that show counts by period, and EDI providers usually show document history in their portals.
Write down what each number measures: order headers or order lines, loads or stops, threads or messages. When a figure is a guess, mark it as an estimate and name who gave it; unknown is a valid answer and better than a confident wrong one.
Watch where history stops. A current system's first year is usually its go-live date, and earlier years may sit in a retired system, a backup or nowhere at all, which makes that boundary one of the most useful facts in the sheet.
How should rights notes and personal data flags be written?#
Rights notes and personal data flags should be short, factual and tied to a named document or a named group of people. They are prompts for counsel and for preparation work, not legal conclusions.
For rights, name the governing documents: client warehouse services agreements, shipper contracts, carrier agreements, EDI trading partner agreements, software vendor terms and employee notices. Where the answer differs by client, say so and keep a separate client-level list.
For personal data, say who appears: consumers on ship-to labels, drivers in dispatch notes, buyers on purchase orders, employees in email. Mark sensitive classes such as driver qualification or testing records as excluded rather than inventorying them in detail.
Illustrative: a regional 3PL completes its inventory#
Illustrative: a fictional regional 3PL with several warehouses runs one WMS, a small brokerage desk on a separate TMS and NetSuite for accounting. The COO assigns the template to the IT manager with one instruction: fill it from reports only.
The first draft brings three surprises. A retired WMS still holds history from before the current go-live, the EDI provider keeps document history further back than anyone assumed, and claims correspondence lives in one manager's mailbox rather than in the TMS.
The COO adds rows for the retired WMS and the claims mailbox, asks the controller to list client agreements by data clause, and flags consumer ship-to data on the ecommerce clients' rows. The finished sheet becomes the input to a metadata-only fit check.
What happens after the inventory is finished?#
A finished inventory feeds a fit check, a rights review and a scope decision, and it stays useful even if no licensing follows. The same sheet supports system retirements, retention policy work and diligence in a sale of the company.
SourceX uses an inventory like this in the Supply step of the SourceX five-step transaction, and only metadata is shared during that initial assessment. Rows that move forward carry their rights notes into the Rights step and their personal data flags into Preparation, and the sheet later supports the provenance section of the SourceX Evidence Packet.
Frequently asked questions
Should EDI archives be a separate row?
Yes. EDI archives often hold the cleanest record of purchase orders, ship notices, load tenders and invoices, with reference numbers that link other systems. They may be retained by a provider rather than by you, so note who holds them and how far back they go.
How detailed should record types be?
Detailed enough that each row has one owner, one rights answer and one personal data answer. If a row needs two different answers, split it. Going too fine is also a problem, so avoid listing individual database tables or report names at this stage.
Who should fill in the template?
An IT manager or systems analyst usually drafts it from reports, and each row's business owner checks the record types and years. The controller or counsel adds rights notes. Keep one person responsible for the sheet so versions do not multiply across inboxes.
Should retired systems be included?
Always. Retired WMS, TMS and ERP systems often hold the deepest history a company has, and they are the easiest to lose when a server is decommissioned or a vendor contract ends. Record where the data now sits and whether it can still be read.
Is the inventory shared with a buyer?
Not at the first stage. The inventory is an internal document used for a fit check, which collects metadata such as system names, years and record families. Anything shared later is summarized, approved by you and covered by confidentiality terms.
Related resources
- InsightHow do I de-identify dispatch logs for AI training?
- InsightOwner-operator data in dispatch records: privacy and rights
- InsightCan freight brokerage email threads be licensed for AI training?
- SolutionData partnerships between businesses and AI developers
- IndustryBPO & contact centers data
- IndustryRecruiting & staffing data
See if your company qualifies
A short company assessment. No data uploads are needed.