ZigZag and Lightspeed
Integration Agency & Consultants
Returns management often creates mistrust in inventory data. We use AI-powered integration delivery, guided by experienced operators, to connect ZigZag with Lightspeed properly. As returns are processed, inventory levels update automatically, giving teams confidence that the stock figures they see are accurate and ready for resale.
Auditing returns workflows and POS data
We connect your ZigZag and Lightspeed integrations quickly, ensuring your Returns and POS systems work together efficiently. Our consulting services are invaluable, with our system audit providing a thorough review of your tech stack—including ZigZag, Lightspeed, Returns, and POS—pinpointing inefficiencies and integration gaps. This enables our consultants and your team to take decisive action, helping your technology ecosystem run smoothly and efficiently, so you can deliver an excellent experience to your customers.
Solution Design
We design ZigZag and Lightspeed integrations with a clear inventory hierarchy. In typical setups, Lightspeed acts as the primary source of truth for stock levels and product SKUs. ZigZag manages the logistics of the return event. A core design decision involves the timing of inventory restocks. We usually sequence the data flow so inventory updates in Lightspeed once a return reaches a confirmed disposition status. This prevents phantom stock from appearing before it is saleable. A common trade-off is a slight lag in intra-day availability, which is often preferred over the risk of overselling unverified returns. This approach ensures finance can reconcile settled refunds against POS transactions while operations teams maintain a clean view of sellable inventory across locations.
Mapping SKU data and disposition statuses
This integration connects ZigZag's return logistics with Lightspeed's inventory and POS management. When a return is processed, disposition data flows into Lightspeed to update stock levels based on whether an item is being restocked or scrapped. Refund statuses are synchronised to keep financial records aligned with physical stock movements. The process relies on consistent SKU data across both systems to prevent inventory drift. Operational monitoring surfaces issues such as missing SKU mappings or sync interruptions before they impact reconciliation.
Governing data flow on secure middleware
Leveraging IPaaS with ISO 27001 and SOC 2 and above security accreditations enables secure, efficient integration of ZigZag Returns and Lightspeed POS. ZigZag Returns and Lightspeed POS benefit from automated data flows, reducing manual errors and supporting rapid, secure connections. IPaaS platforms simplify complex integrations, ensure compliance, and provide a centralised, scalable solution for managing Returns and POS data, making integration faster and more reliable for both ZigZag and Lightspeed.
Surfacing discrepancies between warehouse and POS
Standard dashboards often fail to highlight the discrepancies between a return being received in the warehouse and the inventory being updated in Lightspeed. Disconnects in status updates can lead to inventory drift that only becomes visible during physical stock takes. We focus on surfacing these exceptions early, identifying where a return process has stalled or where a refund does not align with a stock adjustment. This visibility ensures that operational issues are resolved before they impact financial reconciliation.
Workflows for finance and operations teams
Adopting the ZigZag and Lightspeed operating model requires clear ownership across finance, operations and CX teams. We hand over a system where CX typically manages return exceptions, while finance handles the reconciliation between ZigZag refund data and Lightspeed sales records. Your operations team monitors the flow of restocked items to ensure Lightspeed inventory remains accurate. Training covers how to read status alerts and who is responsible for resolving specific data exceptions. We provide operational documentation focused on daily and monthly workflows rather than technical reference. This ensures your team can manage the return lifecycle, keeping financial and stock records in sync as part of their standard routine.
Monitoring sync health and data exceptions
Support focuses on maintaining the reliability of the connection between systems. We monitor the integration for data mismatches or sync interruptions that could lead to inventory discrepancies. When exceptions occur, they are surfaced and addressed before they impact customer service or financial reporting. Our goal is to ensure the return-to-restock process remains automated and accurate as your business scales.
Common failures
Delayed or incorrect restock of returned items.
Operational impact: ZigZag processes a return and dispositions an item for restock, but the update to Lightspeed fails or is delayed. This results in saleable inventory being physically present in the warehouse but unavailable for sale in Lightspeed, depressing revenue. The customer service team faces queries they cannot answer, and finance teams find discrepancies between physical stock counts and the inventory value in the ledger.
Prevention / Action: The integration logic must treat the inventory update in Lightspeed as a critical, high-priority transaction. Design a queueing system for inventory webhooks from ZigZag, with automated retries and alerts for persistent failures. A clear process is needed where ZigZag's disposition decision triggers an immediate update that Lightspeed must accept, with any discrepancies flagged for manual review by an operations team.
Mismatched refund and sales order data.
Operational impact: A refund processed in ZigZag fails to link correctly to the original Lightspeed Sales Order, particularly for partial returns. This leaves the finance team unable to reconcile daily payouts and refund journals because the refunded amount does not match a clear transaction. The result is significant manual labour during the month-end close and potential inaccuracies in financial reporting.
Prevention / Action: Ensure the integration maps ZigZag's refund record directly to the corresponding Lightspeed Sales Order ID. The integration must handle cases where Lightspeed generates new transaction IDs for returns, logging this for traceability. Automate a daily reconciliation report comparing ZigZag refund logs against Lightspeed's transaction records to flag exceptions for the finance team.
Product master data misalignment.
Operational impact: A product matrix (e.g. size or colour variants) is updated in Lightspeed, but this change does not synchronise to ZigZag. When a customer returns a newly created SKU, ZigZag cannot recognise it, forcing a manual exception process in the warehouse. This delays the return, requires manual intervention from the operations team, and prevents the SKU from being correctly logged and restocked in Lightspeed.
Prevention / Action: Establish Lightspeed as the definitive master for all product SKUs and their attributes. Implement a process where any creation or update to a product in Lightspeed triggers an immediate, corresponding update to the product catalogue in ZigZag. This synchronisation process requires robust monitoring to flag any failed product updates for immediate review by the merchandising or ecommerce team.
Inability to process returns against the correct warehouse location.
Operational impact: ZigZag processes a return designated for a specific warehouse or stock location, but this location data is not correctly passed to or recognised by Lightspeed. The returned units are then added to a default or incorrect inventory location within Lightspeed's records. This creates a mismatch that confuses fulfilment logic, potentially leading to failed dispatches or requiring manual inventory adjustments by the warehouse operations team to make the stock available.
Prevention / Action: The integration must include a strict mapping between ZigZag's 'Warehouse Code' and Lightspeed's 'Location Code' or equivalent field. Before processing a restock, the integration logic should validate that the location from ZigZag exists and is active in Lightspeed. Any mismatches must be blocked and flagged in an exception report for the operations team to resolve, preventing inventory from being checked into a black hole.
Frequently asked questions
How does the integration handle returns for products with variants like size and colour?
Lightspeed uses a strict parent-child structure for its matrix items, so each variant has a unique SKU. The integration must correctly map the SKU from the ZigZag return to the exact child SKU in Lightspeed. A mismatch can result in returned stock being unavailable for sale because the inventory level for that specific variant is not correctly updated.
Our finance team is worried about reconciliation. How does the integration handle partial returns?
This is a common concern because Lightspeed can issue a new transaction ID for partial returns, which is separate from the original sales order. The integration must be designed to link the ZigZag refund data to both the original sale and this new return transaction. Without this, the finance team might see what looks like an unconnected refund, leading to manual investigation during the month-end close process.
When ZigZag marks a return as 'restocked', is Lightspeed's inventory updated automatically?
Yes, this is a primary function of a correctly configured integration. Once a return is processed and ZigZag records the item's disposition as 'restock', it should trigger an inventory level adjustment for the corresponding SKU in Lightspeed. This ensures accurate stock levels are available for repurchase and prevents selling items that are physically in the warehouse but not yet reflected in the point-of-sale system.
What happens if we discontinue a product in Lightspeed? Will ZigZag know not to accept a return for it?
Typically, deleting a product record in Lightspeed does not automatically block a return in ZigZag, which initiates the process based on original sales order data. This can lead to operational problems, for instance, accepting returns for SKUs you no longer stock. The correct process involves managing the product lifecycle across both systems, such as updating a flag on the item record to make it non-returnable before it is deleted from Lightspeed.