Microsoft Dynamics Business Central and ZigZag
Integration Agency & Consultants
Returns reconciliation usually becomes a financial risk when the volume of unprocessed returns creates a gap between your physical warehouse and the general ledger in Business Central. At scale, manual entry of returns data into Microsoft Dynamics leads to reconciliation debt and inaccurate available-to-sell stock levels. This integration connects ZigZag directly with Business Central to ensure returned goods are correctly categorised, financials are reconciled, and inventory updates follow physical inspections without manual intervention.
Auditing returns workflows and ERP alignment
We connect Microsoft Dynamics Business Central and ZigZag quickly, ensuring your ERP and Returns processes work together efficiently. Our consulting services, including our system audit, help uncover issues in your Microsoft Dynamics Business Central and ZigZag integrations, empowering your team to take action. By focusing on ERP and Returns workflows, our audit enables both our consultants and your staff to keep your tech ecosystem running smoothly, so you can deliver a great customer experience.
Solution Design
Our consultants work side-by-side with you to architect your ERP ecosystem, putting you in control of Microsoft Dynamics Business Central and ZigZag. We design a blueprint that ensures your ERP and Returns processes are future-ready, with Microsoft Dynamics Business Central and ZigZag integration at the core. Well-planned Returns integrations save time and energy, laying the groundwork for sustainable growth and giving you the confidence to scale with precision.
Mapping return triggers to ledger entries
Data integrity between Microsoft Dynamics Business Central and ZigZag is defined by how returns are sequenced and where the financial accountability sits. In a standard configuration, once a return is initiated in the ZigZag portal, the system requires an exact match on the Product SKU or Variant ID to identify the original sale. Any mismatch at this stage typically prevents the return from sync-ing, which can leave customer service to manually reconcile the record before the item reaches the warehouse.
The integration commonly triggers a Sales Return Order in Business Central on a defined schedule or trigger, such as when a return label is generated or a carrier scan occurs. If the 'Restock' action is triggered in ZigZag before the inventory is physically received and inspected, it can create phantom stock levels in Business Central, leading to potential overselling on connected channels.
For teams managing high volumes, the source of truth for the refund must be clearly defined. When ZigZag triggers a refund, the finance team must ensure Business Central is configured to generate the corresponding Credit Memo. Without this synchronisation, the general ledger will drift from the actual payout, requiring manual month-end adjustments to correct figures. Ensuring the 'Restocking Location ID' in ZigZag maps directly to the correct 'Location Code' in Business Central is essential to maintain a clean audit trail from the warehouse floor to the balance sheet.
Orchestrating secure data flows via IPaaS
Leveraging IPaaS with ISO 27001 and SOC 2 and above security accreditations enables secure, efficient integration between Microsoft Dynamics Business Central, ZigZag, ERP, and Returns systems. This approach simplifies connecting Microsoft Dynamics Business Central and ZigZag, supporting ERP and Returns processes while ensuring data protection. IPaaS platforms reduce manual effort, improve reliability, and maintain compliance, making integration between these platforms straightforward and secure.
Monitoring data drift and sync exceptions
Visibility is more than a status dashboard; it is the ability to track a return from the ZigZag scan to the final inventory adjustment in Microsoft Dynamics Business Central. When these systems are not perfectly aligned, issues like SKU mismatches or unmapped restocking locations cause returns to stall.
Typically, these failures remain hidden until a customer asks about a refund or finance identifies an inventory discrepancy. In many implementations, the gap exists because a ZigZag event fails to trigger the corresponding Credit Memo or stock update in Business Central. We prioritise surfacing these exceptions as they happen, ensuring that data drift is caught before it impacts your month-end accounts or your customer service response times.
Operational handover for finance and operations
Cogent2’s training equips your team to confidently manage your ERP and tech stack, supporting your brand’s growth ambitions with Microsoft Dynamics Business Central and ZigZag. You’ll gain practical skills to optimise ERP processes, handle Returns efficiently, and leverage Microsoft Dynamics Business Central. ZigZag integration ensures Returns are managed smoothly, aligning your systems for scalable success.
Maintaining inventory integrity and governance post-launch
Microsoft Dynamics Business Central and ZigZag are supported for both ERP and Returns, ensuring business continuity and peace of mind. With on-hand technical knowledge, you receive expert support for Microsoft Dynamics Business Central and ZigZag, covering ERP and Returns processes. This guarantees your operations remain resilient, with rapid assistance and ongoing guidance, so you can focus on your business while knowing your systems are in safe hands.
Common failures
Mismatched return disposition and stock location.
Operational impact: When ZigZag grades a return as 'resellable' but the integration fails to place it in the correct Business Central inventory location, the result is phantom stock. This leads to overselling, failed Sales Orders for items that are not truly available, and costly manual stock takes. The finance team also contends with an inaccurate inventory valuation on the balance sheet until a correction is posted.
Prevention / Action: The integration's logic must include a clear mapping matrix between ZigZag's return disposition codes ('Grade A', 'Grade B', 'Damaged') and the corresponding inventory locations in Business Central. The process design must treat Business Central as the source of truth for all inventory locations. Exception handling should route any unmapped dispositions to a queue for manual review by the operations team to prevent incorrect data from being posted automatically.
Delayed or missing Sales Credit Memos.
Operational impact: If a return is processed and refunded via ZigZag without a corresponding Sales Credit Memo being created and posted in Business Central, the finance team faces significant reconciliation challenges. They will see payments leaving the bank without an associated transaction in the ERP, leading to overstated revenue and VAT liabilities. This creates unnecessary manual work during the month-end close to identify and reconcile these discrepancies.
Prevention / Action: The integration process must ensure a confirmed return and refund action in ZigZag is the definitive trigger for creating a Sales Credit Memo in Business Central. This requires robust sequencing and error handling, where the integration confirms the successful creation of the Credit Memo before considering the returns process complete. A monitoring dashboard should track any orders where this process fails, allowing for prompt intervention.
Incorrect valuation of returned stock.
Operational impact: When returned stock is added back to inventory without the correct valuation, it distorts the cost of goods sold (COGS) and gross margin calculations. For example, if a 'damaged' item is returned to sellable stock at full value, or if a generic cost is used instead of the original cost from the sales transaction. This forces the finance team to perform manual journal adjustments to correct the inventory value and COGS accounts.
Prevention / Action: The integration logic responsible for creating the inventory transaction in Business Central must be designed to retrieve the original item cost from the posted sales invoice. For write-offs, the logic must post the value to a designated 'damaged stock' general ledger account. This ensures that the financial impact of every return is accurately and automatically recorded in the correct accounts from the outset, based on its physical disposition from ZigZag.
Return initiation rejections for valid orders.
Operational impact: Customers attempting to register a return through the ZigZag portal may be blocked if the integration has not yet confirmed the order is 'returnable'. This typically happens when the order data sync is delayed or dependent on a slow downstream process in Business Central. The immediate result is a poor customer experience and an increase in contacts for the CX team, who must then manually verify the order and initiate the return themselves.
Prevention / Action: The operating model must define a clear source of truth for when an order becomes eligible for return, which is typically after the Sales Invoice is successfully posted in Business Central. The integration should only make an order available for return processing in ZigZag once this confirmation is received from BC. This prevents timing issues and ensures the customer-facing portal and the ERP are always aligned on an order's status.
Frequently asked questions
If ZigZag processes a refund, how do we ensure a corresponding Credit Memo is created in Business Central?
A common failure is a refund being processed via ZigZag and Shopify, but no matching Sales Credit Memo appearing in Microsoft Dynamics Business Central. A correctly configured integration listens for refund confirmation from ZigZag and uses it to automatically generate the correct credit memo against the original Sales Order. This avoids hours of manual reconciliation work for the finance team at month-end.
How does the integration handle different return dispositions, like items for resale versus damaged goods?
The integration maps disposition codes from ZigZag to specific actions within Microsoft Dynamics Business Central. An 'A-Grade' return can trigger an inventory adjustment to place the SKU back into sellable stock. A 'damaged' item can be routed to a non-sellable location or trigger a write-off journal entry, ensuring both inventory counts and financial records are accurate.
How does a return processed in ZigZag update our inventory levels in Microsoft Dynamics Business Central?
Once ZigZag determines the status of a returned item, it signals the integration to create an inventory adjustment in Business Central, updating the Item record for that specific SKU. This ensures that restocked goods are immediately reflected in your available inventory. It prevents your finance team from having to manually process returns, which can cause data errors and make your stock levels unreliable.
My returns volume is growing. How does this integration prevent manual reconciliation work in Business Central?
The integration automates the creation of Sales Credit Memos and inventory adjustments in Microsoft Dynamics Business Central based on data from ZigZag. Instead of a finance clerk manually keying in data from a spreadsheet, which is slow and prone to error, the process is triggered automatically when a return is completed. This directly addresses the operational drag and financial risk of manually reconciling high volumes of returns.