Fulfil and Centra
Integration Agency & Consultants
At scale, the gap between an order being cleared in Centra and inventory being updated in Fulfil becomes a primary source of overselling. When finance teams can no longer trust the VAT records or stock counts across systems, the manual effort of reconciliation creates significant operational drag. This integration connects Centra and Fulfil to automate order flow and inventory accuracy, ensuring that fulfilment teams work from a single, reliable source of truth while finance maintains clear ownership of the ledger.
Mapping data gaps and system inefficiencies
Cogent2 connects your Fulfil and Centra integrations quickly, supporting both ERP and Ecommerce needs. Our consulting services are invaluable, with our system audit uncovering inefficiencies and integration gaps across Fulfil, Centra, ERP, and Ecommerce platforms. This enables our consultants and your team to take decisive action, ensuring your technology ecosystem operates efficiently. By addressing issues early, we help you deliver a consistently excellent customer experience, keeping your business agile and your systems aligned with your goals.
Solution Design
We design the Fulfil and Centra integration with clear ownership of the order lifecycle. Typically, Centra acts as the source of truth for the order entry, while Fulfil owns the inventory master and final financial record. A primary design decision involves the trade-off between real-time inventory updates and system stability. High-frequency updates can increase API load and fragility, so we often implement a prioritised sync to protect storefront performance during peak trade. Order flow is typically sequenced first to ensure fulfilment can begin, while financial records are often batched to simplify daily reconciliation. This design ensures the ecommerce team works from live storefront data in Centra, while finance maintains accurate records in Fulfil based on verified shipments.
Synchronising SKU hierarchy and fulfilment status
The integration establishes a clear flow for orders to move from Centra into Fulfil for ERP-managed fulfilment. Orders post to Fulfil only once they reach a status that permits fulfilment, ensuring valid transactions reach the warehouse queue. We map SKU variations to Fulfil's product hierarchy to maintain a consistent item master and protect automated purchasing workflows. As picks are confirmed in the warehouse, status updates and tracking numbers flow back to Centra. This reduces operational latency and ensures customer notifications are triggered by actual despatch events. The integration layer monitors these flows to catch SKU mismatches or sync errors before they compound into reconciliation debt.
Orchestrating workflows via secure middleware platforms
Leveraging IPaaS with ISO 27001 and SOC 2 and above security accreditations ensures secure, efficient integration between Fulfil, Centra, ERP, and Ecommerce platforms. This approach simplifies connecting Fulfil and Centra with ERP and Ecommerce systems, automating data flows while maintaining strict security standards. The benefits include reduced manual effort, improved data accuracy, and compliance, making integrations reliable and secure for businesses handling sensitive information.
Surfacing inventory drift and sync errors
Dashboards only tell one side of the story. True visibility requires surfacing the specific data mismatches that cause inventory drift between Fulfil and Centra. Hidden issues, such as failed SKU mappings or currency rounding errors, often compound if only the top-line status is monitored. Our approach uses operational intelligence to detect exceptions early, such as orders that have cleared in Centra but failed to reach Fulfil. By prioritising these errors based on their impact on delivery or finance, your team can resolve bottlenecks before they lead to customer service enquiries or reconciliation gaps.
Practical playbooks for cross-departmental teams
Handover focuses on how finance, operations, and ecommerce teams manage the live Fulfil and Centra connection. We provide an operational playbook that defines where data objects live and who owns each exception type. Finance teams learn to reconcile Centra orders against Fulfil financial postings, while operations teams learn to monitor fulfilment status and inventory sync health. We establish a clear cadence for daily checks and alert responses, ensuring your team knows how to interpret data from the integration layer. This documentation is written as a practical reference for running the business, anchored in the specific design decisions of your setup rather than technical archives.
Managed health monitoring and exception handling
Post-launch support moves from implementation to ongoing operational ownership. We monitor the health of the Fulfil and Centra sync to detect issues like stalled orders or inventory mismatches before they escalate. Our team provides an escalation path for complex data exceptions, ensuring that technical errors do not become permanent manual workarounds for your finance or ops teams. This model ensures the integration continues to align with your evolving business processes, providing the visibility needed to manage high-volume retail without constant firefighting.
Common failures
Inventory latency and overselling
Operational impact: When updates from Fulfil lag, Centra continues to sell stock that no longer exists in the warehouse. This leads to cancelled orders and significant manual work for CX teams. It also complicates fulfilment with back-orders rather than clean pick lists, creating operational drift between the live site and the physical shelf.
Prevention: Fulfil must remain the source of truth for inventory availability. Centra orders with 'Pending' payment status should be filtered to prevent stock allocation to orders that may fail fraud checks. The integration must map Fulfil's 'available-to-sell' quantity, accounting for reservations and buffers, to ensure the storefront remains accurate.
Failed shipment synchronisation
Operational impact: Orders are despatched in Fulfil, but tracking numbers and carrier details fail to reach Centra. This stops 'order shipped' notifications, causing a spike in WISMO queries. If Centra does not receive the signal, the order stays open, creating reconciliation debt as the financial status remains out of step with the physical reality.
Prevention: Centra typically requires complete line-item fulfilment before accepting a tracking update. The integration must map carrier name strings and tracking numbers from the Fulfil despatch record, with automated monitoring to catch and retry failures.
SKU and attribute mapping failures
Operational impact: Inconsistent mapping of Centra's 'Size' and 'Variant' attributes to Fulfil's 'Template' and 'Product' hierarchy causes duplicate SKU creation. This breaks automated purchasing and reporting. Finance teams are then forced to manually reconcile VAT and sales data, creating a financial trust boundary that delays month-end close.
Prevention: Define ownership boundaries early. Centra's line-level tax calculations should be carried into Fulfil without recalculation. Correct mapping of the product hierarchy at the point of sync prevents duplicate SKU generation and ensures inventory accurately reflects the physical items.
Frequently asked questions
How does the integration prevent overselling?
Fulfil is the authoritative source for physical inventory. The integration pushes updated stock levels to Centra on a defined trigger. To protect your stock, orders with 'Pending' payment status are typically filtered out, ensuring Fulfil only allocates inventory to orders that are ready for fulfilment.
How does Centra's 'Market' structure map to Fulfil?
Each Centra 'Market' or 'Store' should be mapped to a corresponding facility or business unit in Fulfil. If these do not match, orders may fail to post. We map these IDs early to ensure orders route to the correct warehouse and use the correct currency.
How does this affect financial reconciliation?
The integration can be configured to carry Centra's line-level tax calculations into Fulfil. This prevents recalculation errors that cause settlement drift. By finalising records in Fulfil based on actual shipments, the finance team can close the month with higher confidence in the data.
What happens with SKU variants and sizes?
To maintain a clean item master, Centra's product attributes are mapped to Fulfil's hierarchy. This prevents the creation of duplicate SKUs and ensures that inventory counts remain accurate across both systems.