# Adding to cart — Flows

Shopping online means users need to easily add products they want to their cart. This fundamental action can make or break a sale, so getting it right is crucial.

Source: https://www.checklist.design/flows/adding-to-cart

## Items

### Outline variant selection for product
Whether it’s size, colour, amount or something else, it must be clear what details must be picked to be able to add an item to cart.

### Primary action on product page is add to cart
One of if not the most prominent button on the page to draw the user’s attention. This may change if you want an 'add to cart' button on a grid view of multiple products.

### Feedback once added
Immediate confirmation the item has been added. This can be done several ways and depends on the amount of intrusion you want to have, which is why 2 options are shown.

### Link to cart view
Typically in a primary navigation, so that if the user continues shopping but is then ready to checkout, the cart is easily accessible. Showing the number of products is a way to catch their attention that they have items added but not purchased yet. A total price can also be considered to be shown.

## License for the Checklist Design collection

Checklist Design collection: https://github.com/Checklist-Design/skills
Snapshot: bfae71e507b1b7c03c12e0756402b60eb80f5d14 · Imported: 2026-11-12
Republished under the MIT License. Original checklist text belongs to Checklist Design.

MIT License

Copyright (c) 2026 Checklist Design

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.