How to validate orders and payments after migrating to Shopware 6?

Real transaction testing

Sandbox tests are useful, but they do not catch everything. You need at least one live transaction per payment method after migration. That includes card payments, PayPal, bank transfer, BNPL providers, and any local gateways your store depends on. We regularly see stores pass staging tests and still fail live because API credentials, return URLs, or webhook endpoints changed during DNS cutover.

Order state mapping

Shopware 6 handles order, payment, and delivery states separately. During migration, older platform logic often gets flattened into incorrect statuses. A paid order showing as “open” can stop fulfillment automation, ERP exports, or invoice generation. Check how imported orders map into Shopware states before your warehouse starts processing new orders.

Webhook delivery validation

Payment providers rely heavily on webhooks for capture confirmation, refunds, cancellations, and subscription events. If webhook URLs still point to the old platform, Shopware never receives the update. The checkout appears successful to customers, but the order stays unpaid internally (this catches most teams off guard).

Email and invoice triggers

Migration projects often focus on checkout completion and forget post-purchase automation. Test whether order confirmation emails, invoices, shipment notifications, and refund emails still trigger correctly. One missing Flow Builder condition can silently stop every transactional email after launch.

Refund and cancellation handling

Successful payment capture is only half the validation process. You also need to test partial refunds, failed captures, voided payments, and cancelled orders. Some plugins update Shopware states correctly during payment capture but fail during refund events because the migration skipped provider-specific plugin settings.

Third-party integration sync

Orders rarely stay inside Shopware alone. Validate that orders sync properly into your ERP, WMS, CRM, tax platform, fraud tools, and shipping systems. We usually recommend checking at least five real post-launch orders end-to-end before considering the migration stable.