Brightpearl and Lightspeed
Integration Agency & Consultants
Operational pressure usually spikes when a busy shop floor starts selling items that the warehouse has already allocated elsewhere. At scale, manual stock updates between Lightspeed and Brightpearl cannot keep pace with high-frequency retail, leading to overselling and inventory drift. This integration becomes critical when stock levels in your physical stores no longer match the central records. We focus on establishing a clear system of record, ensuring shop floor transactions update stock in real-time while Brightpearl maintains the total inventory and accounting ledger.
Audit and diagnostic for core systems
Cogent2 connects your Brightpearl and Lightspeed systems, integrating ERP and POS platforms efficiently. Our consulting services are invaluable, offering a thorough systems audit to uncover inefficiencies and integration gaps between Brightpearl, Lightspeed, ERP, and POS solutions. This audit empowers both our consultants and your team to take decisive action, ensuring your technology ecosystem operates smoothly and efficiently. As a result, you can deliver an outstanding experience to your customers, confident that your systems are optimised for reliability and growth.
Solution Design
Design decisions for Brightpearl and Lightspeed centre on balancing retail transaction speed with accounting accuracy. We typically establish Brightpearl as the master record for total inventory while Lightspeed owns the store-level transaction. A key trade-off involves inventory sync frequency: frequent updates protect against store overselling but can increase system load, so we sequence data flows to prioritise high-velocity locations. We help you choose between batching store totals for cleaner reconciliation or posting individual transactions for immediate stock visibility. This approach ensures finance can rely on Brightpearl for month-end reporting while store teams work from accurate shop-floor stock levels in Lightspeed.
Mapping data flows across store locations
The integration maintains Brightpearl as the master record for total inventory and product specifications. Orders created in Lightspeed post to Brightpearl to trigger stock updates and financial record-keeping, while Brightpearl pushes updated inventory levels back to Lightspeed to reflect warehouse arrivals or online sales. We sequence these flows to ensure that store floor stock is protected, using mapping rules to distinguish between different physical locations. Monitoring is embedded at the transaction level to catch data mismatches before they reach the month-end ledger.
Secure orchestration via enterprise grade IPaaS
Leveraging IPaaS with ISO 27001 and SOC 2 and above security accreditations ensures secure, efficient integration between Brightpearl ERP and Lightspeed POS, as well as Brightpearl POS and Lightspeed ERP. IPaaS platforms simplify complex connections, automate data flows, and reduce manual errors, providing reliable, scalable integration. This approach guarantees data protection and compliance, making it easier to connect Brightpearl and Lightspeed systems while maintaining high security standards.
Managing exceptions to protect data trust
Visibility often fails when teams rely on dashboards that only show successful syncs while inventory drift compounds silently. We focus on exposing the exceptions that actually threaten operations: orders stalled by mapping errors, tax discrepancies between POS and the ledger, and shop floor stock levels that have fallen out of step with the warehouse. Our monitoring surfaces these issues as individual records, allowing your team to resolve a specific inventory mismatch before it turns into a week-end reconciliation project. This approach replaces manual spot-checks with a proactive exception-management workflow.
Operational handover for internal business teams
Handover focuses on how your finance, retail ops, and ecommerce teams own the Brightpearl and Lightspeed operating model. We define who manages specific exception types, such as inventory mismatches between store locations and the central warehouse. Training covers the routine checks required to keep POS transactions aligned with the ledger and how to interpret alerts before they impact the physical store. We provide operational documentation written for the people running the business, not for an IT archive. This ensures your team knows exactly what to look for to maintain data integrity across all physical and digital locations.
Post-launch monitoring and root cause resolution
Post-launch support is about preventing the accumulation of data errors. We provide ongoing monitoring that prioritises significant exceptions, such as inventory sync failures or missing financial postings. Our model ensures that issues are surfaced with the necessary context for finance or operations to take action. We don't just restart a failed sync; we identify the underlying cause to prevent it from recurring, ensuring the integration remains reliable as your volume grows.
Common failures
Mismatched stock location logic for Click and Collect
Operational impact: Brightpearl allocates stock from the central warehouse for an in-store collection order because it cannot see the sale is tied to a specific retail location in Lightspeed. This creates a ghost Goods Out Note (GON) for the warehouse team, disappoints the customer awaiting collection, and requires manual intervention from the CX and operations teams. It also means the retail store's floor stock is not depleted correctly in Brightpearl, creating a risk of overselling that specific item.
Prevention / Action: The integration's order processing logic must map Lightspeed's retail outlets to the corresponding inventory locations within Brightpearl. When a Sales Order is created, the integration must check the fulfilment type. If it is a Click and Collect order, stock must only be allocated from the specified store's location in Brightpearl, not the default e-commerce warehouse.
Disconnected daily sales and payment reconciliation
Operational impact: Lightspeed's end-of-day register closures and payout summaries do not naturally align with the individual Sales Orders posted into Brightpearl. The finance team is left with a single bank deposit from Lightspeed but no simple way to match it against hundreds or thousands of separate transactions in Brightpearl. This turns daily reconciliation and the month-end close into a time-consuming manual exercise.
Prevention / Action: Align the integration's financial postings with the operational process. Instead of only syncing individual orders, the integration should generate a daily sales summary journal in Brightpearl that matches the format of Lightspeed's payout report, including breakdowns by payment type. This allows the finance team to reconcile the bank deposit from Lightspeed directly against a single corresponding journal entry in Brightpearl.
Product variant and matrix sync errors
Operational impact: Lightspeed organises variants (e.g. size or colour) into a 'matrix' parent product, whereas Brightpearl manages these as individual SKUs. If this relationship is not managed correctly, updates or new variants created in Brightpearl fail to appear on the retail POS. This leads to an inconsistent catalogue, lost sales opportunities, and forces the merchandising team to spend time manually correcting data in both systems.
Prevention / Action: Establish Brightpearl as the single source-of-truth for all product and variant creation. The integration logic must be designed to correctly map new Brightpearl SKUs to the appropriate parent matrix item in Lightspeed. All product updates should follow a clear sequence, pushing from Brightpearl to Lightspeed, with robust monitoring and exception handling for any items that fail the sync.
Unlinked returns and sales credits
Operational impact: A return processed in a Lightspeed retail store fails to create a corresponding, linked Sales Credit in Brightpearl. This means the returned item is not officially booked back into the correct Brightpearl inventory location, leaving stock levels inaccurate and visible stock unavailable for sale. For the finance team, it creates reconciliation gaps where cash refunds or credit memos exist in the payment system but have no corresponding accounting entry in the ERP.
Prevention / Action: The integration's returns logic must be able to retrieve the original Lightspeed transaction details when a return is processed. Using this data, it should locate the original Sales Order in Brightpearl and generate a linked Sales Credit against it. This sequence ensures inventory is accurately restocked and provides the finance team with a clear, auditable trail from the original sale to the final credit.
Frequently asked questions
Which system should own product creation and pricing? Brightpearl or Lightspeed?
For a reliable single source of truth, Brightpearl should act as the master record for your product catalogue. New Item records and price lists are created and managed in Brightpearl, then synced to Lightspeed. This ensures that essential product data, from SKUs to pricing, is consistent across your retail operations and your central ERP.
We're opening a new store. Can the integration prevent us from selling the same item in-store and online at the same time?
Yes, this is a primary function of the integration. Your total inventory picture lives in Brightpearl, which syncs available stock levels to both Lightspeed and your ecommerce channels. When an item sells in a Lightspeed-powered store, the sale is posted back to Brightpearl, which then updates the central inventory and pushes the new, lower stock level out to all other sales channels, preventing overselling.
How do returns in Lightspeed get reflected in Brightpearl's accounts?
A return processed in Lightspeed needs to generate a corresponding Sales Credit in Brightpearl to ensure your accounts are accurate. The integration can automate this, but a common failure occurs if the original sales order is not fully invoiced in Brightpearl. This blocks the creation of the Sales Credit, forcing the finance team to perform a manual reconciliation.
What happens if we 'archive' a product in Lightspeed to hide it from the POS?
Archiving a product in Lightspeed can break the stock sync if the item remains active in Brightpearl, which is the inventory master. Brightpearl will continue attempting to send stock updates for the SKU, but these updates will fail because the Lightspeed product is no longer active. This results in a stock discrepancy between your ERP and your store, requiring manual investigation to fix.
How does the integration handle product variants like size and colour?
Lightspeed uses a strict parent-child structure for products with variants, known as matrices. For the integration to work correctly, the product structure in Brightpearl must be configured to map perfectly to this matrix logic. If a variant's attributes (like 'Colour') are mismatched between the two systems, it will cause the product sync to fail for that item.