Start with the purchase journey: category, product, cart, and checkout. Add delivery and contact pages, because customers use these pages to check the terms. For each step, note what the audit checks and what action needs to be repeated manually.
A checkout page loading does not confirm that an order was placed. To verify a purchase, agree on a clearly marked test and confirm that the order appeared in the store's system and reached the responsible recipient.
Create a checklist for the purchase journey
| Page | What to get from the technical check | What to check manually |
|---|---|---|
| Category | URL response, links, and metadata | Products, menu, important filters |
| Product | Response, images, and links | Price, options, adding to cart |
| Delivery | URL availability | Terms for the relevant region |
| Cart | Response for the selected URL | Items, quantity, and total |
| Checkout | Response and test text | Whether the test order is saved and received |
Take the URLs from the live site. The cart may depend on the selected products and browser state: an automated URL request does not perform all these actions. Do not use an empty cart as the only confirmation of a purchase.
Choose different product pages and categories
Many product pages in a large store use the same template. For an initial check, it is useful to select a few representative pages with different content: a short and a long description, one and several photos, and different product options. This can help uncover a template defect without manually reading every product page.
Categories need their own sample. Check a regular category, a nested section, and a page with filters if it is an important part of the site. URLs with parameters may serve a different purpose, so they cannot automatically be treated as duplicates that should be removed.
For example, choose a regular product, a product with size selection, and an out-of-stock product. For categories, choose a regular section and a filter in use. Give these URLs to the developer when changing the template. The principles of site structure are covered in the URL structure guide.
Check the transitions that affect a purchase
For a store, a broken link in the menu, on a product page, or in the delivery terms can prevent a customer from continuing. But different links have different levels of impact. Determine whether a transition leads to a required step or supplementary material, then set its priority.
Check the source and destination URLs. If a product has been discontinued, redirecting to another page may be intentional rather than a technical error. Find out the expected behavior from the catalog owner before making a bulk change to redirects.
For a broken link, record the source page, destination URL, and intended destination. Include an example of the transition from a product page or menu so the person responsible can reproduce it.
Place an agreed test order
An open cart and a “order accepted” message are only intermediate signs. Confirmation requires proof that the order was saved in the live system and the agreed confirmation reached its recipient. If the notification to the restaurant, warehouse, or manager has not been checked, do not describe the entire flow as fully functional.
A safe test is marked as a test in advance and agreed with the person responsible. Choose the product, delivery method, and actions to take after the test. The team arranges these steps manually; monitoring does not automatically place or cancel an order.
Record the time and test ID. If the order was saved but the manager did not receive a notification, report that specific break in the flow. If a message arrived but there is no record in the system, that is a different result. Do not mark the entire flow as working based on a single success screen.
Repeat the affected steps after an update
When a new product page template is introduced, repeat selecting options and adding a product to the cart. When payment or delivery changes, go through checkout separately. A test saved a month ago relates to the previous implementation.
The daily audit in the monitoring dashboard checks up to 100 pages. For a large catalog, confirm which URLs were checked. After a bulk change, a full manual audit of a suitable size may be needed, up to 1000 pages in one batch. Active paid subscriptions include manual checks with no monthly limit on the number of runs; package and concurrency limits still apply.
Give your colleague a brief record: product and URL, actions checked, date, where the order was saved, and manager confirmation. If a step was not checked, assign someone to it and specify the next action.