SnapFulfil WMS and ERP
Integration Agency & Consultants
Intelligent Consulting
Detailed Solution Design
Smooth Integration
Visibility
Training
BigCommerce
Common failures
Inventory drift from snapshot updates
Operational impact: When the ERP relies on periodic inventory snapshots from SnapFulfil without reconciling transactional data, stock levels inevitably diverge. This leads to overselling on high-velocity SKUs and inaccurate safety stock calculations. The finance team is then forced to manually reconcile physical counts against ERP records, delaying the month-end close.
Prevention / Action: The integration's design must treat SnapFulfil as the definitive source of truth for physical stock counts, not just a reference. A resilient sync process will use event-driven updates for stock movements (e.g. goods in, adjustments, picks) rather than relying only on a scheduled full snapshot. This ensures the ERP's 'available to sell' figure accurately reflects warehouse reality.
Partial shipment desynchronisation
Operational impact: SnapFulfil correctly processes a partial shipment, but the confirmation message fails to update the correct Sales Order lines in the ERP. This leaves the order in a 'partially fulfilled' state indefinitely, blocking automated invoicing and creating confusion for customer service teams handling queries. It also misrepresents liabilities and fulfilment status in financial reporting.
Prevention / Action: The integration must be designed to map SnapFulfil's despatch data back to the specific ERP Sales Order Line ID. This ensures each line item can be independently fulfilled and invoiced. Implement exception handling to flag orders that remain in a partially fulfilled state beyond a defined business rule, ensuring they are reviewed manually.
Unhandled warehouse exceptions
Operational impact: A 'short pick' occurs in the warehouse due to a misplaced or damaged SKU, and is recorded in SnapFulfil. If this warehouse-level exception does not trigger a corresponding hold or review status on the Sales Order in the ERP, the order remains stuck. The CX team cannot see the problem, the customer is not informed, and the order-to-cash cycle is stalled.
Prevention / Action: Map every SnapFulfil exception code (e.g. 'short pick', 'damaged in pick') to a specific, actionable status in the ERP. The integration should place the affected Sales Order into an exception queue for review by the operations or CX team. This ensures that warehouse realities are visible and can be actioned inside the core commercial system.
Master data mismatch
Operational impact: Inconsistent master data, such as different Unit of Measure (UoM) conventions or SKU formatting between the ERP and SnapFulfil, causes persistent transaction failures. This typically affects stock adjustments and shipment confirmations, creating daily reconciliation work for operations teams and undermining the integrity of inventory data used by finance.
Prevention / Action: Enforce a strict source-of-truth policy, where one system (typically the ERP) owns the creation and maintenance of master product data. The integration layer should include validation logic to reject or flag any data that does not conform to agreed standards before it is passed to the other system. Regularly scheduled audits can help catch discrepancies before they impact operations.
Frequently asked questions
How do you reconcile SnapFulfil's inventory levels with our ERP's financial stock records?
SnapFulfil is the source of truth for physical stock quantity, while the ERP holds the financial value. A common failure is relying on a single daily snapshot from SnapFulfil to update the ERP, which can miss transactions and cause discrepancies. A robust integration uses event-driven updates for every stock movement (like goods received, adjustments, and shipments) and a separate periodic reconciliation to catch any drift, preventing major write-offs during month-end close.
What happens if an order is cancelled in the ERP just before SnapFulfil ships it?
This is a frequent timing issue that requires a specific control in the integration logic. If SnapFulfil sends a shipment confirmation for a Sales Order that has just been voided in the ERP, you risk shipping products that cannot be invoiced. The integration must perform a final status check with the ERP immediately before confirming dispatch, or the ERP must be configured to reject a shipment update against a cancelled order, preventing a complex manual returns and credit process.
How are stock discrepancies found during picking, like 'short picks' in SnapFulfil, handled by the ERP?
A 'short pick' event in SnapFulfil signifies a mismatch between system stock and warehouse reality. This event must immediately create a stock adjustment in the ERP, not just in the WMS, to ensure the central item record is accurate. If this sync fails, the ERP may try to allocate that 'ghost' stock to another Sales Order, causing another fulfilment failure and an inaccurate stock valuation for the finance team.
How does the integration handle partial shipments to ensure our ERP tracks them correctly?
When SnapFulfil processes a partial shipment, it must send the specific ERP 'Line ID' or 'LineNum' for each fulfilled item, not just the parent Order ID. Without this line-level detail, the ERP cannot correctly close the fulfilled lines on the Sales Order, leaving them open and creating errors in backorder reporting. This leads to inaccurate stock demand and requires manual correction by the operations or finance teams before invoicing.
How are kit or bundle SKUs from our ERP translated for fulfilment in SnapFulfil?
An ERP often manages a 'bundle' as a single virtual SKU on the Sales Order, but SnapFulfil needs the individual component SKUs to manage the picking process. A key integration task is to 'de-kit' the order, breaking the bundle SKU down into its constituent item records before sending it to SnapFulfil. A failure to map these correctly means any order containing a bundle will fail to sync, halting the order-to-cash process until it's fixed manually.