An ecommerce redesign should preserve the meaning of existing orders, important catalogue destinations and the measurement needed to assess the new journey. Start with a before-and-after acceptance record, then test representative customer tasks in a separate copy. Keep presentation changes, URL changes and transaction checks identifiable so a visual improvement can be reviewed alongside the store’s working records.
A redesigned product page can change how a customer makes a choice without needing to change the underlying order history. Some projects also change routes or move content. List those changes explicitly before implementation so the team knows which records, links and events need comparison and which should remain stable.
The original redesign acceptance sheet below uses a fictional catalogue and sample historical order. Narrow guidance comes from Google Search Central’s site-move documentation and WooCommerce’s testing guidance, retrieved on 24 October 2026. See online stores and web development for broader planning.
What should be recorded before the redesign?
Prepare an inventory of important customer routes, catalogue references, representative orders and the current measurement definitions. Give each an owner and a proposed acceptance question. Retain approved evidence privately so the new design can be compared with a known baseline rather than a colleague’s memory of the old interface.
Google recommends changing one major thing at a time during a site move. Its site-move guide gives a useful principle for separating route changes from other changes. A redesign brief should say whether it changes appearance, content location, platform or several of these, with an assessable sequence.
Google recommends mapping old URLs to their new destinations. Google includes images and downloads in move preparation. Build the route inventory around actual customer uses, including a product link saved in an old message or an important downloadable document. These are meaningful acceptance cases when a project changes their locations.
For the fictional store, choose Product A, its category, an image route and a sample order-reference journey. Write what each old link should lead to after the proposed change. Keep a route that is intentionally retired as a separate decision with an appropriate response.
How should catalogue destinations be checked?
Google recommends updating internal links to the new URLs. Google recommends server-side permanent redirects for changed URLs where possible. These documented recommendations apply to route changes; use the actual old-to-new map to determine what needs checking in the redesign.
Google recommends self-referencing canonical annotations on new URLs. Retain the intended destination and relevant page identity in the acceptance sheet. A reviewer should be able to compare the route reached from an old link, the route used by the new navigation and the page’s own identity.
Inspect the customer’s task as well as the response code. A route can reach a working page that describes the wrong product or loses the intended variant context. Ask the catalogue owner to identify the item and explain the information shown at the destination. Record any mismatch as a specific route or content-mapping issue.
| Redesign area | Proposed baseline | After-change check |
|---|---|---|
| Product route | Old URL and intended item | Correct destination and product identity |
| Category route | Relevant browsing task | Products remain reachable through useful links |
| Existing order | Approved sample record and details | History remains interpretable through the intended interface |
| Checkout | Sample selection and expected test result | Chosen item reaches the correct order |
| Measurement | Event definition and test route | Comparable evidence is collected for the same task |
| Retired content | Explicit removal decision | Appropriate response and onward guidance |
This is an original acceptance sheet. Populate observed results during the staging review rather than treating the baseline as proof of preservation.
How should order and checkout evidence be protected?
WooCommerce says test orders can trigger customer emails. WooCommerce also says test orders can appear in analytics. Its testing-orders guide makes the test arrangement part of the redesign brief. Use a separate staging copy and designated test recipients, with the relevant connected processes identified beforehand.
WooCommerce does not give test orders a distinct visual status. WooCommerce notes that other integrations may not distinguish test and real orders. Record the test fixture, sample order references and expected downstream treatment so the review remains understandable to everyone involved.
For the sample historical order, define which details the business expects to preserve and how an authorised reviewer will inspect them. Compare the same approved fields before and after the redesign in the test copy. Keep sensitive customer data out of ordinary presentation material and retain the record identifiers privately for correlation.
A checkout exercise should begin with the redesigned product journey. Choose the sample item, continue through the documented test route and inspect the resulting order. Compare the selected item and relevant details with the baseline so the review covers the customer task across page boundaries.
What makes measurement comparable?
Write the event or observation being compared in business language. A completed enquiry and a click on a product card answer different questions. Keep the event definition, collection point and relevant filtering decisions with the acceptance sheet. If the redesign changes one of those definitions, record the break in comparability explicitly.
Use designated test observations to inspect the collection route before drawing conclusions from later traffic. Record which sample action should produce which evidence and where the reviewer checks it. The exercise can establish whether the intended event is observed; later business-performance claims need their own actual data and interpretation.
Original catalogue-and-order preservation exercise
Prepare the fictional catalogue routes and an approved sample order in a separate copy of the store. Retain the old-to-new URL map, relevant order fields and measurement definitions. Have the business owner confirm the expected outcomes before the redesign is assessed.
First, follow each representative old link and compare its destination with the map. Continue through the new browsing route and identify the product. Next, inspect the sample historical order using the intended account and compare the agreed fields with the retained baseline. Record the actual observations and their configuration context.
Then run the documented checkout test from the redesigned product page. Inspect the resulting order and the designated measurement evidence. Review any difference with the relevant catalogue, transaction or measurement owner so the issue is assigned to the correct part of the work.
Finally, revisit intentionally retired routes and unresolved cases. Keep the acceptance record connected to the exact build and configuration assessed. For wider discoverability questions, see SEO. To discuss the redesign scope and preservation evidence, get started with the baseline sheet and route map.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.