Payments & Global
Run distinct store experiences with their own market settings, language choices, currency presentation, payments, and delivery methods. Keep the operational work in a shared backend while tailoring what customers see.
Multi-Store per market · 3min read
The big picture
Selling in several markets does not mean every customer should receive the same store configuration. HEYA exposes a current-store context throughout its settings, letting teams work on a specific store’s identity, coverage, payment methods, and shipping arrangements. Store prefixes also provide a structured way to identify a market in the storefront URL. This gives the business a common operating environment while preserving decisions that belong to each market.
A closer look
Basic settings include the store name, group or region, prefix, time zone, and unit preferences. The documented storefront URL structure combines a store prefix with a language, such as a US store viewed in English. Establish those conventions early so both your team and your customers can understand which market and language experience they are using.
Country coverage, default and available currencies, payment methods, and shipping methods are managed in the store’s settings context. Review them as a connected configuration. A currency shown to customers should make sense alongside the payment choices offered, while a delivery promise should match the coverage and service arrangements for that store.
Market settings include a store-specific list of operation managers who should receive relevant operational emails, such as new orders, order edits, and low-stock alerts. This supports a practical distinction between centralized oversight and market-level responsibility. Make the current store an explicit part of your team’s review process before changing settings or investigating an order.
In practice · illustrative scenario
A brand can operate a USA storefront and a UK storefront with distinct currency presentation and delivery methods. The team works within a shared backend, while each store communicates the market-specific choices that matter to its customers. English-language shopping can remain familiar in both without requiring identical commercial settings.
Good to know
Yes. Store context and language context are separate parts of the settings experience. Configure the languages available in each store and select the appropriate default language.
No. The store-specific settings provide a place to configure those commercial choices. Review each market’s coverage, delivery promise, currency presentation, and available payment methods together.
Your next chapter
Explore the plans, connect your catalog, and build the commerce experience your customers need.
