> For the complete documentation index, see [llms.txt](https://docs.klai.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/pages/cart.md). # Cart 🛒 * [ ] Metadata of items added Name, size, style, quantity, price and images should all be present * [ ] Change or remove item Give the user the ability to edit their items inside the cart * [ ] Shipping options Variants in delivery based on location, weight and time ⭐️ Clearly show alternative shipping methods and the costs for each (if available) * [ ] Apply promo, discount or coupon An obvious text field to enter a code for a reduced price * [ ] Accepted payment methods Ways a user can fulfil their purchase * [ ] Link to support Incase a user has issues or questions about their items * [ ] Link to checkout For when they're ready to move on and fulfil their purchase * [ ] Suggested items to add A great opportunity to upsell items that are relevant to those in the cart already --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/pages/cart.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.