Marketplace Ops

Operations

Part of Operating marketplace seller software as a state machine, not a status label

A marketplace software launch that has not happened, reviewed and placed on hold

Review an unperformed marketplace software launch through a disclosed desk method, missing evidence, untested gates and an explicit HOLD verdict.

Reviewer status: to-be-assigned named UK marketplace launch reviewer, supported by the specialists in the front matter. Subject: a proposed software connection for one fictional England seller, authorised marketplace account and approved product, stock and later order-state journey. Review date: 6 September 2026. Method: desk comparison of an empty launch dossier with current official evidence boundaries. Conflicts: none declared above. Verdict: HOLD, untested and not ready for launch.

Evidence actually reviewed

The available material comprised the six D063-P07 editorial specifications and the public sources cited below. No merchant identity, marketplace permission, exact software supplier or edition, first-party technical record, contract, product file, data map, configuration, test result or service evidence was supplied.

That absence is not adverse evidence about any provider. It means there is no exact subject for a pass, score or recommendation. No marketplace, supplier or managed service is named.

Required product and customer dossier

The later reviewer needs seller and account authority, product identifiers, claims, media rights, traceability, warnings and safety regime. OPSS product-safety advice provides the official role and territory boundary. It does not show that an unseen product record is adequate.

Consumer evidence must include the rendered seller identity, description, total price, delivery, optional choices, payment route, order correction and confirmation. GOV.UK's online-selling page supports those inspection subjects. The review also needs cancellation, return, refund, complaint and correction routes for the exact offer.

Required technical and control dossier

Supply the exact legal software entity, service, edition, UK availability, interface permission, schema, identifier mapping, retry and duplicate controls, release method, support record and change notice. First-party evidence must be current and attached. None was available in this review.

Map order placed, accepted, payment authorised, captured, fulfilled, cancelled, returned, refunded, disputed and settled. Provide fictional fixture results for rejected product updates, stock conflicts, late events, refused tracking, duplicate orders, reversal, privileged-access removal, rollback, export and isolated restore.

The ICO's final storage and access guidance supplies a current PECR boundary. NCSC SaaS guidance covers customer configuration, monitoring, protected copies and recovery. Neither page is evidence about the missing configuration.

Hands-on actions and untested areas

No account was opened. No API, feed, interface, listing, stock update, order, payment, customer message or support route was used. No product claim, total price, choice, accessibility task, data role, device operation, privilege, alert, incident, correction, rollback, export, restore or deletion was observed.

Service standards are also unknown. No clock, population, exclusion, contractual threshold, supplier performance record or response result was provided. Buyer fields must remain blank rather than being filled with a customary SLA.

Conditions for reopening

Reopen only when the exact version has a complete evidence packet and each named specialist records PASS, FAIL or UNRESOLVED. The seller must demonstrate authorised synthetic tests, accessible customer and staff tasks, reconciled order and payment states, incident containment, rollback to a safe route, usable export, isolated restore and access removal.

HMRC's VAT record guidance supports preserving supplies and adjustments, but an accountant and tax adviser must decide the specific treatment. Consumer, safety, tax, privacy and PECR, security, accessibility, advertising and exit decisions remain independent.

Any unresolved gate keeps the verdict at HOLD. A later review applies only to the documented seller, account, product population, supplier edition, configuration and evidence date. Material change cancels the earlier result and starts a new review.

More in Operations

Operations

Operating marketplace seller software as a state machine, not a status label

Run marketplace seller software through controlled product, stock and order states, with clear owners, evidence gates, recovery and tested exit.

Operations

Running a marketplace workflow through approved product, stock and order states

Run a marketplace software workflow through approved product, stock and order states, with evidence-led hand-offs, exceptions, rollback and exit.

Operations

A marketplace software quality checklist with evidence IDs and an exit test

Check marketplace software with evidence IDs, pass, fail or unresolved results, separate legal and assurance gates, rollback and an exit test.

Operations

Marketplace software service standards chosen around customer harm

Define marketplace software service standards through events, clocks, evidence and failure responses while leaving unsupported thresholds blank.