Shopping Sites

• Usability principle: Shopping sites rely on progressive disclosure, meaning users see only the choices needed at each stage of buying. This works because fewer simultaneous decisions reduce confusion and speed completion. It is especially important on mobile screens where space and attention are limited.

• Trust and security principle: Users share personal and financial data only when a site signals credibility through secure payment flow and clear policy communication. Trust works as a prerequisite variable: if perceived risk is high, conversion drops even when products are attractive. This is why security is both a technical requirement and a user-experience requirement.

• Conversion-oriented metrics: A shopping site is evaluated with measurable outcomes such as conversion and basket value rather than page views alone. A common metric is $\text{Conversion Rate} = \frac{\text{Orders}}{\text{Visits}} \times 100\%$, where visits are sessions and orders are completed purchases. Another useful metric is $\text{Average Order Value} = \frac{\text{Revenue}}{\text{Number of Orders}}$, which helps assess basket and upsell design.

Purchase Flow Design

• Step sequence: A robust flow follows discover -> select -> basket -> checkout -> pay -> confirmation. This order works because each step resolves one decision layer before introducing the next. It should be implemented with visible progress so users know where they are and what remains.

• Catalogue-to-basket technique: Add clear product cards, filter controls, and a prominent add-to-basket action with immediate feedback. This reduces uncertainty by confirming that the selection was successful and editable later. It is most effective when each product page includes price, availability, and delivery cues.

• Checkout optimization: Keep forms minimal, support account sign-in or guest checkout, and place delivery, voucher, and payment actions in a predictable order. This works because form friction and hidden fees are major causes of drop-off. A simple total-cost model is $\text{Order Total} = \sum (\text{Item Price} \times \text{Quantity}) + \text{Delivery} - \text{Discount}$, which should always be shown before payment.

Key takeaway: Reduce steps, reduce uncertainty, and reduce re-entry of data to increase successful transactions.

• Functional differences matter: Similar interface elements can serve very different goals, so students should identify each stage by purpose rather than appearance. This prevents mixing up browsing, temporary selection, and commitment actions in exam responses. Distinguishing intent is often more important than naming a button.

Comparison Table

• Guest checkout vs account checkout: Guest checkout minimizes barriers for first-time buyers and can improve completion speed. Account checkout supports history, saved details, and personalization but may create sign-up friction. The best strategy is to support both and let users choose based on intent.

• Mistaking basket for purchase: A frequent misconception is that adding to basket means the order is complete. In reality, basket status is provisional until checkout and payment succeed, so stock and payment states may still change. This distinction matters when explaining transaction processing.

• Assuming security is only technical: Learners often describe encryption but ignore user trust signals such as transparent pricing and recognizable payment handling. Security works as both backend protection and front-end reassurance. Answers are stronger when both dimensions are included.

• Ignoring operational trade-offs: Students may state that online shopping is always better because it is faster and available all day. However, convenience can be offset by delivery fees, delays, and less personal support. Strong reasoning acknowledges context instead of absolute claims.