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: One England contracting case. A topic qualified if it could change authority, delivery, evidence, risk or exit.

Research date: 6 September 2026. Geography: England 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: Drafting, legal conclusions, supplier names, prices, service levels, negotiation advice and marketplace terms not inspected.

Ranking: Non-ranked. Conflicts: No party paid for inclusion or supplied a private dossier.

What to take away

The seven topics run from entity and authority through to export, deletion and end state.
Keep a dependency diagram outside the contract wording to expose subcontractor and interface changes.

1. Entity, service and authority

Record exact legal and trading entities, service and edition, contracting authority, seller-account permission, territory, term and document hierarchy. Check the parties clause, authority clause and change-of-control clause. 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. Check the responsibilities clause and marketplace interface clause. 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. Check the product safety clause and recall clause. 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. Check the data processing clause, audit right clause and subprocessor clause. 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 fields such as availability percentage, response time and service credit rate. Check the service level clause, change control clause and suspension clause. 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. Check the fees and payment clause and limitation of liability clause. Keep liability, indemnity and insurance as solicitor-owned questions. HMRC VAT records 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. Check the termination clause, transition assistance clause and deletion clause. The ICO contract page includes end-of-contract considerations. Verify export and restore with synthetic records before commitment.

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.

Before you act

Record exact legal and trading entities and contracting authority.
Map controller and processor facts, subprocessors and transfers.
Leave service thresholds blank for buyer-set fields.
Verify export and restore with synthetic records before commitment.
Compare the schedule with the order form and incorporated policies.
Hold if a material answer exists only in sales correspondence.

A worked evidence-schedule table makes the fields concrete. Each row is illustrative; replace placeholders with verified facts.

Field	Clause type	What to record	Worked entry
Entities and authority	Parties clause; authority clause; change-of-control clause	Exact legal and trading names, company numbers, signatory authority, seller-account permission	Buyer: exact Companies House registered name and company number. Supplier: exact registered name and company number. Authority: named signatory and board minute reference.
Marketplace interfaces	Responsibilities clause; marketplace interface clause	Interfaces, permissions, ordering states, who handles price, cancellation and refund	Account: named marketplace account ID. Interface: seller central and order API. Responsibility: supplier handles listing correction; buyer handles refund.
Product safety	Product safety clause; recall clause	Evidence, traceability, escalation, suspension, withdrawal and recall roles	Traceability: batch code and listing ID. Escalation: named safety contact. Recall: supplier supports withdrawal within the recall clause timescale.
Data and security	Data processing clause; audit right clause; subprocessor clause	Purposes, roles, subprocessors, transfers, incident and audit evidence	Role: processor for order data. Subprocessor: named hosting provider. Audit: annual audit right, evidence pack.
Service and change	Service level clause; change control clause; suspension clause	Eligible events, clocks, exclusions, support route, buyer-set fields	Availability percentage: buyer to set. Response time: buyer to set. Credit rate: buyer to set. Change: supplier release notice.
Fees and VAT	Fees and payment clause; limitation of liability clause; insurance clause	Currency, VAT basis, unit, period, limits, pass-through charges, refunds and exit costs	Currency: GBP. VAT: standard rate. Limits: solicitor to confirm. Exit cost: only from current terms.
Exit and deletion	Termination clause; transition assistance clause; deletion clause	Export fields, format, assistance, access removal, retention, deletion evidence and open-order handover	Export: CSV of order and catalogue fields. Deletion: certificate of deletion. Handover: open orders list.

Common questions

What does the article say about model clauses?

The article does not recommend copied model clauses. It builds the schedule from the named account and service facts.

How should liability, indemnity and insurance be treated?

The article says to keep liability, indemnity and insurance as solicitor-owned questions. Record currency, VAT basis, unit, period, term, limits, pass-through charges, refunds, disputes and exit costs only from current terms, and leave those legal questions to a solicitor.

What happens if a field is missing?

Any missing non-compensating field produces hold.