Brightpearl and John Lewis Marketplace
Integration Agency & Consultants
Securing a Direct to Customer partnership with John Lewis requires precise, automated order processing to meet strict vendor service level agreements. At scale, manual entry or incorrect carrier mapping in Brightpearl leads to rejected tracking data and withheld payments. This integration protects the commercial value of the partnership by ensuring inventory accuracy and dispatch compliance are maintained without manual intervention. Success depends on handling the specific transit time requirements that standard connections often miss.
Diagnosing gaps in your retail ecosystem
We connect your Brightpearl and John Lewis Marketplace integration quickly, supporting ERP and Marketplaces. Our consulting services are valuable because our system audit identifies inefficiencies and integration gaps across Brightpearl, John Lewis Marketplace, ERP, and Marketplaces. This enables our consultants and your team to take decisive action, ensuring your technology ecosystem runs efficiently. With our audits, you can deliver a great customer experience by keeping your systems aligned and performing at their best, supporting your business growth and operational excellence.
Solution Design
For this Brightpearl and John Lewis Marketplace integration, the primary design decision is establishing Brightpearl as the master for inventory and price. In most setups, we prioritise the automation of dispatch data and carrier code mapping to meet retailer service standards. We typically opt for a controlled approach to financial postings to ensure cleaner reconciliation against settlement statements, acknowledging the trade-to-reporting lag as a compromise for ledger accuracy. The sequencing prioritises core order and inventory flows, while complex edge cases may stay manual during the initial phase. This approach ensures finance closes the month with verified revenue while ops works from a single, reliable pick list in Brightpearl.
Mapping carrier codes and status synchronisation
Brightpearl serves as the master for inventory and price, while John Lewis Marketplace pushes customer orders for centralised fulfilment. The integration must map John Lewis carrier codes precisely within Brightpearl. Any deviation causes the retailer to reject tracking data, which can delay payments and violate service level agreements. Once a dispatch confirmation is generated in Brightpearl, the integration transmits the tracking reference and status update to meet John Lewis transit time requirements. Monitoring is configured to detect instances where a dispatch appears successful in Brightpearl but has not been correctly accepted by the retailer system.
Secure orchestration via accredited middleware platforms
Leveraging IPaaS with ISO 27001 and SOC 2 and above security accreditations enables secure, efficient integration between Brightpearl, John Lewis Marketplace, ERP, and other Marketplaces. This approach simplifies connecting Brightpearl to John Lewis Marketplace and ERP systems, ensuring data protection and compliance. IPaaS platforms reduce manual effort, support scalability, and maintain high security, making integration with Marketplaces and ERP straightforward and reliable.
Surfacing tracking failures and retailer penalties
Visibility into the Brightpearl and John Lewis sync is about more than a simple status light. Hidden issues often reside in the mismatch of dispatch statuses where an order is marked as shipped in Brightpearl but remains pending in John Lewis due to rejected tracking data. Our approach surfaces these specific failures, identifying which orders are at risk of breaching retailer standards. By monitoring the data flow between systems, we ensure that tracking gaps and inventory discrepancies are flagged for intervention before they lead to retailer penalties.
Operational handover and exception ownership training
Internal teams including finance, ops, and ecommerce must adopt specific ownership boundaries for the John Lewis integration to remain compliant. We hand over an operating model that defines how data moves between systems and where the source of truth sits for each object. Your team learns to check inventory sync logs and perform regular reconciliation of dispatch data against Brightpearl sales orders. We train operators to identify and resolve carrier code mapping exceptions to maintain service standards. Documentation is provided as a concise operational handbook for the people running the business, focusing on alert interpretation and exception ownership rather than technical architecture.
Post-launch governance to protect vendor ratings
Post-launch support focuses on preventing issues that could lead to your brand being de-listed. We monitor for status discrepancies between Brightpearl and John Lewis, specifically watching for rejected tracking updates or inventory mismatches. Our process identifies where manual interventions—such as incorrect courier selections in the warehouse—break the retailer requirements. We resolve these errors before they impact your vendor rating, ensuring the operations team can rely on automated status updates.
Common failures
Mismatched carrier codes on dispatch
Operational impact: John Lewis systems will reject dispatch notifications if the carrier information does not exactly match their approved list. This failure means the customer is not notified of shipment, seller performance metrics are negatively impacted, and payments are automatically delayed. The finance and operations teams are then forced into a manual process of investigating failed updates and chasing delayed payouts from John Lewis.
Prevention / Action: The integration's fulfilment logic must include a definitive mapping table to translate Brightpearl's internal shipping methods to the exact John Lewis carrier codes. This mapping should be maintained as a core part of the integration configuration, not left to manual user selection. Exception handling should be configured to flag and hold any Goods Out Note with an un-mappable carrier, preventing the data from being sent and alerting the operations team to correct it in Brightpearl first.
SKU mismatches causing inventory sync failures
Operational impact: If SKUs in Brightpearl do not perfectly match the corresponding product identifier in the John Lewis catalogue, inventory level updates for those items will fail. This leads to stale stock data on the marketplace, creating a high risk of overselling popular items or, conversely, lost sales from items showing as out of stock. Repeated overselling due to these data gaps is a primary cause for compliance warnings and potential de-listing from the marketplace.
Prevention / Action: Brightpearl must be designated as the single source of truth for all product and inventory master data, including the SKU. Before go-live, and on a regular basis thereafter, the integration should run a comparison audit between Brightpearl SKUs and John Lewis product listings. This process should generate an exception report for the merchandising or ecommerce team to resolve any discrepancies, ensuring data alignment before they can cause live inventory errors.
Delayed or failed creation of Sales Credits for returns
Operational impact: When a customer return is processed by John Lewis, the integration is responsible for creating a corresponding Sales Credit in Brightpearl. If this fails, the returned item is not booked back into sellable stock, skewing inventory levels and potentially causing lost sales. Furthermore, the finance team's reconciliation of John Lewis payout reports against Brightpearl's general ledger becomes impossible without correct Sales Credit records.
Prevention / Action: The integration's returns-handling logic must ensure that every authorised John Lewis return generates a corresponding Sales Credit in Brightpearl. The process needs to account for timing, such as waiting for the original Brightpearl Sales Order to be in a non-pending state before attempting to create the credit. The integration should also feature a retry mechanism and an exception queue to manage any returns that fail the initial creation attempt, alerting an operator to resolve the underlying data issue in Brightpearl.
Dispatch updates failing due to incorrect Goods Out Note status
Operational impact: The integration reads Brightpearl Goods Out Notes (GONs) to trigger dispatch notifications to John Lewis. If warehouse staff or other processes move a GON to a status the integration is not designed to handle, such as 'Picked', the dispatch update will never be sent. The operations team sees the order as fulfilled, but from John Lewis's perspective, the order is late, directly threatening seller performance scores and payment timelines.
Prevention / Action: Define a specific, agreed-upon status in Brightpearl (e.g., 'Packed') as the sole trigger for initiating a dispatch notification to John Lewis. The integration should be configured to only poll for GONs in this exact status, ignoring all others. This must be aligned with the fulfilment team's documented operational procedures to ensure process and system logic are synchronised, preventing records from becoming stuck in an invalid state.
Frequently asked questions
How does this integration ensure our shipments meet John Lewis's strict carrier and tracking requirements?
The integration specifically maps your Brightpearl shipping methods to the official John Lewis carrier codes, a common failure point for vendors. When a Goods Out Note is marked as dispatched in Brightpearl, the integration sends a dispatch confirmation with the correct carrier and tracking details to John Lewis. This ensures your tracking data is accepted, which is critical for meeting their service levels and ensuring timely payment.
Which system acts as the master record for inventory, and how does this prevent overselling?
Brightpearl serves as the central source of truth for all inventory levels in this operating model. Any stock change in Brightpearl, whether from a receipt of goods or a sale on another channel, triggers an update to the available quantity on your John Lewis Marketplace listings. This centralised stock sync is essential for preventing the sale of out-of-stock items, which would negatively impact your vendor performance metrics.
We've secured a John Lewis partnership. Why is an automated integration essential from day one?
John Lewis operates under strict service level agreements for order processing and dispatch that are very difficult to meet with manual workflows. An integration automates the creation of Sales Orders in Brightpearl from John Lewis and the return of dispatch confirmations, ensuring you consistently meet their required time windows. This automation is a core requirement for maintaining a healthy \"Direct to Customer\" partnership and avoiding penalties for non-compliance.
How does the integration handle customer returns and refunds between John Lewis and Brightpearl?
A return initiated on John Lewis can trigger the creation of a Sales Credit in Brightpearl, but the workflow must be configured correctly. A common failure occurs if the original Brightpearl Sales Order is not fully invoiced, as this blocks the Sales Credit from being generated. Properly managing this returns handling process is key to maintaining accurate stock figures and simplifying financial reconciliation.
Can our fulfilment workflow in Brightpearl cause issues with John Lewis order updates?
Yes, operational sequence in Brightpearl is critical for keeping John Lewis updated. A dispatch confirmation can only be sent once a Brightpearl Goods Out Note (GON) is moved to a 'Printed' or 'Shipped' status. If your internal processes create a delay at this stage, the dispatch update to John Lewis will also be delayed, putting your service level performance at risk.