Brightpearl and Marketplacer
Integration Agency & Consultants
Our AI-powered delivery, guided by experienced operators, connects Brightpearl and Marketplacer without creating downstream financial complexity. Moving to a marketplace model puts immense pressure on manual processes. We establish a clean connection for orders and supplier settlements, so you can pay your third-party sellers accurately and on time.
Audit system gaps and integration logic
We connect your Brightpearl and Marketplacer ERP and Marketplaces swiftly, ensuring your systems work together efficiently. Our consulting services are invaluable, with our system audit uncovering integration gaps and inefficiencies across Brightpearl, Marketplacer, ERP, and Marketplaces. This enables our consultants and your team to take decisive action, optimising your technology ecosystem for smooth operations. By addressing issues early, you can deliver a consistently excellent experience to your customers and keep your business running efficiently as you grow.
Solution Design
Architecting Brightpearl and Marketplacer requires clear decisions on virtual inventory ownership and financial settlement. Brightpearl typically acts as the source of truth for order processing and accounting, while Marketplacer manages the multi-seller storefront. We sequence the 'virtual inventory' loop early, ensuring Brightpearl triggers automated purchase orders to sellers without physically holding stock. A key trade-off involves sync frequency. While real-time inventory updates reduce overselling risks, they increase API load during peak periods, so we often implement a prioritised batch approach for lower-velocity catalogues. This design ensures finance closes the month with accurate revenue and tax categorisation, even when Marketplacer collects VAT that Brightpearl must process as a third-party liability. The operating result is a reconciled ledger that avoids manual work during supplier payout cycles.
Map data flows for supplier settlement
Data flows between Brightpearl and Marketplacer are designed to protect the integrity of the supplier settlement loop. Marketplacer captures the order and handles seller-side stock visibility, while Brightpearl serves as the authoritative source for order statuses and accounting. Orders post to Brightpearl on a defined schedule, where they trigger automated dropship purchase orders to the correct seller. We implement monitoring at the line-item level to ensure tax and shipping fees are mapped correctly before the financial record is locked. This sequencing ensures that if a seller provides incorrect tracking data or fails to ship, the integration surfaces the exception early, preventing the accounting mess that occurs when finance tries to fix reconciled orders.
Standardise connections via secure middleware logic
Leveraging IPaaS with ISO 27001 and SOC 2 and above security accreditations ensures secure, efficient integration between Brightpearl, Marketplacer, ERP, and Marketplaces. IPaaS simplifies connecting Brightpearl and Marketplacer with ERP and Marketplaces, automating data flow while maintaining strict security standards. This approach reduces manual effort, supports scalability, and ensures compliance, making integrations reliable and future-proof.
Monitor transactional accuracy and revenue drift
Standard dashboards often miss the quiet failures that break marketplace financials, such as a seller's shipping fee being incorrectly categorised as revenue in Brightpearl. Our platform monitors these specific data drifts, surfacing failures before they compound into reconciliation gaps. We track the synchronisation of shipment events and tracking IDs to ensure Marketplacer is updated when a seller fulfils an order. Monitoring focuses on transactional accuracy: if a seller cancels an order but the credit note fails to post to Brightpearl, finance is alerted before the settlement run. This level of visibility transforms the integration from a black box into a manageable business process.
Enable teams to manage operational exceptions
Handover focuses on how finance, operations, and ecommerce teams manage the daily flow between Brightpearl and Marketplacer. We define ownership for each exception type, such as seller stock mismatches or order status drift, so CX and warehouse teams know exactly where to intervene. Documentation is an operational reference rather than a technical archive, detailing what to check daily and how to interpret alerts from the integration layer. Training is anchored in your specific design decisions, ensuring your team can reconcile supplier settlements and manage third-party seller performance. This shift in operating model ensures that when Cogent steps back, your team owns the logic that drives settlement accuracy and marketplace fulfilment.
Post launch governance and performance monitoring
Post-launch support focuses on operational ownership and the prevention of data drift between Marketplacer and Brightpearl. We monitor the integration layer for marketplace-specific exceptions, such as seller out-of-stock events occurring after order capture or tracking ID failures that prevent Brightpearl from closing out a drop-ship purchase order.
When these discrepancies occur, the platform surfaces them to prevent them from becoming accounting errors. This ensures your finance team can resolve seller performance issues before they impact automated supplier payouts or VAT reconciliation in Brightpearl. We provide escalation for technical faults, but we prioritised keeping your ops team in control of the daily sync logic. Regular performance reviews ensure that as your seller list grows, your Brightpearl configuration is adjusted to handle the increased transaction volume and settlement complexity.
Common failures
Mismatched tax and fee revenue
Operational impact: Marketplacer collects gross revenue, but Brightpearl is the system for financial record. If the integration does not accurately split VAT, commissions, and seller-specific fees when creating sales orders in Brightpearl, automated supplier payout journals will be incorrect. This leads to significant reconciliation work for the finance team, inaccurate liability reporting, and risks overpaying or underpaying third-party sellers.
Prevention / Action: The integration's order creation logic must map Marketplacer's line-item charges to specific nominal codes in Brightpearl. Work with your finance team to define the accounting treatment for each revenue and fee type before building. Design a periodic reconciliation process that compares Marketplacer's payout reports against completed sales orders and journals in Brightpearl to catch and correct mapping errors.
Inventory latency causing overselling
Operational impact: Brightpearl acts as the central inventory master. If sync updates to Marketplacer are delayed, an item can sell out in Brightpearl but still appear available on Marketplacer. This results in failed sales orders and cancelled shipments, creating negative customer experiences and requiring manual follow-up from the customer service team.
Prevention / Action: Establish a near-real-time inventory synchronisation from Brightpearl to Marketplacer, prioritising these updates over other data flows. Implement stock buffers within Brightpearl for SKUs sold via Marketplacer to account for any unavoidable sync latency. The integration must include robust retry logic and monitoring to alert the operations team immediately if the inventory feed is failing or delayed.
Delayed or failed dispatch notifications
Operational impact: Brightpearl generates dropship purchase orders to sellers, but Marketplacer owns the customer communication and seller payment trigger. If the seller's tracking information is not passed back to Brightpearl and then synced promptly to Marketplacer, customers are not notified of shipment. This also delays seller payment, harms the marketplace's reputation with its sellers, and increases 'where is my order?' queries for the CX team.
Prevention / Action: The integration workflow must ensure that updating a dropship purchase order in Brightpearl with tracking details reliably triggers a shipment notification to Marketplacer. Define this sequence clearly in the integration logic, with exception handling for cases where tracking information is missing or invalid. Log all successful and failed shipment updates for audit purposes.
Return and refund process disconnect
Operational impact: When a customer initiates a return, the process touches both systems and multiple teams. A refund processed directly in Brightpearl without a corresponding action in Marketplacer will not trigger the correct workflow for the seller or update the order status for the customer. This leads to finance team confusion, incorrect seller settlement reports, and a poor customer experience when they have to chase refund status.
Prevention / Action: Define a single source of truth for initiating returns and refunds, which is typically Marketplacer. The integration should listen for return requests from Marketplacer and create the corresponding sales credit in Brightpearl. Ensure the process is operationally aligned so that the finance team knows to process the final refund payment only after the sales credit is correctly posted, keeping both systems in sync.
Frequently asked questions
How does Brightpearl handle orders for products from third-party sellers that we don't physically stock?
When a customer places an order on your storefront, Marketplacer creates the initial Sales Order. The integration then creates a corresponding dropship Purchase Order in Brightpearl, assigned to the correct third-party seller. This process directly addresses the 'virtual inventory' loop, automating seller instructions without needing you to manually re-key order details.
Manual order entry is becoming a problem. What specific risk does automating with Brightpearl remove?
Relying on manual order entry between Marketplacer and Brightpearl as you scale introduces significant risks of shipment delays and incorrect supplier payments. Automating the flow ensures that every Sales Order created in Brightpearl is a perfect mirror of the Marketplacer order. This protects the integrity of your order-to-cash process and prevents payment errors caused by simple data entry mistakes.
What happens if Marketplacer's tax calculations don't match our setup in Brightpearl?
This is a common failure point that creates reconciliation headaches and incorrect supplier payouts. If Marketplacer applies a tax or fee that Brightpearl is not configured to handle on the Sales Order, your automated accounting will be wrong. This forces your finance team to make manual journal entries to correct the discrepancies, particularly during the month-end close.
If a third-party seller fails to ship an order, how do we fix the accounting in Brightpearl?
The integration is designed for this scenario, which is a key concern for marketplace operators. Because Brightpearl creates a dropship Purchase Order for the seller, a failure to ship means that PO is never marked as fulfilled. Your operations team can then simply cancel the Purchase Order in Brightpearl, which prevents the supplier from being paid and ensures your financial records remain accurate without manual intervention.
Which system should be the source of truth for product data, Marketplacer or Brightpearl?
For effective catalogue management, Brightpearl should typically act as the master source of truth for the core Item record and SKU. However, individual sellers will manage their own stock levels and pricing within Marketplacer. The integration's role is to correctly map the seller's Marketplacer listing to the master SKU in Brightpearl when a Sales Order is created, ensuring financial data is consistently reported.