Skip to main content

2026Q1

8
Product Development

PDP Discount Simulation

Enable merchants to display the best possible price on PDP by extending Brink’s pricing service to simulate discount- and cart-rule conditions. The feature calculates and returns applicable discounts as if the product were in an ideal cart state — including campaigns, promotions, and conditional rules (e.g., tax deductions). Benefit: Improves price transparency for end customers and ensures accurate, rule-based discount stacking across PDP and checkout.

Product Development

GDPR – “Forget Me” Endpoint

A new GDPR-compliant “Forget Me” endpoint will be introduced, allowing merchants to remove customer data upon request. The endpoint will trigger an event that can be used to build integrations with external systems, ensuring that customer data is deleted consistently across all connected platforms. The functionality will be accessible via API and within the Merchant Portal. Value / Impact: This feature strengthens Brink’s compliance with GDPR regulations and simplifies data privacy management for merchants. It enables automated and verifiable customer data deletion workflows, reducing manual effort and minimizing legal and operational risks related to data handling.

Product Development

Improve Order Overview

Brink Commerce will introduce an enhanced Order Overview that provides deeper granularity and clearer traceability within a single consolidated view. The updated interface will surface key operational elements — including discounts, campaigns, deliveries, compensations, refunds, and more — all aggregated into one place to reduce navigation and minimize clicks. Value / Impact: This improvement streamlines operational workflows, giving support and operations teams faster access to the full lifecycle of an order. It reduces handling time, improves accuracy in issue resolution, and provides a more intuitive way to understand the complete order context at a glance.

Product Development

Draft-Based Approval Flow for Sensitive Operations

Brink Commerce is introducing a 4-eye approval process for refund and compensation operations in the Merchant Portal. This change is designed to reduce the risk of errors by requiring two separate users to create and approve these actions before execution. Impact: By enforcing a separation of duties, merchants can ensure more controlled and accountable handling of sensitive financial operations, helping to prevent mistakes and unauthorized actions within Customer Experience teams. Benefits: Reduced Risk: Prevent accidental or unauthorized refunds and compensations. Stronger Process Control: Enforces clear handover between initiator and approver. Auditability: Improves traceability of who created and who approved each operation. Key Features: Refunds and compensations must first be created as drafts from the order view. Drafts are displayed in a dedicated approval view (Operations Dashboard). A second user must approve and start the operation; creators cannot self-approve. UI clearly separates the create and execute steps to avoid confusion. To use this approach most effectively is by dividing users into CX-User and CX-Admin CX-User only have access to create operations CX-Admin only have access to start operations Scope: Applies to: All Operations

Product Development

External Prices

Brink Commerce is introducing support for external price control, allowing merchants to dynamically set product prices directly in the cart using external systems. This capability is ideal for merchants leveraging real-time pricing models, such as auctions, or using external price list services that manage complex pricing data. Impact: Merchants gain the ability to offer flexible, context-driven pricing, ensuring customers see the most accurate and competitive prices without being limited by pre-set price lists. This is a game-changer for businesses that need to respond to market conditions instantly. Key Use Cases: Auction-Based Pricing: Dynamically set product prices in real-time as customers add items to their cart. Dynamic Price Lists: Use external pricing services to calculate and apply prices without preloading them in Brink. Market-Responsive Discounts: Adjust prices based on external factors, such as demand, competitor pricing, or customer segment. Benefits: Ultimate Pricing Flexibility: Merchants can offer real-time, competitive prices without manual updates. Enhanced Customer Experience: Shoppers always see accurate prices, avoiding confusion or price conflicts. Scalable for Complex Models: Supports both simple price adjustments and complex, dynamic pricing strategies.

Product Development

Price Service

Brink Commerce will expand its Price Service with two key capabilities, available exclusively to merchants with a Campaign Manager license: New campaign price feeds, enabling external systems to consume campaign-specific pricing in a structured and reliable format. A new query endpoint that returns all price, product, or campaign changes within a specified timeframe, allowing downstream systems (such as search and indexing clusters) to update dynamically and efficiently. Value / Impact: These enhancements ensure fresher, more accurate pricing across the merchant’s ecosystem. Search, indexing, and personalization services can react to price and campaign updates in near real time, reducing inconsistencies, improving data alignment, and strengthening the overall customer experience.

Product Development

TaxJar integration

Brink Commerce is integrating a native TaxJar integration within the checkout flow. The integration will initially support Kustom Checkout, the former Klarna Checkout, and Adyen. It enables external tax calculation directly during checkout and provides support for tax reporting via delivery APIs, ensuring accurate calculation and presentation of U.S. sales tax. Value / Impact: This integration simplifies U.S. tax compliance for merchants by offloading complex tax logic to TaxJar. It ensures accurate tax calculation in real time, improves operational efficiency through automated reporting, and supports smoother expansion into the U.S. market.

Product Development

Automated Workflow

Brink Commerce is introducing Rule-Based Order Workflow Automation within Brink OMS, empowering merchants to create dynamic, conditional workflows that automatically guide orders based on predefined rules. This capability transforms order management from a static process into a flexible, intelligent system that adapts to each merchant’s unique needs. Impact: Merchants can automate complex decision-making, ensuring that orders are handled based on criteria like order value, customer profile, payment method, or product type. This means faster processing, reduced manual workload, and improved risk management. Key Benefits: Increased Control: Customize how orders are processed, reviewed, or fulfilled. Enhanced Risk Management: Automatically flag high-risk orders for review. Operational Efficiency: Minimize manual intervention with automated decisions. Adaptable Workflows: Scale from simple review rules to complex multi-condition routing.

2026Q2

7
Product Development

AI Cart Recommendations

Brink Commerce is partnering with Cursive, an AI-native personalization engine, to bring real-time, generative product recommendations directly into the cart experience. Through a native integration with Brink's Shopper Service and Shopper Insights, merchants can activate AI-driven cart recommendations and dynamically generated headlines without building or training their own ML models. Every time a shopper updates their cart, the service responds in roughly 40 ms with a fresh, context-aware set of recommendations and a generative headline tuned to that exact basket, market, and channel. Activation is handled in the Brink Merchant Portal, the same configuration flow merchants already use for payment and shipping providers. Impact Cart is one of the highest-intent surfaces in the funnel, but historically a hard place for merchants to drive incremental revenue without heavy merchandising effort. With Cursive plugged into Brink, cart becomes a revenue-bearing surface powered by generative AI — with measurable uplift, full attribution, and no replatforming required. Benefits Incremental revenue uplift on cart. AI-driven recommendations and generative headlines designed to lift average order value and conversion on an underutilized surface. No ML investment required. Cursive owns the model, ranking, and generative copy. Merchants get AI-native UX without hiring data science teams or training their own models. Real-time relevance (~40 ms). Recommendations are generated on every cart update, based on the actual basket, market, and channel context — not pre-built bundles. Generative, not rule-based. No need to hand-curate bundles or write headlines in advance. The model produces both the product selection and the copy on the fly. Merchandiser stays in control. Curated picks, pinning, and overrides remain available whenever the team wants to steer the model. Built-in measurement. Brink's Shopper Insights tracks what was shown, clicked, and converted — giving full transparency on the value delivered. Per-channel, per-market activation. Roll out gradually: start with a single channel on one market and scale from there. Fast time-to-live. API ready within roughly a week of data access; model training can complete in as little as 24 hours. No replatforming. Activated via a toggle in Merchant Portal plus an initial data push same flow as any other Brink provider. Key Features Generative product recommendations rendered in the cart on every basket update. AI-generated headlines tailored to the live cart context, market, and channel. Native integration with Brink Shopper Service (cart context) and Shopper Insights (training and measurement). Merchant Portal activation — turn Cursive on per channel and per market, the same way you configure payment or shipping. Manual overrides and pinning so merchandisers can always steer the model. Attribution and performance data built into Shopper Insights, including what was shown, clicked, and converted. Interested in joining the early access program? Contact your CSM or the Brink Product team.

Product Development

LLM-Native Operations in Merchant Portal

MCP (Model Control Plane) for Merchant Portal enables merchants to operate Brink entirely through their own Large Language Model (LLM) over HTTP, without relying on a graphical user interface. Through MCP, an LLM becomes a first-class operational client to Brink. It can securely read data, query insights, and execute real operations by interacting with Brink’s Management and OMS APIs using natural language translated into validated API calls. This allows merchants to run their daily commerce operations via conversation, scripts, or AI agents—searching orders, managing deliveries and refunds, configuring markets, inventory, pricing, and campaigns—without clicking through UI workflows. MCP is not a chatbot layer. It is a controlled execution plane that exposes Brink’s domain logic, schemas, and permissions to LLMs in a safe, auditable, and deterministic way, governed by user roles and access. Core Capabilities Data access via language Search and filter orders Retrieve customers, products, prices, inventory, campaigns Query operational and performance insights Operational execution Create shipments and deliveries Perform refunds and cancellations Transition OMS states Configure inventory rules and availability Set up new markets, currencies, store groups, and channels Create or modify campaigns and discounts LLM-native API interaction Natural language → validated API requests Schema-aware payload generation Permission-scoped execution Full auditability of actions HTTP-based integration Works with merchant-owned LLMs Supports AI agents, scripts, automations, and internal tools No dependency on Merchant Portal UI Spotlight: Discount Operations Discount management is the single highest-friction area in day-to-day Brink operations. The majority of merchant support requests fall into one of four patterns: configuring rules, simulating outcomes, diagnosing unexpected behavior, or reporting on usage. MCP collapses each of those into a single LLM prompt — backed by the same permission model and audit trail as direct API access. Configuration "Create code KLARA10K, capped at 10,000 SEK, calculated on regular price even during active campaigns, valid only on these SKUs." "Set up a Gift-with-Purchase rule that adds the size-matched mystery item when cart total exceeds threshold X." "Add an OR condition to discount rule Y so it triggers for either VIP or member tier." Simulation "If a customer with the VIP tag adds 4 pairs of socks in size 36–40, which mystery variant is selected and what is the final cart total?" "Show how stacked codes A and B combine on a 1,200 SEK cart with express shipping in the SE market." "Preview the discount outcome for this exact cart before I commit the rule change." Diagnostics "Why has code X been used more times than its usage limit?" "List all reasons code Y was rejected at checkout in the last 24 hours." "Why is the express-shipping member discount not applying for this customer on the FI market?" "Find all discount rules where the cache status is stale." Reporting "Top 10 discount codes last month by revenue, split by store market." "Usage and revenue trend for cart rule X over the last 90 days."

Product Development

Custom Feature Visibility Control

Custom Feature Visibility Control allows users to hide specific features from the Brink Merchant Portal, providing them with the ability to control which features are accessible. This feature is valuable for users who want to prevent certain features from being used, especially when new features have not been integrated by external systems yet.

Product Development

Avalara Tax Provider Support

We're adding Avalara as a supported tax provider in Brink Commerce, bringing full parity with our existing TaxJar integration. This includes tax calculation during cart and checkout, as well as complete support throughout the order lifecycle — including deliveries, refunds, cancellations, releases, and other OMS operations. What's included: Cart & checkout tax calculation via Avalara Full OMS support: deliveries, refunds, modifications, cancellations, and releases Configuration aligned with existing tax provider patterns Why this matters: Avalara is one of the most widely used tax compliance platforms globally. This addition gives merchants more flexibility in choosing their preferred tax provider without sacrificing coverage across the full order lifecycle.

Product Development

Universal Commerce Protocol for Brink Commerce

Create a UCP adapter layer that translates between UCP's standardized schemas and Brink's native APIs. —> Allow Merchants to configure their UCP Profile in Brink Merchant Portal —> Create adapter for Checkout Session API and Shopper —> Payment Handlers for Payment Providers —> Shipping Handlers for Shippig Providers —> Identity Linking —> Discounts/Promotions —> Tax Calculation

Product Development

Order Data Access API

Brink Commerce will introduce a flexible and performant API that allows merchants to query and retrieve order and fulfillment data — including tracking URLs — in a single call. The new endpoint supports multiple search parameters such as order reference, email (case-insensitive), and date ranges, eliminating the need for multi-step API requests and simplifying integrations with customer service and operational systems. Value / Impact: This feature enhances data accessibility and integration efficiency, giving merchants faster, more flexible ways to retrieve order information while maintaining strict control over exposed data. It reduces complexity for support tools like chatbots and CRMs, improves response times, and provides a scalable foundation for future data access capabilities within Brink OMS.

Product Development

Split Shipments in Checkout

This feature enables split shipment handling in the checkout flow when using the Ingrid V2 integration. The checkout will be able to split carts into delivery groups based on inventory allocation rules, allowing different parts of an order to be fulfilled and shipped separately. On the order level, Brink OMS will split order lines into groups according to the defined delivery configuration. Acceptance Criteria: Cart is automatically split into delivery groups based on inventory allocation type. Order lines are grouped accordingly for fulfillment and shipment operations. Use Cases: Product Type Split: Split between bulky and AutoStore items — defined at the product level. Customer-Selected Split: Allow the customer to choose to split delivery when an order contains both cross-dock and warehouse items — also defined at the product level. Value / Impact: This feature improves the flexibility and accuracy of the checkout and fulfillment process. It ensures more efficient logistics handling, reduces delivery times for available items, and enhances customer experience by offering more transparent and convenient shipping options.

2026Q3

3
Product Development

Ship-from-Store Strategy for Flexible Fulfillment

Brink Commerce is introducing a ship-from-store fulfillment model, allowing merchants to dynamically route and fulfill orders from stores or central warehouses based on inventory availability, market priorities, and operational conditions. This approach enables flexible fulfillment scenarios such as store pickup, localized shipping, and hybrid warehouse-store delivery models — all managed seamlessly within Brink Order Management and Checkout. Impact: Merchants gain increased control and efficiency in order fulfillment, optimizing logistics and reducing shipping costs through dynamic prioritization of store and warehouse inventory. Customers benefit from faster, more flexible delivery options, including store pickup and localized delivery, leading to improved satisfaction and conversion rates. Benefits: Customizable Fulfillment Priorities: Adjust store vs. warehouse allocation dynamically based on market needs or seasonal demand. Dynamic Store Fulfillment Toggle: Enable or disable store-based fulfillment at the market or store level without disrupting warehouse operations. Enhanced Customer Experience: Provide transparent messaging in checkout about fulfillment logic, split shipments, and return policies. Store Selection in Checkout: Allow customers to select “Pick up in store” directly within the delivery step. Item Availability Validation: Notify customers if all items are available at the selected store, with options to choose another store or split the order. Seamless Confirmation Process: Deliver immediate, clear confirmation after store selection for a smooth checkout experience.

Product Development

Sitoo Integration

Brink will introduce a native integration with Sitoo POS, enabling seamless omnichannel operations between online and in-store environments. The integration will support: Buy Online, Pick Up In Store (BOPIS) — allowing customers to collect online orders in physical stores. Buy Online, Return In Store (BORIS) — enabling in-store returns for online purchases. Inventory Updates — ensuring real-time synchronization of stock levels between Sitoo and Brink OMS. Value / Impact: This integration enhances the unified commerce experience by connecting online and offline sales channels. It empowers merchants to offer flexible fulfillment and return options, improves inventory accuracy across all locations, and strengthens customer satisfaction through faster and more convenient post-purchase experiences.

Product Development

Replacement Order

As a customer service representative, or integrator, I want to be able to exchange a product for a customer on their existing order by creating a linked new order, So that the customer can receive their preferred item with minimal hassle and without the need to enter their payment and shipping details again. Acceptance Criteria: Linked New Order Creation: On initiating a product exchange, a new order (type? Exchange?) should be created and linked to the original order via a unique identifier. The exchange must be trackable across both orders. Inherited Payment Authorization: The new order should carry over the payment authorization from the original order to avoid asking the customer for payment details again. Management Domain Integration: Stock levels, pricing, and other relevant information should be pulled from the "Management" domain in Brink Commerce. Consistent Customer Information: The new order should use the same shipping and billing information as the original order. Customer Communication: Upon successful creation of the new exchange order, an event/webhook should be emitted, to automatically notify listening integrators (CRM, ERP) that an exchange /update has been created. Replacement Order Creation: The Admin UI should allow customer service representatives to create a new order marked as a "Replacement Order."

2026Q4

4
Product Development

Omnichannel Fulfillment Enhancements

Brink Commerce is expanding its fulfillment and inventory capabilities to deliver a more advanced and precise omnichannel fulfillment experience across checkout, routing, and customer delivery options. The enhancements focus on strengthening allocation logic, improving inventory visibility in checkout, and enabling more flexible shipping scenarios. Key improvements include: Enhanced Allocation Algorithm Configurable rules for single-inventory fulfillment, ensuring an entire order can be fulfilled from one location when required. Support for fallback inventory logic (e.g., default to a central warehouse) and safety stock thresholds per location to reduce overselling and increase allocation accuracy. Enriched Shipping Selector Integrations Deeper integrations with providers such as Ingrid, Nshift, Kustom, and Avarda. Checkout now surfaces inventory type visibility (store, warehouse, drop-ship) and updates allocation in real time based on customer selection, improving lead-time accuracy for immediate or deferred pickup. Split Shipment Support More advanced coordination between allocation logic and shipping selectors, enabling mixed fulfillment scenarios where customers can pick up part of an order in-store while other items are shipped separately. Value / Impact: These enhancements deliver greater operational control for merchants and a more transparent, flexible customer experience. They reduce overselling risk, improve delivery promise accuracy, and streamline BOPIS/BORIS flows. Overall, they strengthen Brink’s role as a true omnichannel commerce platform capable of dynamic, multi-location fulfillment at scale.

Product Development

Ship-from-Store Strategy for Flexible Fulfillment

Brink Commerce is introducing a ship-from-store fulfillment model, allowing merchants to dynamically route and fulfill orders from stores or central warehouses based on inventory availability, market priorities, and operational conditions. This approach enables flexible fulfillment scenarios such as store pickup, localized shipping, and hybrid warehouse-store delivery models — all managed seamlessly within Brink Order Management and Checkout. Impact: Merchants gain increased control and efficiency in order fulfillment, optimizing logistics and reducing shipping costs through dynamic prioritization of store and warehouse inventory. Customers benefit from faster, more flexible delivery options, including store pickup and localized delivery, leading to improved satisfaction and conversion rates. Benefits: Customizable Fulfillment Priorities: Adjust store vs. warehouse allocation dynamically based on market needs or seasonal demand. Dynamic Store Fulfillment Toggle: Enable or disable store-based fulfillment at the market or store level without disrupting warehouse operations. Enhanced Customer Experience: Provide transparent messaging in checkout about fulfillment logic, split shipments, and return policies. Store Selection in Checkout: Allow customers to select “Pick up in store” directly within the delivery step. Item Availability Validation: Notify customers if all items are available at the selected store, with options to choose another store or split the order. Seamless Confirmation Process: Deliver immediate, clear confirmation after store selection for a smooth checkout experience.

Product Development

Sitoo Integration

Brink will introduce a native integration with Sitoo POS, enabling seamless omnichannel operations between online and in-store environments. The integration will support: Buy Online, Pick Up In Store (BOPIS) — allowing customers to collect online orders in physical stores. Buy Online, Return In Store (BORIS) — enabling in-store returns for online purchases. Inventory Updates — ensuring real-time synchronization of stock levels between Sitoo and Brink OMS. Value / Impact: This integration enhances the unified commerce experience by connecting online and offline sales channels. It empowers merchants to offer flexible fulfillment and return options, improves inventory accuracy across all locations, and strengthens customer satisfaction through faster and more convenient post-purchase experiences.

Product Development

Replacement Order

As a customer service representative, or integrator, I want to be able to exchange a product for a customer on their existing order by creating a linked new order, So that the customer can receive their preferred item with minimal hassle and without the need to enter their payment and shipping details again. Acceptance Criteria: Linked New Order Creation: On initiating a product exchange, a new order (type? Exchange?) should be created and linked to the original order via a unique identifier. The exchange must be trackable across both orders. Inherited Payment Authorization: The new order should carry over the payment authorization from the original order to avoid asking the customer for payment details again. Management Domain Integration: Stock levels, pricing, and other relevant information should be pulled from the "Management" domain in Brink Commerce. Consistent Customer Information: The new order should use the same shipping and billing information as the original order. Customer Communication: Upon successful creation of the new exchange order, an event/webhook should be emitted, to automatically notify listening integrators (CRM, ERP) that an exchange /update has been created. Replacement Order Creation: The Admin UI should allow customer service representatives to create a new order marked as a "Replacement Order."