Switching from Algolia to Layers: A Shopify Plus Migration Guide

If you run a Shopify Plus store on Algolia and you are weighing a move to Layers, start with the honest part. Algolia is a genuinely good search engine, with one of the best developer APIs in the category.

This guide is not about a broken product. It is about fit, cost, and what you would rebuild, for a brand that sells only on Shopify Plus.

Why are Algolia customers looking right now?

Not because of a merger or a sunset. For a brand that lives entirely on Shopify Plus, the question is narrower: is a general-purpose search engine the right shape when you sell in exactly one place?

Give Algolia real credit first. In March 2026 it shipped Commerce Pipeline, "a next-generation indexing architecture," and closed most of the old catalog gap.

That release added native indexing of Shopify's Standard Product Taxonomy, started indexing Metaobjects, removed the previous 10-market limit, and cut update latency to "an average of two minutes."

So catalog sync is no longer the reason to look. What Commerce Pipeline did not change is the shape of the tool.

You still assemble your own search frontend, stand up a separate index for every market, and pay on records and requests as traffic grows.

For a multi-platform business, that is a fair trade. For a Shopify Plus brand, it is overhead you can put down.

Should you switch from Algolia to Layers?

Switch if you sell only on Shopify Plus, you want merchandising your own team can run, and you would rather not meter search by the record and the request.

Stay on Algolia if you sell across several platforms, run search on web, app, and internal docs, or you want a general-purpose engine your developers fully control.

The teams that switch and are glad they did tend to share a profile:

• One Shopify Plus store, or a Markets setup, not a multi-platform or headless estate.
• A team tired of watching the bill move with record counts and search-request volume.
• A merchandiser who wants drag-and-drop ranking without a developer ticket or an Elevate upgrade.
• A team fine owning storefront markup, but done maintaining an index pipeline and widget config by hand.

What are you actually running on Algolia?

More than a search box. A live Algolia install is a record index, a developer-built frontend, a separate index per market, metering on records and requests, and tuning that lives in Rules. Five things make up the surface.

1. A record index, not your catalog. Algolia searches records, "an item or object that contains data that someone would search (or get recommendations) for." Your products, variants, collections, pages, and articles are flattened into four indexed data types.
2. A frontend your developers built. The storefront UI is InstantSearch, an open-source "UI library... to build a search interface in your frontend app," wired up as autocomplete and instantsearch widgets through App Embed and App Blocks.
3. An index per market. On Shopify Markets, the app creates a separate index for each market and language, so every locale you add is another index to run and tune.
4. Two meters, records and requests. Algolia bills on both: 100K records then $0.40 per additional 1K, and 10K search requests then $0.50 per 1K on Grow, $1.75 on Grow Plus. The bill moves with your catalog and your traffic.
5. AI gated to the top tier. NeuralSearch semantic search is Elevate-only, Dynamic Re-Ranking sits on Grow Plus, and relevance leans on Rules and synonyms your team maintains per index.

What changes when you move to Layers?

Three things change. The record pipeline goes away, the sync moves to near real-time, and your catalog stops being a flattened index; we read it straight from Shopify instead.

What ports over, and what you retire?

Two things port, and the rest retires by design. The synonyms and Rules you actually rely on can come across. The record pipeline and the per-index synonym upkeep stay behind, because we read your catalog natively and expand queries for you.

Your synonyms and Rules live in Algolia's dashboard and API, per index. You can pull them out through the API.

But copying them across indices is a per-rule toggle, so a market-by-market setup rarely lifts cleanly without scripting the API.

On Layers, the ongoing tuning shrinks. Our query understanding expands queries automatically, so the hand-maintained synonym lists mostly go away.

You can still add an explicit synonym when a brand term needs it, but you are not keeping equivalence lists per index by hand.

That flattened-index pipeline does not port either, and it does not need to. We read your Shopify catalog natively, so there is nothing to rebuild.

We re-author the handful of Rules that encode a real merchandising call, and our engine starts learning from your shoppers at cutover.

How does the migration actually work?

A staged switch, not a big-bang cutover. You build and prove it on a draft theme before a single shopper sees it, then publish and move template by template, with your old theme one revert away.

1. Map your URLs and config first. Export your Algolia synonyms and Rules through the API, and scope which search and collection URLs stay put. Those URLs live in your Shopify theme routes, so they hold through the switch and you rarely need SEO 301s.
2. Install Layers and sync the catalog. Installing the app syncs your catalog through real-time webhooks at the store level. Nothing shopper-facing changes yet.
3. Rebuild the storefront UI on a draft theme. This is the real work, and it is a lateral move. Algolia already rendered through your InstantSearch build, so you rebuild that UI on the Layers SDK, and our team does that build.
4. Validate before you publish. Preview merchandising on your live storefront with live preview, and validate search on the draft theme, confirming collection pages stay server-rendered with crawlable product links. Algolia keeps serving production.
5. Bring over the little that ports, retire the rest. Import the synonyms and redirects you still want, re-author the few Rules that reflect a real decision, and drop the per-index pipeline for good.
6. Publish, and cut over template by template. Both systems can coexist behind template gates during the transition. We scope tracking per template so events are not double-counted, and revenue reads from your native Shopify order data, one source of truth.
7. Prove each surface, with rollback ready. Validate ranking changes with Layers' sort-order A/B experiments (in beta, one Layers sort order against another) or a matched pre and post read against Algolia. Your previous theme is one revert away.
8. Retire Algolia last. Only after cutover, remove the Algolia app embeds and blocks, delete the injected widgets, and cancel the Algolia plan.

How do we de-risk the switch?

Yes, this is an engineering project, and the frontend rebuild is the bulk of it. We run it end to end, from the theme build to the cutover, so it does not land on your team.

Onboarding, catalog sync, theme implementation, and strategy are fully managed, at a fraction of the cost of a re-platforming.

You prove each surface on a draft theme before it goes live, then check it against a sort-order experiment or a matched pre and post read.

Your previous theme is one revert away, so if a change hurts conversion, you put the old one back in a click.

We have a real switcher on record. Rainbow Shops, an apparel chain with roughly 1,000 stores, moved off Salesforce Commerce Cloud onto Shopify, tried Algolia there, and replaced it with Layers.

Algolia was expensive, had data sync issues, and overrode their sort order when the team tried to merchandise collections by hand.

In the words of their VP of eCommerce and Digital, David Cost, on getting that merchandising control back:

"Layers was the first time we were able to create some customization and essentially create the same kind of sort orders that we were used to having in Salesforce. And we could see a pretty immediate impact on the conversion rate."

After the move, Rainbow Shops reported a 30% increase in conversion rate and now re-orders every collection page daily based on the last seven days of demand.

On the frontend rebuild, Jason Hassold, Founder and Lead Developer at Negative Space, put it this way:

"the SDK is easy to use and gives us the flexibility to build any search experience a merchant can imagine. The team's Shopify dev agency roots mean they actually get what dev partners need."

📌 CUSTOMER PROOF PLACEHOLDER

Add a second named Algolia-to-Layers switch quote here as more come on record. Rainbow Shops above is a real Algolia migration; this slot is for a second reference that widens the proof.

What Algolia does that we don't, and the reverse

Credit where it is due. Algolia runs one of the best developer APIs in the category, its documentation is excellent, and the March 2026 Commerce Pipeline made its Shopify catalog sync genuinely good.

If you want a general-purpose engine for web, app, and internal docs, or you are not on Shopify at all, Algolia is the better tool, and we will say so.

What we do that Algolia does not: we assume Shopify Plus from the ground up, in one bundle.

• Native catalog reading instead of a record pipeline.
• One setup across every Market, not an index per locale.
• Merchandising a non-engineer can run, with no Elevate upgrade.
• Semantic search in the base, not the top tier.

The trade-offs are real. We only serve Shopify Plus, our review volume is younger than Algolia's, we are not a search API for every platform, and you build your storefront markup on our SDK.

The difference from Algolia is that you were already building that frontend yourself. Moving to us swaps one developer-owned build for another; it does not hand you a turnkey template.

If a general-purpose API or a non-Shopify stack is what you need, Algolia is the better fit, and that is fine.

What does this cost?

We charge one usage-based price for all four products, metered on your collection page views and total search requests. There is no per-record fee and no separate charge for the AI.

Algolia instead bills on two axes, records and search requests, so the number moves with both your catalog size and your traffic.

On Grow that is 100K records then $0.40 per additional 1K, plus 10K search requests then $0.50 per 1K, and the semantic search you likely want sits on the Elevate tier.

Our pricing runs below the legacy platforms, with no six-figure floor.

All four products are bundled with no feature gating. You can see AI Search, Merchandising, and Visual Discovery working on your own catalog before you commit.

FAQs

Can I export my configuration from Algolia? Partly. Synonyms and Rules live in Algolia's dashboard and API per index, so you can pull them through the API.

But copying Rules across indices is a per-rule action, so a multi-market setup usually needs the API to move in bulk.

On Layers most of that tuning goes away, because our query understanding expands queries automatically and we read your catalog natively.

Didn't Algolia fix its Shopify sync in 2026? Yes, and we will not pretend otherwise. Commerce Pipeline added native taxonomy and Metaobject indexing and cut Markets latency to about two minutes.

The remaining question is fit and cost, not sync speed: an assembled frontend, an index per market, and usage-based billing, for a brand that sells only on Shopify Plus.

Will I lose my search rankings when I switch? Not if you plan for it. Your search and collection URLs live in your Shopify theme routes, so they stay put, and we keep collection pages server-rendered with crawlable product links.

Map your redirects up front and confirm your sitemap, robots, and canonical tags are unchanged through the cutover.

Do I have to rebuild my search UI? Yes, but you were already building it. Algolia renders your storefront through InstantSearch widgets your team wired up, so moving to Layers swaps that for a build on our SDK.

Our team does that build, and the app embed handles auth, tracking, and redirects with no theme code.

How long does it take, and do I need engineers? Not on your side. Theme implementation, SDK wiring, and cutover are handled by our team.

A standard theme often goes live in around a week, and a heavily customized storefront takes longer, because the frontend rebuild is the gate. We scope the timeline against your actual theme before you commit.

Does Layers support Shopify Markets and B2B? Yes, from a native setup. Markets configuration, per-country pricing, and B2B catalogs are read natively, so adding a market is a setting, not a new index to stand up.

Ready to see it on your catalog?

We will sync your store to a draft theme, show you Layers running on your real products next to what Algolia does today, and give you the staged migration plan before you decide anything.

Book a managed migration and we will do the heavy lifting.