Menu
Guides
Storefront Development

Storefront Development

Managing currency and product availability

Understand how bindings and Sales Channels control currency, assortment, prices, and product availability in a localized FastStore storefront.

2 min read
In a localized FastStore storefront, the Sales Channel associated with a binding defines the shopper's commercial context. It controls the currency and determines which catalog, prices, inventory, and trade policy conditions the storefront uses.
For the complete Localization model, see Understanding the Localization feature.

How bindings define the shopping experience

A binding connects:
  • A storefront domain
  • A locale, such as en-US or pt-BR
  • A Sales Channel, also called a trade policy
The locale selects language and regional content. The Sales Channel selects the commercial conditions. Keeping these responsibilities separate lets a store reuse one language across markets while offering different currencies or assortments.

What the Sales Channel controls

Storefront elementSource
CurrencySales Channel configuration
Product assortmentCatalog linked to the Sales Channel
Prices and promotionsTrade policy conditions
Inventory and fulfillment availabilityLogistics and inventory for the commercial context
Language and CMS contentLocale associated with the binding
Changing only the locale doesn't convert prices. To offer another currency, associate the binding with a Sales Channel configured for that currency and commercial context.

Example

An account can use the same FastStore project for two markets:
DomainLocaleSales ChannelShopper experience
www.example.com/en-usen-US1English content, USD prices, US assortment
www.example.com/pt-brpt-BR2Portuguese content, BRL prices, Brazil assortment
The two storefronts can share components and fallback content while displaying different products, prices, promotions, and inventory.

Configure the commercial context

  1. Define the Sales Channel and its trade policy conditions in the VTEX platform.
  2. Confirm that the intended catalog, prices, promotions, and logistics settings apply to the Sales Channel.
  3. Request the binding association by following Handling internationalization with the Localization feature.
  4. Configure a CMS locale whose ISO code matches the binding.
  5. Rebuild the FastStore project after the binding configuration changes.

Validate each market

Open every localized storefront and confirm:
  • Prices use the expected currency and formatting.
  • PLPs, search, and shelves contain only products available to the Sales Channel.
  • PDPs don't expose unavailable locale-specific URLs.
  • Promotions and price conditions match the intended trade policy.
  • Cart totals preserve the same currency and commercial context.
  • Switching locales leads to an equivalent available product or a safe fallback page.
Product translation and product availability are independent. A translated product is shown only when it also belongs to the Sales Channel's assortment and is available under its commercial conditions.
Localize product information
Translate product names, descriptions, and product-level SEO fields for each locale.
Configure locales
Create CMS locales and connect their ISO codes to the corresponding storefront bindings.