An ecommerce checkout can look finished and still become difficult at the moment a customer needs to choose delivery, enter details or pay. A practical test checks the complete path—from product page and cart through payment, confirmation and the order record—rather than relying on a quick visual scan. For Australian stores, that means checking details such as postcode-based delivery, displayed prices and GST treatment, and the payment methods your store actually offers. Work through the checklist on a phone and desktop, using representative products and delivery addresses. Test the normal route as well as predictable snags: an unavailable item, a declined payment, an invalid postcode or a discount that should not apply. Use your provider’s test mode where available; confirm how to avoid or reverse a real transaction before testing live. Record what you expected, what happened and how to reproduce any issue, then retest after changes. A hypothetical example: a store owner tests a regional postcode and finds the free-shipping threshold is calculated before a discount, contrary to the store’s stated rule. This guide helps you identify such gaps systematically, without treating any single checkout design as right for every shop.
Content
Map the journey
Map the journey before testing
Before placing an order, write down the route a customer is expected to take from product selection to order confirmation. This gives you a clear sequence to follow and makes it easier to spot where the checkout behaves differently from the store’s intended process. Include choices customers can make, such as checking out as a guest or signing in, selecting a delivery method, entering a discount code and choosing a payment option. Note any alternate route, such as collection or a subscription purchase, only if your store offers it.
Start by reviewing the checkout as it is currently configured, rather than relying on what you remember. Note each page, screen or step, and what the customer must do to continue. A typical sequence might be:
- Add a product to the cart and review the cart contents.
- Proceed to checkout and choose guest checkout or sign in, if both are offered.
- Enter contact and delivery details, then select a delivery option.
- Review the order summary, including discounts, delivery charges and GST information.
- Choose a payment method and submit the order.
- Check the confirmation shown to the customer and the order information available to staff.
Next, decide what you are testing and record the setup. Include the date, the store environment (such as a staging site or live site), device and browser, products in the cart, and customer details or postcode used. Use test customer details where appropriate, and avoid exposing real customer information in notes or screenshots. If the store has a payment gateway test mode, confirm how to use it and what it does not cover: a simulated payment may not exercise every part of a real transaction. For a live transaction, agree on the process with the store owner first, including how the order will be identified and any required cancellation or refund steps.
For every step, write down the expected outcome before you run the test. Be specific enough that another person could decide whether the result passed. For example, after adding a product, expect the cart to show the selected item and quantity. After entering delivery details, expect the available delivery choices to match the store’s configured rules. Before submitting payment, expect the order summary to show the selected items and charges, with a clear total. After submission, expect a message and order status that reflect whether the order was accepted and whether payment is complete, pending or failed. These are test expectations, not assumptions about what a particular platform will do; check them against the store’s settings and policies.
Keep the checklist simple and record the actual result beside each expectation, including the step where anything unexpected happens. Note whether the issue is repeatable and what action led to it. This creates a useful starting point for investigating problems and retesting after a change. It also helps separate a checkout defect from a setup difference, such as using a different delivery region or payment environment. Once the journey and expected outcomes are clear, you can test consistently instead of placing orders without a defined purpose. If more than one person tests the store, share the same setup and expected outcomes so their results can be compared.
Test cart and forms
Check cart changes and form behaviour
Start with a test product and follow the store’s normal route into checkout. Change the quantity, remove an item and, where relevant, change a size, colour or other option. Check that the cart and checkout reflect each change, including the item description, quantity and displayed subtotal. Use the cart’s back, continue-shopping and edit controls, then return to checkout. Confirm that earlier choices remain correct rather than relying on what the page appeared to show before you left it. If a product has options that affect price, verify that the selected option and its price remain clear in the order summary.
Also test what happens when you refresh the page or use the browser’s back button. The cart should not unexpectedly duplicate an item, revert to an old quantity or lose a valid selection. If the store displays stock or availability information, check that it does not contradict the product choice shown in the cart. Try an item that is no longer available if you can do so safely in a test environment, and note whether the customer receives a useful explanation and a practical next step. Record the exact steps whenever the result differs from what you expect; this makes it easier to reproduce and investigate the issue.
Work through every customer-details field using realistic test information. Check that labels make each field’s purpose clear and that required fields are identified. Review fields for names, email, phone, billing and delivery addresses, including any apartment or unit details your customers may need to enter. For an Australian address, check that the state and postcode can be entered in a straightforward way. If billing and delivery details can be different, try both the same-address and separate-address paths and confirm the form responds as expected. Check optional fields too, such as delivery instructions, to ensure they are not mistakenly treated as mandatory.
Check whether the form asks only for information needed to complete the order. Try the browser’s autofill where available, and confirm it puts information in the correct fields rather than, for example, placing a suburb in the street-address field. Enter valid details, then test common mistakes such as leaving a required field blank or entering an email address in the wrong format. Errors should explain what needs attention and appear close enough to the relevant field to find easily. Correct the mistake and continue: verify that the customer does not have to re-enter unrelated details. Do not rely on colour alone to signal an error, and check that a keyboard user can reach and identify the field that needs correction.
Repeat the journey on a phone and a desktop-sized screen. On a phone, check that fields and buttons are easy to tap, text is readable without horizontal scrolling, and the on-screen keyboard does not obscure the field being completed. Try moving between fields and correcting an error. On desktop, check that the form is easy to scan and that the main action is visible without confusing or competing controls. If possible, test on a real phone as well as resizing a desktop browser; touch and keyboard behaviour can differ. Use a store test mode or another safe, documented process so you do not create unintended live orders or use real customer information. Record the device, steps and outcome for any problem, then repeat the same steps after a correction.
Verify payments and totals
Check every payment path and the final amount
Start by listing the payment methods customers can actually choose at checkout, then test each one separately. Depending on your store, these might include card payments, a digital wallet, buy now, pay later, or another option. Do not assume that a successful test with one method proves the others work: each can have its own checkout flow, confirmation and failure behaviour. Use your payment provider’s test mode or sandbox when available, following its instructions for test details. If you need to test a real transaction, arrange it with the business, use an authorised payment method, and understand any fees and refund steps before proceeding. Never use a customer’s payment details.
For each path, place an order using a product with a known price. Check that the payment option is presented clearly, that you can complete the payment, and that the order reaches the expected status in the store. Confirm the customer-facing confirmation and the order record show the same payment method and amount. If the payment is declined, cancelled or abandoned, note what the customer sees and whether the order is left in an accurate state. Do not treat a test card number or provider message as universal; use only the scenarios documented by the provider for your account. If a method redirects customers to another service, check that the return to the store is understandable and does not imply success before payment is confirmed.
Reconcile prices, GST and totals
Check the product price on its page, in the cart and in checkout. Confirm that any selected variation or quantity change updates the line price and subtotal correctly. For a consumer-facing Australian store, where GST applies, the total price displayed to consumers generally needs to include GST. GST can also be shown as a separate item in the breakdown, but it should not appear as an unexpected extra added to the advertised or displayed consumer price at checkout. Check the product page, cart and checkout together so the customer sees a consistent total, including any applicable delivery charge or other unavoidable charge once it can be calculated.
Some stores quote prices to business customers exclusive of GST. If that is the intended audience and pricing basis, make the GST-exclusive treatment clear before a customer commits to the purchase and show the applicable GST and payable total in the order summary or tax invoice. Do not assume a business customer label alone makes an unexpected checkout surcharge appropriate; the pricing presentation should match the customer audience, the stated terms and applicable Australian requirements. If your store serves both consumers and businesses, check how each audience sees prices and totals rather than relying on a single test account.
Recalculate the order using the figures shown to the customer. Check that the subtotal, any discount, delivery charge, GST and final amount agree with the checkout summary and the order record. If shipping is not yet known at an earlier checkout step, confirm the total updates once the customer enters the relevant details, rather than implying that an incomplete figure is final. Also check whether a discount changes the taxable amount as intended under your store’s configuration. Consider items with different tax settings, if your catalogue includes them, and check that rounding does not produce a confusing difference between displayed components and the total. For tax questions about your business, confirm the correct treatment with your accountant or tax adviser; a checkout test can reveal a calculation or display inconsistency, but it cannot determine your tax obligations.
Keep a short record for each test: the product and quantity, payment path, figures expected, figures displayed, and the result in the order record. If something differs, note the exact step and capture the relevant screen or order details without retaining sensitive payment information. Check the store’s tax and payment settings before changing them, and retest affected payment paths and totals after any correction. This makes it easier to distinguish a display issue from a payment or tax-configuration problem and gives you a repeatable check whenever products, checkout settings or payment arrangements change.
Check delivery and discounts
Check delivery and discounts
Delivery options and promotional rules can depend on details that are easy to overlook, such as a customer’s postcode, the products in the cart or whether the order meets a minimum spend. Test these rules deliberately rather than checking only one familiar address and a straightforward order. Before testing, note the store’s stated delivery policy and the expected outcome for each scenario. That gives you something specific to compare with the checkout, and helps distinguish a configuration problem from an unclear policy.
Use postcodes that represent the areas your business serves, including metropolitan, regional and remote locations where relevant. Enter each postcode in the checkout and check which delivery methods, rates and delivery messages appear. If the store offers collection, check whether it is shown under the intended conditions. Try an address outside the delivery area too, if the policy excludes one, and confirm the checkout explains what the customer can do next rather than presenting a confusing or contradictory option. Test the address fields together: a postcode accepted on its own may still produce an unexpected result once the suburb and state are completed.
Then test the shipping rules that affect the price. Check an order below and above any free-shipping threshold, and compare carts with different product types if rates vary by size, weight or category. Confirm that the displayed charge matches the rule you intended, and that adding or removing an item updates the delivery options and total. If a rate is calculated by an external service, check that the checkout’s response is clear when a rate cannot be returned; do not assume an unavailable option means delivery is free. If delivery cost depends on a later fulfilment decision, make sure the customer is told how and when the final charge will be confirmed.
Test promotions separately and in combination with delivery rules. Enter valid and invalid codes, and check the conditions that matter for your store: minimum spend, eligible products or categories, exclusions, expiry and whether codes can be combined. Try a cart just below the minimum, then one that qualifies. Check that the discount is applied to the intended items and that the revised subtotal, shipping charge and order total remain clear. If a code is rejected, read the message as a customer would: it should help explain the issue without suggesting a discount has been applied when it has not. Where a promotion affects GST or a shipping threshold, confirm the outcome matches the store’s configured policy and seek tax advice if required.
Hypothetical example: A regional postcode reveals that a shipping rule does not match the store’s stated delivery policy. The owner can record the postcode, cart contents, displayed method and charge, then compare those details with the policy and adjust the rule or wording as appropriate. The point of the test is to identify the mismatch before a customer encounters it, not to assume every regional address should receive the same rate.
Keep a simple record of each test: the postcode or promotion code used, relevant cart details, expected result and actual result. Where possible, use a test environment or another safe process that avoids creating an unintended live order or charging a customer. After changing a shipping or discount setting, repeat the affected scenarios and check the final total again. This makes it easier to spot unintended interactions—for example, a code changing whether an order qualifies for a delivery threshold—and gives you a repeatable check when policies, products or checkout settings change.
Test errors and confirmations
Use controlled failure scenarios
Test failures in a payment provider’s sandbox or test mode where available, following its documented test procedures. Avoid deliberately triggering test scenarios with a live card: you could create a real charge or order. Check how checkout responds to a declined payment, an incomplete payment form and a required field that has been left blank. The message should explain what the customer can do next, such as checking their details or choosing another payment method, without exposing technical errors or sensitive payment information. Check that the message remains visible long enough to read and is understandable on a phone as well as desktop.
Also consider what happens if the customer loses connection, refreshes the page or uses the back button while a payment is processing. Do not simulate an interruption by cutting off a live transaction. In a safe test environment, check whether the customer can tell if payment succeeded and whether trying again risks creating a duplicate order or charge. If the outcome is unclear, check the order record and payment provider’s transaction record before retrying. Never assume a payment failed just because the browser did not show a confirmation page. Where the provider’s test tools do not simulate a scenario, document that limitation rather than testing it with a live customer transaction.
Check what customers and staff are told
For each test, compare the final checkout message and any order email with what actually happened. A successful payment should not be presented as failed, and a failed or pending payment should not be described as a completed, paid order. Check that the customer can see whether the order was placed, what action is needed next and how to contact the store if they need help. Make sure messages do not show full card details, internal error traces or other information that should remain private. Read the message in context: a generic “thank you” page is not enough if the payment still needs customer action.
Then check the store’s order screen and any staff notifications that are configured. Confirm that the order appears once, its payment status is understandable, and the recorded items, quantities, delivery details, discounts, GST and total match the checkout. If the payment is pending or has failed, staff should be able to distinguish that from a paid order before preparing or dispatching it. Where notifications are used, verify that they go to the intended recipients and contain enough information to identify the order and its status, without including unnecessary customer or payment data. Check that the customer’s email address and the order reference are accurate in the confirmation.
Keep a brief record of each scenario, the expected response and what you observed. Use test customer details, and remove test orders or clearly mark them according to your store’s procedures so they are not mistaken for real purchases. If the checkout displays a vague error, creates duplicate records, or leaves the payment and order statuses inconsistent, pause further live testing and investigate the settings or seek help from the relevant platform or payment provider. Retest the same scenario after making a change to confirm the customer-facing message and staff record now agree. Include any limitations in the test record, such as a provider flow that could not be safely simulated.
Conclusion: Retest routinely
Conclusion: Retest routinely
A checkout test is most useful when it is repeated, not left as a one-off task. Keep a dated copy of your checklist and note the test setup, expected outcome and any issues found. After changing checkout settings, adding a payment method, updating a plugin or theme, or changing delivery rules, retest the affected steps and place a complete test order where practical. Check that the order appears correctly in the store and that any customer and staff notifications contain accurate details.
Set a regular review interval that suits how often your store changes, and assign someone to carry it out. Use a safe test method approved by your payment provider, and avoid creating real charges or sending confusing messages to customers. If a problem appears, record the device, browser, steps and error message, then investigate or ask your developer or hosting provider for help. Once fixed, repeat the relevant test and confirm the rest of checkout still works. Keep the checklist practical: prioritise the payment, pricing, delivery and form paths customers use most, while retaining tests for less common cases that could prevent an order.
Explore related information: Booking Website Design & Development; Web Design Sunshine Coast.

