Reading a marketplace software contract for identity, money, audit and exit

Marketplace seller software commercial contracts need a buyer-owned evidence schedule, not copied model clauses. These seven topics concern one England merchant, authorised seller, named marketplace account and exact software service.

Method: A topic qualified when it could change authority, delivery, evidence, risk or exit, and a current official source supported the boundary.

Research date: 6 September 2026. Geography: England contracting case with UK or Great Britain sources kept in their stated scope.

Inclusions: Supplier and managed-service due diligence for the bounded product, stock and later order journey.

Exclusions: Model drafting, legal conclusions, supplier names, prices, service levels, negotiation advice and marketplace terms not inspected.

Ranking: Non-ranked. Sequence follows identity through exit. Conflicts: No party paid for inclusion or supplied a private dossier.

1. Entity, service and authority

Record exact legal and trading entities, service and edition, contracting authority, seller-account permission, territory, term and document hierarchy. Companies House register guidance can verify narrow filed facts. It does not prove service capability, authority or fitness.

2. Marketplace and consumer dependencies

List interfaces, marketplace permissions, ordering states and seller responsibilities. State which party handles product information, price, confirmation, cancellation, return, refund and support. GOV.UK's online-selling page supplies the current journey context, not a clause or transfer of duty.

3. Product safety and correction

Allocate product evidence, traceability, incident escalation, listing suspension, withdrawal and recall support by actual role. OPSS business guidance distinguishes Great Britain and Northern Ireland treatment and warns that product-specific rules may apply. Safety counsel owns the contract review.

4. Data roles, security and audit

Map purposes, controller and processor facts, subprocessors, transfers, instructions, confidentiality, rights help, incidents, evidence and inspection. ICO contract guidance is under review following DUAA changes. NCSC supplier-assurance questions can structure security evidence; answers are not government approval.

5. Service, change and suspension

Define eligible events, clocks, exclusions, support route, evidence owner and buyer-set service fields. Leave thresholds blank. Address marketplace interface changes, supplier releases, emergency suspension, correction, rollback and restart authority. NCSC SaaS guidance supports reviewing privilege, monitoring and recovery for the exact configuration.

6. Fees, VAT, liability and insurance review

Record currency, VAT basis, unit, period, term, limits, pass-through charges, refunds, disputes and exit costs only from current terms. Keep liability, indemnity and insurance as solicitor-owned questions. HMRC VAT record guidance supports transaction records; it does not settle the tax treatment of this contract.

7. Export, transition, deletion and end state

Specify export fields and format, assistance, access removal, record retention, deletion evidence, open-order handover and restoration of the current process. The ICO contract page includes end-of-contract considerations. Verify export and restore with synthetic records before commitment.

Any missing non-compensating field produces hold. The completed schedule goes to named contract, privacy, consumer, safety, security, accessibility and tax reviewers; it does not certify the agreement.

Keep a dependency diagram outside the contract wording. Link the seller's source system, marketplace account, supplier service, managed operator, payment records and archive. Give each connection an owner, evidence source and failure route. This makes an unrecorded subcontractor or marketplace interface change visible before it interrupts catalogue correction or an open refund.

At signature review, compare the schedule with the order form, incorporated policies and negotiated documents. Record which version prevails and who accepted it. If a material security, data, safety, fee or exit answer exists only in sales correspondence, hold until commercial counsel decides how it should be captured.