Store Views
Navigate to yStore → Store → Store Views.
Store views let you run multiple storefronts from a single yStore installation. Each view can have its own language, currency, checkout flow, product rules, customer settings, and order behaviour. A typical use case is a regional store: one view for Slovakia (SK, EUR), one for Hungary (HU, HUF), sharing the same product catalog but with locale-specific prices, taxes, and emails.
How store views work
Each store view shares:
- The same product catalog
- The same order management system
- The same admin CP
Each store view can have its own:
- Currency and locale
- Tax rules
- Checkout configuration
- Shipping methods
- Customer group defaults
- Email templates and branding
Store view fields
| Field | Description |
|---|---|
| Name | Display name shown in the CP store selector |
| Code | URL-safe identifier used in API calls and multi-store routing (e.g. sk, hu, b2b) |
| Enabled | Toggle — disabled views are inaccessible from the storefront |
| Currency | Default currency for this view |
| Locale | Language and regional formatting (date, number formats) |
| Timezone | Store-local timezone for order timestamps and scheduled rules |
Per-view configuration tabs
Each store view has five configuration tabs. Navigate to yStore → Store → Store Views → [View name].
- Customer
- Product
- Checkout
- Order
- Cart
Controls how customer accounts behave for this store view:
| Setting | Description |
|---|---|
| Account approval required | New accounts need admin approval before they can purchase |
| Allow guest checkout | Whether visitors can purchase without registering |
| Default customer group | Group assigned on registration |
| Wishlist enabled | Show wishlist functionality in this view |
| Max wishlist items | Per-wishlist item limit |
Controls product display and pricing rules:
| Setting | Description |
|---|---|
| Show prices including tax | Whether catalog prices display with tax included |
| Price rounding | Rounding precision for calculated prices |
| Allow backorders | Whether out-of-stock products can still be purchased |
| Stock threshold for low-stock alerts | Quantity below which a product triggers an inventory alert |
Controls checkout flow and payment behaviour:
| Setting | Description |
|---|---|
| Require shipping address | Whether a shipping address is mandatory (disable for digital-only stores) |
| Checkout terms page | Entry to link as the required terms & conditions |
| Allow order notes | Whether customers can add a note during checkout |
| Order note label | Custom label for the order note field |
| OTP verification | Whether phone OTP is required at checkout |
Controls post-checkout order behaviour:
| Setting | Description |
|---|---|
| Default order status | Status assigned to new orders |
| Auto-complete orders | Automatically move orders to Complete after N days |
| Invoice generation | Whether invoices are generated automatically |
| Invoice plugin | Which invoicing integration to use for this view |
| Order number prefix | Optional prefix for order increment IDs (e.g. SK-) |
Controls cart behaviour:
| Setting | Description |
|---|---|
| Cart lifetime (minutes) | How long an idle cart is retained before cleanup |
| Abandoned cart timeout | Minutes before a cart is flagged as abandoned |
| Merge guest cart on login | Whether guest cart items merge into the account cart on login |
| Cart sharing enabled | Whether customers can generate shareable cart links |
Creating a store view
- Go to
yStore → Store → Store Views. - Click New Store View.
- Enter a name and unique code.
- Select the currency and locale.
- Configure the five tabs: Customer, Product, Checkout, Order, Cart.
- Enable the view and save.
The store view code is used as a key throughout the system (API routes, settings keys, email overrides, flow conditions). Once set and used in production, changing it requires updating all references. Choose a stable, short, lowercase code from the start.
Routing store views
Store views are resolved from the request URL or a query parameter. The typical setup maps a Craft site to a store view:
| Craft site | URL | Store view code |
|---|---|---|
| Slovak storefront | sk.yourbrand.com | sk |
| Hungarian storefront | hu.yourbrand.com | hu |
| B2B portal | b2b.yourbrand.com | b2b |
The store view code is passed via the storeCode parameter in API requests from the frontend. See the Frontend documentation for how to configure your Twig templates and API calls per store view.
Multi-site vs. multi-store-view
| Craft Multi-site | yStore Store Views | |
|---|---|---|
| Controls | Content, URLs, translations | Currency, checkout, taxes, customer rules |
| Scope | Craft entries and assets | yStore orders, products, and settings |
| Typical mapping | 1 Craft site per language | 1 store view per market or segment |
In most setups, one Craft site maps to one store view. You can also have multiple store views on a single Craft site (e.g. a B2B toggle within the same site).