Ecommerce platforms tool implementation: Shopify/WooCommerce

Use this ecommerce platforms tool implementation guide to compare Shopify and WooCommerce implementation routes for one England merchant. The shared controls below apply to both; platform-specific sections cover import and recovery differences. Treat implementation as a reversible change, not a design launch; use synthetic records until authorised owners approve a limited production migration.

What to take away

Establish the change boundary

Name the legal seller, goods, UK customer geography, platform edition, payment provider, integrations, existing route and launch authority. Freeze the accepted requirements and vendor evidence. Create a responsibility map for catalogue facts, product-safety records, consumer wording, personal data, payment reconciliation, fulfilment, accessibility, security, tax, support and contracts.

Shopify and WooCommerce implementation routes

Shopify is a hosted ecommerce service, while WooCommerce is an ecommerce plugin for WordPress. Shopify operates the platform infrastructure; with WooCommerce, the merchant chooses hosting and manages more of the operating stack, including WordPress and plugin updates and backups. Neither removes the merchant’s responsibilities for customer journeys, data, payments or fulfilment.

Compare the platforms against the required integrations, payment arrangements, data exports, fulfilment flow, accessibility needs and exit plan. The implementation route differs: Shopify uses its product CSV tools and can use Shopify-focused migration apps, while WooCommerce has a built-in product CSV importer and runs within a WordPress environment.

Platform-specific import and migration steps

For Shopify, export the existing product catalogue and keep an untouched copy. In the Shopify admin, use Products > Import to load a validated product CSV; check field mapping, variants and image URLs in staging before the production import. Shopify’s product export instructions note that sorting an exported CSV can disassociate variants or image URLs.

For WooCommerce, use Products > All Products > Import to upload a product CSV and review its field mapping. Test a small staging import first, including variants and stock, then check the imported catalogue against the source export before proceeding.

Migration options include Matrixify for Shopify, WooCommerce’s built-in CSV importer, and third-party services such as Cart2Cart and LitExtension. Treat each as a candidate, not a guarantee: confirm that it supports the source, destination and data types you need, then test mappings and records in staging. Keep independent exports of orders, customers, transaction references and configuration; a product import alone does not prove that the full store has migrated.

Build a state dictionary before configuring screens. A product needs draft, reviewed, published, paused, corrected and withdrawn states. An order needs initiation, authorisation, capture, acceptance, fulfilment, cancellation, return, refund and dispute, with owners and timestamps. Never allow the supplier's labels to replace the merchant's accounting and customer obligations.

Configure a clean test environment

Use invented product names, non-personal email addresses and provider-approved test payments. Restrict administrator access, record configuration versions and disable unnecessary integrations. Use Playwright or Cypress for repeatable browser journeys, Lighthouse for automated page audits, and Faker-generated synthetic records where suitable; automated results do not replace human accessibility checks. Do not copy a live customer database to make a test look realistic.

Import a small catalogue containing variants, unavailable stock, delivery restrictions and corrected facts. Shopify warns that sorting an exported product CSV can disassociate variants or image URLs in its product export instructions.

WooCommerce recommends a backup and a small staging import for large catalogues in its CSV documentation. These cautions support controlled testing only; they do not establish migration success.

Exercise customer and operator paths

Run keyboard and assistive-technology checks across browse, product, basket, checkout, confirmation, account, cancellation, return and contact. Verify seller identity, complete prices, delivery, payment action and contract confirmation against the relevant scope in GOV.UK's online-selling guidance. Review consumer-facing information and relevant order flows against the Consumer Rights Act 2015 and the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013. Check accessibility against WCAG 2.2 AA and obtain advice on the merchant’s duties under the Equality Act 2010. A named accessibility specialist and consumer lawyer should approve separate results.

Create successful, declined, abandoned, duplicate and refunded test orders. Reconcile platform event, gateway reference, merchant order, fee, refund, dispute and settlement fields. If money may be received for another seller, stop for FCA perimeter review using its payment-services page.

Test product correction and withdrawal without deleting the supporting record. Trigger a fake unsafe-product incident and show that the safety owner can identify affected listing versions and customers. Test tracking choices, suppression, data access and deletion separately. Review personal-data handling against the UK GDPR and Data Protection Act 2018, and tracking and electronic marketing against the Privacy and Electronic Communications Regulations 2003 (PECR). Privacy counsel must review purpose, roles and current processor terms.

Prove recovery and exit before launch

Export catalogue, orders, transaction references, customers, permissions, suppressions, content and configuration. Shopify's order export record says its transaction history contains captured-payment data but not authorisation data, illustrating why a named field inventory matters. Restore the exported set into an independent environment or documented manual fallback and list every loss.

Rehearse an unavailable checkout, corrupted stock feed, compromised administrator, failed payment callback and supplier outage. The NCSC's supplier assurance questions provide prompts for incidents, recovery, cloud dependencies and evidence. Set recovery thresholds from the merchant's risk assessment, not a generic benchmark.

Release in a controlled window

Take verified backups and exports, freeze catalogue changes, assign rollback authority and record open orders. Migrate only the authorised data using the selected platform’s importer or a tested migration tool. Reconcile products, variants, stock, customers, orders and payment references against the source records, then repeat critical accessibility, consumer, payment, privacy, safety and security checks. Publish only after named specialists sign their own non-compensating gates.

Monitor orders, stock, settlement mismatches, customer contacts, tracking choices and errors during the agreed observation window. Roll back if a critical journey fails, accounting cannot reconcile, product evidence separates from a listing, personal data escapes its approved route or export becomes unavailable. For WooCommerce, rehearse restoring a verified files-and-database backup; for a DNS failover, retain the previous storefront and rehearse switching the domain back. For Shopify, do not assume an in-place rollback: use a platform rollback feature only if it is available for the change and has been tested, or route traffic back to a retained previous storefront where appropriate. Pause or reconcile new orders before switching to avoid leaving records out of sync. Close the old service only after records, contractual duties and deletion evidence are complete.

Before you act

Platform-specific cutover checks:

Common questions

Why should a platform implementation be treated as a reversible change?

Because the method assumes one England merchant moving a direct store for physical consumer goods, using synthetic records until authorised owners approve a limited production migration. This approach allows rollback if critical journeys fail or accounting cannot reconcile, avoiding irreversible design launches.

What should a state dictionary include for products and orders?

A product needs draft, reviewed, published, paused, corrected and withdrawn states. An order needs initiation, authorisation, capture, acceptance, fulfilment, cancellation, return, refund and dispute, with owners and timestamps. Never allow the supplier's labels to replace the merchant's accounting and customer obligations.

How can a merchant prove recovery and exit before launch?

Export catalogue, orders, transaction references, customers, permissions, suppressions, content and configuration. Restore the exported set into an independent environment or documented manual fallback and list every loss. Rehearse failures like unavailable checkout, corrupted stock feed, compromised administrator, failed payment callback and supplier outage.