Scayle and Reveni
Integration Agency & Consultants
At scale, returns volume exposes the fracture between your commerce platform and the returns portal. Weaknesses in data flow between Scayle and Reveni result in missing inventory updates, duplicate refund triggers, and reconciliation debt for finance. We connect these systems to close the gap between a customer's return request and the final ledger entry. This ensures your operations team has trust in the stock levels and your finance team has confidence in the payout record without resorting to manual workarounds.
Diagnosing the Scayle and Reveni architecture
Integrate Scayle and Reveni seamlessly to enhance your multi-channel, omnichannel, and unified retail strategy. Our expertise ensures quick connectivity with these systems. Leverage our consulting and delivery skills to boost operational efficiency, optimize tech stack performance, and provide comprehensive training, enabling rapid scaling.
Solution Design
Design decisions for the Scayle and Reveni integration prioritise Scayle as the financial source of truth for orders while Reveni masters return logistics. A primary decision involves lookup logic. We use the Scayle Order ID for lookups in the Reveni portal to avoid customer login exceptions. We also configure instant refunds processed in Reveni to register as Manual payment types in Scayle. This trade-off ensures customers receive immediate funds while preventing Scayle from double-triggering the original payment provider. Inventory updates to Scayle are typically sequenced after physical inspection in Reveni, ensuring the Warehouse ID is correctly passed to the Scayle Inventory Service to prevent stock pool discrepancies. This model allows finance to close month-end from Scayle while CX teams work from live returns data in Reveni.
Operational data flow and purchase validation
The integration establishes Scayle as the primary order capture system while Reveni owns the end-to-end returns lifecycle. When a customer initiates a return, data typically flows from Scayle to Reveni to validate the original purchase. As the return progresses through inspection and approval, status updates are pushed back to Scayle to trigger the appropriate financial action, such as a refund or credit note. This sequencing ensures that inventory levels and order statuses remain synchronised. Monitoring is often included at the integration layer to detect when a return status fails to update in Scayle, preventing the issue of a customer expectation being set in one system but not met in the other.
Orchestrating the stacks via middleware logic
Cogent2 uses IPaaS to streamline Scayle and Reveni integrations, enhancing efficiency and scalability. IPaaS offers seamless connectivity, real-time data synchronization, and reduced integration complexity, enabling faster deployment and improved collaboration between systems, ultimately driving better business outcomes for integration agencies and consultants.
Auditing the delta between system records
Standard dashboards often hide the most damaging errors, such as a return that is marked as received in one system but remains pending in the other. These discrepancies compound, leading to manual reconciliation work for finance teams and confusion for customer service. We focus on surfacing these exceptions by monitoring the delta between Scayle and Reveni. The goal is to flag any return record that has stalled in the sync queue or failed to post a refund. This level of visibility helps move the team from reactive manual checks to proactive management, ensuring that returns are correctly accounted for in financial reporting.
Defining ownership boundaries for internal teams
Handover focuses on operations, finance, and CX teams to ensure long-term ownership of the returns journey. We define the ownership boundary: CX maintains the return experience in Reveni, while finance manages the financial trust boundary within Scayle. Training covers the daily check of the returns queue and how to respond when a Warehouse ID error prevents stock from updating. Documentation is provided as an operational reference, explaining how to interpret alerts from the integration layer and which team owns specific exception types. This is written for the people running the business rather than a technical archive.
Monitoring for settlement drift and exceptions
We provide ongoing operational monitoring that targets the logic gaps where returns typically fail. After launch, we monitor for specific edge cases, such as return notifications missing a Warehouse ID or stock failing to increment in the Scayle Inventory Service. When these exceptions occur, they are surfaced with the full order context, meaning your team spends time resolving variances rather than manually investigating every sync record. Support is anchored in the end-to-end return journey, helping to catch reconciliation debt and settlement drift before they impact the month-end close.
Common failures
Failure to identify Stock Pool increments
Operational impact: When Reveni sends a return notification to Scayle without a valid Warehouse ID, the Scayle Inventory Service cannot determine which stock pool to increment. This causes synchronization failures where items are physically returned but never become available for resale in the digital storefront.
Prevention: The integration must map the physical return location in Reveni to a specific Warehouse ID in Scayle. We implement validation at the integration layer to block notifications that lack this identifier and alert operations immediately.
Double-triggering original payment provider refunds
Operational impact: If an instant refund processed via Reveni is not registered in Scayle as a Manual payment type, the commerce system may attempt to trigger a second refund through the original payment provider. This creates financial discrepancies and forces finance teams into manual reconciliation to recover double-paid funds.
Prevention: We configure the Scayle Return entity with a zero-value flag or mark the payment as Manual when Reveni has already executed the payout via its own financial rails.
Order Not Found exceptions during portal login
Operational impact: Customers may be unable to log in to the Reveni returns portal if the integration incorrectly passes a Reservation ID instead of the primary Order ID. This leads to an immediate spike in customer support tickets and prevents customers from initiating returns.
Prevention: Lookups must be mapped to the Scayle Order ID core object. We verify this mapping during the audit phase to ensure the customer-facing identification matches the data indexed by Reveni.
Frequently asked questions
Why do customers get \"Order Not Found\" errors in the Reveni portal?
This usually occurs when the integration passes a Reservation ID instead of the primary Order ID. Reveni requires the specific Order ID for lookups. We ensure the mapping identifies the correct object so customers can access the portal without friction.
Why do some returned items fail to appear in my Scayle inventory?
Scayle's Inventory Service requires a specific Warehouse ID to allocate stock to the correct pool. If the Reveni return notification lacks this ID, the sync fails. We configure the mapping to ensure every return event includes the destination Warehouse ID for accurate resale levels.
How does the integration handle Reveni's instant refunds?
To prevent Scayle from attempting a double refund through your payment provider, we register Reveni's instant refunds as Manual payment types. This allows the financial record in Scayle to reflect the return without triggering a second, duplicate payout to the customer.
How are stock discrepancies handled during a return?
We use physical inspection events in Reveni to trigger Scayle updates. If an item is graded differently than expected, the integration passes the corrected status to Scayle, ensuring your available-to-sell count matches the actual condition of the stock in the warehouse.