> For the complete documentation index, see [llms.txt](https://script-and-theory.gitbook.io/all-in-one-commerce-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://script-and-theory.gitbook.io/all-in-one-commerce-docs/checkout-blocks/settings.md).
# Settings
1. **General Settings:**
1. In the Checkout Settings tab of the app, merchants can customize various aspects of their checkout experience. This section allows for image styling, product review integration, and automatic recommendations to enhance the user experience and boost conversions.
2. **Product Images:** This setting allows merchants to define how product images appear in the checkout. They can choose between Cover, which ensures the image fills the available space by cropping if necessary, or Contain, which keeps the entire image visible without cropping, maintaining its aspect ratio.
3. **Product Reviews:** Merchants can display product ratings in the checkout by integrating with third-party review apps such as Fera.ai, Judge.me, Loox, and others. Once connected, the selected app will show star ratings and reviews for products directly in the checkout, helping to build customer trust and increase conversions.
4. **Automatic Recommendations:** This setting lets merchants control product suggestions in the checkout. They can manually select specific products to hide from the recommendations section, ensuring that only relevant products appear as upsell suggestions, optimizing the shopping experience for customers.
2. **Data Privacy:**
1. They are representing which data scopes we have access to from your store using our app.
3. **Translations**
In the app we have some default checkout phrases translation option. So merchants will be able to set the language against the predefined phases for some checkout blocks.
---
# 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://script-and-theory.gitbook.io/all-in-one-commerce-docs/checkout-blocks/settings.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.
