Six marketplace planning mistakes, starting with treating account access as approval

These marketplace seller software strategy mistakes are observable planning failures, not claims about prevalence. Each can be found in an evidence pack before an England merchant enables production access.

Method: An item qualified when it could invalidate the bounded seller decision and a current UK official record supported the relevant boundary.

Research date: 6 September 2026.

England and UK scope: The example merchant operates in England. Consumer, safety, data, security and tax records retain their stated UK or Great Britain scope.

Inclusions: Failures involving one authorised seller, marketplace account, product record, stock and later order states.

Exclusions: Supplier rankings, alleged incidents, frequency estimates, prices and unverified marketplace rules.

Ranking: Non-ranked. Order follows the seller journey.

Conflicts: No marketplace, supplier or adviser paid for inclusion.

1. Treating account access as seller approval

A marketplace login cannot prove who may approve product content, change price or accept commercial risk. Record the legal seller and authority for each action. GOV.UK's online-selling guidance places information and ordering duties in the seller context. A tool's ability to publish does not transfer those decisions.

2. Sending a listing without its evidence

A successful transmission says nothing about description rights, safety or traceability. Attach approved product identifiers, content, images, restrictions and withdrawal status. OPSS product-safety advice for businesses makes product role and applicable rules central. A safety specialist must review the actual category.

3. Letting the checkout choose for the customer

Preselected extras may turn a clean technical flow into an unacceptable consumer journey. GOV.UK says optional charges need express consent. Test the presented choice and resulting order evidence, not only the total passed to a payment service.

4. Calling every money event a sale

An order, authorisation, capture, settlement, refund and dispute are not interchangeable. Keep each event and correction traceable. HMRC's VAT record guidance addresses supplies, invoices, adjustments and credit or debit notes. An accountant and VAT adviser decide the merchant's treatment.

5. Adding tracking to measure the change

Measurement does not bypass device-access or personal-data review. The ICO's final April 2026 storage and access technologies guidance reflects DUAA amendments and covers PECR alongside UK GDPR where relevant. Record the exact technology, purpose and permission decision before activation.

6. Leaving access and exit until after selection

A route is incomplete if the buyer cannot revoke privileges, recover records or restore the accepted process. NCSC SaaS security guidance covers privileged access, logs and resilient backups. Test account removal, rollback and export with synthetic records before production.

Any one of these failures produces hold. Do not average it against a faster workflow. Assign an owner, evidence request and recheck date, then retain the controlled current process until the issue is resolved.

For each finding, save the source record, affected product and order states, configuration version and person authorised to close it. Re-run only the cases touched by the correction, followed by the agreed regression set. If evidence cannot show what changed, restore the accepted baseline rather than improvising in production.

The list is a planning aid, not a legal or technical certification. Consumer, product-safety, privacy, security, accessibility and accounting reviewers each decide their own field. Publication also requires a fresh check of the linked official pages and the exact marketplace terms governing the account.