A blank marketplace software plan covering seller authority, gates, tests and rollback

This marketplace seller software planning template is deliberately blank. Complete it for one England merchant, authorised legal seller, named marketplace account and bounded catalogue-to-order job. An empty field means hold; it must not be filled with a typical value or supplier promise.

Decision record

Field	Buyer entry
Decision owner and authority	[enter authorised owner]
Seller legal entity	[enter verified entity]
England operating rule and evidence	[enter geographic evidence]
Marketplace, account and contract owner	[enter account record]
Product population and identifiers	[enter eligible catalogue]
Source system and accepted baseline	[enter current process]
Observed problem, period and evidence	[enter bounded observation]
Options, including current method	[enter comparable routes]
Decision date and recheck trigger	[enter review condition]

Do not infer authority from a job title or public profile. Record which person may approve account access, contract changes, catalogue content, safety decisions and production release.

Product and consumer fields

For each in-scope product, attach the approved identity, description, price basis, images and rights, delivery terms, safety and traceability evidence, restrictions and withdrawal route. Record listing-field ownership and the response expected from the marketplace.

Add a consumer-journey sheet for seller identity, product information, total price, optional choices, ordering, confirmation, cancellation, return, refund and support. GOV.UK's online-selling guidance describes current seller and ordering information. The CMA separately explains express consent for optional extras. Qualified consumer counsel must review the real journey.

State and data map

Object	Source	Allowed state	Destination	Evidence	Exception owner
Product record	[enter origin]	[enter product state]	[enter account field]	[enter acknowledgement]	[assign catalogue owner]
Stock position	[enter stock source]	[enter availability state]	[enter stock destination]	[enter response record]	[assign inventory owner]
Price and charge	[enter approved price]	[enter price state]	[enter display field]	[enter journey evidence]	[assign commercial owner]
Order	[enter order source]	[enter order state]	[enter order destination]	[enter acceptance record]	[assign operations owner]
Payment and settlement	[enter payment source]	[enter money event]	[enter finance record]	[enter reconciliation]	[assign finance owner]
Cancellation, return or refund	[enter case source]	[enter later state]	[enter case destination]	[enter closure evidence]	[assign service owner]

Specify placed, authorised, captured, accepted, fulfilled, cancelled, returned, refunded, disputed and settled events separately. Add rules for late, missing, duplicate and rejected messages. HMRC's VAT record guidance provides the current accounting boundary; an accountant and VAT adviser own its application.

Assurance register

Create independent rows for consumer law, product safety, privacy and PECR, security, accessibility, tax and accounting, contract and marketplace terms, supplier continuity, export and deletion. Each row needs a named reviewer, evidence version, pass/hold/stop outcome, expiry and recheck event.

Add a permissions sheet for every human and service account. Enter the approved task, minimum role, credential owner, grant date field, review event, logging source and revocation test. A managed provider receives its own row. Do not reuse the marketplace account owner's authority as approval for a software supplier or contractor.

The ICO's controller and processor contract guidance is under review after DUAA changes. Record publication-day verification rather than copying a permanent conclusion.

Test and decision fields

List synthetic cases for an approved and rejected product change, stock conflict, corrected price, cancellation, refund, dispute, duplicate, late event and refused tracking. For each, enter expected output, evidence owner, blank acceptance threshold, stop condition and rollback step. Production access remains disabled.

Add accessible customer and staff tasks to the same test register. Record keyboard and assistive-technology setup, expected completion evidence, observed barrier and remediation owner. Do not convert an automated scan or supplier statement into an accessibility verdict.

Finish with blank fields for full cost, budget approval, dependencies, residual risks, export restore, supplier exit and final verdict. The only permitted verdicts are pass for the tested scope, hold pending named evidence or stop. A completed template is a decision record, not proof of compliance or results.