BMOS checkout actions let merchants choose where buyers complete checkout.

What Checkout Actions Are

Checkout actions are product-level instructions in the BMOS agentic feed. They tell a human storefront, AI shopping surface, or buyer agent which checkout paths are available for a sellable product.

The original singular checkout_action remains the compatibility field. The additive checkout_actions[] array is the forward model for merchant-selected destinations and multiple checkout paths.

Backwards Compatibility

• /agentic-commerce/feeds/STOREFRONT_ID?version=0.1 preserves the legacy feed shape and does not include checkout_actions[].
• /agentic-commerce/feeds/STOREFRONT_ID and ?version=0.2 can include additive v0.2 fields, including checkout_actions[].
• The singular checkout_action field remains present when BMOS checkout is available, even when checkout_actions[] is also present.
• Consumers that ignore unknown fields continue to work without code changes.
• Merchant-selected destinations are additive routing options; enabling Shopify or WooCommerce actions does not disable the existing checkout.best action unless the merchant removes that destination from settings.

Action Shape

Each action has a stable id, a destination platform, an intended audience, a human-readable label, and a numeric priority. Lower priority values should be shown first.

Supported Destinations

Feed Example

{
  "id": "SKU-123",
  "title": "Premium Wireless Speaker",
  "checkout_action": {
    "type": "bmos.agentic_checkout",
    "endpoint": "https://app.buildmyonlinestore.com/agentic-commerce/checkout",
    "method": "POST"
  },
  "checkout_actions": [
    {
      "id": "shopify-product-page",
      "type": "merchant_product_page",
      "platform": "shopify",
      "audience": "human",
      "label": "View on Shopify",
      "priority": 10,
      "method": "GET",
      "url": "https://merchant.example/products/speaker",
      "requires_redirect": true
    },
    {
      "id": "shopify-cart",
      "type": "merchant_cart",
      "platform": "shopify",
      "audience": "human",
      "label": "Add to Shopify cart",
      "priority": 15,
      "method": "GET",
      "url": "https://merchant.myshopify.com/cart/49123456789012:1",
      "requires_redirect": true
    },
    {
      "id": "secure-checkout-best",
      "type": "human_redirect",
      "platform": "secure.checkout.best",
      "audience": "human",
      "label": "Secure checkout",
      "priority": 20,
      "method": "POST",
      "endpoint": "https://app.buildmyonlinestore.com/agentic-commerce/checkout"
    },
    {
      "id": "machine-checkout-best",
      "type": "agentic_checkout",
      "platform": "machine.checkout.best",
      "audience": "agent",
      "label": "AI Agent Checkout",
      "priority": 30,
      "method": "POST",
      "endpoint": "https://app.buildmyonlinestore.com/agentic-commerce/checkout"
    }
  ]
}

Merchant Settings

In the BMOS app, merchants manage checkout destinations in storefront settings under Advanced - Protocols and Checkout Destinations. The selected protocols are stored as storefront checkout settings and reflected in the public feed.

• Select shopify to expose safe product-page or cart actions for Shopify-connected products.
• Select woocommerce to expose safe product-page or cart actions for WooCommerce products.
• Select secure.checkout.best to expose human checkout.best session creation.
• Select machine.checkout.best to expose AI Agent Checkout when the storefront is enabled for agent selling.

Consumer Guidance

• Read checkout_actions[] first when present, sorted by priority ascending.
• Filter by audience. Human interfaces should prefer audience: "human"; buyer agents should inspect audience: "agent".
• Use url actions for direct redirects and endpoint actions for BMOS checkout-session creation.
• Do not assume every product has every destination. Product URLs, variant IDs, checkout readiness, and merchant settings vary by product and storefront.
• If checkout_actions[] is absent, fall back to the singular checkout_action.

Public Data Safety

Checkout actions are public feed metadata. They must not expose app tokens, private install IDs, internal catalog visibility flags, wholesale cost, factory cost, merchant margin, or private channel strategy.

If a product is not public or agent-visible for a storefront, BMOS omits it from the feed rather than exposing hidden status fields.

Related Docs