@spree/docs 0.1.106 → 0.1.108

package/dist/developer/core-concepts/architecture.md

@@ -1,6 +1,6 @@
 ---
 title: Architecture
-description: How Spree's core models, APIs, and packages work together
+description: Explore how Spree's core models, APIs, and gems fit together — catalog, shopping, checkout, fulfillment, and pricing — for headless or embedded commerce.
 ---
 
 ## Overview
@@ -119,7 +119,7 @@ Events from both APIs can trigger [Webhooks](webhooks.md) to notify external sys
 
 ## Multi-Store Architecture
 
-Spree supports [multiple stores](../multi-store/quickstart.md) from a single installation. Each Store can have:
+Spree supports running [multiple storefronts](../multi-tenant/quickstart.md) from a single installation. Each Store can have:
 
 - Its own domain and branding
 - Different currencies and locales

package/dist/developer/core-concepts/markets.md

@@ -290,7 +290,6 @@ spree api delete /markets/market_xxx
 ## Related Documentation
 
 - [Markets (Store SDK)](../sdk/store/markets.md) — Listing, resolving, and reading markets from the Store SDK
-- [Stores](stores.md) — Multi-store setup and configuration
 - [Pricing](pricing.md) — Price Lists, Price Rules, and the Pricing Context
 - [Addresses](addresses.md) — Countries, States, and Zones
 - [Localization](../../api-reference/store-api/localization.md) — Locale, currency, and country headers in API requests

package/dist/developer/core-concepts/staff-roles.md

@@ -1,6 +1,6 @@
 ---
 title: Staff & Roles
-description: Admin users, roles, invitations, and permissions
+description: Manage Spree admin users, roles, invitations, and permissions — create admins via the CLI, scope access per store, and customize role-based permissions.
 ---
 
 ## Overview
@@ -168,6 +168,5 @@ See the [Customize Permissions guide](../customization/permissions.md) for detai
 - [Custom API Authentication](../how-to/custom-api-authentication.md) — implement a custom identity-provider strategy (the full guide)
 - [Admin API Authentication](../../api-reference/admin-api/authentication.md) — keys, JWTs, scopes, and the refresh-cookie flow
 - [Customers](customers.md) — Customer accounts and authentication
-- [Stores](stores.md) — Multi-store setup
 - [Permissions](../customization/permissions.md) — Roles and authorization
 - [Events](events.md) — Subscribe to invitation events

package/dist/developer/core-concepts/stores.md

@@ -1,6 +1,6 @@
 ---
 title: Stores
-description: The Store is Spree's top-level multi-tenant boundary — learn how products, orders, channels, and markets are scoped to a store.
+description: Understand Spree Stores — the top-level tenant boundary that scopes products, orders, channels, markets, and branding, with the Admin API for store config.
 ---
 
 ## Overview
@@ -73,12 +73,10 @@ Each store owns its own resources. Products, orders, channels, markets, and taxo
 
 ## Running Multiple Storefronts
 
-If you need one Spree backend to serve **multiple distinct merchant brands** — different domains, different catalogs, different admin teams — there are two patterns:
+If you need one Spree backend to serve **multiple distinct merchant brands** — different domains, different catalogs — there are two patterns:
 
 - **Multiple channels under one store** (recommended for most cases) — model each storefront as a Sales Channel. Products are scoped per-channel via publications, orders carry the channel that originated them, and routing/pricing can differ per channel. This is the supported pattern in core Spree 5.5+.
-- **Multiple stores in one app** — the legacy multi-store pattern, where each store is fully independent (catalog, admin, branding). In Spree 5.5+ this requires the [spree_multi_store](../multi-store/quickstart.md) extension. Core Spree treats each product as belonging to a single store.
-
-For most multi-brand operations, the channel pattern is simpler and more flexible. Reach for [spree_multi_store](../multi-store/quickstart.md) only when stores need genuinely independent catalogs, branding, and admin teams.
+- **Multiple isolated stores (tenants) in one app** — full data isolation, only recommended if you're building a SaaS platform or a multi-tenant application. Each store can have different staff members, payment methods, shipping methods, and branding. This is supported by the [Spree Multi Tenant](../multi-tenant/quickstart.md) extension, which is a separate gem from core Spree.
 
 ## Related Documentation
 

package/dist/developer/core-concepts/translations.md

@@ -131,5 +131,4 @@ Once installed, all translation files are available automatically — no need to
 - [Markets](markets.md) — Locale and currency configuration per geographic region
 - [Localization](../../api-reference/store-api/localization.md) — Locale, currency, and country headers in API requests
 - [Slugs](slugs.md) — Localized slugs and URL identifiers
-- [Stores](stores.md) — Multi-store setup
 - [Products](products.md) — Product translations

package/dist/developer/multi-tenant/core-concepts.md

@@ -32,7 +32,7 @@ bin/rails g model Spree::NewModel tenant:references name:string --parent SpreeMu
 
 ## Tenant selector
 
-By default the current tenant is selected based on the subdomain or `Spree::CustomDomain`. The selector works in tandem with the default [Spree::Stores::FindCurrent](https://github.com/spree/spree/blob/main/core/app/finders/spree/stores/find_current.rb) finder.
+By default the current tenant is selected based on the subdomain or `Spree::CustomDomain`.
 
 First it finds the current store, and later sets the current tenant based on the store's `tenant_id`.
 

package/dist/developer/multi-tenant/quickstart.md

@@ -1,20 +1,118 @@
 ---
-title: Building a Multi-Tenant Spree Application
-sidebarTitle: Quickstart
+title: Spree Multi Tenant Installation
+sidebarTitle: Installation
+description: Install and configure Spree Multi-Tenant to run a SaaS ecommerce platform, including prerequisites, gem setup, license keys, and tenant provisioning.
 ---
 
-Spree out of the box is a single-tenant application. You can have multiple stores on the same instance of Spree, but they share the same products, admin user accounts and other resources.
-Multi-Store Spree setup is recommended for running multiple brands or multiple language versions of the same brand on the same instance.
+> **WARNING:** This installation instructions assume you have a clean Spree Starter installation and you've purchased the [Spree Enterprise Edition license](https://spreecommerce.org/pricing).
+>   
+>   For migrating existing application from single-tenant to multi-tenant, please contact us at [support@spreecommerce.org](mailto:support@spreecommerce.org).
 
-If you want to have a true multi-tenant application, you will need to purchase [Enterprise Edition license](https://spreecommerce.org/pricing) which includes `spree_multi_tenant` gem providing full multi-tenant support.
+## Prerequisites
 
-## Multi-Store vs Multi-Tenant
+* You need to be on Spree 5.1+, we recommend using [spree_starter](https://github.com/spree/spree_starter) as a base for your application
+* You need to have 2 environment variables set:
+  * `KEYGEN_ACCOUNT_ID`
+  * `KEYGEN_LICENSE_KEY`
+* We support both PostgreSQL and MySQL databases
 
-To sum it up:
+> **INFO:** Environment variables will be provided to you after purchasing the [Spree Enterprise Edition license](https://spreecommerce.org/pricing).
 
-* Multi-Store setup is recommended for running multiple brands or multiple language versions of the same store
-* Multi-Tenant allows you to create a SaaS application with multiple tenants, each of them with their own Spree instance
+> **WARNING:** You will need to add these environment variables to your CI/CD pipeline and production environments.
 
-## Setup SaaS application
+## Customer User Class
 
-[Follow the installation instructions](installation.md) to set up a multi-tenant Spree application.
+Please follow [Authentication](../customization/authentication.md) documentation to create a new user class.
+
+Now we will need to make slight adjustments to the generated user class so it can work in a multi-tenant environment.
+
+If you're using Devise, you will need to remove `:validatable` module. This module is responsible for validating the user's email uniqueness. We need to change it to validate it in the scope of the tenant.
+
+Spree Multi-Tenant gem injects `SpreeMultiTenant::CustomerUserConcern` that handles that instead.
+
+## Admin User Class
+
+For our multi-tenant setup we will need a separate Admin user class. Our standard User class will be only used for customer accounts which will be isolated by tenant. 
+Admin user classes will be shared across tenants allowing them to manage multiple tenants from a single admin panel.
+
+Let's create a new model with Devise (unless you already have one):
+
+
+```bash Spree CLI (Docker)
+spree rails g devise Spree::AdminUser
+```
+
+```bash Without Spree CLI
+bin/rails g devise Spree::AdminUser
+```
+
+
+Replace the generated Devise code with the following:
+
+```ruby
+class Spree::AdminUser < Spree::Base
+  # Include default devise modules. Others available are:
+  # :confirmable, :lockable, :timeoutable, :trackable and :omniauthable
+  devise :database_authenticatable, :registerable,
+        :recoverable, :rememberable, :validatable
+
+  # Spree modules
+  include Spree::UserMethods
+end
+```
+
+If you already have a custom Admin user class, you can add the following code to it:
+
+```ruby
+  # Spree modules
+  include Spree::UserMethods
+```
+
+This will make sure that the Admin user class works well with Spree ecosystem.
+
+Register new model in `config/initializers/spree.rb`:
+
+```ruby
+Spree.admin_user_class = "Spree::AdminUser"
+```
+
+## Installing gems
+
+1. Add the following code to your `Gemfile`:
+
+    ```ruby
+    source "https://license:#{ENV['KEYGEN_LICENSE_KEY']}@rubygems.pkg.keygen.sh/#{ENV['KEYGEN_ACCOUNT_ID']}" do
+      gem 'spree_enterprise'
+      gem 'spree_multi_tenant'
+    end
+    ```
+
+2. Install gems:
+
+    
+
+    ```bash Spree CLI (Docker)
+    spree bundle install
+    ```
+
+    ```bash Without Spree CLI
+    bundle install
+    ```
+
+    
+
+3. Run generators:
+
+    
+
+    ```bash Spree CLI (Docker)
+    spree generate spree_enterprise:install && spree generate spree_multi_tenant:install
+    ```
+
+    ```bash Without Spree CLI
+    bin/rails g spree_enterprise:install && bin/rails g spree_multi_tenant:install
+    ```
+
+    
+
+    > **INFO:** This will copy and run migrations for `spree_enterprise` and `spree_multi_tenant` gems.

package/dist/developer/upgrades/4.2-to-4.3.md

@@ -1,9 +1,9 @@
 ---
-title: 4.2 to 4.3
+title: Upgrading to Spree 4.3
 section: upgrades
 order: 0
 hidden: true
-description: This guide covers upgrading a 4.2 Spree application to Spree 4.3.
+description: Upgrade a Spree 4.2 application to Spree 4.3 — split out spree_emails, spree_backend, and spree_frontend gems, remove merged extensions, and run migrations.
 ---
 
 > **NOTE:** If you're on an older version than 4.1 please follow previous upgrade guides and perform those upgrades incrementally, eg.
@@ -28,7 +28,7 @@ These gems were merged into Spree Core in version 4.3. All of their functionalit
 
 ### Optional Remove SpreeMultiDomain
 
-If you used that gem in the past you need to remove it. Multi-Store is now incorporated into Spree core and you cannot use that gem anymore.
+If you used that gem in the past you need to remove it.
 
 1. Remove `spree_multi_domain` from your `Gemfile`
 

package/dist/developer/upgrades/5.3-to-5.4.md

@@ -1,6 +1,6 @@
 ---
 title: Upgrading to Spree 5.4
-description: This guide covers upgrading a Spree 5.3 application to Spree 5.4.
+description: Upgrade a Spree 5.3 application to Spree 5.4 — remove spree_sample, update gems, run migrations, switch to AdminUserMethods, and backfill image thumbnail IDs.
 ---
 
 > **INFO:** Before proceeding to upgrade, please ensure you're at [Spree 5.3](5.2-to-5.3.md)
@@ -252,20 +252,6 @@ Also, add `jsonapi-rspec` gem to your `Gemfile`:
   
 And run `bundle install`
 
-### (Optional) Install Spree Multi Store
-
-[Multi-store](../multi-store/quickstart.md) features like multiple store management & custom domains were moved to a separate gem [spree_multi_store](../multi-store/quickstart.md).
-
-If you rely on these features please run:
-
-  ```bash
-  bundle add spree_multi_store
-  ```
-  
-> **INFO:** Spree Multi-Store is licensed under the [AGPL v3 License](https://opensource.org/licenses/AGPL-3.0). 
-> 
-> If you would like to use it in a commercial application, please [contact us](https://spreecommerce.org/get-started/) to obtain a commercial license.
-
 ### (Optional) Install Legacy Product Properties extension
 
 Product Properties have been extracted from Spree core to a separate gem `spree_legacy_product_properties`. Product Properties were already deprecated in favor of [Metafields](../core-concepts/metafields.md) and disabled by default since Spree 5.1.

package/dist/developer/upgrades/5.4-to-5.5.md

@@ -122,7 +122,7 @@ This is a no-op on the default Database provider (there is no external index to
 
 #### Multi-store catalogs
 
-If you have products attached to multiple stores via the legacy `spree_products_stores` join, the `populate_publications` task picks **one** "home" store per product and creates publications on every store's default channel. The `spree_products_stores` table is **kept** as legacy compat surface — the upcoming [spree_multi_store](../multi-store/quickstart.md) extension restores the full `Product has_many :stores` association on top of it.
+If you have products attached to multiple stores via the legacy `spree_products_stores` join, the `populate_publications` task picks **one** "home" store per product and creates publications on every store's default channel. The `spree_products_stores` table is **kept** as legacy compat surface.
 
 For single-store deployments this is invisible; you can move on without touching `spree_products_stores` again.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@spree/docs",
-  "version": "0.1.106",
+  "version": "0.1.108",
   "description": "Spree Commerce developer documentation for AI agents and local reference",
   "type": "module",
   "license": "CC-BY-4.0",

package/dist/developer/multi-store/quickstart.md

@@ -1,78 +0,0 @@
----
-title: Multi-Store Spree Commerce Quickstart
-sidebarTitle: Quickstart
-description: Enable multiple storefronts on a single Spree app with the spree_multi_store gem, including per-store products, payment methods, taxonomies, and promotions.
----
-
-To enable multiple stores, you will need to add the [spree_multi_store](quickstart.md) gem to your project via:
-
-
-```bash Spree CLI (Docker)
-spree bundle add spree_multi_store
-```
-
-```bash Without Spree CLI
-bundle add spree_multi_store
-```
-
-
-> **INFO:** Spree Multi-Store is licensed under the [AGPL v3 License](https://opensource.org/licenses/AGPL-3.0). 
-> 
-> If you would like to use it in a commercial application, please [contact us](https://spreecommerce.org/get-started/) to obtain a commercial license.
-
-![](/images/mulit_store_978x2.png)
-
-## Store resources
-
-Each Store can have its own resources. For example, a Store can have its own Products, Taxonomies, Promotions, etc.
-
-| Resource                                          | Relationship                                                                                                                               |
-| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
-| [**Order**](/core-concepts/orders)                            | One Order belongs to one Store                                                                                                             |
-| [**Product**](/core-concepts/products)                        | One Product can be associated with many Store(s), you can pick and choose in which Store(s) each Product will be available                 |
-| [**Payment Method**](/core-concepts/payments)                 | One Payment Method can be associated with many Store(s), you can select in which Stores given Payment Method will be available on Checkout |
-| [**Taxonomy**](/core-concepts/products#taxons-and-taxonomies) | One Taxonomy belongs to one Store                                                                                                          |
-| [**Promotion**](/core-concepts/promotions)                    | One Promotion can be associated with multiple Stores                                                                                       |
-| **Store Credit**                                  | One Store Credit belongs to and can be used in one Store
-
-## Current Store
-
-Spree will try to determine the current store based on the current URL. If the URL does not match any of the stores in the database, Spree will fall back to the default store.
-
-All Spree controllers or any other controllers that include [Spree::Core::ControllerHelpers::Store](https://github.com/spree/spree/blob/main/core/lib/spree/core/controller_helpers/store.rb) have access to the `current_store` method which returns the `Store` matching the current URL.
-
-All parts of Spree (API, Admin Panel) have this implemented.
-
-> **INFO:** Under the hood `current_store` calls [Spree::Stores::FindCurrent.new(url: url).execute](https://github.com/spree/spree/blob/main/core/app/finders/spree/stores/find_current.rb).
-> 
-> This logic can be easily overwritten by setting 
-> 
-> ```ruby
-Spree::Dependencies.current_store_finder = 'MyStoreFinderClass'
-```
-> 
-> in `config/initializers/spree.rb` file
-
-## Default Store
-
-If the system cannot find any Store that matches the current URL it will fall back to the Default Store.
-
-You can set the default Store via Rails console:
-
-```ruby
-Spree::Store.find(2).update(default: true)
-```
-
-To get the default store in your code or rails console type:
-
-```ruby
-Spree::Store.default
-```
-
-## Custom Domains
-
-Spree supports managing custom domains for Stores. In the Admin Panel, you can manage custom domains for each Store in the **Settings -> Domains** page.
-
-## Setup multi-store application
-
-[Follow the setup guide](setup.md) to get started.

package/dist/developer/multi-store/setup.md

@@ -1,38 +0,0 @@
----
-title: Multi-Store Setup
-sidebarTitle: Setup
----
-
-## Root domain
-
-You need to set a wildcard `root_domain` on the store to enable multi-store setup
-
-```ruby
-Spree.root_domain = ENV.fetch('SPREE_ROOT_DOMAIN', 'lvh.me')
-```
-
-This will be used to generate the store URLs, eg. `store1.lvh.me`, `store2.lvh.me`, etc.
-
-`store1` part is the unique store `code` identifier, which is auto-generated based on the store name. You can change it in the admin panel in **Settings -> Domains**.
-
-> **INFO:** If you later change the `root_domain`, you will need to run:
-> 
->   ```ruby
-  Spree::Store.all.each(&:save)
-  ```
->   
->   to update the store URLs.
-
-## Creating new stores
-
-After you restart your application, you will see a new option in the admin panel, under new item menu:
-
-![](/images/new_store_dropdown.png)
-
-You can also create a new store from the rails console:
-
-```ruby
-Spree::Store.create!(name: 'New Store')
-```
-
-This will create a new store with the given name, code and URL.

package/dist/developer/multi-tenant/installation.md

@@ -1,118 +0,0 @@
----
-title: Spree Multi Tenant Installation
-sidebarTitle: Installation
-description: Install and configure Spree Multi-Tenant to run a SaaS ecommerce platform, including prerequisites, gem setup, license keys, and tenant provisioning.
----
-
-> **WARNING:** This installation instructions assume you have a clean Spree Starter installation and you've purchased the [Spree Enterprise Edition license](https://spreecommerce.org/pricing).
->   
->   For migrating existing application from single-tenant to multi-tenant, please contact us at [support@spreecommerce.org](mailto:support@spreecommerce.org).
-
-## Prerequisites
-
-* You need to be on Spree 5.1+, we recommend using [spree_starter](https://github.com/spree/spree_starter) as a base for your application
-* You need to have 2 environment variables set:
-  * `KEYGEN_ACCOUNT_ID`
-  * `KEYGEN_LICENSE_KEY`
-* We support both PostgreSQL and MySQL databases
-
-> **INFO:** Environment variables will be provided to you after purchasing the [Spree Enterprise Edition license](https://spreecommerce.org/pricing).
-
-> **WARNING:** You will need to add these environment variables to your CI/CD pipeline and production environments.
-
-## Customer User Class
-
-Please follow [Authentication](/docs/developer/customization/authentication) documentation to create a new user class.
-
-Now we will need to make slight adjustments to the generated user class so it can work in a multi-tenant environment.
-
-If you're using Devise, you will need to remove `:validatable` module. This module is responsible for validating the user's email uniqueness. We need to change it to validate it in the scope of the tenant.
-
-Spree Multi-Tenant gem injects `SpreeMultiTenant::CustomerUserConcern` that handles that instead.
-
-## Admin User Class
-
-For our multi-tenant setup we will need a separate Admin user class. Our standard User class will be only used for customer accounts which will be isolated by tenant. 
-Admin user classes will be shared across tenants allowing them to manage multiple tenants from a single admin panel.
-
-Let's create a new model with Devise (unless you already have one):
-
-
-```bash Spree CLI (Docker)
-spree rails g devise Spree::AdminUser
-```
-
-```bash Without Spree CLI
-bin/rails g devise Spree::AdminUser
-```
-
-
-Replace the generated Devise code with the following:
-
-```ruby
-class Spree::AdminUser < Spree::Base
-  # Include default devise modules. Others available are:
-  # :confirmable, :lockable, :timeoutable, :trackable and :omniauthable
-  devise :database_authenticatable, :registerable,
-        :recoverable, :rememberable, :validatable
-
-  # Spree modules
-  include Spree::UserMethods
-end
-```
-
-If you already have a custom Admin user class, you can add the following code to it:
-
-```ruby
-  # Spree modules
-  include Spree::UserMethods
-```
-
-This will make sure that the Admin user class works well with Spree ecosystem.
-
-Register new model in `config/initializers/spree.rb`:
-
-```ruby
-Spree.admin_user_class = "Spree::AdminUser"
-```
-
-## Installing gems
-
-1. Add the following code to your `Gemfile`:
-
-    ```ruby
-    source "https://license:#{ENV['KEYGEN_LICENSE_KEY']}@rubygems.pkg.keygen.sh/#{ENV['KEYGEN_ACCOUNT_ID']}" do
-      gem 'spree_enterprise'
-      gem 'spree_multi_tenant'
-    end
-    ```
-
-2. Install gems:
-
-    
-
-    ```bash Spree CLI (Docker)
-    spree bundle install
-    ```
-
-    ```bash Without Spree CLI
-    bundle install
-    ```
-
-    
-
-3. Run generators:
-
-    
-
-    ```bash Spree CLI (Docker)
-    spree generate spree_enterprise:install && spree generate spree_multi_tenant:install
-    ```
-
-    ```bash Without Spree CLI
-    bin/rails g spree_enterprise:install && bin/rails g spree_multi_tenant:install
-    ```
-
-    
-
-    > **INFO:** This will copy and run migrations for `spree_enterprise` and `spree_multi_tenant` gems.