In order for CX to get a better and easier look of all comments placed on a certain customer there needs to be a clear overview in the UI. Right now, the comment is only viewable on the specific order that the comment was placed, meaning if a customer has plenty of orders the customer service agent would need to check through all orders to see if they have any previous comments, such as suspected fraud. A better overview would save time and give the agent the info they need right away. This would also be useful when managing the block email functionality. The most optimal solution for this would be to show all manual order comments placed on a customer on all orders. Alternative solutions would be to either add a button “See all comments” or under the already existing button “See all orders” reach a page that directly shows all the customers comments straight away without any additional click.

Summary Expose a new event that fires whenever WMS/ERP updates product variant stock in Brink, so that downstream consumers (e.g. auction services) can listen and reconcile their own inventory counts in near-real-time. Background & Motivation External services that manage their own view of available stock currently have no way to know when a warehouse has updated inventory in Brink. They need a reliable event to trigger their own stock reconciliation logic, particularly when quantity increases after a restock or replenishment from WMS. Use Cases Stock reconciliation — A warehouse sends updated stock levels to Brink. An external auction service listens to the event and adjusts its own inventory accordingly. Proposed Behaviour Emit a stock.updated event (or equivalent) on theProductVariantInventory resource whenever stock quantity is changed via the inventory API (i.e. WMS/ERP-initiated updates). The event payload should include: productVariantId inventoryId before.quantity after.quantity timestamp This enables consumers to derive their own logic, such as: Reconciliation — before.quantity < after.quantity (restock / replenishment)

We would like to be able to set the fallback shipping required by the KSA solution in Brink and not in our CMS. — Vi har snackat snabbt med Brink om det, så lite info: Vi behöver också sätta upp en fallback för shipment. https://docs.kustom.co/contents/checkout/shipping-assistant/overview https://docs.brinkcommerce.com/workflows-and-integrations/integrations/payments/klarna https://docs.kustom.co/contents/api/checkout/other/createordermerchant#other/createordermerchant/t=request&path=shipping_options

Add the ability to export data to Excel in the Orderview

It would be very useful to have an overview over latest changes to discount codes, who changed what and who created the codes in order to stay compliant. (similar to how it looks on orders)

It would be neat to extract all products from brink via an endpoint. Specifically useful when changing master data source or switching services connected only to brink, i. e a WMS.

must-have Failed orders Operations that need approval Failed workflow executions nice-to-have External events on DLQ Orders with blocked-order custom state id

How many orders have a specific custom state?

Default Mode Dark Mode Light Mode

Each new external event need to be enabled and then added to an external destination. We should be able to improve this UX process.

Reservation Custom Attributes on products

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.

as a merchant I want to offer addon services, i.e logo / name /customization to a product.

Extend Brink/Inretrn integration to include exchange orders.

Hi, Currently we need to manually set refund fee when handling refunds in Brink. Looking for a solution that allows us to preset different “refund fees”. It could work similar to how shipping does, where you can easily include the refund fee based on a set of refund fees we have created in Brink. This would help minimize manual errors when creating refund fees, where you have to type the amount, name and tax percentage.

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 Typical Use Cases “Find all failed orders from yesterday and explain why they failed.” “Refund this order and notify the customer.” “Create a new market for Canada with CAD pricing and default shipping.” “List all orders delayed due to inventory constraints.” “Adjust safety stock rules for this warehouse.” “Generate a campaign payload for 20% off selected SKUs.” Benefits Operational speed Execute complex workflows in seconds instead of navigating multiple UI views Faster issue resolution and daily operations Lower operational friction Work directly in language, scripts, or AI agents No UI learning curve for advanced users Automation-ready by design Same interface supports human-driven commands and automated agents Natural path from assisted actions to full automation Merchant control & safety Scoped permissions and explicit execution boundaries Explainable actions with full traceability Future-proof operations Enables AI-first operating models Allows merchants to build their own operational assistants on top of Brink Positioning MCP for Merchant Portal turns Brink into an LLM-native commerce operations platform—where managing orders, inventory, markets, and insights can happen entirely through language, APIs, and automation, without a traditional UI.

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

There are cases where CX need to contact the customer first, and others where they need assistance from Finance to resolve them. Would it be possible to have some kind of tagging functionality? For example, tag cases with “Customer contacted” or “Finance contacted.”

Discovery on updating the maximum orderline size on an order.

When an order is deleted we should remove the customer in Voyado.