A desk review of a marketplace software launch that has not happened, with a 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.

What to take away

Marketplace software in scope and evidence reviewed

The launch dossier named no platform. Five real systems are common candidates for a UK seller connection. Each has public pricing or a known pricing model.

The available material comprised the six D063-P07 editorial specifications and the public sources cited below. No merchant identity, marketplace permission or exact software supplier was supplied. No edition, first-party technical record or contract was supplied. No product file, data map or configuration was supplied. No 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 in the supplied dossier.

Required product and customer dossier

The later reviewer needs seller and account authority, product identifiers, claims and media rights. Traceability, warnings and safety regime are also required. 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 and delivery. It must also cover 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 and edition. UK availability, interface permission, schema and identifier mapping are also required. Retry and duplicate controls, release method, support record and change notice are also required. First-party evidence must be current and attached. None was available in this review.

Map order placed, accepted and payment authorised. Then map captured, fulfilled and cancelled. Continue with returned, refunded, disputed and settled. Provide fictional fixture results for rejected product updates, stock conflicts and late events. Also cover refused tracking, duplicate orders, reversal and privileged-access removal. Include 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 or stock update was used. No order, payment, customer message or support route was used. No product claim, total price, choice or accessibility task was observed. No data role, device operation, privilege or alert was observed. No incident, correction, rollback, export or restore was observed. No deletion was observed.

Service standards are also unknown. No clock, population, exclusion or contractual threshold was provided. No 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 and accessible customer and staff tasks.

It must also show reconciled order and payment states, incident containment and rollback to a safe route. A usable export, isolated restore and access removal are also required.

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

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

Before you act

Common questions

Why did the review place the launch on hold?

The material comprised only the six D063-P07 editorial specifications and public sources. No merchant, permission, supplier or edition was supplied. No technical record or configuration was supplied. The absence is not adverse evidence about any provider. It leaves no exact subject for a pass or score.

What must the later reviewer receive about the product and customer journey?

The reviewer needs seller and account authority, product identifiers, claims and media rights. Traceability, warnings and safety regime are also required. Consumer evidence must include the rendered seller identity, description, total price and delivery.

It must also cover optional choices, payment route, order correction and confirmation. The review also needs cancellation, return, refund, complaint and correction routes for the exact offer.

What conditions must be met before the review reopens?

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 and accessible customer and staff tasks.

It must also show reconciled order and payment states, incident containment and rollback to a safe route. Usable export, isolated restore and access removal are also required. Any unresolved gate keeps the verdict at hold.