Former customers' shipment data: can a 3PL keep or reuse it?

Can a 3PL keep a former client's shipment data?#

A 3PL can usually keep some of a former client's shipment data, but what it may keep and what it may reuse are separate questions answered by the agreement's exit and confidentiality clauses. Many 3PL agreements require return or deletion of client data at termination, with exceptions for records the 3PL must hold for legal, tax or dispute purposes.

Reuse is narrower than retention. A record kept to defend a billing dispute is held for that purpose. Using the same record for analytics, benchmarking or an AI data license is a different use, and the contract decides whether it is allowed, not the fact that the file still sits in the WMS.

Start with the signed agreement, every amendment and the termination correspondence. Termination letters and transition plans sometimes add data obligations that were never in the original contract.

The answer by clause type#

Former-client data falls under one of four clause patterns, and each points to a different answer. Most agreements combine more than one, such as a return obligation with a legal retention exception, so read the exit clause and the survival clause side by side.

How an aggregated data clause changes the picture#

An aggregated data clause can change the outlook in any row of that table. Some agreements let the 3PL keep and use de-identified, combined data that no longer identifies the client or its customers, and some say expressly that this right survives termination.

Read the definition closely. Aggregated may mean data combined across many clients, while de-identified may mean only that names were removed. A clause that allows internal service improvement is narrower than one that allows commercial use or licensing, and counsel should confirm which one you have.

Which records are the client's and which are yours?#

Client data in a 3PL relationship usually means records about the client's goods, orders and customers, while the 3PL's own operating records describe how it ran the building. The line depends on the contract's definitions, so the list below is a starting point for counsel rather than a rule.

• 1Usually client data: item masters, purchase orders, ASNs, customer orders, ship-to names and addresses, lot and serial records, inventory balances and client-specific reports.
• 2Often contested: exception notes, damage reports, receiving discrepancies, cycle count adjustments and carrier claims tied to client orders.
• 3Usually the 3PL's own: labor schedules, equipment maintenance logs, safety incidents, facility records, internal procedures and the 3PL's cost records.
• 4Mixed: invoices to the client, which are the 3PL's records but reveal the client's volumes and rates.

Retained for legal reasons is not retained for reuse#

A legal retention exception lets a 3PL keep records it needs for tax filings, audits, claims, litigation holds or regulatory requests, but it does not usually expand what those records can be used for. Contracts often state that retained data stays confidential for as long as it is held.

Keep legally retained records apart where your systems allow, for example by archiving the client's account in the WMS and limiting access to finance and legal. That separation makes it easier to show a former client, or later a buyer of the business, that retained data was not reused.

Litigation holds need their own note. Records under a hold must be preserved and cannot be deleted through an ordinary return-or-destroy process until the hold is lifted.

When the contract says nothing#

A silent contract leaves the question open rather than answering it in the 3PL's favor. Confidentiality clauses that survive termination may still cover the data. Consumer names and addresses in ship-to records may fall under state privacy laws regardless of the contract. Emails exchanged during offboarding can also shape what each side reasonably expected.

When the agreement is silent, counsel usually weighs three paths: leave the client's records out, use only records clearly within the 3PL's own operations, or ask the former client for written permission. Asking a former client is uncommon, but it can work when the relationship ended on good terms.

Illustrative: a fulfillment 3PL reviews three former clients#

Illustrative: a fictional fulfillment 3PL in the Southeast is preparing for a fit check and finds years of history for three former clients in its WMS. Client A's agreement required deletion with written certification, and the 3PL had certified deletion except for invoices kept for tax. Client B's agreement required return but allowed de-identified aggregated use that survived termination. Client C's agreement had no exit clause at all.

Counsel excludes Client A entirely, including the retained invoices. Client B's receiving discrepancy notes and exception codes stay in scope after client names, product identifiers and all ship-to details are removed. Client C is left out pending a decision on whether to ask, and the 3PL notes that its own labor and equipment records from that period are unaffected.

An offboarding record that keeps options open#

An offboarding record that documents data decisions at each client exit is the simplest way to keep later options clear. Without one, a 3PL often cannot tell what was returned, what was deleted and what it still holds. SourceX treats former-client records as a rights question first: in the Rights stage of the SourceX five-step transaction, records under return, delete or retention-only terms are typically left out unless counsel concludes otherwise, and any basis for inclusion is recorded in the SourceX Evidence Packet.

• 1Agreement file: the signed agreement, amendments and side letters, with clause references for exit, survival, confidentiality and aggregated data.
• 2Termination file: the notice, any transition plan and the correspondence that added or changed data obligations.
• 3Return record: what was delivered, in what form, to whom and on what date, with the recipient's acknowledgment.
• 4Deletion record: the systems and backups covered, the date, and a copy of any certification exactly as sent.
• 5Retention register: records kept for tax, claims or legal holds, the reason for each and who may access them.
• 6Counsel's note: whether any de-identified or aggregated use survives, and the wording that conclusion rests on.