NewStore POS and ZigZag
Integration Agency & Consultants
Returns processing usually becomes a bottleneck when NewStore POS sales volume outpaces your ability to manually reconcile stock. At scale, the gap between a parcel arriving at the warehouse and the inventory level updating in the POS creates operational lag that can lead to overselling. This integration connects ZigZag to NewStore, ensuring that return authorisations and inspection results update inventory levels based on defined triggers instead of manual entry.
Auditing data flow and system alignment
We connect your NewStore POS and ZigZag quickly, ensuring your POS and Returns processes work together efficiently. Our consulting services are invaluable, with our system audit services uncovering integration issues between NewStore POS and ZigZag. This enables our consultants and your team to take decisive action, helping your tech ecosystem run smoothly. By addressing inefficiencies in Returns and POS operations, we help you deliver a great customer experience and keep your technology aligned with your business needs.
Solution Design
Designing for NewStore POS and ZigZag requires clear ownership of the returns lifecycle to prevent inventory drift. In many implementations, NewStore remains the master for product SKUs and physical stock levels, while ZigZag acts as the authority for return authorisation and logistics status. We commonly sequence return authorisations as real-time to maintain the customer experience, while batching final stock adjustments to ensure high-volume processing remains stable. A primary trade-off involves the timing of refunds. Validating returns instantly via scanning at a drop-off point prioritises customer satisfaction but requires careful management of restocking records. We build our design around these operational realities, ensuring finance closes the month with verified stock figures while CX maintains visibility of the return journey.
Mapping order data and payment signals
The integration uses NewStore POS as the master of the original transaction, providing the Order ID and SKU data ZigZag requires for validation. The data flow occurs when a return notification in ZigZag triggers the return process in NewStore. To maintain financial trust, NewStore remains the Master of Refund; ZigZag provides the return arrival signal while NewStore handles the actual payment gateway reversal. This prevents the reconciliation debt caused by orphaned transactions or duplicate refunds.
Securing data transfer with accredited middleware
Leveraging IPaaS with ISO 27001 and SOC 2 and above security accreditations ensures secure, efficient integration between NewStore POS and ZigZag, supporting both POS and Returns processes. IPaaS simplifies connecting NewStore POS with ZigZag, reducing manual effort and risk. Benefits include robust data protection, faster deployment, and reliable Returns management, all while meeting strict compliance standards. This approach delivers secure, scalable integration for modern retail operations.
Monitoring the physical to financial gap
Operational visibility requires monitoring the state of a return across both systems, not just a single dashboard. We look for gaps between the warehouse scan in ZigZag and the financial post in NewStore. By surfacing these discrepancies early, we ensure that if a return arrives but the NewStore order record fails to update, the issue is flagged before it requires manual work to resolve during month-end reporting.
Operating manuals for finance and ops
We hand over the NewStore and ZigZag operating model to your finance, ops, and CX teams to ensure they own the post-launch process. Training focuses on daily reconciliation of returns authorised in ZigZag against stock updates in NewStore. Your teams learn to identify exception types, such as when a physical inspection at the warehouse contradicts the digital return status. We provide operational documentation written for the people running the business, not for IT. This manual covers how to interpret alerts from the integration layer and defines clear ownership for resolving inventory discrepancies. Handover is anchored in your specific design decisions rather than generic system features.
Managing sync exceptions and inventory drift
Support means maintaining data health between systems to prevent manual backlogs. We monitor for instances where ZigZag reports a success but the NewStore inventory record has not updated. Our model includes active exception management, identifying when specific order types or shipment configurations cause sync failures and resolving them before they disrupt your warehouse operations or customer service teams.
Common failures
Missing Inventory Re-stock A common failure is processing partial returns in ZigZag without correctly updating the NewStore order state. This creates a mismatch where the POS believes stock is still with the customer, but the physical item is back in the warehouse. This makes available-to-sell figures untrustworthy and complicates inventory planning.
Webhook Sync Failures Failing to trigger the correct 'Return Received' signal in ZigZag to hit the 'Mark as Returned' endpoint in NewStore causes the transaction to remain open in NewStore. The item is physically received, but the financial record is not updated. This prevents the final reconciliation and requires manual investigation by the finance team.
Multi-Shipment Errors When NewStore orders contain split shipments, the return process may fail if it attempts to sync against a single fulfilment ID. Without logic to handle orders shipped in multiple parts, the return record can fail to post to NewStore, forcing operations teams to manually link the return to the correct original shipment.
Frequently asked questions
How do we prevent double-refunding across NewStore and ZigZag?
The integration enforces NewStore as the Master of Refund. ZigZag signals that a return has arrived, but the actual payment reversal is triggered through NewStore. This prevents duplicate transactions by ensuring the refund process is handled by the system that owns the original payment record.
What happens with orders that have split shipments?
In many implementations, the integration must link the ZigZag return to the correct fulfilment record in NewStore. Without this, the return may fail to post or link to the wrong shipment. We design the flow to ensure returns are correctly attributed to the items and shipments they belong to.
Why is my POS inventory still showing stock that was returned?
This is often caused by a failure in the communication between ZigZag and NewStore. If the return signal does not correctly hit the update endpoint in NewStore, the physical item may be back in the warehouse while the digital record shows it is still with the customer.
Can we trigger refunds before the item is inspected?
Yes, this is typically handled by a 'Refund on Scan' trigger. The integration allows the carrier scan in ZigZag to signal NewStore to initiate the refund process, providing a faster experience for the customer while the physical logistics continue in the background.