When the sale date is close, readiness is not a bigger wish list. It is a controlled decision about what could stop the next valid order, what still needs evidence and what should wait. Use a few representative customer journeys, name the owner of each result and keep a rollback path for every change.
Use one rule: protect the next valid order
Start with the journeys that must still work when the promotion begins: a customer can find an eligible product, understand the offer, see a valid delivery option, pay, receive confirmation and leave one usable order for the operating team. A defect that breaks that chain deserves attention before a cosmetic improvement.
- Fix a repeatable failure that blocks a valid order or creates a known incorrect promise.
- Test a risk whose effect depends on cart, address, device, consent or system state.
- Defer work that changes presentation without protecting the purchase or recovery path.
Run six checks with representative carts
Choose a small set of real products and destinations that exercise the rules you actually use. Include a popular item, a discounted item, a low-stock variant, a cart that crosses a shipping threshold and the mobile route most customers see. Record the expected result before testing so the team does not accept whatever appears.
On Shopify, discount combinations have eligibility and plan restrictions, and third-party carrier-account rates depend on the store plan and carrier setup. Test orders can check checkout, inventory, shipping and notifications, but payment test mode prevents live customer orders while it is active. Confirm the current store configuration before using any feature as part of the sale plan.
- Mobile checkout: product, cart, discount, address, payment and confirmation.
- Discount combinations: eligible products, minimums, exclusions, free shipping and the order in which discounts apply.
- Shipping-rate fallback: representative weights, dimensions, destinations and what the buyer sees when a carrier or app rate fails.
- Stock ownership: the system of record, fulfilment location and whether any variant is intentionally allowed to oversell.
- Tracking receipt: the consent state, checkout event and downstream receipt—not only whether a tag appears in source code.
- Rollback: the exact promotion, app, theme or configuration change that can be restored, by whom and from which known state.
Choose fix now, test first or defer
Use the same decision rule for every finding. Severity alone is not enough: require a reproducible example, the affected customer or operating promise, a safe change and a person who can approve it. If the team cannot yet explain the failure, the next action is evidence gathering rather than a hurried production change.
A useful triage board has three columns. The owner can move an item only when the evidence changes, not because the launch date creates pressure.
- Fix now — checkout cannot complete; no eligible shipping route appears; a discount charges the wrong amount; a known stock rule permits unintended overselling; an accepted order fails to reach the system that must fulfil it.
- Test first — a failure appears only for one address, device, discount pair, consent state, product mix or fulfilment location; reproduce it with the same inputs before changing the rule.
- Defer — a new app, broad redesign, extra animation or campaign idea has no tested owner, rollback or direct role in completing and operating the sale.
Work one failure from evidence to handoff
Illustrative example: a bulky discounted product shows no delivery option for one Canadian postal code. First preserve the exact product, quantity, address, package weight and dimensions. Compare the expected shipping profile and carrier account with the checkout result. Check whether another eligible rate or configured backup exists before changing prices or promises.
If the same inputs repeatedly produce no valid route and the product is meant to ship there, treat the missing route as a fix-now issue. If only one service differs from the carrier account, isolate the configuration and test first. After the correction, repeat the same cart, record the result and hand the decision to the person responsible for fulfilment. This is an illustrative workflow, not a client result or a promised turnaround.
- Reproduce with named inputs and capture the observed result.
- Identify the owning rule, integration or system of record.
- Choose the smallest safe correction or restore the known state.
- Repeat the same journey and one nearby control case.
- Record who approved the release, what changed and how to reverse it.
Leave the operating team a usable owner checklist
Readiness ends with ownership, not a green screenshot. Name the person who can pause a promotion, restore a theme or app configuration, choose a shipping exception and confirm whether the order reached fulfilment. Keep contact details, access and vendor escalation paths in the business's controlled operating record rather than in an article or public document.
Separate the paid assessment from the free first conversation. The paid Readiness Review examines one storefront and agreed sample journeys, then produces evidence, priorities and a next-step plan; implementation is separately agreed. A free initial review only assesses the information you provide and recommends a direction. Neither creates an unagreed emergency SLA.
- Promotion owner and the approved start, stop and rollback conditions.
- Checkout, shipping, inventory, analytics and fulfilment owners.
- One incident record with timestamps, evidence, decisions and customer impact.
- A handoff note for unresolved risks and the next controlled test.
Commerce Readiness & Support
The paid Readiness Review suits one storefront when checkout, shipping, catalog or integration risks need evidence and prioritisation before implementation. It is a defined assessment, not an implied emergency response or unlimited support arrangement.
Readiness Review · $540 USD
One storefront and agreed samples of catalog and purchase journeys. Includes one review call and a factual clarification pass. Implementation, checks of every product and variant and specialist security or regulatory audits are separate.
