> ## Documentation Index
> Fetch the complete documentation index at: https://docs.uselayers.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrate from Boost Commerce

> Reference for teams moving from Boost Commerce Search & Discovery to Layers, including feature mapping for collections, search behavior, analytics, and API integration.

This page maps the features Boost Commerce stores depend on to their Layers equivalents, so you can plan a migration without losing functionality. It is organized around the questions teams ask most often when evaluating a switch.

## Collection management

Boost stores typically build collection pages from custom rules layered on top of Shopify collections. Layers preserves this model:

* Layers syncs your Shopify collections natively — you do not need to recreate them.
* **[Merchandising rules](/platform/merchandising)** provide three approaches that map to Boost workflows: manual pinning, automated expression-based rules driven by product attributes, and a hybrid of both.
* **[Sort orders](/platform/sorting)** let you compose multi-signal rankings (sales, recency, inventory, custom metrics) and apply them per collection.
* **[Soft boost](/platform/sorting/soft-boost)** gives you Boost-style nudges (e.g., "lift new arrivals into best sellers without overwhelming the page") without hard-clustering products.

You keep the Shopify collection as the source of truth and use Layers to control what shows, in what order, with which pins or boosts on top.

## Search behavior

| Boost feature                       | Layers equivalent                                                                                                                                   |
| ----------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| Synonyms and stop words             | Built-in [query expansion](/engine/user-intent-processing#how-query-expansion-works) and [query interpretation](/engine/query-interpretation)       |
| Typo tolerance                      | Automatic, context-aware [typo correction](/engine/typo-tolerance) — preserves brand names, SKUs, and stylized spellings                            |
| Conversational and question queries | [Query interpretation](/engine/query-interpretation) — detects intent, generates candidate phrases, and routes to results or redirects              |
| Redirects and landing pages         | [Semantic redirects](/platform/semantic-redirects), matched by AI embeddings plus query interpretation                                              |
| Boosting and pinning                | [Merchandising rules](/platform/merchandising) with pins, expressions, and [soft boost expressions](/platform/merchandising/soft-boost-expressions) |
| Filters and facets                  | [Attributes](/platform/attributes) — including AI-generated facet value ordering                                                                    |

Most of this works out of the box. Where Boost requires you to maintain a synonym list manually, Layers infers expansions from your catalog and from query interpretation.

## Analytics

Every new Layers store ships with an **Overview** dashboard pre-populated with search volume, revenue, orders, collection views, image search, similar products, and recommendation block performance. See [Default dashboard metrics](/platform/metrics#default-dashboard-metrics).

For deeper analysis, [LayersQL](/platform/layersql/overview) is a query language that runs against the raw behavioral datasets ([search-text](/platform/layersql/datasets/search-text), [products](/platform/layersql/datasets/products), [blocks](/platform/layersql/datasets/blocks), etc.). You can:

* Create custom metrics and pin them to dashboards.
* Segment by country, device, channel, sort order, or any context field.
* Reference metric results inside sort orders and merchandising rules.

See [Metric recipes](/platform/metrics/recipes) for ready-to-paste examples.

## API and theme integration

Boost stores integrating via API often hit gaps where a Boost feature is dashboard-only and never exposed to the storefront API. Layers is API-first — every platform feature (search tuning, merchandising, ranking, redirects, recommendations, personalization) is available through the [Storefront API](/api-reference/search) and the [`@commerce-blocks/sdk`](/sdk/api-reference).

If your team chose API over widget to customize the UI, you keep that flexibility:

* The [SDK](/sdk/framework-integration) ships reactive bindings for React, Vue, Svelte, Lit, and vanilla JS.
* Search, Browse, Blocks, Autocomplete, and Similar Products are all available as REST endpoints.
* For Shopify themes that prefer Liquid, the [Liquid + Fetch guides](/developers/rendering-blocks-in-liquid) and [Liquid + SDK guides](/developers/implementing-search-with-the-sdk) cover both patterns.

See [Headless integration](/engine/contextual-information#headless-integration) for the context, identity, and geo fields you need to pass on server-side calls.

## Mobile apps (Tapcart, Fuego, Canvas)

If you run a mobile app alongside your online store, Layers detects, syncs, and merchandises it natively. See [Mobile apps](/shopify-integration/mobile-apps).

## Price testing and A/B platforms

Layers returns pricing on every product in every Search, Browse, and Blocks response — so sort-by-price stays consistent as the shopper loads more results, and an A/B platform can re-sort or override prices on the page without a second round-trip. See [Price testing and A/B platforms](/developers/price-testing).

## Lean teams: reducing operational overhead

A few capabilities that shorten the time merchandisers and engineers spend in the platform day to day:

* **[MCP server](/developers/mcp-servers)** — exposes nearly every platform action (merchandising rules, ranking, sort orders, search tuning, redirects, metrics, dashboards) to AI assistants. Merchandisers can ask Claude or ChatGPT to make changes that execute against Layers directly.
* **[AI Explain](/help/evaluate/test-text-search#ai-explain)** — generates a grounded explanation of how the search pipeline processed any query and why specific products ranked where they did.
* **[Lab Search quality](/help/lab/search-quality)** — surfaces the optimizations Layers is testing for your store (synonyms, intent modifiers, attribute weights) with the source signal behind each one, so search improvements are observable, not guesswork.
* Sensible defaults out of the box, so most stores ship with tuned ranking, typo handling, and analytics without manual setup.

## Next steps

* [Dashboard home](/help/onboarding/dashboard-home)
* [Configure search behavior](/help/configuration/configure-search-behavior)
* [Exporting search data](/help/onboarding/exporting-search-data) — useful when bringing historical Boost search logs into LayersQL for benchmarking