How to rehearse one ecommerce conversion risk scenario, field by field

A risk rehearsal works on one scenario at a time. Pick a single failure, write its record, and test the recovery on a copy of the journey, never on live customers. Two examples show the fields in use: a price regression and a delivery-promise failure.

What to take away

Write a record, not a forecast

Each rehearsal begins as a written record for one England online merchant. It says what would go wrong, who acts and how the store returns to normal. It does not say how likely the failure is, because no local frequency data was supplied.

Give the record an expiry. It lapses after its stated review date, or sooner when the journey, the evidence or a system changes. A record past its expiry is a prompt to review, not proof that the risk has gone.

Add two optional lines when you can support them: the observable indicator that would show the failure, and the consequence, such as a release hold. Leave confidence blank rather than guessing.

Start from a trigger you can observe

A trigger is an event someone can check, not a worry. For a price regression it is that the payable total omits a mandatory component, or that an optional extra becomes selected without an active choice.

The CMA's price-transparency guidance covers mandatory fees, taxes and charges that belong in the pricing information. Use it as the reference for what the total should hold, and have a qualified UK consumer-law review confirm the reading.

The observable indicator here is a mismatch between the price components, or the choice state, and the approved path. If the indicator appears, the consequence is a release hold. No commercial result is allowed to override it, and the wider list of strategy mistakes explains why a higher completion rate is no reason to wait.

Name the owner, then contain first

Name one owner who can act, with the right review behind them. For the price example that is the consumer-journey owner with a qualified consumer-law reviewer. A named owner with authority is worth more than a long list of interested people.

Containment comes before diagnosis. Stop the affected variant, and preserve screenshots, configuration and orders so that nothing needed later is overwritten. Writing the containment step in advance means nobody debates it while customers are still seeing the fault.

Define recovery and rollback evidence

Recovery restores the approved state. For the price example it means restoring the approved price path, identifying affected customers and reconciling corrections. Rollback evidence then proves the restore happened.

Good rollback evidence is checkable by someone who was not there. For the price example, a synthetic journey shows the correct total and the unselected option. A claim that the fix was deployed is not evidence.

Reversible has a precise meaning here: the store can return to the last approved state without losing customer orders, payment records or access logs. If a change cannot be undone by restoring that state, treat it as irreversible and rehearse it in a copy of the journey, not live. The release and rollback gates show where this sits in a change.

A worked record: the delivery promise

A filled-in rehearsal record for a delivery-promise failure shows the six fields together.

Delivery terms have a legal side too. GOV.UK sets a default for goods sold online: a seller should deliver the goods within 30 days unless it has agreed otherwise with the customer. The record should cite the promise the store actually made, not a default.

Choose which journey to rehearse first

To decide where to start, list the store's customer journeys and mark those where a failure would touch money, personal data, consumer law or supplier access. Rehearse the marked journeys first, in order of how many customers they reach.

Supplier change needs care, because access, logs and exports live outside the store. Rehearse it on a copy, without live customer data. Other themes that merchants watch are set out as dated checks in the 2027 trend checks.

Before you act

Common questions

Why does a rehearsal record leave probability blank?

No defensible local frequency data was supplied, so the record states no probability. It gives a confidence note where one can be supported, and otherwise leaves the field empty.

What counts as good rollback evidence?

Evidence that someone not involved can check. A synthetic journey that shows the correct total and the unselected option is evidence. A statement that a fix went out is not.

When should a rehearsal record be retired?

When its source or system no longer matches, or after its review date passes. Record the reason for retiring it, and write a new record if the risk still applies.