Fulfil and Centra
Integration Agency & Consultants
Cogent2’s AI-powered integration delivery and experienced operators connect Centra with Fulfil. We often see brands struggle when order volume makes manual work between these systems unreliable, leading to fulfilment errors. A properly built integration provides a single source of truth for orders and inventory, improving shipment times and financial accuracy across the business.
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 creates a structured path for orders from Centra to Fulfil, where Fulfil serves as the system of record for fulfilment and inventory. Orders typically post to Fulfil once they reach a defined status in Centra, ensuring valid transactions reach the warehouse queue. We map SKUs and variations to ensure data integrity across both systems, preventing orphan items during the sync. As fulfilment updates occur in Fulfil, status changes and tracking numbers flow back to Centra to trigger customer notifications. The integration layer monitors these events to identify failed syncs or SKU mismatches before they impact the customer experience.
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: Incorrect stock levels in Centra, caused by delays in receiving updates from Fulfil, lead to overselling. This creates a poor customer experience through cancelled orders and increases the workload for CX teams handling complaints. Operationally, it complicates fulfilment runs with exceptions and back-orders instead of clean pick lists, eroding trust in the live site inventory.
Prevention / Action: Design the integration to use event-driven updates (webhooks) from Fulfil wherever possible, rather than relying on scheduled polling. This ensures that changes to stock levels in Fulfil, such as goods receipts or adjustments, are pushed to Centra in near real-time. The integration logic must correctly interpret Fulfil's 'available-to-sell' quantity, accounting for reserved stock and buffers, to ensure Centra has the most accurate view.
Incomplete shipment data synchronisation
Operational impact: An order is dispatched in Fulfil, but the tracking number and carrier details fail to update the order in Centra. This prevents Centra from triggering 'order shipped' notifications, leading to a spike in 'Where Is My Order?' (WISMO) queries for customer service teams. It can also prevent orders from being marked as complete, affecting financial reporting and performance analytics.
Prevention / Action: The integration must map all required fields for a shipment update, including carrier name strings, service levels, and tracking numbers, between Fulfil and Centra. The process should be triggered by the creation of an Item Fulfilment or equivalent dispatch record in Fulfil. Implement a monitoring and exception handling queue for any updates that Centra fails to acknowledge, allowing for automated retries and a clear process for manual intervention by an operations team if necessary.
Mismatched order and financial values
Operational impact: Discrepancies in how each system calculates taxes, tiered discounts, or shipping charges cause mismatched totals between a Centra order and the resulting Sales Order in Fulfil. This creates significant manual work for the finance team, who must perform daily checks and adjustments to reconcile revenue figures. At month-end, these small discrepancies accumulate into a major data integrity problem that delays the financial close.
Prevention / Action: Define Centra as the source of truth for all order values at the point of transaction. The integration logic must be designed to carry over all financial values (including discounts and taxes) as final, overriding any recalculations within Fulfil. Before go-live, test extensively with complex orders, including multiple promotion types and cross-border transactions, to ensure the Sales Order created in Fulfil perfectly mirrors the Centra order's financial breakdown.
Delayed or failed refund and return processing
Operational impact: A refund is processed in Centra, but the corresponding credit memo is not created or applied correctly in Fulfil. This breaks the financial audit trail, as payment gateway settlements will not match the Fulfil ledger. Furthermore, if the returned stock is not correctly processed back into Fulfil's inventory records, it remains unavailable for sale, leading to missed revenue opportunities.
Prevention / Action: The returns process requires synchronisation in two directions: financial and inventory. When a return is processed in Centra, it should trigger the creation of a corresponding credit memo in Fulfil against the original Sales Order. A separate process must be defined for the physical inventory, ensuring that a stock adjustment is only made in Fulfil after the warehouse confirms receipt and inspection of the returned goods.
Frequently asked questions
How does the integration prevent overselling during high-volume sales?
The integration establishes Fulfil as the single source of truth for inventory, ensuring stock levels are accurate. When an order is placed in Centra, inventory is allocated in Fulfil, and the updated stock level is immediately synchronised back. This closed-loop process means Centra's storefront always displays an accurate available-to-sell quantity, preventing overselling even during peak demand.
We use Centra's 'Markets' for different regions. How does the integration handle this?
This is a critical part of the setup, as each Centra 'Market' or 'Store' ID must be mapped to a corresponding 'Facility' or 'Business Unit' in Fulfil. If this mapping is missing or incorrect, it is a common failure where order synchronisation stops. This would cause orders to require manual correction before they can be released for fulfilment.
How does this integration help our finance team with reconciliation?
The integration automates the order-to-cash process by posting all order and payment data from Centra directly into Fulfil. This creates all the required transactions, ensuring revenue from Centra is accurately reflected in Fulfil's financial records. Your finance team can then perform their reconciliation within Fulfil, eliminating the manual effort of exporting and matching sales data, which is a common source of delays at month-end.
What happens if an order fails to sync from Centra to Fulfil?
While the goal is full automation, sync failures can occur, typically due to data mismatches. For instance, if a new SKU is sold on Centra before it has been created in the Fulfil item master, the order will fail to post. The integration provides visibility of these exceptions, allowing an operator to correct the data in the source system and re-process the order without manual data entry.