Short Answer

No. BMOS is not intended to replace a merchant's Shopify store.

For Shopify merchants, BMOS should usually be treated as an add-on layer: it imports or mirrors product data, publishes agent-friendly product surfaces, and creates additional paths for AI tools and buyer agents to discover or transact with the merchant's products.

A practical setup is: Shopify remains the commerce and operations system, while BMOS publishes the canonical agentic feed, discovery metadata, an optional conversational agent, and merchant-approved checkout actions. A BMOS conversation may hand a shopper back to Shopify without competing with Shopify checkout.

System Roles

Layer Shopify BMOS
Human storefront Primary ecommerce website, theme, product pages, cart, checkout, customer accounts, and merchant admin. Optional store pages, embedded buy buttons, product widgets, or AI-built storefronts that can point back to existing product URLs.
Product data Often the merchant's source system for products, variants, price, inventory, images, and fulfillment workflows. Normalizes product data into BMOS catalogs and storefront-specific visibility rules for feeds, buttons, and agentic checkout.
AI discovery Shopify supports agentic commerce through Shopify's agent and UCP surfaces. Publishes a dedicated BMOS agentic feed and site metadata so AI tools can inspect structured product, merchant, availability, and checkout-routing information.
Checkout Shopify checkout remains the standard path for the Shopify store and Shopify-supported agentic channels. Publishes merchant-selected checkout actions. For a Shopify-connected pilot, BMOS can route to a trusted Shopify product page or exact-variant cart; other checkout providers are optional and must be explicitly enabled.
Conversational identity Shopify does not supply the merchant's BMOS .agent identity. A connected .agent name identifies the merchant's conversational assistant and references the BMOS-hosted conversation and canonical feed.

Recommended Data Flow

  1. Merchant keeps Shopify live as the existing storefront and operations system.
  2. BMOS imports Shopify products into a BMOS catalog, preserving Shopify product and variant identifiers in source metadata.
  3. Merchant chooses which products belong in each BMOS storefront, feed, button set, or agentic store.
  4. BMOS publishes a public agentic feed at /agentic-commerce/feeds/<storefront_id>.
  5. An optional .agent identity points supported users and clients to the merchant-specific BMOS conversation experience; it is not the feed host.
  6. For Shopify products with trusted product URLs or variant IDs, BMOS can publish additive checkout_actions[] that route human shoppers back to Shopify product pages or cart links.
  7. The merchant links that feed from the Shopify theme, footer, product pages, or metadata using the BMOS badge or a plain alternate link.
  8. AI tools can inspect the BMOS feed while humans continue shopping through the Shopify storefront.

Safe First Import

Connecting Shopify from BMOS starts OAuth only. It does not import products, overwrite a catalog, publish a feed, change the Shopify theme, or change Shopify checkout.

  1. Choose the destination BMOS catalog. For the first test, a dedicated catalog such as Shopify Import is the safest choice.
  2. Enter the store's myshopify.com domain and approve the app in Shopify.
  3. Return to BMOS Products, preview Shopify products, then select specific products or import all.
  4. Review the imported products before using them in the public BMOS agentic feed.
Import preserves Shopify product identity first, then uses SKU to adopt a compatible legacy row. If two different Shopify products reuse the same SKU, BMOS keeps them separate and generates a deterministic collision-safe SKU instead of overwriting one product with the other. Imported rows retain Shopify product and variant IDs in source metadata so the connection can be audited and reconciled later.

For large-catalog pagination, count reconciliation, inventory modes, and “continue selling when out of stock,” see the Shopify Catalog Sync guide.

Checkout Actions

BMOS keeps the legacy singular checkout_action field for existing feed consumers and adds checkout_actions[] for newer agents and storefronts that understand multiple checkout destinations.

For Shopify-connected products, BMOS should prefer safe human actions that send shoppers back to Shopify. Product-page actions use the trusted Shopify product URL. Cart actions are included only when a reliable Shopify variant ID or cart URL is available.

See the BMOS Checkout Actions guide for the full field shape, destination IDs, consumer fallback behavior, and merchant settings.

This does not replace Shopify checkout. It lets BMOS publish AI-readable catalog and routing metadata while Shopify remains the merchant's customer, checkout, fulfillment, app, and operations system.

For the end-to-end identity, conversation, and Shopify handoff model, see the Shopify Conversational Agent guide.

Protocol Positioning

Shopify's Universal Commerce Protocol work is important for agentic commerce. BMOS should not position against it as if merchants must choose one path.

Instead, BMOS gives merchants another structured surface for AI discovery and checkout experimentation. BMOS feeds are designed for agent-readable commerce data and can support ACP-style and UCP-style workflows as agent platforms evolve.

In plain terms: Shopify is one major commerce system with its own agentic commerce rails. BMOS is a merchant-controlled catalog, feed, and checkout layer that can sit beside Shopify, WooCommerce, custom sites, marketplace pages, and distributor sites.

What To Tell Merchants

It does not replace Shopify

Your Shopify store can stay live. BMOS adds structured product discovery and optional agent checkout surfaces.

It is not a theme migration

You do not need to rebuild your Shopify theme to test BMOS. Start with catalog sync, a feed link, and a small set of products.

It can be rolled out gradually

Use BMOS first for AI discoverability, then add buy buttons or machine checkout where the merchant wants a separate checkout experiment.

Shopify Theme Metadata

When a Shopify store has a BMOS agentic storefront, link the BMOS feed from the Shopify site so crawlers, LLM-connected tools, and buyer agents can find the machine-readable catalog.

<link
  rel="alternate"
  type="application/json"
  title="BMOS agentic commerce feed"
  href="https://app.buildmyonlinestore.com/agentic-commerce/feeds/STOREFRONT_ID">

<meta
  name="bmos-agentic-store-feed"
  content="https://app.buildmyonlinestore.com/agentic-commerce/feeds/STOREFRONT_ID">

For visible trust and discovery, the merchant can also add a footer or product-page link to the BMOS agentic feed.

This alternate-feed link does not install the conversational shopping widget. Feed discovery belongs in the page <head>; the shopper-facing widget uses a separate script installed before </body> in layout/theme.liquid.

Install and Submit the Shopping Widget

The shopper-facing widget appears as a floating chat button on any merchant-controlled website where its script is installed and the hostname is allowed in BMOS. That can be the primary Shopify store, a separate branded domain, a landing page, a blog, or a campaign microsite. When opened, it lets a visitor describe a need, budget, style, or product question; returns grounded recommendations from the merchant-approved BMOS catalog; and offers trusted Shopify product or cart handoffs.

It assists existing visitors

The widget helps shoppers navigate and compare products without replacing Shopify pages, checkout, orders, or fulfillment.

It records an attributable funnel

BMOS can measure widget opens, questions, recommendations, and checkout handoff clicks.

It is not traffic acquisition by itself

Directory listings, editorial content, SEO, partner links, and other distribution work are separate ways to bring new visitors to the merchant.

  1. In BMOS, open the storefront's AI Shopping Widget settings and save every merchant-controlled hostname where the widget may run. It does not need to be the primary Shopify domain.
  2. Enable the widget, generate the one-time install snippet, and copy it immediately. Generating a new snippet rotates the previous key.
  3. For Shopify, open Online Store → Themes → Edit code → layout/theme.liquid. For another platform, open its site-wide custom code or footer injection area.
  4. Paste the widget script immediately before </body> and publish the site.
  5. Return to BMOS, enter a public page containing the widget, and select Verify & submit for promotion.

BMOS fetches the page and confirms the widget script, storefront key, allowed domain, and enabled channel. A passing check creates a review request; it does not silently publish an unreviewed installation.

After approval, BMOS can mark the store's public directory data as widget-verified. Publication or refresh in connected third-party directories is a separate operator-reviewed step and may depend on each directory's rules.

Implementation Notes

External References