Orderwise and Reveni
Integration Agency & Consultants
High returns volume creates invisible work reconciling inventory and refunds. Cogent2’s AI-powered delivery, guided by experienced operators, connects Reveni to Orderwise to automate this process. We ensure returned stock is accurately accounted for, giving your finance and warehouse teams a reliable, single view of your true inventory position.
Auditing your ERP and returns stack
We connect your Orderwise and Reveni integration quickly, ensuring your ERP and Returns processes work together efficiently. Our consulting services are valuable because our system audit identifies issues in your tech stack, enabling both our consultants and your team to take decisive action. This helps your Orderwise and Reveni integrations, ERP, and Returns management run smoothly, supporting a reliable customer experience. With our audits, you gain clear insights and practical steps to keep your technology ecosystem operating at its best.
Solution Design
The Orderwise and Reveni integration is designed with Orderwise as the definitive source of truth for inventory and financial postings. We typically configure Reveni to push return notifications, while managing the financial reconciliation back to Orderwise to ensure tax codes and fees align with your accounts. A key trade-off is the decision to delay restocking inventory in Orderwise until an inspection is confirmed. While this prevents immediate stock updates, it protects your available-to-sell figures from phantom stock errors. This design ensures that finance closes the month with accurate credit note data, while operations works from verified inventory levels rather than assumptions. The result is a system where teams can trust the numbers because the data flow reflects physical reality.
Automating stock movements and ledger updates
The integration establishes a controlled loop between Reveni's return workflow and Orderwise inventory management. Orderwise remains the source of truth for stock levels and financial records, while Reveni acts as the specialised engine for customer returns. Return status updates and disposition data typically flow back into Orderwise to automate stock movements. We sequence these updates to ensure inventory is only restocked based on defined operational triggers, preventing phantom stock from appearing in your sales channels. Ongoing monitoring detects when a return record fails to map to an original order, stopping data errors before they hit your core ledger.
Orchestrating workflows via secure middleware
Leveraging IPaaS with ISO 27001 and SOC 2 and above security accreditations enables secure, efficient integration between Orderwise, Reveni, ERP, and Returns systems. This approach simplifies connecting Orderwise and Reveni, automates ERP data flows, and manages Returns processes securely. Benefits include rapid deployment, reduced manual effort, and robust compliance, ensuring Returns and sensitive data are protected while supporting business growth and operational reliability.
Proactive monitoring for financial data gaps
Dashboards often show that returns are moving but fail to highlight where the financial data has stalled. Hidden issues, such as tax code mismatches or unlinked SKUs, create discrepancies between your records and your ERP that only surface during month-end audits. Our approach to visibility means surfacing these exceptions early. We monitor the bridge between Reveni and Orderwise to identify orphaned returns or failed restock commands. Your team receives targeted alerts when a specific return requires manual intervention to maintain ledger integrity.
Standardising handovers for finance and warehouse
Implementation success depends on adoption by your finance and warehouse teams. We hand over an operating model that clearly defines who owns each exception type, such as stock mismatches or failed credit notes. Your team will learn to check return data in Reveni against the stock updates appearing in Orderwise, ensuring physical counts remain accurate. Training is anchored in your specific configuration, providing finance with the knowledge to read alerts from the integration layer during reconciliation. Handover documentation is purely operational, focusing on the actions required to maintain data integrity rather than technical reference.
Post-launch governance and exception management
Ongoing support focuses on operational stability. We monitor the flow of return data to catch synchronisation errors before they impact your warehouse or finance teams. When exceptions occur, we provide the context needed to resolve them quickly, ensuring your integration continues to reflect your real-world inventory.
Common failures
Inventory latency and overselling
Operational impact: When Reveni processes a return, the stock adjustment must be reflected in Orderwise. If this integration step is delayed or fails, Orderwise inventory levels become inaccurate. This leads to overselling of returned SKUs, resulting in cancelled orders and increased workload for the customer service team, or it leads to underselling available stock, which directly impacts revenue.
Prevention / Action: The integration logic should treat the Orderwise stock update as a critical, queued transaction with a robust retry mechanism and rate-limit handling. Design the data flow to use a specific return status from Reveni as the trigger. Implement monitoring to flag any failed updates and consider a daily reconciliation process to compare Reveni's 'returned to stock' dispositions against 'goods in' records in Orderwise.
Financial reconciliation gaps
Operational impact: If Reveni issues a refund but the corresponding Sales Credit fails to generate correctly in Orderwise, the finance team faces reconciliation challenges. This creates discrepancies between Reveni's payout reports and the Orderwise sales ledger. It leads to manual, time-consuming investigations at month-end to ensure P&L statements and VAT returns are accurate.
Prevention / Action: The integration should be designed so that the Orderwise Sales Credit is created only upon a confirmed refund notification from Reveni. The refund value and tax treatment must be owned by a single source of truth to prevent calculation mismatches. An exception handling process is essential to alert the finance team if a Sales Credit cannot be created or matched to an original Sales Order.
Failed creation of exchange orders
Operational impact: When a customer requests an exchange through Reveni, a new Sales Order must be created in Orderwise to dispatch the replacement item. Failure in this workflow means the customer's exchange is never fulfilled, leading to a negative experience and inbound queries for the customer service team. This breaks the automated loop, forcing operations staff to create manual Sales Orders to resolve the issue.
Prevention / Action: Define a specific returns status in Reveni (e.g., 'exchange approved') to trigger the creation of a new, zero-value Sales Order in Orderwise. This workflow must include immediate stock allocation for the outbound SKU to prevent it from being sold to another customer. The integration should include monitoring to flag any order creation failures for manual review by an operations or CX team member.
Returned stock disposition errors
Operational impact: Reveni allows for different return dispositions, such as 'sellable' or 'damaged'. If this disposition data is not correctly mapped and sent to Orderwise, all returns may be added back to sellable stock by default. This results in damaged goods being sent to other customers, harming brand reputation, and requires the fulfilment team to manually inspect, segregate, and adjust stock records.
Prevention / Action: The integration must correctly map Reveni's disposition statuses to corresponding logic in Orderwise. For example, 'sellable' items trigger a stock adjustment into the main warehouse, while 'damaged' items are moved to a specific quarantine location or bin. Align operational processes to ensure warehouse staff handle items according to the data received from the integration, preventing manual workarounds.
Frequently asked questions
If Orderwise is our source of truth for stock, how does a return in Reveni update our inventory levels?
When Reveni processes a return and marks an item as 'sellable', the integration triggers a corresponding stock adjustment or Goods Received Note in Orderwise against the correct SKU. This ensures the central inventory record in Orderwise accurately reflects physically returned stock, preventing overselling or holding incorrect stock values. Without this, teams must manually adjust stock in Orderwise based on reports from Reveni, a process prone to error and delay.
Our returns volume is high. Will this integration just create new manual reconciliation work for our finance team?
No, the primary goal is to prevent this by automating financial entries. When Reveni confirms a refund, the integration automatically creates the corresponding Sales Credit Note in Orderwise against the original Sales Order. This removes the need for the finance team to manually create these credit documents and reconcile refund reports from Reveni, a common cause of delays during the month-end close.
What happens if a customer returns an item from a bundle or a promotional SKU that doesn't exist in Orderwise?
This is a frequent integration failure point that must be handled by the integration logic. If Reveni attempts to sync a return for a SKU that isn't mapped to an active item record in Orderwise, the stock update will fail. A properly designed integration includes rules to map multiple ecommerce SKUs to a single Orderwise product code or flags these returns for manual review, preventing data errors.
We use multiple warehouse locations in Orderwise. How does the system know where to restock returned items?
This is managed by mapping return locations in Reveni to the specific warehouse 'Location Codes' in Orderwise. During implementation, we define these rules so that when Reveni processes a return for a specific location, the integration directs the stock adjustment to the correct inventory pool. If this is not configured, inventory from returns will either fail to sync or will be added to a default location, compromising stock accuracy across your network.