> 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/light-touch-integration/features/fixed-pricing.md).
# Fixed Pricing
ESW Light Touch Integration (LTI) fixed pricing lets you set product prices directly for selected countries. It removes the need for dynamic price conversion in those markets.
With fixed pricing, you control the shopper-facing product price. ESW checkout uses those pre-set prices and then calculates shipping, duties, and taxes.
### Supported LTI platforms
Platform
Description
Web Platform
Supports fixed pricing through the LTI web integration path.
Callback API
Supports fixed pricing through the custom LTI integration path.
### Fixed pricing countries
Fixed pricing countries are countries configured to use the **Fixed** pricing model. In those countries, you are responsible for displaying the correct shopper price.
ESW checkout receives the PreOrder with prices already set in shopper currency. It then calculates shipping, duties, and taxes from those prices.
### When to use fixed pricing
Use fixed pricing when:
* You want to set your own prices for selected countries.
* You do not want LTI to convert those prices dynamically.
* You still want shoppers in those countries to pay through ESW checkout.
* You want ESW to manage those orders while you keep pricing control.
### How fixed pricing works
{% stepper %}
{% step %}
#### Configure fixed prices
Pre-configure product prices in your e-commerce platform for the countries that use fixed pricing.
{% endstep %}
{% step %}
#### Sync the catalog with ESW
Your catalog, including fixed prices, is synchronized with ESW for checkout handling.
{% endstep %}
{% step %}
#### Display shopper prices
There are no real-time currency conversions at checkout. Shoppers see the pre-configured price in shopper currency.
{% endstep %}
{% step %}
#### Use the correct cart logic
If at least one country uses fixed pricing, your cart retrieval logic must handle country and currency parameters correctly.
{% endstep %}
{% step %}
#### Return the right cart by pricing model
For dynamic pricing countries, the `GetCart` response returns prices in default retailer currency. For fixed pricing countries, LTI sends `GetCart` with explicit country and currency parameters so you can return the correct price catalog.
{% endstep %}
{% step %}
#### Keep storefront prices aligned
If the shopper switches between fixed pricing countries, you remain responsible for updating and validating prices on the page and in the cart.
{% endstep %}
{% endstepper %}
### Fixed pricing scenarios
#### Shopper switches to a fixed pricing country
When a shopper changes the shipping country to a fixed pricing country:
* LTI updates the `ESW_LTI` cookie.
* If you subscribe to that cookie, you can detect the country change and fixed pricing status.
* Once fixed pricing is `true`, you should update all storefront prices from the price book for that country.
* Pricing Advisor multipliers are not used.
You are responsible for setting prices and calculations on the storefront. ESW only consumes those prices at checkout.
#### Shopper switches from fixed pricing to dynamic pricing
When a shopper changes from a fixed pricing country to a dynamic pricing country:
* LTI updates the `ESW_LTI` cookie immediately.
* LTI resumes using the base price data attributes.
* LTI applies multiplier, rounding, and display model logic for the selected country.
* Storefront prices then follow the dynamic pricing model.
#### Shopper selects a custom country
When a shopper selects a custom country:
* The retailer fully manages prices, currency, rounding, and display logic.
* LTI still updates the `ESW_LTI` cookie when the shipping country changes.
* LTI does not control or modify storefront prices for that country.
### Storefront behavior
#### Fixed pricing country
LTI does not update prices on the page. You are responsible for displaying prices from the correct price book for that country.
#### Custom country
Custom country behavior depends on whether fixed pricing exists in the tenant:
1. **No fixed pricing countries configured:** when a shopper selects a custom country, LTI reverts prices to the values in the data attribute. You should then update and manage prices for that country.
2. **At least one fixed pricing country configured:** when a shopper selects a custom country, LTI does not revert prices. You should update and manage prices for that country.
### Checkout behavior
#### Fixed pricing country
LTI sends the `cart id`, `pricingsyncid`, default country, and default currency. Product prices are then retrieved from the cart in shopper currency from your platform backend.
No further product price calculations are needed at checkout. Only shipping, duties, and taxes are calculated.
#### Custom country
The shopper is redirected to checkout, which may or may not be ESW checkout. ESW does not charge the shopper, create an order, or take further action for custom country shoppers.
{% hint style="info" %}
#### Notes
* In a Callback API integration with no fixed pricing countries configured, LTI controls prices only for configured ESW countries. If a shopper selects a custom country, LTI reverts product prices to the default country and currency values, and you must update the prices, currency, and calculations for that country.
* If at least one fixed pricing country is configured, LTI never reverts prices automatically. When a shopper selects a fixed pricing country, you should override product prices, discounts, subtotals, and totals for that country.
* When at least one fixed pricing country exists, you can trigger a page reload to fetch the correct price books from the backend.
* In that same setup, when the shopper selects a dynamic pricing country, LTI overrides prices, discounts, subtotals, and totals using the base price for the selected shipping country and currency combination.
{% endhint %}
---
# 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/light-touch-integration/features/fixed-pricing.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.