DSA Article 30 Checks Turn Seller Onboarding Into a KYBC File

Why onboarding changed

DSA Article 30 pushes online marketplaces to know which traders use their services. For a seller, this means onboarding is no longer only a commercial form. It becomes a know-your-business-customer file that connects the public store to the legal trader and the product record.

A seller may use a brand name, a trading company, a different payment account and several fulfilment partners. That structure can be legitimate. It becomes risky when nobody can explain it in one file. A platform reviewer will not study months of chat history to understand the arrangement.

Identity file fields

The practical file should answer three questions. Who controls the seller account? Who takes responsibility for the product offer? Who receives notices and money? If the answers point to different parties, the seller should write a relationship note and keep supporting documents.

This file also helps buyers. A buyer doing supplier due diligence can compare store profile, invoice issuer, payment beneficiary and complaint contact. A mismatch does not prove fraud. An unexplained mismatch raises the cost of trust.

Case pattern for account growth

A seller starts with one marketplace account and later adds regional stores. The team changes payment routing after opening a local bank account. Product files stay with the original supplier manager. When a platform asks for trader details, the store operator can answer some questions but not the product-responsibility questions.

A stronger onboarding file would keep those changes visible. It would record the date of each entity, bank, contact or fulfilment change. It would also explain whether older product listings were reviewed after the change.

Seller checklist

Sellers should build the file before a suspension, safety notice or illegal-product complaint. The file should be short enough for an operations manager to update, but clear enough for legal or platform support to use.

The file should also expire. If the seller changes ownership, bank details, invoice issuer or warehouse route, the team should reopen the identity pack. A stale identity file creates the same problem as no file.

• Match store name, legal entity and invoice issuer.
• Explain payment beneficiary differences in writing.
• Keep current contact details for product notices.
• Attach seller identity to high-risk product pages.
• Review the file after bank, ownership or fulfilment changes.

Thirty-day field test

A useful test is to put one live order, one active listing and one supplier file beside this briefing. The team should walk through the records as if a platform reviewer, customs officer or buyer asked for proof tomorrow morning. The exercise should produce a short gap list, not a presentation. Each missing record needs an owner, a due date and a business decision if the record cannot be obtained.

Do not wait for a perfect compliance system. Pick the highest-risk product in the category and test the file with the people who would answer the real request: sourcing, logistics, finance, marketplace operations and customer support. If those teams give different answers, the company has found the risk before an outside reviewer does. That is the value of the exercise.

Keep the record of the test in the same folder as the order or listing. A short note with the reviewer name, date, missing evidence and final decision gives the next reviewer a starting point. It also stops teams from repeating the same conversation after every customer question, route change or platform notice.

Set a review rhythm after the first pass. Thirty days is enough for an initial cleanup, but supplier changes, product edits and route changes should reopen the file. The rule is simple: when the commercial fact changes, the evidence file changes with it.

The team should keep a change log beside the evidence. It should say which document changed, who approved the change and which live product, route or supplier record was affected. That log turns a pile of files into a working control because later reviewers can see the decision path instead of guessing why an old record was replaced.

• Choose one product or shipment that is still active.
• Ask who owns each evidence item and where it is stored.
• Compare the public claim with the internal document.
• Record the business action if evidence is missing.
• Repeat the test after the next supplier, route or listing change.

Source links

• European Commission DSA Policy Page
• Regulation (EU) 2022/2065