Brink is a set of APIs and events, not a fixed platform. Here's literally what that unlocks.
Brink does not force you into a predefined storefront. Cart, checkout, pricing, and catalog are available through documented REST APIs, so your team can build the customer experience in Next.js, Remix, Astro, or the stack you already prefer. And if you want to replace the frontend later, you can do that without rebuilding the backend.
Your mobile app can use the same session, cart, pricing, and checkout APIs as your website. There is no separate mobile backend to build or keep in sync. One cart. One set of prices. One source of truth across every device.
Brink supports both B2C and B2B commerce models. Each Store Group can have its own tax rules, capabilities, and pricing logic. That means you can run a consumer storefront and a wholesale portal side by side, on the same platform, with the rules each channel needs.
Store Groups and Store Markets let you manage currency, tax, providers, and market-specific settings independently. Launch a new brand or market through configuration, not a full rebuild. Run it all from one Brink account.
The data your POS needs is available through real-time APIs. Stock, pricing, and product data can be shared with a partner solution like Sitoo or Kustom, or with a custom in-store setup. Store teams work from the same inventory and pricing data as the website, without another system to reconcile.
Cart and checkout are API-first, which means checkout is not limited to a browser. Build it into a self-checkout kiosk, mobile app, voice assistant, chat interface, or any other customer touchpoint. If it can make an HTTP request, it can complete a sale.
Catalog, pricing, stock, tax, discounts, orders, and checkout each run as their own Go service, with its own database, API, and event stream. Use one, use five, or replace one later without touching the rest.
Every write is idempotent and conflict-safe. Sequence-number-based optimistic concurrency means retries, duplicate webhooks, and out-of-order events never corrupt state.
Every meaningful change publishes a schema-validated event via EventBridge or webhook. Failed deliveries retry automatically, and outages can be recovered with a replay instead of manual fixes.
Built on AWS Lambda, DynamoDB, EventBridge, and Step Functions. No servers to provision, no capacity planning before Black Friday — it scales up and down automatically.
The Merchant Portal runs on the same public APIs as any integrator. Anything it does, you can build, automate, or replace via the API — no private UI-only logic.
Every API call — human, integration, or AI agent — follows the same access model: OAuth 2.0 client credentials with tightly scoped permissions like deliveries/write or orders/read.
EQPE is taking its next step in digital commerce with a new online store on Brink Commerce. In collaboration with NoA Ignite, the brand has built a modern
Read article
