> For the complete documentation index, see [llms.txt](https://developer.esw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.esw.com/adobe-commerce-magento/adobe-commerce-extension-integration/getting-started/general-setup.md).
# General Setup
## Enabling ESW Checkout
The configuration section for the Checkout is accessible from the main ESW Module configuration tab.
When the Checkout option is enabled, custom pricing logic applies, and directing shoppers to the ESW Checkout will only be active for selected countries as configured.
If a customer initially selects a non-ESW country and then changes the shipping address to an ESW country during the native checkout process, they will receive an error notification and be blocked from proceeding further.
### Configuring Frontend Widgets
The configuration section for the Retailer Display Configuration is accessible from the main ESW Module configuration tab with default settings.
The ESW Adobe Commerce (Magento) extension uses the native Adobe Commerce (Magento) configuration to setup countries to be displayed on the ESW landing page and footer.
The welcome mat and drop-down selections are a part of the extension templates. If you want to change the default output provided by the extension, override the theme in your Custom Theme. This is the basis of template customization in Adobe Commerce (Magento).
* The shipping country, currency, and language options displayed in the front-end widget are based on the Adobe Commerce (Magento) configuration. The shipping countries are based on all countries selected under General > Allowed Countries.
* Only a unique country per website is allowed within multiple running websites. The mapping between a country and currency is supported by the extension and can be changed by navigating to Checkout > Country - Currency Mapping.
The default look is provided for the Adobe Commerce (Magento) Luma theme.
### Redirection to ESW checkout flow
There are two types of checkout flows:
* ESW supported countries, where the shopper cuts across to the ESW checkout.
* Traditional or domestic ecommerce platform flow for non-ESW supported countries.
The following steps describe the flow
{% stepper %}
{% step %}
####
When a shopper clicks Proceed to Checkout after adding products to their cart, a call is made to the Checkout API (called Preorder request)
{% endstep %}
{% step %}
###
On success, an ESW redirect URL is passed in the response and the shopper is redirected to the ESW checkout. On failure, the shopper remains on the retailer’s cart page.
{% endstep %}
{% endstepper %}
---
# 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://developer.esw.com/adobe-commerce-magento/adobe-commerce-extension-integration/getting-started/general-setup.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.