Prima and Reveni
Integration Agency & Consultants
Cogent2's AI-powered integration delivery is guided by operators who have managed finance and logistics. For retailers using Reveni, inaccurate returns data entering Prima creates serious reconciliation headaches as volume grows. Our approach connects both systems reliably, giving your finance team clean ledgers and accurate inventory records without the manual data entry.
Auditing your returns ecosystem and ERP
Cogent2 will connect your Prima and Reveni integrations quickly, ensuring your ERP and Returns processes work together efficiently. Our consulting services are invaluable, with our system audit services enabling both our consultants and your team to identify and resolve issues across your tech ecosystem. This means Prima, Reveni, ERP, and Returns systems can operate smoothly, helping you deliver a great customer experience. By addressing integration gaps and inefficiencies, we empower your business to maintain reliable Returns management and ERP operations with Prima and Reveni at the core.
Solution Design
Design for Prima and Reveni prioritises the reconciliation of returns disposition with your core financial ledger. In most setups, Reveni is the source of truth for the return request, while Prima remains the master for inventory value and tax adjustments. A critical decision involves the timing of stock updates. We typically recommend aligning stock re-entry into Prima depots with warehouse verification cycles, rather than real-time updates that risk inaccurate inventory levels. This trade-off ensures finance reconciles against verified physical stock, even if digital inventory lags slightly during the day. This architectural choice allows the finance team to close month-end with confidence, while CX teams manage expectations using Reveni's customer-facing data. The resulting design provides operational control without introducing phantom stock into your ERP.
Synchronising inventory status and credit notes
The integration between Prima and Reveni is built on data mapping rules that protect your stock integrity. When a return is processed, Reveni passes the SKU-level data and disposition status to the integration layer. We then map these to specific Prima locations and product records, ensuring the ledger is updated based on whether an item is fit for resale or requires quarantine. Reconciliation typically occurs where we compare the total refunded value in Reveni against generated credit notes in Prima. This prevents duplicate refunds and ensures that your financial reporting reflects the movement of cash and inventory. Monitoring alerts surface any mismatches in product IDs or tax codes, preventing incorrect data from entering your ERP.
Orchestrating workflows on secure integration platforms
Leveraging IPaaS with ISO 27001 and SOC 2 and above security accreditations, Prima and Reveni integrations are delivered securely and efficiently. IPaaS connects ERP and Returns systems, ensuring Prima and Reveni data flows safely between ERP and Returns platforms. This approach reduces manual errors, accelerates deployment, and maintains compliance. Security is prioritised, with ISO 27001 and SOC 2 and above as the minimum requirement, giving confidence in handling sensitive Returns data.
Monitoring financial reconciliation and sync errors
Standard dashboards often show that a return completed, but they rarely show if the financial credit note actually posted to Prima correctly. Our approach focuses on exception visibility. We monitor the integration for data inconsistencies, such as when a refund total does not match the Prima order value due to tax rounding or other adjustments. Instead of digging through logs, your team can see specific sync failures, allowing for the resolution of discrepancies before they impact your bank reconciliation. This level of visibility ensures that small errors in the returns process do not compound into significant financial gaps in your ERP.
Defining system ownership for internal teams
Training focuses on how your finance, warehouse, and CX teams own the returns lifecycle. We hand over an operating model that defines Prima as the master for financial reconciliation and Reveni as the driver for customer communication. Your teams learn to check daily reports for discrepancies between return dispositions and depot stock levels. Finance teams learn to identify and resolve refund exceptions, while CX leads own the resolution of return status updates. Documentation is provided as a practical operational manual, ensuring the people running your business know exactly which system to trust for inventory versus customer credits. This approach ensures ownership is clear from day one.
Maintaining ledger integrity and technical performance
Post-launch, our support model focuses on maintaining the health of your financial and inventory flows. We provide monitoring to detect and resolve sync errors between Prima and Reveni before they impact your operations or financial close. When exceptions occur, such as a rejected credit note in Prima, our team helps triage the issue and provides clear steps for resolution. We maintain ownership of the integration behaviour, ensuring that as you scale your volumes, the connection remains stable. This is operational support designed to keep your warehouse and finance teams functioning without interruption.
Common failures
Returned stock not reflected in ERP inventory.
Operational impact: When Reveni marks a returned item as 'sellable', a failure to update Prima causes a discrepancy between physical stock and system stock. This leads to underselling available goods and inaccurate stock valuation, impacting merchandising and finance teams. At scale, operational teams spend significant time manually verifying stock levels against warehouse reports, and CX handle avoidable out-of-stock complaints.
Prevention / Action: The integration must treat Reveni's disposition status as the trigger for an inventory adjustment journal in Prima. A mapping should be defined for each disposition (e.g., 'sellable', 'damaged') to a specific stock ledger action. Using a queuing system with retry logic for these updates ensures that transient API errors do not lead to permanently lost inventory updates, preserving Prima as the financial source of truth.
Mismatched refund and credit journals.
Operational impact: If Reveni processes a refund but a corresponding credit note fails to be created in Prima, the finance team faces reconciliation gaps. This forces manual investigation of individual Sales Orders to align payout reports with ERP records. This work delays the month-end close process and creates uncertainty about reported revenue and liability figures.
Prevention / Action: The integration sequence must ensure that a refund confirmation from Reveni atomically triggers the creation of a linked Credit Memo or journal entry in Prima. Each financial transaction created in Prima must inherit the original Sales Order identifier for clear traceability. An exception dashboard should be implemented to monitor any refund events that do not have a corresponding Prima transaction within an agreed timeframe.
Exchange order creation failures.
Operational impact: When a customer selects an exchange in Reveni, the integration must create a new Sales Order in Prima. If this process fails due to invalid SKU data or customer record validation, the exchange is blocked. The fulfilment team does not receive the order, the customer's new item is not dispatched, and the CX team must intervene to manually create the Sales Order.
Prevention / Action: The integration's logic for creating exchange orders in Prima should first validate SKU availability and customer data integrity before attempting creation. The process should place any failed exchange creations into an exception queue with clear error reasons. This allows an operations user to resolve the underlying data issue and re-process the exchange without losing the original customer request.
Delayed return authorisation and receipt.
Operational impact: Latency in creating a Return Merchandise Authorisation (RMA) in Prima after a customer initiates it in Reveni causes downstream problems. The warehouse cannot efficiently process incoming parcels without a valid RMA record in the ERP. This slows down the physical check-in and inspection process, delaying when stock can be made available for sale and when the customer's refund can be approved.
Prevention / Action: Structure the integration to create the RMA record in Prima as soon as the return is authorised in Reveni. This is best handled via an immediate webhook from Reveni. This ensures that when the return parcel arrives at the warehouse, the operations team has a record in Prima to book the item against, connecting the physical workflow with the system data from the start.
Frequently asked questions
What happens in Prima when a customer return is processed in Reveni?
When Reveni processes a return, it sends the item's disposition, such as 'sellable' or 'damaged', to Prima. This automatically updates the stock level for the relevant SKU in the correct warehouse location. This automation ensures Prima's inventory records are an accurate reflection of available stock, preventing overselling of returned items.
Our finance team manually reconciles returns data. How does this integration address that?
The integration automates the financial part of the returns process by creating the necessary transactions, such as credit notes, in Prima as soon as a refund is confirmed in Reveni. This removes the need for your finance team to manually re-key data from Reveni into the ERP. This directly reduces the manual workload and the risk of errors during month-end close.
How does the integration handle different return outcomes, like damaged goods versus items for resale?
We map specific return dispositions from Reveni to corresponding actions and inventory locations within Prima. For example, a 'sellable' item updates the main stock quantity for its SKU, while a 'damaged' item is routed to a separate non-sellable location in Prima. This prevents damaged returns from being accidentally added back into your sellable stock.
Will connecting Reveni to Prima risk introducing new data errors into our ERP?
No, the integration is designed to prevent data discrepancies by using Prima as the source of truth for all core financial and inventory records. Reveni provides the returns status updates, and the integration ensures these are validated before updating Prima's ledger. This prevents a return processed in Reveni from creating an inaccurate inventory level or financial record in Prima.
If we use multiple warehouses, how does the integration correctly update stock levels in Prima?
The integration maps your physical warehouse locations to their corresponding 'Depots' in Prima. When Reveni processes a return, it specifies the location where the item was received. The integration uses this data to update inventory for the correct SKU in the matching Prima depot, which prevents your stock records from becoming inaccurate.