Headless commerce visible to AI agents — without rewriting your stack
Whether you're on Medusa, commercetools, Saleor, or a custom Rails/Django catalog, SignalixIQ ingests your product data via REST, GraphQL, or JSON feed and exposes it through a hosted MCP server.
About this integration
Custom commerce stacks (Next.js + Stripe, Remix + Medusa, custom Rails) and headless commerce platforms (commercetools, Saleor, Spree). SignalixIQ ingests catalog via a flexible REST/GraphQL adapter or direct JSON feed.
Why Headless / Custom Commerce stores need MCP
Headless setups are agent-invisible by default
Headless commerce often relies on client-side rendering, which AI agent crawlers handle inconsistently. Even with SSR, custom product schemas usually lack canonical fields like GTIN and structured availability. SignalixIQ bypasses this by ingesting from your data source directly.
Multi-frontend setups create catalog inconsistency
Headless merchants often run multiple frontends (web, mobile, partner portals) against the same catalog. Agents see different data depending on which frontend they hit. SignalixIQ unifies by pulling from your single source of truth.
Custom commerce gives you the cleanest agent integration possible
Unlike platform-specific quirks (Shopify's variant pricing, WooCommerce's missing GTIN), headless stores can map exactly to SignalixIQ's canonical schema. The result is the highest GEO scores in the customer base.
How to connect Headless / Custom Commerce to AI shopping agents
- 1
Choose your ingestion mode
REST endpoint (recommended), GraphQL endpoint, or signed JSON feed delivered on schedule. The SignalixIQ dashboard guides you through the right choice based on your stack.
- 2
Map your fields to the canonical schema
Use the SignalixIQ field-mapping UI to map your custom field names (e.g., 'productSlug', 'priceCents') to canonical fields (title, price). Validation runs in real-time.
- 3
Set sync cadence
Polling (every 5/15/60 min) or webhook push. Push is recommended for real-time inventory and price accuracy.
- 4
MCP endpoint live
Same as the platform integrations — registered with ChatGPT, Claude, Perplexity within 24-72 hours.
Headless / Custom Commerce → SignalixIQ field mapping
Exactly which Headless / Custom Commerce fields SignalixIQ reads and how they map to the canonical agent-product schema.
| SignalixIQ field | Headless / Custom Commerce field | Notes |
|---|---|---|
product.title | Your product name field | Required. |
product.description | Your description field (markdown OK) | Markdown auto-converted to clean prose. |
product.gtin | Your GTIN/UPC/EAN field if available | Strongly recommended. If absent, SignalixIQ runs heuristic matching against GS1. |
product.brand | Your brand field | Required for agent product disambiguation. |
product.price | Your price field (cents or dollars; both supported) | Configurable unit. |
product.availability | Stock status enum or numeric quantity | Either format accepted. |
product.url | Canonical product URL on your storefront | Used in agent click-through. |
product.images | Image URL array | Up to 8 images surfaced to agents. |
Common Headless / Custom Commerce issues that hurt agent discoverability
- Field naming inconsistency across data sources (catalog API vs search index)
- Stale data when sync cadence is too long (recommend ≤15 min polling or webhook push)
- Currency unit confusion (price in cents vs dollars vs subunit)
- Image URLs requiring auth or hotlink protection — must be publicly accessible
- Missing brand fields on white-label or generic products
SignalixIQ's free GEO score audits your store and ranks these issues by agent-discoverability impact. Run a free scan →
Frequently asked
Does this work with Medusa, Saleor, commercetools, Spree, or other open-source commerce?▾
Yes. All major headless platforms expose REST or GraphQL endpoints that SignalixIQ can ingest. Medusa, Saleor, commercetools, and Spree have battle-tested setup guides. Custom Rails/Django/Laravel commerce works via the JSON-feed mode.
What if my product data is split across multiple services?▾
Common in mature headless setups (catalog service + pricing service + inventory service). SignalixIQ can pull from multiple sources and merge based on product ID. Configuration is per-customer for the first multi-source ingestion; subsequent ones are self-serve.
Can I push to SignalixIQ instead of having you pull?▾
Yes — webhook push is the recommended approach for headless setups. SignalixIQ provides a signed-webhook endpoint; you POST product changes when they happen. Lower latency and avoids polling overhead.
Make your Headless / Custom Commerce store discoverable
SignalixIQ hosts the MCP server so AI shopping agents can find your products. Free GEO score in 60 seconds — no signup required.
Other platform integrations
Shopify
Shopify is the largest hosted commerce platform, powering ~4.5M stores. SignalixIQ connects via the Shopify Admin API and exposes products, variants, inventory, and structured metadata to AI shopping agents via MCP.
WooCommerce
WooCommerce powers ~3.5M live e-commerce stores on WordPress. SignalixIQ integrates via the WooCommerce REST API and exposes products to AI shopping agents through MCP.
BigCommerce
BigCommerce powers ~50,000 mid-market and enterprise stores. SignalixIQ integrates via the BigCommerce Storefront API and exposes catalog data to AI shopping agents via MCP.
Magento (Adobe Commerce)
Magento and Adobe Commerce power large-catalog mid-market and enterprise merchants. SignalixIQ integrates via the Magento REST API and exposes catalog data to AI shopping agents through MCP — with attention to Magento's complex attribute set and store-view multi-language structure.
Squarespace Commerce
Squarespace Commerce powers ~1M small-to-medium online stores. SignalixIQ integrates via the Squarespace Commerce API and exposes products to AI shopping agents via MCP.
Wix Stores
Wix Stores powers ~700k commerce sites. SignalixIQ integrates via the Wix Stores API and exposes products to AI shopping agents via MCP.