DSA Trader Traceability Files Should Survive Staff Turnover

Traceability fails when it lives in chat

A platform may ask a seller to verify trader details long after the employee who opened the account has moved on. If the proof sits in chat screenshots and personal folders, the seller loses time and may submit inconsistent records.

A durable file should contain legal entity data, address proof, tax or registry material where relevant, platform submission dates, rejection reasons and the latest accepted version.

The file should start with the live commercial record. Name the SKU, account, supplier, route, claim or customer promise that creates the exposure. Then name the evidence owner and the next event that should reopen the review. This keeps the work close to operations instead of turning it into a detached compliance memo.

Case pattern: the second verification

A marketplace asks for updated trader information after a policy refresh. The seller submits a new address proof that conflicts with the old accepted record, and the account enters review.

The company needed a single traceability file instead of recreating evidence from memory.

The team should write the corrective note while the facts are fresh. The note should say what changed, which file now supports the decision and what the business will stop claiming until stronger evidence exists. That sentence prevents a private fix from turning into another public promise.

Keep one accepted version

The file should mark the evidence version the platform accepted and explain any later change before staff submit it.

When a staff member leaves, transfer platform evidence folders the same way the business transfers passwords and payment authority.

• Store accepted legal entity records.
• Keep address proof version history.
• Record platform case IDs.
• Name the account evidence owner.
• Transfer files during staff changes.

Review rhythm

Use one small sample each month while the issue remains active. Pull one recent order, one public page, one internal note and one customer or platform message. If those records tell the same story, record the sample date and move on. If they conflict, fix the specific field and ask whether other products, suppliers or routes share the same weakness.

The review should stay practical. A seller does not need a meeting for every small discrepancy. It needs a habit that catches drift before the drift reaches a customer, a platform reviewer, a customs desk or a payment partner.

Ask a new marketplace operator to prepare a trader verification packet from the shared folder. Any missing document becomes a process fix.

The sample should include one negative example when possible. A complaint, rejected shipment, failed document request or confused customer message often shows the gap faster than a clean order. The reviewer should not treat the negative example as proof of failure. It is a stress test for the file.

If the sample exposes a gap, the team should fix the live record first and the policy note second. Customers, carriers and platforms see the live record. A polished internal rule does not help if the product page, invoice, support script or supplier instruction still says something else.

The review note should also record what the business will not expand yet. Do not add a new market, claim, bundle, route, supplier or campaign while the evidence for the current scope remains unresolved. This limit keeps a small file gap from becoming a wider operating problem.

That restraint is part of the control, not a delay tactic.

Handoff note

The handoff should be readable in ten minutes. It should name the business owner, file owner, missing evidence, accepted limit and next review trigger. If the answer depends on a chat thread or one employee memory, the record is too fragile.

Keep the handoff beside the working file. Product issues belong with listing, label, sample and complaint records. Supplier issues belong with purchase and due diligence records. Account and payment issues belong with access logs, finance approvals and platform notices.

Add an expiry trigger: a product version change, supplier change, new market, policy update, route change, complaint pattern or certificate date. Evidence that lacks a trigger can look complete long after it stops matching the live business.

Closing note

Traceability controls should survive the people who first handled the account.

A shared evidence file gives the seller a stable answer when platforms ask again.

Reference links

• European Commission Digital Services Act