StoreRouter vs. Shopify Catalog
Product discovery beyond a commerce platform.
Your agent's product selection shouldn't depend on which ecommerce platform a store uses—or whether its merchant has joined another catalog network. StoreRouter indexes covered storefronts across ecommerce platforms and adds a shared semantic layer so agents can search, filter, and compare products even when merchant labels are inconsistent.
- /v1/products/search
- /v1/products/parse
- JSON · Markdown
Evidence recorded October 9, 2026 · StoreRouter, formerly Octogen
| Capability | StoreRouter | Shopify Catalog |
|---|---|---|
| Catalog foundation | Independent index of covered storefronts | Products available through Shopify's catalog network |
| Merchant participation | Supported public storefronts; no merchant-submitted feed required | Native Shopify data, plus imports and ongoing sync for participating non-Shopify merchants |
| Product understanding | Shared taxonomy, normalized fields, and semantic enrichment on indexed products | Structured product data with normalized options and AI-inferred fields |
| Custom storefront content | Store-specific extraction can incorporate available storefront sources | Configurable field mappings for custom Shopify data |
| Developer workflow | Search covered catalogs; parse a product URL into a shared schema | Search and retrieve products through Shopify's catalog interfaces |
Fit
Which fits your agent?
Choose StoreRouter when
you need discovery across covered Shopify and non-Shopify storefronts, with a shared product schema and semantic enrichment that doesn't depend on merchants maintaining a Shopify integration.
Choose Shopify Catalog when
its participating catalog fits your needs and you want product discovery within its broader agentic commerce workflow, including cart and checkout integrations. Shopify's agent tools.
Product understanding
Understand the product beyond the merchant's labels
A shopper asks for a linen summer dress. The merchant may call it “The Sunday,” tag it “New Season,” and put its fabric composition in a separate details panel. Useful product search needs to connect those facts to what the shopper means.
StoreRouter's enrichment layer interprets product information into a shared taxonomy and attributes such as material, fit, style, pattern, and occasion. That gives agents a consistent vocabulary across stores, without requiring each merchant to label products the same way. It can also help recover useful meaning from incomplete or incorrect merchant categorization when the available product evidence supports it.
This is an illustrative example, not a measured Shopify search result. Derived attributes can be incomplete or wrong; enrichment is not a guarantee that every label is corrected.
The storefront can contain more than the core product record
A storefront can combine commerce data with a content management system (CMS), a product information management system (PIM), or a review service. Depending on the integration, those details may be synced into the commerce platform or appear only in the customer-facing experience.
StoreRouter's store-specific extraction can use available storefront sources to assemble the product record before normalization and enrichment. The aim is to capture the information needed to understand the product, including details outside the store's default product fields. Actual fields depend on the source and extractor.
Shopify supports custom mappings from product attributes, metafields, and metaobjects. It also documents inferred descriptions and attributes including material, style, and occasion. Both systems interpret product data; a claim that one captures more detail requires a comparison of actual product records. Catalog Mapping · Inferred fields.
Platform independence
Reach stores without requiring them to join Shopify
Platform independence matters when the stores your shoppers want use different commerce systems. StoreRouter's coverage is built by indexing storefronts. A supported store does not need to migrate to Shopify or maintain a Shopify catalog for StoreRouter to include its products. Developers query one schema across the catalogs we cover.
Shopify's Agentic plan lets non-Shopify merchants participate while keeping their existing stores. They must import products and keep them current in Shopify; documented options include CSV, API synchronization, and PIM connectors. Agentic plan setup.
For an agent developer, the distinction is concrete: StoreRouter can add coverage through storefront integration without waiting for the merchant to set up that Shopify connection.
Platform independence does not mean universal coverage. Check the coverage directory for the stores your application needs.
Before you build
Integration notes
- Does Shopify enrich product data too?
Yes. Shopify documents AI-inferred descriptions and product attributes as well as normalized options. Enrichment is part of StoreRouter's value, but its existence alone does not establish better search relevance. Shopify's inferred fields.
- Is every StoreRouter Parse response enriched?
No. Semantic enrichment is available on indexed products. On-demand Parse does not run enrichment, so those responses can be sparser.
- Can I use both?
Yes. Evaluate StoreRouter for independent product discovery and Shopify's commerce tools where the merchant and workflow support them. StoreRouter focuses on discovery and product data; it does not provide checkout.
- Does an agent developer have to upload merchant feeds?
Using Shopify Catalog does not require the agent developer to upload every participating merchant's feed. The import and synchronization work described here is for non-Shopify merchants joining through the Agentic plan. Merchant setup guide.
Start with the stores your shoppers care about
Check coverage, try a real shopping query, and inspect the attributes your agent needs to make a recommendation.
Documentation reviewed · 2026-10-09
Sources and scope
This page compares documented approaches. We have not run a Shopify benchmark or established better relevance, more accurate enrichment, broader total coverage, or fresher prices.
- Shopify catalog interfaces: catalog scope and product discovery tools.
- Global Catalog inferred fields: generated and enriched product information.
- Catalog Mapping: custom data sources and product grouping.
- Agentic plan setup: product imports and ongoing synchronization for non-Shopify merchants.
Shopify's developer overview describes Global Catalog in terms of Shopify merchants, while its Agentic plan help docs explain non-Shopify participation. We do not assume every Agentic plan import is exposed identically through every developer interface or AI channel.