Cin7 Core and Lightspeed
Integration Agency & Consultants
This integration usually becomes critical when the gap between the warehouse and the retail till leads to inventory write-offs. We connect Cin7 Core with Lightspeed to resolve the tension between available-to-sell online stock and physical stock on the shelf. This ensures you have a single view of inventory from the central fulfilment centre to each physical site, preventing the manual recount marathons that usually occur when a business expands into new locations or pop-ups.
Defining the inventory master and stock logic
Diagnosis for Cin7 Core and Lightspeed begins by defining the inventory master. We examine the source of truth for stock levels to ensure physical retail shelf stock and central warehouse availability do not contradict each other. Our consultants audit current manual workarounds where staff adjust stock between the till and the warehouse, which often leads to inventory write-offs. We identify whether pricing changes in Lightspeed fail to update the base price in Cin7 Core or if register-specific transfers miss the correct warehouse journal. The integration design is finalised during this discovery phase, deciding on sequencing and batching rules. This upfront work prevents go-live failures and ensures finance and operations agree on one operating model before any technical build begins.
Solution Design
Our design for Cin7 Core and Lightspeed prioritises inventory accuracy across multiple physical sites. We typically designate Cin7 Core as the inventory master and procurement engine, while Lightspeed serves as the retail sales channel. A key design decision involves how to handle 'available to sell' stock. We must manage the tension between stock on the retail shelf and quantities promised to online orders. We often choose to batch daily register closures to simplify financial reconciliation, even though this creates a slight lag in intra-day stock reporting. This trade-off ensures that finance can close the month accurately off Cin7 Core figures while operations trust the physical counts. Every design choice is opinionated and built to reflect how your retail and warehouse teams actually interact.
Connecting the retail register to the ERP
The integration establishes Cin7 Core as the central inventory master, pushing stock levels and product data out to Lightspeed. As sales occur in-store, Lightspeed captures the transaction and pushes daily register closures back to Cin7 Core to update the ledger and reduce stock. To maintain integrity, we map each retail register to a specific location in Cin7 Core, ensuring that a sale in one shop does not incorrectly deduct stock from the central warehouse. We implement validation rules to catch SKU mismatches before they enter the ERP. Early issue detection is built into the flow, monitoring for orphaned sales or failed stock movements so that physical reality and digital records do not drift apart during peak trading periods.
Governing the data layer and sync rules
A controlled integration layer governs the critical data flow between Cin7 Core and Lightspeed. This layer actively manages the movement of sales orders, stock adjustments, and daily register closures. By validating data at the boundary, we catch failure scenarios such as SKU mismatches or dropped stock updates during peak trading before they corrupt your inventory records. Failures are handled through business-rule validation, a defined retry schedule, and full payload logging, with threshold-based alerts sent to the operations team. This infrastructure is built to enterprise-grade security standards, including ISO 27001 and SOC 2. The layer is not a passive pipe but is actively monitored by Cogent consultants and operational intelligence agents to ensure continuous synchronisation between the retail till and the central ERP.
Monitoring data drift and reconciliation gaps
Standard dashboards often miss the subtle data drift that happens between the shop floor and the ERP. Visibility here means detecting when a Lightspeed sale fails to trigger a corresponding stock journal in Cin7 Core, or when a price override at the POS isn't reflected in the gross margin report. Our platform surfaces these discrepancies early, moving beyond simple 'success or failure' alerts to identify reconciliation gaps. When an inventory transfer is initiated in the warehouse but never 'received' in the retail branch, the system flags it as an exception. This allows floor managers and finance teams to resolve hidden issues before they compound into a major stocktake discrepancy or financial reporting error during month-end close.
Operational handover for retail and finance teams
Operational handover ensures retail and finance teams can manage the daily flow between Cin7 Core and Lightspeed. We define what the store managers and operations team own, covering daily register closures, stock transfer validation, and daily inventory sync checks. Training is anchored in the specific design decisions of your setup, showing the team how to read alerts and who owns each exception type, such as a failed stock journal. Documentation is created as an operational reference for the people running the business, not a technical archive for IT. This ensures that when Cogent steps back, your internal teams can confidently manage the system and maintain data integrity across the shop floor and warehouse.
Maintaining sync integrity after go live
Ongoing support focuses on preventing data drift and resolving sync exceptions before they impact store operations. We monitor the movement of orders and inventory between Cin7 Core and Lightspeed, targeting friction points like stock transfers or failed register closures. This oversight ensures that as you add new physical sites, your inventory remains synchronised without increasing manual workload or causing reconciliation gaps at month-end.
Common failures
Inventory latency and overselling
Operational impact: A sale in a Lightspeed retail store fails to update Cin7 Core stock levels with sufficient speed. This makes the same unit available for sale via other channels connected to Cin7 Core, leading to overselling. The fulfilment team receives an impossible Sales Order, the customer service team must cancel and disappoint the customer, and operations teams must perform manual stock reconciliations to correct the ongoing variance.
Prevention / Action: The integration's architecture must prioritise stock-level synchronisation from Lightspeed to Cin7 Core, scheduled at the highest practical frequency the APIs will support. For high-velocity SKUs, a stock buffer can be configured in Cin7 Core to absorb some of the latency risk. A clear operational process must be defined for handling oversell exceptions when they inevitably occur, including how to adjust stock records and communicate with customers.
Incomplete daily sales reconciliation
Operational impact: The end-of-day register closure summary from a Lightspeed terminal fails to generate the corresponding daily sales journal in Cin7 Core. This leaves the finance team unable to reconcile daily takings, payment types, and VAT against bank deposits without manual intervention. Across multiple retail locations, this creates a significant and error-prone workload, delaying the month-end close.
Prevention / Action: Treat the Lightspeed register closure as a critical, auditable event. The integration should use a queue-and-retry mechanism for posting the sales summary to Cin7 Core, protecting the process from transient API failures. An exception handling process should alert the finance team to any closures that repeatedly fail to post, allowing for targeted intervention instead of daily manual checks.
Unrecorded inter-location stock movements
Operational impact: Stock is physically moved from a central warehouse to a specific Lightspeed retail store, but the corresponding warehouse journal or stock transfer is not correctly created and completed in Cin7 Core. This causes a direct discrepancy between physical inventory and the system of record. Retail and fulfilment teams can no longer trust system stock levels, which leads to failed click-and-collect orders and requires time-consuming manual stocktakes to resolve.
Prevention / Action: Establish Cin7 Core as the definitive source of truth for all inventory locations and movements. All stock transfers must be initiated and tracked within Cin7 Core. The integration logic should only update Lightspeed's location-specific inventory counts after the transfer is marked as received in the destination warehouse inside Cin7 Core, ensuring both systems remain synchronised throughout the process.
Mismatched product and pricing data
Operational impact: A retail price is changed in Lightspeed but fails to update the base price in the corresponding Cin7 Core product record, or vice versa. When sales orders are synced, the revenue and margin data in Cin7 Core becomes inaccurate, creating reconciliation work for the finance team. This problem is compounded when managing promotions or price tiers across multiple stores, leading to inconsistent pricing and flawed reporting.
Prevention / Action: Define a single, authoritative source of truth for product pricing, which is typically Cin7 Core in this operating model. Integration logic should be designed to enforce this hierarchy, overwriting price information in the target system (Lightspeed). Implement monitoring to detect and flag any sync failures or SKU-mapping errors, allowing the data or merchandising team to correct issues before they cause significant financial reporting discrepancies.
Frequently asked questions
Which system should be the master for product information?
For most retail operations, Cin7 Core acts as the central inventory master and procurement engine. It should hold foundational data, including the SKU, cost price, and supplier information. Lightspeed functions as the retail sales channel, holding store-specific data like retail price points and local promotions.
How does the integration handle inventory across multiple stores?
Each retail outlet is mapped to a specific stock location in Cin7 Core. When a sale is processed, inventory is drawn down from the correct retail location. This prevents the manual stock adjustments between the warehouse and the till that often lead to inventory write-offs during expansion into new sites or pop-ups.
How do we prevent overselling between in-store and online channels?
The integration establishes Cin7 Core as the single source of truth for inventory. A sale in a Lightspeed store updates the master stock level in Cin7 Core, reducing the available-to-sell count for other channels. This prevents a walk-in customer from buying the last item that has already been promised to a web order.
How are returns handled in Cin7 Core?
Refunds and partial returns initiated in Lightspeed often require specific reconciliation to generate Credit Notes in Cin7 Core. We ensure the workflow captures restock instructions so that returned items aren't physically in the storeroom but missing from the central inventory database.