Written by DROPS.ST.
Check what the customer enters against what staff receive: contact fields, items, quantities, fulfilment choice and order record. A confirmation page proves only part of the result.
DROPS connects product selection, cart and checkout with customer-linked order items. Connected Telegram uses the same catalogue and order system, giving your team concrete records to reconcile.
Software acceptance and legal/provider eligibility remain separate. An age prompt or payment choice does not establish approval.
Agree on a test that cannot become a real sale
Use an approved test environment with outbound messages and fulfilment disabled. Use fictional records; do not send funds, create funded requests or use real identity documents.
If the environment cannot safely create an order, test through the last safe step. Mark order creation and the staff handoff as untested. A walkthrough is useful evidence, but it is not a completed end-to-end test.
Write down the shop address, device, browser, test date and configuration being assessed. List the enabled ordering methods rather than assuming every possible method is included.
Start with the agreed menu-software requirements. This guide then tests what happens after a customer selects those products.
Use an evidence grid, not a row of ticks
For each check, record the expected result, observed result and evidence. Use passed, failed or untested as the outcome.
| Check | Expected result | Evidence |
|---|---|---|
| Contact | Clear required fields | Fictional values and labels |
| Missing field | Useful rejection | Error and affected field |
| Selection | Correct item and pack | Reference, unit and quantity |
| Quantity limits | Agreed boundaries | Values and messages |
| Fulfilment | Choice preserved | Checkout and record |
| Review | Correct items and charges | Screen and calculation |
| Submission | Success/failure clear | Exact response |
| Staff record | Customer and items match | Test reference and comparison |
Test contact fields on a phone
Open the checkout at a realistic phone width and enter the fictional details yourself. Check that labels remain visible, the keyboard suits the field and an error does not leave the next action unclear.
Leave one required field empty. Correct it after the error appears. Check whether the valid information already entered remains available. Repeat with an invalid format where the form defines one, such as an incomplete email address.
W3C’s form guidance recommends clear success and error feedback, including an explanation of how to correct mistakes. Use that as a usability criterion; it does not certify the shop’s overall accessibility. W3C: form submission notifications.
Follow each supported fulfilment choice
Test each supported fulfilment method separately; one successful path does not establish another.
Switch methods and check for incorrect leftover fields or charges. Delivery information should not silently become a pickup requirement.
Compare the resulting record with the method, destination, timing and instructions staff need.
Keep undemonstrated fields or rules marked untested, rather than treating them as included.
Match the order record to the customer’s selection
Choose a simple item first. Record its reference, unit, quantity and displayed price. Then test a package or quantity tier if that is part of your catalogue.
Compare the customer-facing review with the staff record line by line. Check the customer link as well as the product name. A correct total cannot explain a wrong package or quantity to the person preparing the order.
After a failed or interrupted submission, inspect the test records before retrying. Missing confirmation does not establish that no order exists.
Payment instructions, an unpaid order and confirmed receipt of funds are different states. This test does not require a live payment to show that distinction.
Hypothetical example: pickup succeeds but the handoff fails
A test customer selects two units and chooses pickup. The confirmation shows pickup, but the staff record available to the tester does not show how the order should be fulfilled.
The submission check passes. The fulfilment handoff fails because staff would need to ask what the customer already selected.
Record both observations, assign the issue and repeat the same case after correction.
Make acceptance a decision your team can explain
Block acceptance for errors that change the item, quantity, customer association or fulfilment instruction. Give lesser presentation issues an owner and a review date. Keep untested paths visible.
Choose DROPS when you want a shop whose catalogue and customer-linked order records can be assessed together. The value is a clear route from a buyer’s selection to the information your team needs, with optional Telegram ordering on the same system.
Explore DROPS and open the demos. Bring this grid to the demonstration and use an approved environment for the record and staff-handoff checks.