Definition:
An electronic cart or shopping cart is the function of a digital shop that retains selected products or services before an order is confirmed.
It allows the selection to be reviewed and modified and transfers it to the purchasing process. Adding an item to the cart does not necessarily reserve stock, preserve its price or complete a purchase.
Table of contents
How an electronic cart works
When a person adds an item, the system creates or updates a state associated with a session, account or another permitted identifier. This state may remain available during navigation and be retrieved later according to the shop’s configuration.
A cart commonly contains:
- Products or services: Identifiers for the selected items and the information required to display them.
- Variants and configuration: Size, colour, option, date, personalisation or other choices affecting the selection.
- Quantities: Number of units, applicable limits and controls for modifying or removing items.
- Prices: Unit amount, subtotal and currency, indicating when a value is provisional or may be updated.
- Discounts: Coupons, promotions or applied rules and the conditions for retaining them.
- Estimated costs: Taxes, shipping, fees and other amounts when they can be calculated before checkout.
- State and continuity: Update time, relationship with a session or account and conditions for retrieving or synchronising the selection.
The interface may show availability, delivery times and an estimated total, but this information needs to be checked again before the order is confirmed. Changes in stock, price, address, taxes or delivery option may alter the result.
Differences between a cart, wishlist, checkout and payment gateway
A cart contains a selection prepared to progress towards a possible order. A wishlist stores items for later reference without assuming an intention to purchase them at that time.
Checkout is the process in which contact, billing, delivery, cost, terms and payment information are confirmed. It may begin from the cart but constitutes a separate stage.
A payment gateway transmits or coordinates the information needed to authorise payment. The cart should not directly handle card details unless it forms part of an architecture specifically prepared for that purpose.
An order is created or confirmed according to the shop’s rules. An authorised payment, an accepted order and an inventory reservation are related states but do not necessarily occur simultaneously.
Persistence, availability and user experience
A cart may last only for a session, be stored for a period or be linked to an account. When a person signs in after adding items, the system needs to decide whether to retain the local cart, retrieve the account cart or combine both.
Cross-device continuity depends on an authorised way to recognise the same account or session. It is not an automatic cart property and may create conflicts when quantities, prices or stock have changed.
Persistence needs to be limited to necessary information and comply with the applicable privacy configuration. Stored products may reveal interests or personal circumstances, particularly in sensitive categories.
The interface needs to allow items, variants, quantities, costs and errors to be reviewed before continuing. It also needs to work with keyboards, assistive technologies and different screen sizes.
Fast payment may reduce some checkout steps when it uses securely stored information, but it does not remove the need to display the order and its conditions. Recommendations may also accompany the cart, although they should not add products or change quantities without an understandable action from the person.
Cart abandonment and evaluation
Cart abandonment occurs, within a defined measurement, when a cart is started and the corresponding purchase is not recorded during the selected window.
The rate can be calculated by dividing initiated carts without a purchase by all initiated carts and multiplying the result by 100. The definition of an initiated cart, the identifier being used and the time allowed for purchase need to remain consistent.
The add_to_cart, view_cart, begin_checkout and purchase events represent different stages. The Google Analytics ecommerce documentation describes these events and their parameters, but their collection needs to be verified in the actual implementation.
Abandonment locates an interruption but does not automatically identify its cause. A person may be comparing products, saving a selection, postponing a decision or encountering problems with availability, costs, trust, navigation, accounts, delivery or payment.
CRO can use technical logs, usability tests, surveys, segmentation and experiments to assess these hypotheses. Improvements need to be evaluated alongside errors, returns, order quality and satisfaction, not only by the percentage of purchases.
Reminders require a valid contact route, an appropriate basis and proportionate frequency. Discounts should not be applied automatically as a universal response because they may affect margins, expectations and behaviour without addressing the cause of abandonment.