Centra and Reveni
Integration Agency & Consultants
Cogent2’s approach combines AI-powered integration delivery with deep operational experience. When return volumes grow, connecting Centra and Reveni becomes less about features and more about data integrity. Our operators focus on building a correct connection, so returns are processed accurately and your team isn’t stuck manually reconciling mismatched order and refund data.
Scoping retail logic and system architecture
With a Centra and Reveni integration, connect swiftly to these systems to enhance your multi-channel, omnichannel, and unified retail strategy. Utilize Cogent's consulting expertise to boost operational efficiency. Leverage our delivery skills to scale rapidly, optimizing your tech stack performance and providing essential training for seamless implementation.
Solution Design
Our design for Centra and Reveni prioritises the customer experience by treating Centra as the source of truth for original order data while Reveni manages the refund lifecycle. We typically sequence the flow so that return requests in Reveni are validated against Centra order history before an RMA is authorised. A core design decision involves the trade-off between real-time and batch updates for inventory. While real-time restocks improve availability, they can increase system load during peak periods, so we often implement a governed sync to ensure accuracy without risking stability. This approach ensures finance can close the month with reconciled refund data while the warehouse team maintains an accurate view of returned stock. Information flows so that CX teams have immediate visibility into return status.
Mapping order data and inventory triggers
The integration works by syncing Centra order details into Reveni to facilitate self-service returns. Centra remains the authority for the original sale, while Reveni handles the return request, disposition, and refund trigger. Data integrity is maintained by ensuring that every RMA created in Reveni is mapped back to the specific line items in the Centra order. We typically sequence updates so that stock levels are adjusted only after the return has been processed. Monitoring is built into the flow to detect issues like duplicate refund prompts early, preventing errors before they impact the general ledger or the customer.
Orchestrating workflows through a central platform
Cogent2 uses IPaaS to streamline Centra and Reveni integrations, enhancing data flow and connectivity. Benefits include reduced integration complexity, faster deployment, scalability, and improved collaboration, enabling efficient management of diverse applications and services for clients.
Monitoring sync exceptions and reconciliation gaps
Operational visibility means knowing exactly where a return sits at any moment. Dashboards often show that a sync happened, but they miss hidden discrepancies like a refund that failed at the gateway or a restock that did not update the inventory count. Our approach surfaces these exceptions early, highlighting where Centra and Reveni differ. Instead of waiting for a customer complaint or a month-end reconciliation gap, you can see failures as they occur. This level of monitoring allows operations teams to act on specific data issues before they compound into larger inventory problems.
Defining team ownership and operating models
Handover focuses on the teams running the returns lifecycle: Finance, Operations, and CX. We move away from technical manuals to provide operational documentation that defines exactly who owns each exception type, such as a refund failure or a SKU mismatch. Finance teams learn how to reconcile Reveni settlements against Centra records, while CX and Ops teams are trained to monitor return statuses and restock triggers. We establish clear ownership for regular health checks and reconciliation tasks. This ensures your internal teams have a plain English guide to the operating model. Documentation serves as a living operational reference for daily business processes.
Managing system divergence and high volumes
We monitor integration health to catch sync failures before they impact your customer service team. Potential issues with refund triggers or stock updates are addressed through ongoing operational support, ensuring the connection between Centra and Reveni remains reliable during peak return periods.
Common failures
Delayed or failed inventory updates for returned stock.
Operational impact: When Reveni confirms a return has been received and restocked, a failure to update Centra causes a stock discrepancy. This leads to inaccurate inventory levels on the storefront, risking overselling of popular SKUs or, conversely, showing items as out of stock when they are physically available. The fulfilment team then has to deal with pick exceptions and the CX team handles unnecessary customer complaints.
Prevention / Action: The integration should use a reliable, queued process for handling 'restock' webhooks from Reveni to trigger an inventory adjustment in Centra. This process needs robust retry logic to manage transient API failures. The operational model must define Centra as the master for saleable stock, with exception reports flagging any failed syncs for the operations team to manually correct.
Mismatched refund records and reconciliation gaps.
Operational impact: If Reveni processes a refund but the corresponding credit note fails to post against the original sales order in Centra, the transaction becomes invisible to standard reporting. This creates significant manual work for the finance team during month-end close. They must manually trace payouts back to orders, which undermines trust in revenue and returns data and can delay the accurate closing of the books.
Prevention / Action: The integration must use the original Centra order ID as the immutable key for all return transactions. When a refund is confirmed in Reveni, the integration logic must create a corresponding credit memo or refund object linked directly to the parent order in Centra. A dedicated exception queue should be implemented for any refund notifications that fail to post, ensuring the finance team can resolve mismatches promptly.
Failed creation of exchange orders.
Operational impact: A common failure occurs when a customer requests an exchange via Reveni, but the integration fails to create the corresponding new sales order in Centra. The customer may receive a notification that their return is processed, but the replacement item is never dispatched. This leads to frustrated customers and forces the CX team to manually create the replacement order, creating a poor experience and extra operational work.
Prevention / Action: Design a separate, robust workflow for handling exchange requests from Reveni, distinct from simple refunds. This process must validate the requested SKU's availability in Centra before attempting to create a new, zero-value sales order. The logic must include clear exception handling and notifications, alerting the CX or operations team immediately if an exchange order cannot be created automatically due to stock issues or other errors.
Frequently asked questions
Which system acts as the source of truth for the original order data used by Reveni?
Centra is the source of truth for the initial transaction, holding the master Sales Order data, including all line items, pricing, and customer information. Reveni fetches this order data from Centra to initiate a return, ensuring customers can only request returns for items they actually purchased. This prevents incorrect or fraudulent returns from being processed before they start.
How does Reveni update our stock levels in Centra when a customer's return is received?
Once a returned item is received and its disposition is confirmed in Reveni, such as being marked 'sellable', the integration triggers an inventory adjustment for that specific SKU in Centra. This automates the restocking process, ensuring that the inventory level in Centra is accurate without manual data entry from the warehouse team. This accuracy is critical for preventing overselling of returned items.
Our returns volume is high. How does this integration reduce the manual workload for our finance team?
The integration automates the creation of credit transactions when a return is processed in Reveni, which is a common source of manual work. For example, an approved return in Reveni can automatically generate the corresponding credit memo against the original Centra Sales Order in your ERP. This removes the need for the finance team to manually create these entries, reducing errors and accelerating the month-end close process.
How does the integration handle exchanges if the requested item is out of stock?
When an exchange is requested in Reveni, the integration typically attempts to create a new order in Centra for the replacement SKU. If that SKU has no available inventory in Centra when the sync occurs, the process will fail and the exchange order will not be created. This prevents the system from promising an out-of-stock item to a customer, but it also highlights the need for accurate, near real-time stock availability between Centra and Reveni.
What happens if an order is archived in our ERP before a return is processed via Reveni?
Reveni typically uses the original Sales Order ID from Centra to create a Return Authorisation in the connected ERP system. If that original Sales Order has already been archived or moved to a closed state, the integration will most likely fail when Reveni tries to post the return. This error requires manual intervention to locate the original transaction and reconcile the return, delaying the refund process.