Imagine an Australian retailer reviewing the checkout for a small range of household products. Customers ask when delivery costs appear, staff spend time checking incomplete orders and the team is considering several checkout options. This is an illustrative planning scenario, not a report about a real business or measured sales results.
The team wants a shortlist that fits its existing order workflow. Instead of choosing the option with the most features, it follows an ordinary order from the customer’s product choice through payment, confirmation and fulfilment.
The first review finds a workflow problem
In the scenario, the team has focused on the final payment screen while treating product information and delivery choices as separate projects. That makes it difficult to explain which information the customer should already know and which details the checkout needs to collect.
The team sketches the sequence using fictional products and addresses. It identifies where stock availability is shown, when delivery can be calculated and how an order becomes ready for packing. The purpose is to find missing decisions before buying another tool.
Staff then distinguish necessary information from fields added because a template happened to contain them. Each field needs a reason connected to the sale or fulfilment. They leave questions about legal and privacy obligations for appropriate review rather than assuming a shorter form settles compliance.
The pricing check changes the shortlist
The team reviews the ACCC’s current business price-display guidance. It explains that the displayed minimum total cost includes taxes and unavoidable or pre-selected extra fees. The guidance also distinguishes charges that cannot yet be quantified.
They therefore ask each candidate how it displays the product price, selected options, delivery information and final total. They do not accept a demonstration that hides a predictable charge until the last step. Where a cost depends on the destination, they examine when the necessary information is collected and the amount shown.
The retailer chooses not to preselect paid add-ons in its proposed design. That is a design decision to make the choice clearer, rather than a claim that every preselected option is automatically prohibited. The actual pricing arrangements still need review against current requirements.
Two options are compared using the same order
One candidate fits the existing store system with limited configuration; another offers more flexibility but needs additional integration work. The team does not assign either a winner immediately. It asks both to demonstrate the same ordinary order and the same exception.
The ordinary order uses an available product and a supported delivery address. The exception changes the basket after delivery has been selected. Staff check whether quantities, availability and totals remain understandable and whether the customer can correct the order before committing.
They also examine what happens after an unsuccessful or uncertain payment response. The design should not encourage a customer or staff member to guess whether another payment is required. The team asks how the payment and order records can be checked through the approved systems.
The shortlist includes the staff side
A checkout can look simple to the customer while creating repeated work behind the scenes. The retailer asks how paid orders reach the packing process, who can change a status and how customer enquiries can be answered accurately.
They compare setup, ongoing charges, staff training and maintenance alongside the visible screens. They ask which parts are standard features and which depend on another service. An inexpensive first subscription is not treated as the whole cost of operating the arrangement.
- Can staff identify the correct order and payment status?
- Can customers review and correct key details?
- Are totals and selected options understandable?
- Does fulfilment receive the information it needs?
- Can access be limited to appropriate staff roles?
- Are records and exports usable if the service changes?
A small test uses safe information
The team uses fictional customer details and the payment provider’s authorised testing facilities. It does not test by circulating live card information or copying private customer messages into a demonstration. Any later live change needs its own controlled implementation plan.
They ask a person unfamiliar with the design to explain the delivery choice and total before the final action. Confusion becomes a specific note to investigate, not an invented conversion statistic. The exercise tests comprehension and workflow fit rather than promising sales growth.
Testing also includes a small-screen view and correction of an entered detail. The team records issues with labels, navigation and error messages and asks whether the proposed option can resolve them without creating another manual task.
The decision leaves clear conditions
The retailer narrows the shortlist based on the demonstrated workflow, unresolved questions and total operating commitment. It asks for written clarification before agreeing to integration work. No option is described as automatically compliant or certain to increase completed sales.
The useful outcome is a reviewable decision: a checkout that explains the purchase clearly, supports the order process and has known limits. Further spending follows evidence about that fit rather than a feature comparison alone.