Commerce Gateway — initial public release
Commerce Gateway is a self-hosted routing layer that gives any LLM a stable, typed tool surface over your commerce stack — product search, cart operations, order management — without rewiring your integration for each provider or storefront. Initial public release.
What's new
npm package
First public @betterdata/commerce-gateway release on npm.
Documentation
Onboarding and integration guides on the developer hub.
New in LLM Commerce Gateway
### Stable tool surface One set of named tools — product.search, product.detail, cart.add, order.status, and more — defined once and executed against backends you own. The gateway never guesses your catalog: every tool call routes to your code or connector, which calls Shopify, your database, or a headless API. ### Multi-entry LLM support The same backends serve multiple LLM entry points simultaneously: - HTTP tool execution (POST /api/tools/execute) for any agent that can POST JSON - OpenAI-style function-calling adapters for GPT-4o and o-series - MCP server for Claude desktop and hosted MCP clients - Grok and Gemini adapter support Switching providers or adding a second entry point does not require touching your commerce backends. ### Connector model Backends are configured via getBackends() — either from an official connector (Shopify included) or your own implementation. The gateway calls your code; your code calls your platform. Business logic and data stay in your stack. ### Session and auth configuration Session storage (Redis for conversational state) and auth configuration are set at the gateway level, not per-tool. Every tool execution inherits the same session context and returns a normalized success/error shape — consistent across providers and useful for logs.
Why it matters
The standard approach to AI commerce integrations today is hand-wiring each LLM vendor's tool or function-calling format to each platform's APIs — and then repeating that work when the provider changes or a second storefront is added. The integration becomes the maintenance burden.
Commerce Gateway separates the problem into two stable boundaries: what the model is allowed to ask for (the tool surface) and how those requests are fulfilled (the backends). Neither side needs to know how the other is implemented.
That separation gives you three things that are otherwise hard to get at once: provider portability without rebuilding integrations, clear accountability for commerce side effects versus model prompting, and a foundation for governing what an assistant is actually allowed to do — without that governance living inside a prompt.
Upgrade notes
Initial OSS release. SDK at v0.1.0. Shopify connector included. Four LLM adapters live (Claude, OpenAI, Grok, Gemini). MCP server path available for Claude desktop/hosted clients. Self-hosted only at launch — Better Data hosted tier in progress.