Logistics and distribution
Data inventory for 3PLs and distributors: WMS, TMS and EDI
By SourceX Editorial · Updated
Short answer
A data inventory for a 3PL or distributor lists each record family in its WMS, TMS, ERP and EDI systems, plus one column that settles most later questions: whose data it is. Mark every row client-owned, own process record or mixed. Your own exception, slotting and routing records are usually the place to start.
Key takeaways
- Add an ownership lane to every row: client-owned, own process record or mixed, plus third-party confidential for distributors.
- EDI error logs and acknowledgments are often missing from inventories even though they record real exceptions.
- Mixed rows, such as adjustments on client SKUs, can sometimes be used once client and item identities are removed, subject to contract review.
- An inventory can be completed from admin screens and system reports without exporting any records.
- Retired systems belong on the inventory, because they often hold the longest history.
What a logistics data inventory needs beyond system names#
A logistics data inventory needs to say, for each record family, where it lives, how much history exists and whose data it is. Generic inventories stop at the first two, which leaves the hardest question for later, when contracts with shippers and 3PL clients start deciding what can be used.
Use one row per record family, not per system. A WMS holds receipts, picks, cycle counts and adjustments, and each has a different owner profile and value. Seven columns cover it: system, record family, years accessible, approximate volume, ownership lane, personal data flag and export route.
The ownership lane takes one of three values. Client-owned means the record mainly describes a client's goods, orders or customers and is governed by that client's contract. Own process record means it describes how your company works. Mixed means both, and needs a decision. Distributors usually need a fourth value, third-party confidential, for supplier price files, rebate agreements and other material received under confidentiality terms.
Pre-filled WMS rows#
Pre-filled WMS rows give most 3PLs a starting point to correct rather than a blank sheet. Rename them to match your system's record names and delete what you do not hold.
Notice how few WMS rows are purely your own. That is normal for a contract warehouse, and it is why the slotting, task and adjustment rows deserve careful notes.
| Record family | Typical contents | Ownership lane | Notes |
|---|---|---|---|
| Client item master | Client SKUs, descriptions, dimensions, lot and expiry rules | Client-owned | Usually client confidential information |
| Receipts and ASN matches | Expected versus received, overages, shortages, damage | Mixed | Discrepancy handling is your process; quantities are client facts |
| Inventory balances by location | On-hand, allocated and held quantities | Client-owned | Rarely useful outside the client relationship |
| Cycle counts and adjustments | Variances, reason codes, approver, notes | Mixed | Reason codes and notes show your judgment |
| Pick, pack and ship tasks | Task times, user IDs, equipment, short picks | Own process record | Employee user IDs need masking |
| Slotting and replenishment changes | Location moves, velocity reviews, min and max changes | Own process record | Strong evidence of operating expertise |
| Outbound orders and consignees | Ship-to names, addresses, order lines | Client-owned | Often contains consumer personal data |
Pre-filled TMS and carrier rows#
Pre-filled TMS rows sort transport records the same way, with one difference: in brokerage and managed transportation, both the shipper's contract and the carrier agreement can apply to the same load.
Telematics and ELD data may sit with the carrier or a vendor rather than with you. List it anyway, with a note on who holds it and under what terms, so nobody assumes it is available.
| Record family | Typical contents | Ownership lane | Notes |
|---|---|---|---|
| Load tenders and bookings | Origin, destination, dates, equipment, shipper | Mixed | Shipper identity removed before any outside use |
| Carrier selection and rate decisions | Carriers considered, rates, chosen carrier, reason | Own process record | Rates may be confidential under carrier agreements |
| Tracking and status events | Pickup, in-transit, delivery, delay reasons | Mixed | Delay reason codes and notes carry the value |
| Appointments and dwell | Scheduled versus actual times, detention | Own process record | Facility names may need removal |
| Freight bills and accessorial disputes | Invoice lines, disputes, adjustments | Mixed | Dispute notes record your reasoning |
| Claims | Loss and damage reports, photos, settlements | Mixed | Claimant contact details need removal |
EDI rows most inventories miss#
EDI rows are the ones most logistics inventories miss, because the data often lives with a translator or a managed EDI provider and staff think of it as plumbing. The transaction history, and especially the error log, is a record of real exceptions between trading partners.
Check how long your EDI provider keeps transaction archives and error logs, and whether you can export them in bulk. Trading partner agreements may restrict use of transaction data, so mark most EDI rows mixed until those terms have been read.
- Warehouse shipping orders (940) and shipping advices (945): what clients asked for versus what left the dock.
- Stock transfer shipment and receipt advices (943 and 944), and inventory adjustment advices (947).
- Inventory inquiry and advice messages (846), the stock snapshots many 3PLs send clients, which are almost always client-owned.
- Purchase orders (850) and ship notices (856) for distributors buying and shipping goods.
- Load tenders (204), tender responses (990), shipment status messages (214) and freight invoices (210) on the transport side.
- Functional acknowledgments (997) and rejected transactions, with the error and how it was fixed.
- Trading partner maps and change logs, which explain why each field means what it does.
Distributor rows: ERP, email and helpdesk#
Distributor rows add the ERP and customer conversation records that 3PL-only inventories leave out. For a wholesale or industrial distributor, most order and customer records are the company's own, which shifts the balance of the lanes toward own-process records.
The exceptions are material other companies gave you under confidentiality terms. Supplier price files and rebate agreements are usually confidential to the supplier, and customer-specific contract pricing often carries confidentiality terms of its own, so those rows need the third-party lane or a mixed flag.
| Record family | Typical contents | Ownership lane | Notes |
|---|---|---|---|
| Quotes and quote outcomes | Line items, substitutions offered, won or lost, loss reason | Own process record | Customer names removed before any outside use |
| Sales orders, invoices and credit memos | Order lines, prices, credit reasons, original order references | Mixed | Contract prices may be confidential to the customer |
| Returns and RMAs | Return reason, inspection result, restock or scrap decision | Own process record | Reason codes and inspection notes carry the value |
| Substitution and cross-reference tables | Replacement items, approvals, customer acceptance | Own process record | Strong evidence of product expertise |
| Inside sales and customer service email | Product questions, rep replies, order and item references | Mixed | Contact details and pricing need masking |
| Supplier price files and rebate agreements | Cost lists, program terms, claim histories | Third-party confidential | Usually excluded from any outside use |
Decision rules for mixed rows#
Mixed rows need decision rules, not a debate per record. The rules below help an operations lead and counsel sort them consistently and record why.
These are inventory rules, not legal conclusions. Rights are assessed deal by deal with counsel; the inventory simply makes that review faster and better informed.
- If removing client names, consignees and client item numbers leaves the record meaningful, mark it mixed-usable, subject to contract review.
- If the value lies in the client's own quantities, prices or customers, treat the row as client-owned.
- If a contract has a data use or aggregated data clause, put the clause reference in the notes column.
- If a contract is silent, mark the row for counsel rather than assuming either way.
- If a row includes consumer names or addresses, set the personal data flag even when the lane is your own.
Illustrative: a 3PL with a distribution arm fills its inventory#
Illustrative: a fictional company runs public warehousing for food and consumer goods clients and a small foodservice packaging distribution business. Its systems are a mid-market WMS, a TMS for outbound loads, Acumatica for the distribution arm and a managed EDI provider.
The IT lead and the warehouse operations manager fill the inventory from admin screens over a couple of sessions. Client item masters, balances and consignee files land in the client-owned lane. Cycle count notes, slotting changes and appointment histories land in the own-process lane. EDI 947 adjustments and 214 delay events are marked mixed. The distribution arm's quotes, returns and email threads are almost all own-process records. The finished sheet goes to the COO with three open questions for counsel.
What happens after the inventory is finished#
With the inventory complete, a company can answer a fit check from the sheet alone, before a single file is exported. The SourceX fit check asks for exactly this kind of metadata: systems, years of history, record families, approximate volumes and known restrictions.
If the company proceeds, the sheet becomes the starting input for the first two stages of the SourceX five-step transaction, Supply and Rights, where record families are matched to buyer interest and contracts are reviewed. Own-process rows usually move first; mixed rows wait for the rights review, and client-owned rows stay out unless a client agrees otherwise. Anything that goes forward is licensed, not sold, and the company keeps ownership of its records.
Frequently asked questions
How detailed should volume estimates be?
Approximate is fine. Record counts by year from a system report, or a database size from IT, are enough for an inventory. The point is to show scale and depth of history, not exact totals. Mark uncertain figures as estimates so nobody later treats them as audited numbers.
Should we include records from clients we no longer serve?
List them, with the contract status noted. Agreements often require return or destruction of client data at termination, so former clients' records may need to be deleted rather than used. The inventory is the place to find that out before anyone builds a dataset around them.
Do warehouse task records count as personal data?
They can. Pick and task logs tied to user IDs describe individual employees, and productivity data may fall under state rules on monitoring and notices that may apply. Flag them, plan to mask user IDs, and have counsel confirm which notices are in place before any outside use.
Who should sign off on the ownership lanes?
Operations proposes and counsel confirms. The operations lead knows what each record contains; counsel reads the client, carrier and EDI agreements that decide the lane. The CEO or COO signs off on the finished inventory before it is shared with any outside party, even as metadata.
Related resources
- IndustryFreight brokerages data
- IndustryThird-party logistics data
- InsightCan logistics and freight companies sell their data to AI companies?
- InsightCan security and alarm companies sell their data to AI companies?
- SolutionTurn the data your company already creates into a licensing asset
- SolutionOperational data: the step-by-step record of how work gets done
See if your company qualifies
A short company assessment. No data uploads are needed.