Before you start
Agree a safe test method with your agency, including payment-provider test mode where appropriate. Use fictional customer data and avoid accidental real charges.
A recognisable example
DYMR tests a standard tee, an offer and a mixed basket. The owner checks price, delivery and optional extras instead of reviewing only the checkout design.
Step by step
- Review the relevant shop-experience and checkout configuration. Confirm which capabilities your actual frontend supports.
- Test product selection, basket updates, eligible and ineligible offers, delivery address and the displayed totals. Include a phone-sized browser.
- Check that optional choices remain optional and that payment and delivery explanations are consistent. Review the final confirmation and the resulting order in WooCommerce.
- If you also sell to business customers, test an authorised business account and a normal customer separately. Check actual prices, tax display and conditions; a customer label alone does not prove wholesale pricing.
What you should see
You have evidence of the tested purchase path. A public Store Check cannot see every logged-in, payment-provider or order-confirmation state and cannot replace this own-shop test.
If it does not work
An amount or option is wrong? Keep the exact basket, account type, destination and steps. Compare WooCommerce source rules with frontend behaviour before changing multiple plugins or promotions.
Menu names and available actions depend on your app language, permissions and connected shop. Screens show the real Daymerce interface with fictional DYMR data; original screen labels are preserved.