Shopware and Reveni
Integration Agency & Consultants
Returns management becomes a commercial risk the moment reporting shows significant write-offs or a spike in customer service calls. When Reveni and Shopware operate in isolation, stock accuracy often suffers because returned items are not mirrored in the ecommerce platform, potentially leading to overselling. We focus on the end-to-end flow, ensuring inventory updates and refund confirmations stay in step to reduce manual checking.
Scoping your retail and inventory strategy
With a Shopware and Reveni Integration, connect swiftly to these systems to enhance your Multi-channel, Omnichannel, and Unified retail strategy. Utilize Cogent’s expertise to scale rapidly by boosting operational efficiency, optimizing tech stack performance, and providing comprehensive training.
Solution Design
Design decisions for Shopware and Reveni focus on inventory integrity and financial reconciliation. Shopware remains the source of truth for order history, while Reveni owns the return lifecycle from authorisation to settlement. A primary decision involves real-time vs batch processing for stock updates. We typically favour real-time inventory triggers to prevent overselling of high-demand items, acknowledging the trade-off that this increases system dependency compared to batching. We sequence refund data to post only after Reveni confirms successful payout, ensuring finance reconciles against actual cash movement rather than projected returns. This design allows finance to close monthly books off Shopware data while operations work directly within Reveni alerts. The resulting operating model ensures that returned stock is available for resale without manual intervention.
Synchronising returns data and stock movements
The integration synchronises returns data between Shopware and Reveni to preserve stock accuracy and financial integrity. Shopware acts as the system of record for the original sale, while Reveni manages return authorisation and logistics. When a return is processed, status updates flow back to Shopware to trigger inventory movements and update order history. We implement rules to prevent duplicate refunds and ensure that restock events occur at the correct stage of the return process. Monitoring is embedded to detect issues like failed webhook deliveries or SKU mismatches early, reducing the drift between system counts that leads to reconciliation gaps.
Orchestrating data flow via IPaaS layers
Cogent2 uses IPaaS to seamlessly integrate Shopware and Reveni, enhancing data flow and process automation. Benefits include reduced integration complexity, faster deployment, improved scalability, and real-time data synchronization, enabling efficient management and enhanced customer experiences.
Surfacing sync errors and reconciliation gaps
Standard dashboards often miss the quiet failures that erode margins. Between Shopware and Reveni, visibility means knowing why a refund failed to post or why a restock event did not trigger in the storefront. We move beyond simple monitoring by surfacing specific causes of sync errors, such as a SKU mismatch, an order status conflict, or a failed webhook. This allows teams to resolve exceptions before they impact the customer experience. This approach ensures that discrepancies in return counts are surfaced early, helping to maintain accurate stock levels in Shopware and preventing manual reconciliation drag at month-end.
Operational handover for finance and CX
Handover ensures that CX, finance, and operations teams effectively own the returns workflow between Shopware and Reveni. We focus on the operating model: CX teams learn to manage return status updates within Reveni, while finance is trained on how refund data flows back to Shopware for reconciliation. We transition ownership of monitoring, ensuring teams know how to read alerts from the integration layer before issues compound. We provide operational documentation detailing where return data lives and who owns specific exception types, such as failed inventory restocks or refund status mismatches. This documentation is written as a practical guide for the people running the business, not a technical archive for IT.
Active oversight of the returns workflow
Our support model moves beyond reactive troubleshooting to active operational oversight. We monitor the Shopware and Reveni sync for exceptions, handling issues before they affect your customer service metrics or inventory accuracy. After launch, we stay connected to your business needs to ensure that changes to your Shopware setup or Reveni return policies do not disrupt the integration. By identifying and addressing sync failures early, we help your team stay focused on operations rather than troubleshooting technical drag or stock discrepancies.
Common failures
Delayed or inaccurate stock updates from returns.
Operational impact: This leads to overselling returned items before they are inspected, or holding back saleable stock. At scale, this corrupts inventory data in Shopware, forcing the fulfilment team to cancel Sales Orders and creating manual data correction tasks for the finance and operations teams.
Prevention / Action: Design the integration to listen for specific events from Reveni, such as 'item received' versus 'item graded and restocked'. Only update Shopware's saleable stock quantity upon receiving the final 'restocked' confirmation. Ensure asynchronous queue handling is in place to manage API rate limits and retry failed stock updates, with monitoring to alert teams to persistent failures.
Mismatched refund and sales order data.
Operational impact: When a refund processed in Reveni fails to generate a correctly linked credit memo in Shopware, the order-to-cash record becomes inaccurate. The finance team cannot reconcile payouts against sales and refund data, leading to a time-consuming month-end close and potentially inaccurate financial reporting.
Prevention / Action: The integration must enforce the use of the original Shopware Sales Order ID as the primary key for all refund transactions. Logic should ensure that a credit memo is only created in Shopware after a confirmed refund completion event from Reveni. Error handling must catch and flag any refund that cannot be matched to a valid sales order.
Inconsistent return status for customers.
Operational impact: The customer sees a different return status in their Shopware account compared to the email updates from Reveni. This drives high-volume, low-value 'Where is my refund?' queries, increasing the burden on the CX team who must then manually check both systems to provide an accurate answer.
Prevention / Action: Map all of Reveni's key return statuses to a dedicated custom attribute or status field on the Shopware order object. The integration logic should push status updates from Reveni to Shopware as they happen. This centralises the customer-facing status in Shopware, providing a single source of truth for both the customer and the CX team.
Return processing failures for archived SKUs.
Operational impact: When a customer returns a discontinued product, the restock message from Reveni to Shopware fails if the SKU has been archived. The item becomes 'lost' from an inventory perspective until a member of the operations team manually investigates the failure and adjusts stock, delaying its availability.
Prevention / Action: The integration's exception handling must catch 'SKU not found' errors from the Shopware API. Instead of simply failing, the process should create a task for an operator with the required context (Order ID, Return ID, original SKU). Prevention should involve using Shopware's immutable internal Product ID as the canonical identifier in integration traffic, rather than the SKU.
Frequently asked questions
How does this integration prevent us from overselling when returned items are put back into stock?
The integration ensures stock accuracy by using Reveni as the trigger for inventory updates in Shopware. Once a returned product is inspected and approved for resale in Reveni, it sends a message to update the stock level for that specific SKU in Shopware. This prevents the common failure where stock is returned to the shelf in Shopware before it's physically available, which can lead to selling items you don't have.
Will connecting Reveni create more work for our customer service team who operate mainly in Shopware?
No, the integration is designed to reduce their workload by centralising information within Shopware. When a return is processed in Reveni, key status updates are automatically pushed to the corresponding sales order in Shopware. This gives your team visibility of the returns process directly on the customer's record, avoiding the need to switch between systems to answer queries about refund status or exchanges.
We use Shopware's 'Closeout' setting for end-of-life products. How does the integration handle returns for these?
This is a critical point that must be configured during implementation to avoid inventory errors. The integration logic must be built to recognise Shopware's 'Closeout' (Abverkauf) product status and prevent Reveni from restocking these items. If not handled, a returned closeout SKU could be incorrectly added back to your available inventory, undermining your merchandising and stock-down strategy.
Which system is the source of truth for returns data: Shopware or Reveni?
Reveni is the source of truth for the returns handling process, managing the customer return request, the item inspection, and the decision on its outcome. However, the integration makes Shopware the source of truth for the master customer order history and inventory. Reveni pushes status updates and stock adjustments back to Shopware, ensuring the sales order and SKU records are always updated with the final outcome.
Our Shopware promotions sometimes create orders with line items that don't have a SKU. Will this break the returns process in Reveni?
Yes, this can cause the integration to fail, as Reveni's process typically relies on a SKU for each line item being returned. The integration must be designed to correctly identify and filter out these promotional line items from Shopware orders. Without this logic, attempting to process a return for an order containing no-SKU items will likely cause a sync error and require manual intervention from your team.