If the home page opens but a customer can’t place an order, check the purchase journey itself. Website availability and a working cart are different things: the page may respond while a button, data submission, or order receipt by staff does not work.
reChecker checks the website’s response. For an important page, you can specify a URL and expected text, but the service does not place a real order, pay for it, or confirm that a manager received it. Check these steps separately.
Find out where the customer got stuck
Ask them to name the page, action, and time: “I added the product to the cart, clicked ‘Place order,’ and got this message.” Ask what device and browser they used if you can’t reproduce the problem. Don’t ask them to share their full card number or password.
Open the same URL without logging in to the site’s admin area. Repeat the steps up to the point where the problem occurred. Distinguish between specific cases: the button does nothing, fields are cleared, an error appears, a confirmation is shown but the manager can’t see the order.
A green status in uptime monitoring does not disprove the complaint. It indicates that the checked URL responded at the time of the request. If the visitor encountered a problem at a different step, investigate that step.
Prepare a check without placing a real order for goods
Before submitting a test order, agree on the process with the staff member who handles orders. Specify how to distinguish the test from a real purchase and how to end the check. For example, add “TEST — DO NOT SHIP” in the comment, and make sure the manager knows in advance who will be testing the site and when.
If checkout requires payment, agree separately on how to test it. A successful order without payment does not confirm that payment works, and the result of the payment step does not automatically show that the staff member received a notification.
For a small store, the checklist might look like this:
- Open the product page for the selected item on a phone.
- Add one item to the cart and check the price.
- Enter the agreed test details.
- Submit the order and save its number if the site displays one.
- Ask the manager to find the order and confirm its details.
- Close the test record according to the store’s usual procedure.
Adapt the steps to your actual process. A service website may have a form instead of a cart; don’t add a CRM check if the company doesn’t use a CRM.
Check what happens after the “Thank you” message
A success screen is an interface message. It doesn’t prove that the data was saved and forwarded. Check the result the visitor contacted the company to get.
| What you were able to see | What else to check |
|---|---|
| The page opened | Whether you can complete the next step |
| The form showed a confirmation | Whether the request is available where the company receives it |
| The order was found in the internal system | Whether the product, price, and contact details are correct |
| The manager confirmed receipt | Whether normal processing can begin |
For example, the site shows “Order accepted” and displays a number, but the manager hasn’t received an email. That indicates a notification or downstream routing problem, not proof that the cart failed completely. Record what you’ve confirmed and where the check stopped.
Website monitoring can help you compare the time with availability and technical results. The presence of expected text on the cart page still does not replace the steps described above.
Give the developer the details and repeat the check after the fix
In the ticket, include the URL, time and time zone, device, steps, and actual result. State what should happen: “After submission, the manager should see the order with the selected product and the contact details provided.”
A suitable description would be: “04.10 at 14:20 Moscow time, phone, product page /catalog/chair. The product is added to the cart. After submission, confirmation №123 is shown, but the manager can’t find the record. The home page opens. Please check whether this order is being saved.” This is an illustrative example; replace it with your details.
After the fix is published, repeat the same agreed test on the primary domain. Ask the staff member to confirm the step that was broken. If the developer only tested it on their own setup, the published site still needs to be checked. You can get the other fields from the ticket template.