Strategy
Ninety days as five reversible checkpoints for a marketplace software decision
Use ninety days as reversible marketplace planning checkpoints for evidence, synthetic tests, specialist gates, rollback and a bounded decision.
A marketplace seller software ninety day plan is a set of decision checkpoints, not a normal implementation time or forecast. The buyer sets the working days within each phase. Production stays disabled until one England merchant has evidence for its legal seller, named marketplace account and bounded product-to-order job.
What to take away
- Treat the ninety day plan as decision checkpoints, not an implementation time or forecast.
- Keep production disabled until one England merchant has evidence for its legal seller and bounded job.
- Each specialist records pass, hold or stop, and no programme score can compensate for a failed gate.
- A test pass applies only to the recorded case and version, never to general approval.
- The final verdict is retain, investigate further, pass a bounded configuration, hold or stop.
The five checkpoints at a glance
| Checkpoint | Example days | Question it answers | Evidence it produces |
|---|---|---|---|
| One: safe baseline | 15 | Is the current route understood? | Seller entity, account authority, state map |
| Two: assurance pack | 20 | Which gates apply? | Specialist pass, hold or stop per field |
| Three: routes and tests | 20 | What will be tested, and how? | Synthetic records, stop rules, rollback plan |
| Four: controlled tests | 25 | What happened in the recorded case? | Logs, outputs, sign-offs |
| Five: decision and exit | 10 | Retain, investigate, pass, hold or stop? | Decision record, rehearsed exit |
Illustrative example: the days in the table add up to 15 + 20 + 20 + 25 + 10 = 90. The split is a starting point for planning and the buyer replaces it with its own working days.
Checkpoint one: define the safe baseline
Example days: 15. Owner: merchant operations lead.
Record the seller entity, account authority, in-scope products, identifiers, source system and current procedure. Trace approved product content, stock and price into the account, then map placed, authorised, captured, fulfilled, cancelled, returned, refunded, disputed and settled events. The operations and delivery guide holds the state definitions.
Attach the exact source, timestamp, acknowledgement and exception owner to each state.
Under the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013, a sales contract cancellation period ends 14 days after the goods come into the consumer's physical possession. Consumer counsel decides how this applies to the actual offer.
Pause if authority, product ownership or the present source of truth cannot be shown. The accepted manual process remains available while the evidence is repaired.
Checkpoint two: assemble the assurance pack
Example days: 20. Owners: one per gate: catalogue, product safety, privacy and accounts.
Catalogue staff approve descriptions, images and rights. The product-safety owner records traceability, restrictions, alerts and withdrawal. Anyone who makes, imports, distributes or sells consumer products in the UK is responsible for making sure they are safe.
The General Product Safety Regulations 2005 require all products to be safe in their normal or reasonably foreseeable usage, and sellers need records identifying their suppliers so that origins can be traced.
Map total price and optional choices, accessibility, personal data, tracking, account security, marketplace terms, VAT records and supplier exit.
A business must register for VAT if its total taxable turnover for the last 12 months goes over £90,000, and any VAT owed to HM Revenue and Customs (HMRC) is payable from the date of registration. The accountant sets the record boundary.
Each specialist records pass, hold or stop for their field. No programme score can compensate for a failed gate. The selection checklist lists the stop rules.
Checkpoint three: compare routes and prepare tests
Example days: 20. Decision owner: head of ecommerce.
Compare the current manual route, single-account configuration, buyer-built integration, hosted tool and managed service on the same job. Candidate hosted tools include Linnworks, Brightpearl, Cin7, Veeqo and Sellbrite, and the named marketplace account might sit on Amazon, eBay or OnBuy.
These are examples to compare, not findings. Verify exact services and contracts before stating any claim, and keep cost, staffing, thresholds and service levels blank until the buyer sets them.
Create synthetic records for an approved and rejected product change, stock conflict, corrected price, late event, duplicate, cancellation, refund and dispute. Add refused tracking, access removal and an accessible customer task. Define expected output, evidence, owner, stop rule and rollback before execution.
The ICO finalised its storage and access technologies guidance on 29 April 2026.
Under the UK GDPR you must have a valid lawful basis to handle personal information, so a privacy and PECR adviser must review the exact test instrumentation. The planning template records the stop rules.
Checkpoint four: run controlled evidence tests
Example days: 25. Test lead: technical lead.
Use a non-production account or an expressly authorised test facility. Block live listing, payment and customer-message actions. Capture configuration, input, output, logs, exceptions and reviewer sign-off. A pass applies only to the recorded case and version.
A rapid cloud assessment suits SaaS tools, and the NCSC lightweight approach works best for services that solve a single business problem. Test privilege removal, monitoring, export restore and rollback. Stop if personal data enters the test or the accepted baseline cannot be restored. The risk scenarios guide rehearses the failure cases.
Checkpoint five: decide and rehearse exit
Example days: 10. Approver: managing director.
Reconcile every result to its predeclared evidence and blank buyer threshold. Record unknowns rather than converting them to passes. Rehearse disabling writes, revoking credentials, restoring product and stock records, handing back open exceptions and recovering exported evidence, as the tool implementation guide describes.
The final verdict is retain current method, investigate further, pass a bounded configuration, hold or stop. Publish no claim of savings, compliance or readiness. Re-open every official source and marketplace record before approval, and set an expiry for the decision pack. Check the exit terms against the commercial contracts review.
Before you act
- Record seller entity, account authority, products, identifiers and source system.
- Attach source, timestamp, acknowledgement and exception owner to each state.
- Pause if authority, product ownership or source of truth cannot be shown.
- Create synthetic records for approved and rejected product changes.
- Block live listing, payment and customer-message actions during tests.
- Rehearse disabling writes, revoking credentials and restoring product records.
Common questions
What must be in place before production is enabled?
Production stays disabled until one England merchant has evidence for its legal seller, named marketplace account and bounded product-to-order job. The buyer sets the working days within each phase, and the accepted manual process remains available while any evidence gap is repaired.
How should test results be treated?
A pass applies only to the recorded case and version. Capture configuration, input, output, logs, exceptions and reviewer sign-off. Stop if personal data enters the test or the accepted baseline cannot be restored, and reconcile every result to its predeclared evidence.
What happens at the final checkpoint?
Reconcile results to predeclared evidence and blank buyer thresholds, and record unknowns rather than converting them to passes. Rehearse disabling writes, revoking credentials, restoring records, handing back open exceptions and recovering exported evidence. The verdict is retain, investigate further, pass a bounded configuration, hold or stop.
