Centra and Linnworks
Integration Agency & Consultants
Expansion into international markets often makes manual inventory management and order entry between Centra and Linnworks impossible to maintain. At scale, the mismatch between Centra stock pools and Linnworks locations leads to overselling and warehouse friction. We reconcile Centra's architecture with Linnworks SKU mapping to ensure global stock availability is accurate. This integration establishes Linnworks as the engine for inventory truth while Centra captures orders across global storefronts and wholesale channels. This usually becomes painful when the operations team can no longer trust stock levels across multiple currencies and regions.
Scoping your multi channel retail strategy
Integrating Centra and Linnworks enables seamless connection with these systems, enhancing your multi-channel, omnichannel, and unified retail strategy. Utilize Cogent’s expertise to scale efficiently, improving operational performance, tech stack, and training.
Solution Design
Designing the Centra and Linnworks integration requires a clear decision on inventory authority. In many setups, Linnworks acts as the central inventory truth, pushing stock levels to Centra storefronts. We typically sequence order flow first to ensure Centra captures demand while Linnworks handles multi-channel fulfilment and shipping logic. A common trade-off involves the frequency of stock updates. While pushing every change instantly improves accuracy, it can increase system load during peak events. We often advise short-interval updates for non-critical changes to maintain stability. Centra typically manages front-end currency and VAT logic, while Linnworks processes the physical movement. This design ensures finance can reconcile using Centra's commercial data while operations manages daily throughput and carrier selection within Linnworks.
Mapping stock pools and fulfilment triggers
The integration establishes Linnworks as the central engine for inventory and shipping. Orders flow from Centra to Linnworks, carrying currency data and tax details for accurate labelling. We map storefront stock pools to specific Linnworks locations to help ensure availability is accurate across global storefronts. Status updates, including tracking numbers, flow back to Centra once fulfilment is confirmed. To maintain data integrity, we use monitoring that identifies SKU mismatches or tax discrepancies before they affect the shipping queue. This ensures that the commercial record in the storefront matches the physical dispatch in Linnworks.
Orchestrating logic through central middleware platforms
Cogent2 uses IPaaS to seamlessly integrate Centra and Linnworks, enabling efficient data flow and process automation. Benefits include reduced integration complexity, faster deployment, scalability, and enhanced collaboration, allowing businesses to focus on core activities while ensuring reliable and consistent data management across platforms.
Identifying tax discrepancies and sync errors
Basic sync logs are rarely enough to spot the data failures that can occur between complex storefronts and fulfilment engines. Issues often occur during the mapping of tax rates across different regions or the way stock reservations are handled after a cancellation. We provide visibility into these gaps, surfacing errors where an order is stuck or where inventory levels have drifted. This allows your team to catch a mapping error before it causes warehouse delays. By monitoring the behaviour of the data, we help ensure that finance and operations teams are working from the same information.
Practical playbooks for finance and operations
Handover focuses on how operations, finance, and ecommerce teams manage the logic between Centra and Linnworks. Operations teams learn to map Centra stock pools to Linnworks locations to help prevent overselling. Finance teams learn to reconcile global order totals against Linnworks shipping records and VAT outputs. We provide an operational playbook that defines what to check on a regular basis, such as pending orders or SKU mapping errors, and who owns specific issues when a sync fails. Training is anchored in your specific architecture, ensuring the team understands where the data lives and how to act on alerts. Documentation is written as a practical reference for business users, not a technical archive.
Maintaining data integrity after go live
Support for this pair goes beyond fixing broken connections. We monitor the integrity of stock levels and order status updates to find issues before they impact customers. When an issue arises, such as a shipping mapping failure or a tax discrepancy, we provide the context needed to resolve it. Our model is built for brands at scale, providing ongoing oversight of integration behaviour so your internal teams can focus on core tasks rather than troubleshooting data mismatches. We ensure that as your storefronts or warehouse locations change, the integration logic is maintained.
Common failures
Stock pool and location mismatch
Operational impact: If Centra's 'Stock Pools' are not correctly mapped to discrete Linnworks 'Locations', overselling on specific markets is almost certain. This forces the customer service team to cancel Sales Orders, damages customer trust, and requires the fulfilment team to manually adjust stock records. At scale, this constant fire-fighting erodes any confidence in inventory accuracy across the business.
Prevention / Action: The integration's design must include a strict mapping table between Centra Stock Pools and Linnworks Locations, establishing Linnworks as the source of truth for all saleable stock levels. The logic must ensure inventory updates from Linnworks are routed only to the appropriate Centra pool. Implement monitoring to alert operators if a new Stock Pool is created in Centra without being assigned a corresponding Location in the integration configuration.
Mismatched shipping service names
Operational impact: Orders from Centra often fail to process automatically if their 'Shipping Method' string does not exactly match a 'Postal Service' name in Linnworks. This halts orders in the fulfilment queue, forcing manual intervention from the ops team to assign shipping for each affected order. This introduces significant delays to dispatch, risks human error, and creates a major bottleneck as order volumes grow.
Prevention / Action: Define and maintain a rigid mapping of Centra 'Shipping Method' names to Linnworks 'Postal Service' rules within the integration layer. This mapping should be treated as a critical configuration file. The integration must feature exception handling to immediately flag any order containing an unknown shipping method to an operator, preventing it from failing silently inside Linnworks.
Order cancellation race conditions
Operational impact: When a customer cancels an order in Centra, a delay in syncing this instruction to Linnworks can result in the order being fulfilled anyway. This happens if the cancellation message arrives after the warehouse team has already locked or processed the Linnworks order. The result is wasted shipping costs, increased returns processing for the warehouse, and a poor experience for the customer who then has to manage an unwanted delivery.
Prevention / Action: Prioritise cancellation messages from Centra by using a dedicated, high-priority queue for those specific webhooks. The integration logic should attempt to cancel the order in Linnworks immediately upon receipt. Furthermore, the operational process in the warehouse should include a final check for a cancellation status on the Linnworks order immediately before a shipping label is generated.
Inaccurate VAT and currency data
Operational impact: Centra's multi-market and multi-currency order logic is complex. If this detail is not correctly carried across to Linnworks Sales Orders, it can produce incorrect packing slips and invoices, especially regarding VAT. This creates significant reconciliation discrepancies for the finance team and undermines any attempt to use Linnworks data for financial reporting or analysis.
Prevention / Action: The integration must be designed to correctly map Centra's 'Market', currency, and 'Pricelist' context onto every Linnworks Sales Order. The source of truth for pricing (tax-inclusive or exclusive) must be defined and applied consistently. Test the integration logic extensively against all active markets to ensure order totals and tax values match perfectly between the two systems, with alerts for any discrepancies.
Frequently asked questions
How does the integration handle inventory across our multiple international Centra storefronts?
Linnworks acts as the central source of truth for inventory. The integration maps each of your Centra 'Stock Pools' to a corresponding Linnworks location, ensuring stock levels for each sales channel are managed centrally. This prevents overselling on one storefront when an item sells out on another.
Our Centra orders have different currencies and VAT rules per market. Can Linnworks handle this complexity?
Yes, this is a core part of the integration design. We map Centra 'Markets' and 'Price Lists' to the corresponding data in Linnworks. This ensures that when a sales order is created in Linnworks, it correctly reflects the currency, VAT, and customer-specific pricing from the original Centra transaction.
What's the most common failure point when syncing catalogue data from Centra to Linnworks?
The most common issue arises from mismatched product identifiers. For the inventory sync to function correctly, every saleable product variant in Centra must have a unique SKU that maps exactly to a corresponding item record in Linnworks. Any discrepancy will break the stock sync for that specific item.
How does the integration support wholesale orders captured in Centra?
Centra can act as your wholesale portal, capturing B2B orders with specific customer groups and price lists. The integration passes these as new sales orders into Linnworks, with all the correct customer and pricing data attached. This avoids manual re-keying and ensures your wholesale order fulfilment process is consistent with B2C.
If we cancel an order in Linnworks, does it automatically cancel in Centra?
Not without a specific workflow built into the integration logic. If an order is cancelled in Linnworks after it has been sent from Centra, the Centra sales order will typically remain active. This discrepancy can cause issues for customer service and financial reconciliation unless the integration is configured to sync cancellation statuses back to Centra.
What happens when a shipment is processed in Linnworks?
Once a shipping label is created and an order is processed in Linnworks, the integration passes the fulfilment status, tracking number, and carrier information back to Centra. This automatically updates the original customer order in Centra and can trigger shipping confirmation emails, closing the loop on the order-to-cash process.