An online shopping cart is the review-and-decision stage between browsing a store and paying for an order. It holds selected items, lets shoppers change them, and shows prices and fulfillment details before checkout. Adding something to a cart does not guarantee that it is reserved or that the shopper intends to buy immediately.
For shoppers, the cart is where to check what is being bought and what it may cost. For merchants, it is a stateful part of the store that must keep product, price, inventory, delivery, and buyer information in sync. A clear cart reduces uncertainty; it cannot turn every abandoned cart into a lost sale.
What an online shopping cart does
A shopping cart is a temporary or persistent collection of products or services chosen for possible purchase. In a store’s software, it is also a record of items, quantities, pricing context, currency, and sometimes buyer identity. The cart connects the catalog to checkout, where the order is validated and submitted.
Carts serve anonymous visitors, signed-in customers, business purchasing teams, subscription buyers, digital-product customers, and shoppers choosing pickup or delivery. Their purpose is similar across these cases: make the proposed purchase understandable and editable before the transaction is completed.
#1 Best Overall
Cart, checkout, and wishlist are different
| Feature | Cart | Checkout | Wishlist |
|---|---|---|---|
| Purchase intent | Possible or developing | Immediate | Usually future or uncertain |
| Quantity and price calculation | Yes | Final validation | Often limited |
| Shipping and tax | Estimated or partially calculated | Finalized | Usually absent |
| Payment | Usually no | Yes | No |
| Inventory commitment | Usually not guaranteed | Validated during purchase | Usually not reserved |
| Main purpose | Review and decision-making | Transaction completion | Saving for later |
These are functional distinctions, not guarantees about every store’s implementation. Unless the merchant explicitly says otherwise, an item in a cart should not be treated as a reservation. Shopify, for example, describes the cart as part of the buying journey before checkout; its Storefront API cart documentation explains how a cart can carry buyer identity and hand off to checkout.
How a cart works behind the scenes
The storefront creates or updates a cart when a shopper adds an item. A line item normally refers to a product or specific variant, such as a size or color, and a quantity. The commerce system then checks relevant rules, such as availability, price, promotions, shipping eligibility, and tax treatment. The shopper may edit the cart or continue to checkout, where the system performs final validation before accepting payment and creating an order.
- Select: The shopper chooses a product and, where required, a variant or configuration.
- Record: The store adds the item and quantity to cart state associated with a session, browser identifier, account, or server-side cart ID.
- Calculate: The store updates line prices, discounts, subtotal, and any shipping, tax, or duty estimates it can determine.
- Edit or proceed: The shopper changes quantities, removes items, or starts checkout.
- Validate: Checkout rechecks price, inventory, address-dependent charges, and purchase rules.
- Complete: After payment succeeds, the store creates the order and closes or clears the cart.
Common cart storage models
- Session cart: Held temporarily in a browser or server session; it may not survive a long gap or a different device.
- Cookie-based cart: Uses a browser identifier to retrieve cart data. It needs careful privacy, security, and size choices, and usually does not by itself synchronize devices.
- Server-side cart: Stored by the commerce platform or application and accessed through an identifier.
- Persistent cart: Reappears on a later visit, often after sign-in. Persistence can help returning shoppers but can also leave stale items or expose information on shared devices.
- Guest cart: Works without requiring account creation.
- Merged cart: Combines guest-cart contents with an existing account cart after sign-in. The merge needs rules for duplicate items, changed prices, and unavailable products.
- Headless cart: A custom storefront communicates with a commerce platform through an API rather than relying on the platform’s rendered storefront.
For headless implementations, cart state and the transition to checkout are explicit integration responsibilities. Shopify documents those concepts in its Storefront API cart guide.
What a useful cart should show
The cart should answer the questions a shopper needs to decide whether to proceed: What exactly is in the order? What can still be changed? What is the likely cost? How and when will the order arrive? A minimum viable cart should include:
Free tools Windows power users keep installed
One-click scans. No signup required.
- Product name and useful image, plus the selected variant or configuration.
- Quantity controls and a clearly named way to remove each item.
- Line-item price, subtotal, and a clear primary checkout button.
- Availability information and useful errors when an item cannot be purchased as shown.
- Mobile-friendly controls, accessible labels, and keyboard operation.
WooCommerce’s Cart block documentation describes common cart tasks such as reviewing products, changing quantities, removing items, considering shipping options and coupons, and checking totals.
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
Make the cost legible
Show the item subtotal, applied discounts, known mandatory fees, and the total due now. If shipping or tax depends on destination, provide an estimate when practical or explain which information is still needed. International stores should consider duties; subscription carts should make both the initial charge and recurring amount and frequency understandable. For deposits, environmental fees, or other additional charges, identify what is due now and what may be charged later.
A postal-code or location field can improve an estimate, but should not become a needless obstacle. If the final total cannot be calculated until checkout, say why and identify the remaining variables. Unexpected costs are a documented usability concern, but their effect depends on the store and shopper; do not assume every exit is caused by pricing.
Give the checkout action visual priority
Prioritize product identity, options, quantity, price, delivery expectation, and the primary checkout action. Secondary controls—such as continuing shopping or applying a coupon—should remain available without competing with that action. Recommendations, financing prompts, loyalty offers, and promotional banners belong lower in the hierarchy. A mini-cart can be convenient, but it should not hide necessary details or make editing difficult.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Optional features: add only when they solve a real need
Advanced features can improve a particular buying journey, but each adds interface complexity, maintenance, and testing. Select them based on customer needs and operational capability rather than assuming more functionality is always better.
- Save for later and cart persistence: Useful for considered purchases and repeat visits; manage stale prices, changed inventory, and shared-device privacy.
- Delivery estimates, pickup, or local delivery: Helpful when fulfillment choice affects the purchase; estimates should reflect the relevant destination and stock location.
- Gift options, bundles, add-ons, and recommendations: Can support specific product journeys, but should not obstruct review or obscure the total.
- Subscription frequency and recurring-charge details: Put interval, initial charge, and future amount where the shopper can understand them before checkout.
- B2B purchase orders, shared carts, and quantity limits: Appropriate for team purchasing or negotiated rules; make permissions and approval steps clear.
- Back-in-stock alerts and abandoned-cart recovery: Require accurate inventory and communication practices appropriate to the customer and market.
- Multi-currency, localized tax, and duties: Useful for international sales only when display and checkout calculations remain consistent.
Handle price and inventory changes honestly
A cart is not necessarily a promise that price or stock will remain unchanged. Items may become unavailable, a variant may be discontinued, a promotion may expire, or a destination may be ineligible. Minimum quantities, per-customer limits, and cart expiration can also affect what proceeds to checkout.
Behavior depends on the platform and configuration. Shopify says inventory is checked as shoppers progress through checkout and is held only after payment information is submitted; this describes Shopify’s behavior, not a universal rule for all stores. See Shopify’s checkout settings guidance.
When a cart item changes, identify the affected item and explain what changed. Offer a relevant choice—reduce quantity, remove it, or select another variant—while preserving unaffected items. Do not silently alter a quantity or price; recalculate and display totals after an update. If the shopper returns from checkout after a failure, preserve the cart where possible.
Guest checkout and accounts
Guest checkout reduces the work required of first-time, mobile, or one-time buyers and avoids asking for a password before a purchase. Accounts can make repeat orders easier through order history, saved addresses, payment convenience, loyalty features, subscriptions, and cross-device cart access. Neither approach is right for every workflow: B2B approvals or other legitimate operational needs may require identity or account steps.
For ordinary retail purchases, allow checkout without a mandatory account when the business can do so, then offer account creation after the order. If an account is necessary, explain the reason before the customer reaches the final step. Cart merging after sign-in should preserve the shopper’s choices and clearly resolve duplicates, expired promotions, or unavailable products.
Design for mobile, accessibility, and confidence
Mobile usability
- Make quantity and remove controls easy to tap, not dependent on precise gestures.
- Keep product names, variants, prices, and delivery information readable without horizontal scrolling.
- Ensure sticky checkout actions do not cover cart content, and that the on-screen keyboard does not obscure fields.
- Make estimates easy to expand or edit, and ensure interrupted or slow connections do not cause duplicate updates.
- Avoid automatically opening overlays that interrupt review or trap shoppers.
A desktop layout that merely shrinks to fit a phone is not necessarily usable on a phone. Test the actual add, edit, remove, and checkout path at narrow screen sizes and with a slow connection.
Accessibility checks
- Give each quantity field an accessible name and each remove control a name that identifies the product.
- Announce cart updates and changed totals appropriately to assistive technology.
- Associate errors with the relevant control; move focus predictably after removal, updates, and validation failures.
- Make every action keyboard-accessible, including mini-cart dialogs; manage focus when a dialog opens and closes.
- Do not use color alone to communicate errors, discounts, or availability.
- Use meaningful alternative text for informative product images and empty alternative text for decorative ones.
- Use clear wording for checkout actions, maintain readable contrast, and make targets practical to activate.
Accessibility depends on the actual theme, extensions, and implementation, not just the platform name. Baymard’s e-commerce accessibility research discusses WCAG-based considerations for shopping flows. Testing with keyboard navigation and screen readers can uncover problems that a visual review misses.
Rank #4
Build confidence without pressure
Make delivery expectations, returns and cancellation policies, and support information easy to find. Use familiar labels, explain why information is requested, and make the consequences of actions understandable. Shopify’s checkout UX guidance covers clarity and trust in checkout experiences. Avoid false urgency or forced registration; show payment methods that are actually available to the shopper rather than implying universal availability.
Payment security and PCI DSS responsibilities
Payment architecture affects how much sensitive data the store handles, but a hosted payment page, embedded payment fields, and a custom card form are not interchangeable. A hosted or tokenized provider can reduce the merchant’s exposure to card data and PCI DSS scope. It does not remove the need to secure the site and its checkout path.
WooCommerce states that its core plugin is not itself PCI certified; a hosted gateway may significantly reduce scope, while the merchant remains responsible for the wider environment. Its PCI DSS guidance discusses those responsibilities. Use HTTPS across cart and checkout, avoid storing raw card data, keep the platform and integrations updated, limit administrative access, review scripts running on checkout pages, and follow the payment provider’s compliance instructions. Confirm which validation process applies to the particular payment setup; custom payment flows merit review by a qualified security professional.
Understand cart abandonment before trying to recover it
Cart abandonment means items were added but no completed order followed. It is different from checkout abandonment, where a shopper started checkout but did not finish; browse abandonment, where a shopper viewed products without adding them; and payment failure, where an attempted transaction did not succeed.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchBaymard’s checkout usability research page reports an average cart-abandonment rate of 70.19%. This is a benchmark, not a prediction for an individual store or a measure of recoverable revenue. Baymard also notes that some carts reflect browsing, price comparisons, delayed decisions, or gift research rather than a fixable checkout problem. Its benchmark covers 335 top-grossing U.S. and European e-commerce sites against more than 110 cart and checkout guidelines; the same research page reports 65% of evaluated sites as mediocre or worse and 2% as good. These are Baymard’s findings for its benchmark, not universal ratings. See Baymard’s checkout usability research and its discussion of abandonment reasons.
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
Diagnose the point of friction
Do not use one overall abandonment number as a diagnosis. Compare behavior by:
- New and returning shoppers; mobile and desktop.
- Traffic source, product category, and cart value.
- Domestic and international destinations, including shipping country.
- Guest and signed-in carts, and payment method.
- Time from add-to-cart to exit, plus any error or payment-failure reason available.
Check whether the issue is unclear product information, an unexpected delivery cost, an inventory change, a confusing promotion, a slow interface, or a failure during payment. Baymard also reports that 65% of the sites in its benchmark performed at mediocre or worse for checkout UX; that finding indicates room for usability work in the evaluated sites, not a guaranteed conversion increase for any one merchant.
Choose recovery tactics carefully
Cart persistence can help a returning shopper resume. A reminder by email, SMS, or push notification, retargeting, customer-service follow-up for a high-value B2B cart, or a back-in-stock alert may be appropriate when the shopper’s permissions and applicable privacy and marketing rules allow it. Avoid messaging customers after an order has completed, and do not assume a discount is the right response. Many carts are ordinary browsing; routine discounts can reduce margin and teach customers to wait for an offer.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Choosing a cart implementation
Choose based on the need for managed infrastructure, customization, technical capacity, integrations, and operational control. A hosted platform can launch quickly but imposes platform rules; an open-source implementation offers more control while shifting maintenance work to the merchant; headless systems allow deeper customization at the cost of engineering and testing responsibility.
| Approach | Best suited to | Main trade-off |
|---|---|---|
| Hosted SaaS (such as Shopify or BigCommerce) | Teams prioritizing launch speed, managed hosting, and integrated commerce functions. | Recurring platform and extension costs, vendor-specific constraints, and less control over checkout behavior. |
| Open source (such as WooCommerce) | Merchants with WordPress capability, specialized workflows, and willingness to manage their environment. | Hosting, updates, backups, security, compatibility, and extension maintenance are merchant responsibilities. |
| Headless or custom | Businesses needing a tailored storefront or complex integrations, pricing, or channels. | More engineering, testing, security, accessibility, and ongoing upgrade work; greater risk of mismatched inventory or prices. |
Platform-specific considerations
- Shopify: Hosted checkout accepts shipping information and payments after products are added to a cart. Checkout branding and some extensions are managed through Shopify’s checkout and accounts editor, subject to its requirements. See checkout customization documentation and checkout app guidance.
- WooCommerce: Its Cart and Checkout blocks support a block-based store experience. For stores started after WooCommerce 8.3, released in November 2023, those blocks are the default when using a block theme. The cart and checkout pages must be correctly designated in store settings for the blocks to function. See cart and checkout customization documentation and Checkout block documentation. The open-source core is not the total cost of running a store: hosting, payment processing, extensions, security, and development may add costs; see WooCommerce pricing.
- BigCommerce: Its official pricing page presents plan and sales-volume terms that can change. Review current terms directly at BigCommerce pricing rather than relying on an old quoted figure.
- Headless payment collection: A payment provider such as Stripe Checkout may supply hosted or embedded payment components, but it is not by itself a catalog, inventory, or merchandising system. Payment fees and availability vary by market and payment method. See Stripe’s e-commerce checkout guidance.
Test the cart as a system, not just a page
Testing should cover product rules, state changes, checkout handoff, accessibility, and order measurement. Include edge cases such as a variant removed from the catalog, currency changing while a cart is open, a subscription mixed with a one-time item, or a split shipment with multiple delivery dates.
Quick Recap
- Add a product with multiple variants and confirm the chosen option persists.
- Change quantity rapidly, remove an item, and test undo if offered.
- Apply a valid coupon, then an invalid or expired one; verify the displayed and final order totals agree.
- Change shipping country and use postal codes that trigger different shipping rates.
- Make stock unavailable in another session, then verify the cart explains the change without discarding unaffected items.
- Add items as a guest, sign in, and inspect how duplicate or unavailable items merge.
- Open the cart in two tabs and verify concurrent changes do not silently overwrite one another.
- Test keyboard-only use, a screen reader, narrow mobile screens, and a slow connection; disable JavaScript if the implementation claims to support that condition.
- Fail a payment intentionally, refresh after authorization but before confirmation, and return from checkout; check for a preserved cart and no duplicate order.
- Test subscription and one-time items together, plus taxes, duties, and currency for each target market.
- Verify analytics distinguish completed orders from payment failures and duplicate submissions.
Implementation checklist
- Clarity: Show the right product and variant, editable quantities, understandable totals, and realistic delivery information.
- Function: Preserve cart contents through recoverable errors; validate promotions, availability, and checkout handoff.
- Usability: Keep checkout prominent, avoid needless account gates, and test on mobile.
- Accessibility: Label controls, announce updates, associate errors, and verify keyboard and screen-reader behavior.
- Security: Use HTTPS, minimize sensitive data, maintain dependencies, restrict access, and review checkout scripts and payment responsibilities.
- Measurement: Segment abandonment by meaningful shopper and failure characteristics instead of treating every exit as lost revenue.
- Operations: Assign ownership for inventory, pricing, tax, shipping, promotions, extension compatibility, and cart recovery messages.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
