Prepare a basket you can recognise
Choose a small set of test products with known prices and quantities. Include a product with a selectable option, an item eligible for collection and an item with limited stock. Note the starting quantity in each system that holds it. Give the test customer an email address you can check. Use the payment provider's test environment where available and tell the people handling orders which records belong to the trial.
Write one expected result before placing the order. For example, a customer collects two copies of a book from the Valencia shop, pays online and receives a message explaining when to come. The shop should see the two copies against that branch and should have enough information to prepare the parcel. This single sentence gives you a standard for checking the receipt, the order screen and the information sent to the shop.
Buy on a phone from the product page
Start in a fresh browser session on a real phone. Find a product the way a visitor might find it, choose the option you want and add it to the basket. Change the quantity, return to the catalogue, then go back to the basket. Look at the product name, option, quantity and price after every change. A customer who selected the blue item in a particular size must still be able to see that choice before paying.
Complete the contact and address fields using the phone keyboard. Try an apartment number, a surname containing an accent and a valid postcode with a leading zero where that applies. Leave one required field empty. Check that the message identifies the field, moves the customer close enough to fix it and keeps information already entered. On a small screen, a red border hidden behind the keyboard gives the buyer very little help.
Test the edges of the delivery area
Use several addresses that you understand operationally. Try one near the shop, one at the edge of a delivery zone and one outside it. Change the postcode after a delivery method has already been selected. Confirm that the available methods and final total match what the business can actually provide. For collection, the confirmation should contain the chosen location and useful instructions for picking up the order.
Try a basket just below the free delivery threshold and another just above it. Apply a discount if the shop accepts one and check which amount the business intends to use for the threshold. Add a bulky item or a product that cannot be collected, if relevant. Write down the expected result with the person who sets delivery prices. A checkout can calculate its configured rules perfectly and still quote a price the shop never intended to offer.
Follow a successful payment across systems
For each payment method available at launch, record the order number, the amount and the outcome in the payment provider's test dashboard. Follow the customer back to the shop and read the confirmation. Then open the order as a member of staff. Check the currency, delivery charge, discount, order lines and the next action expected from the shop. A thank-you page on its own does not tell the person preparing the order whether payment succeeded.
During a second test, leave the payment provider's page before returning to the shop. Check how the order is recorded once the provider has reported the result. The customer may lose their connection on a train or close the tab after seeing a payment confirmation. Agree which record staff should consult when the customer's screen and the shop initially show different information. A support person should be able to trace the transaction by its reference.
Rehearse refusal, cancellation and a second attempt
Use the test cases offered by your payment provider to simulate a refusal or an abandoned payment. Read the message as a customer. Can you tell whether money was taken, whether the basket is still available and how to try again? Try the successful route afterwards. Compare payment records and shop orders to establish how many charges were made and which order the shop should fulfil. Save the references with the test result.
Cancel an unpaid order and, separately, rehearse the agreed refund procedure for a paid test order. If partial refunds are part of the service, refund one item from a basket containing two different items. Check money, order lines and stock independently. A customer returning a damaged item may receive a refund even though the returned item cannot go back on sale. Record who decides whether the quantity should be restored.
Check what the warehouse and the customer receive
Read the messages received by the customer and by staff on a phone. Is the collection point visible? Does the receipt show the selected product option? Can the customer reply to a monitored address? Follow a link in the message as a visitor who is signed out. If the link requires an account, check what a guest customer should do instead. A successful email delivery is only the beginning of this test.
When a till, warehouse system or customer database is connected, find the same order there. Match the reference and the actual items rather than relying on a green connection indicator. If possible in the test environment, temporarily pause the receiving system, place a test order and restore the connection. Check that staff can find the delayed record and that processing it again creates one shipment. Agree who is notified when a transfer remains incomplete.
Give someone else the launch checklist
Ask a colleague who has not been building the shop to buy a specified item without guidance. Watch where they hesitate and have them describe the problem in their own words. Record the device, browser, page, steps taken, expected result and actual result for each issue. Remove personal details from screenshots. This gives the person fixing the problem enough information to repeat it and gives the tester the same route for checking the fix.
Before opening, verify that the public site uses the intended payment mode and that staff know where real orders will arrive. Remove test products from public view and keep an internal record of the cases already checked. Name the person who will follow the first genuine order from payment to handover. If a payment is recorded but the warehouse has no order, that person should know who can pause the affected checkout method and who can reconcile the records.