Fulfil and ZigZag
Integration Agency & Consultants
Managing returns at scale often breaks when the financial reconciliation can no longer keep pace with physical warehouse receipts. As volume increases, the lag between a customer scanning a return in ZigZag and the staff receiving it in Fulfil creates inventory gaps and manual workarounds for finance. This integration ensures that every return event triggers the correct accounting and stock adjustments in Fulfil. We focus on removing the reconciliation debt that occurs when returns are processed in isolation, turning a high-volume burden into a controlled, auditable operation.
Auditing returns workflows and ERP logic
We connect your Fulfil and ZigZag integration swiftly, ensuring your ERP and Returns processes work together efficiently. Our consulting services are invaluable, with our system audit uncovering issues in your Fulfil and ZigZag integrations, ERP, and Returns workflows. This enables our consultants and your team to take decisive action, helping your technology ecosystem run smoothly and efficiently. With our expertise, you can deliver a great customer experience and keep your operations optimised for growth.
Solution Design
Our design for Fulfil and ZigZag prioritises financial integrity by making Fulfil the source of truth for inventory and returns reconciliation. We typically sequence the flow so that returns data from ZigZag triggers credit notes or warehouse receipts in Fulfil after a defined status change. A key trade-off we manage involves the timing of stock availability. While immediate updates provide visibility, we often advise a buffered sync to ensure items pass inspection before being marked as available to sell. This design ensures your finance team closes month-end with reconciled figures and operations work from validated stock levels. The result is a returns workflow that protects your margins instead of creating a reconciliation backlog.
Mapping line items for inventory integrity
The integration ensures data flows from ZigZag into Fulfil to automate inventory adjustments and financial credit notes. Fulfil remains the source of truth for stock levels and accounting. When a return is processed in ZigZag, the integration triggers a corresponding record in Fulfil, provided the original customer shipment has reached the required status. We map specific data points to ensure ZigZag validates returns against actual shipped items. Monitoring at the line-item level prevents orphaned records and manages the complexity of returns for orders split across multiple shipments. This sequencing preserves financial trust and operational data integrity.
Technical orchestration and scalable data sync
Cogent2 leverages IPaaS to streamline integration processes for Fulfil and ZigZag, enhancing data flow and connectivity. Benefits include reduced integration complexity, faster deployment, improved scalability, and seamless data synchronization across platforms, leading to increased operational efficiency and better client service.
Surfacing exceptions before they reach finance
Standard dashboards often fail to show the 'missing middle' of returns: the gap between a courier scan in ZigZag and the financial reconciliation in Fulfil. Our approach provides visibility into these operational exceptions, surfacing items that are stuck in transit or failed to post to the ERP. Instead of just seeing that a return happened, you see why a credit note failed to generate or why stock levels did not update. This early detection prevents month-end surprises where finance is forced to hunt for missing stock or unexplained customer credits.
Defining daily checks and operational ownership
Handover focuses on how your finance, operations, and CX teams own the returns lifecycle. We define clear ownership: CX manages the ZigZag customer interface, operations handles the physical receipt and stock adjustment in Fulfil, and finance reconciles the resulting credits. Your team learns to monitor for specific risks, such as returns initiated in ZigZag for items that Fulfil has not yet marked as shipped. Documentation is strictly operational, detailing daily checks and exception handling. Rather than a technical manual, this is an operational reference designed for the people running the business, ensuring staff can resolve sync issues and maintain inventory accuracy independently.
Active monitoring of data health post-launch
Support at Cogent means taking ongoing ownership of your integration's operational health. We monitor the Fulfil and ZigZag sync for more than just uptime; we look for the exceptions that disrupt your warehouse and finance teams. Our team identifies and resolves data mismatches before they become customer service issues. We provide a clear escalation path and regular reviews to ensure the integration continues to support your operating model as your return volumes evolve.
Common failures
Mismatched refund and credit values
Operational impact: When a refund is processed in ZigZag, the corresponding credit memo in Fulfil fails to account for original order discounts, return fees, or complex promotions. The finance team is then forced to spend significant time manually reconciling customer accounts and payout reports against Fulfil's general ledger. At scale, this leads to inaccurate liability reporting and eroded trust in financial data.
Prevention / Action: The integration must be designed so that Fulfil is the definitive source for all financial calculations. Logic should fetch the original Sales Order from Fulfil at the start of the return process. All credit calculations must happen against Fulfil's data, ensuring any adjustments are correctly applied before the final credit memo is created and posted.
Inventory delays from un-synced returns
Operational impact: A return is physically received and processed by the ZigZag workflow, but the integration fails to post the corresponding stock update to Fulfil in a timely manner. This creates a lag where sellable inventory sits in the warehouse but is not available in Fulfil's stock record. This latency reduces available inventory for sale, impacting revenue and requiring the fulfilment team to manage exceptions manually.
Prevention / Action: Design the process to ensure return statuses in ZigZag are mapped to discrete inventory movements in Fulfil. When ZigZag confirms an item is inspected and ready for resale, the integration should trigger a stock adjustment or item receipt in Fulfil immediately. The system should have robust queue management and retry logic for these updates, with monitoring to flag any return that has been physically processed but not yet updated in Fulfil's inventory.
Return processing fails for inactive SKUs
Operational impact: A customer returns a product that has since been archived or made inactive in Fulfil's item master database. ZigZag attempts to process the return, but the integration point with Fulfil rejects the update because the SKU is not recognised as active. The physical item is now in the warehouse, but cannot be booked in, creating a discrepancy between physical stock and the inventory record in Fulfil until a merchandising or operations team member manually intervenes.
Prevention / Action: The integration's logic must include a validation step. Before attempting to post a return transaction, the system should first check if the relevant SKU is active and exists in Fulfil. If the SKU is not found or is inactive, the transaction should be routed to an exception queue and a notification sent to the appropriate team to resolve the master data issue before the sync is retried.
Frequently asked questions
If ZigZag says an item is returned but Fulfil shows it as sold, which system is the source of truth?
In a typical operating model, Fulfil remains the central source of truth for all inventory and financial records. ZigZag manages the returns workflow, but the integration ensures that once ZigZag processes a return, it creates the corresponding credit and stock adjustment in Fulfil. This prevents discrepancies and ensures your stock levels in Fulfil are always accurate for order-to-cash processes.
Why can't my team just process returns manually in Fulfil when our volume is low?
Manual processing works at low volumes but creates hidden operational costs as you scale. A delay in updating a return in Fulfil means the SKU is not restocked, risking a lost sale and impacting your stock sync. It also forces the finance team to manually create credit memos from customer records, which can cause errors during the month-end close.
What happens if a SKU for a returned item in ZigZag doesn't match an item record in Fulfil?
This is a common failure point that causes inventory-related losses. If ZigZag processes a return for a SKU that is inactive or does not exist in the Fulfil item record, the stock adjustment will fail. This results in physical stock being in the warehouse but invisible to Fulfil, leading to inaccurate inventory levels and potential write-offs.
How does the integration handle return fees from ZigZag that aren't inventory items in Fulfil?
This is critical for accurate financial reconciliation. The integration must be configured to map non-inventory charges from ZigZag, such as a 'Return Shipping Fee', to specific general ledger accounts in Fulfil. Without this, the automated credit memo will fail, forcing your finance team to make manual journal entries to reconcile the customer's refund.
We use different warehouses for new stock and returns. How does this work?
To maintain accurate, multi-location inventory, the integration maps the 'Warehouse Code' provided by ZigZag to the correct 'Location Code' within Fulfil. If this mapping is not established, Fulfil could restock a returned item into your main fulfilment centre's inventory pool by default. This error disrupts stock sync processes and can lead to incorrect stock availability on your sales channels.