AI Powered integration with expert operators

Amazon Seller Central and Brightpearl

Integration Agency & Consultants

The pressure usually starts when the Amazon settlement report no longer matches your Brightpearl bank records. At lower volumes, manual adjustments for FBA fees and Amazon commissions are manageable. At scale, the gap between Amazon disbursements and your internal ledger becomes a source of reconciliation debt that finance teams spend days trying to unpick. Cogent2 connects Amazon Seller Central and Brightpearl to ensure fees, refunds, and FBA stock movements are accounted for, restoring financial control and reducing manual overhead.

Castore
Lounge
Oliver Bonas
Green People
Tatty Devine
Cult
Auditing your marketplace and ERP architecture

We connect your Amazon Seller Central and Brightpearl systems for Marketplaces and ERP, ensuring your integrations work efficiently. Our consulting services are valuable because our system audit uncovers inefficiencies and integration gaps across Amazon Seller Central, Brightpearl, Marketplaces, and ERP. This enables our consultants and your team to take decisive action, helping your technology ecosystem run smoothly and efficiently. As a result, you can deliver a great experience to your customers and keep your business operations running at their best.

Solution Design

The design prioritises Brightpearl as the inventory master and financial sub-ledger, while Amazon Seller Central remains the transaction engine. In most setups, FBM orders sync on a defined schedule to trigger warehouse picks, while FBA orders download as completed sales. A core design choice involves virtual warehouse mapping. FBA stock is typically held in a separate warehouse in Brightpearl to prevent contamination of merchant-fulfilled stock levels.

The primary trade-off involves how financial data is captured. We often prioritise batch reconciliation via the Amazon Settlement Report over intra-day postings. While this creates a reporting lag, it ensures that every fee and refund matches the cash disbursement exactly. This design allows finance to close the month knowing that Brightpearl records align with the actual Amazon payouts.

Connecting transactions and multi warehouse inventory

Amazon Seller Central acts as the transaction engine while Brightpearl serves as the master for inventory and financial reconciliation. Orders sync on a defined schedule. Merchant Fulfilled (FBM) orders trigger fulfilment in Brightpearl to drive warehouse picks, while FBA orders download as completed sales to reduce stock from a dedicated Amazon warehouse. Inventory levels move from Brightpearl to Amazon to protect against overselling. The process accounts for pending orders in Seller Central so that Brightpearl inventory reflects stock that is committed but not yet shipped, preventing double-counting across channels. Intelligence layers monitor these flows to spot whenever a SKU mismatch or sync delay threatens account health.

Orchestrating workflows via secure middleware platforms

Leveraging IPaaS with ISO 27001 and SOC 2 and above security accreditations enables secure, efficient integration between Amazon Seller Central, Brightpearl, Marketplaces, and ERP systems. IPaaS simplifies connecting Amazon Seller Central and Brightpearl, automating data flows across Marketplaces and ERP platforms. This approach reduces manual errors, supports scalability, and ensures data protection, making integration management easier and more secure for businesses handling sensitive information.

Monitoring settlement accuracy and stock discrepancies

Standard dashboards often hide the discrepancies that cause month-end stress. Practical visibility requires monitoring the delta between Amazon disbursements and Brightpearl records. This includes identifying settlements where fees, liquidations, or reimbursements exist in Amazon but have no corresponding entry in Brightpearl. Monitoring also focuses on identifying SKUs with mismatched FBA stock levels before they impact account health ratings. This approach surfaces exceptions early, such as missing returns or unmapped fee categories, rather than letting them accumulate until the bank reconciliation fails. Data issues are prioritised by their impact on settlement accuracy and stock availability.

Training finance and operations teams locally

Handover focuses on the operational teams running the business. Finance typically learns how to reconcile the Amazon Settlement Report within Brightpearl, specifically handling fee categories and adjustments. The ops team manages the split between FBA and FBM stock pools and learns to check for 'Pending' orders that might affect inventory levels. We also walk the team through reading integration alerts to identify SKU mismatches early.

Documentation is provided as a plain-English operating manual. It details what to check periodically, how to handle exceptions, and which team owns each part of the process. This ensures your team can manage the day-to-day operations with confidence after launch.

Managing operational drift and settlement updates极

Ongoing support focuses on identifying and resolving the operational drift between Amazon Seller Central and Brightpearl. We monitor for errors where SKU mismatches halt order downloads and track integration performance to ensure stock updates remain accurate during peak volumes. When Amazon processes liquidations or reimbursements, we ensure these transaction types are correctly handled to prevent settlement discrepancies. This oversight helps maintain reliable FBA stock levels in Brightpearl and ensures the financial record remains accurate.

Integration operating model

In this model, Amazon remains the high-velocity front end while Brightpearl acts as the financial sub-ledger. Merchant-fulfilled (FBM) orders are treated as standard warehouse picks. FBA orders flow in as fulfilled sales to keep stock levels synchronised across dedicated virtual warehouses. The process handles the transition of orders from pending status to avoid double-counting stock during the Amazon payment verification window. Financial accuracy is maintained via the Settlement Report. This helps reconcile payouts against individual orders, Amazon fees, and VAT adjustments to ensure Brightpearl records match the actual cash landing in the bank. This ensures the month-end close is based on settled reality rather than estimated sales.

Common failures

Settlement report and reconciliation debt

Operational impact: Amazon settlement reports rarely match the final bank disbursement 1:1. Amazon fees, promotional credits, held reserves, and miscellaneous adjustments create a permanent gap between sales revenue recorded in Brightpearl and the cash received. This forces finance into manual investigations to clear reconciliation debt at month-end.

Prevention / Action: Map each transaction type (orders, refunds, fees, adjustments) to specific general ledger accounts. Use a suspense account to handle unrecognised Amazon transaction types or liquidations. For Amazon VAT Calculation Service (VCS) users, ensure Brightpearl's native tax calculation is disabled to prevent rounding discrepancies between the Amazon invoice and the Brightpearl sales receipt.

FBA inventory drift and stock pool mismatch

Operational impact: Brightpearl's view of FBA stock becomes inaccurate if the integration only deducts stock for shipped sales orders. It ignores inventory adjustments for customer returns, warehouse damages, or inter-fulfilment-centre transfers. This leads to flawed replenishment forecasting and overselling risks if the FBA and FBM stock pools are not separated correctly within the account.

Prevention / Action: Synchronise FBA inventory event reports including adjustments and receipts. FBM and FBA stock pools must be managed within distinct Brightpearl warehouses to prevent double-counting. Ensure Amazon MSKUs match Brightpearl SKUs exactly; otherwise, orders may download as non-inventory items, failing to allocate stock and causing operational latency.

Orphaned orders and mapping failures

Operational impact: If an Amazon MSKU does not exist in Brightpearl, the integration may fail to download the order. This halts order creation, leaving the order orphaned. Without immediate intervention, these orders fall behind the fulfilment SLA, leading to late shipment violations for Merchant-fulfilled (FBM) orders or reconciliation gaps for Amazon-fulfilled (FBA) orders.

Prevention / Action: Implement strict SKU matching protocols. The integration should surface mapping errors in a dashboard for the ops team to resolve. Since refunds initiated in Seller Central do not always automatically create Sales Credits in Brightpearl, establish a workflow to sync returns status and preserve the financial trust boundary.

Frequently asked questions

How does the integration handle inventory for both Fulfilled by Amazon (FBA) and Fulfilled by Merchant (FBM) stock?

The integration establishes Brightpearl as the inventory master for all FBM stock, syncing available quantities to Amazon Seller Central to prevent overselling. For FBA inventory, stock levels are pulled from Amazon into a separate, dedicated warehouse location within Brightpearl. This provides a complete and accurate view of your total inventory value across all locations without double-counting stock.

My Amazon settlement reports never seem to match my bank deposits. How does the integration help with reconciliation?

This integration automates the creation of journal entries in Brightpearl that correspond to each Amazon Payout report, correctly allocating sales, refunds, and variable Amazon fees. By processing sales and fees from the settlement report, it avoids the common problem where a finance team has to manually match a single lump-sum payment from Amazon to hundreds of individual sales orders. This makes the month-end close process significantly faster and more accurate.

We're at risk of getting an Amazon account health warning from overselling. How does this integration stop that?

The integration designates Brightpearl as the central source of truth for your Fulfilled by Merchant (FBM) stock levels. When a sale is made on any connected channel, such as your own website, Brightpearl updates the master inventory record and pushes the new stock level to Amazon Seller Central. This ensures you do not advertise or sell stock on Amazon that has already been sold elsewhere, protecting your seller rating.

Can I trust the FBA inventory numbers I see in Brightpearl for my financial reporting?

Yes, maintaining accurate inventory valuation is a core goal of the operating model. The integration pulls stock data from Amazon FBA into a non-sellable warehouse in Brightpearl, reflecting quantities that are available, in reserve, or in transit. This provides an accurate inventory asset value in your Brightpearl sub-ledger without your finance team needing to manually extract reports from Amazon Seller Central.

How are FBA returns and refunds from Amazon reflected in Brightpearl?

When Amazon confirms a customer return, the integration can automatically create a sales credit within Brightpearl linked to the original sales order. This ensures your financial records and revenue reporting remain accurate without requiring manual data entry from your customer service team. The process also accounts for whether Amazon returns the item to your sellable FBA inventory, ensuring stock levels are also kept correct.

Get Started

We would love to hear about your brand and project