n8n for E-commerce: The Complete Automation Guide (Shopify, WooCommerce, PrestaShop)

An online store produces a constant stream of events: orders to confirm, abandoned carts to recover, inventory to keep accurate, reviews to handle, invoices to issue, support tickets to triage. Each task looks harmless on its own; together they eat entire days — or a stack of subscriptions to single-purpose apps. n8n offers a third way: one automation tool, connected to Shopify, WooCommerce or PrestaShop, orchestrating all of these projects with workflows you control end to end. This guide maps out everything an e-commerce merchant can automate with n8n, project by project, each with a link to our detailed guide.

Step zero: connect your platform to n8n

Everything starts here. n8n ships native nodes for the major platforms, and the principle is always the same: API credentials for reading and writing (products, orders, customers), plus webhooks to react to store events in real time.

• Shopify: the native node covers orders and products, and the Admin API exposes reliable webhooks (orders/create, checkouts/update, and so on). Full setup is covered in our guide to connecting Shopify to n8n.
• WooCommerce: also a native node, REST key authentication, webhooks configured from the WordPress back office. Follow the WooCommerce + n8n connection guide.
• PrestaShop: no dedicated node, but the webservice API works very well through the HTTP Request node — our PrestaShop + n8n guide details authentication and the useful calls.

Once connected, every store event lands in n8n as workable JSON. A Shopify orders/create webhook, for instance, delivers everything the downstream workflows need:

{{ $json.order_number }}     → order number
{{ $json.total_price }}      → total amount
{{ $json.customer.email }}   → customer email
{{ $json.line_items }}       → array of ordered items

Project 1 — Order processing

The problem: every order triggers a manual cascade — check the payment, notify fulfillment, log it in the tracking sheet, send the confirmation. At ten orders a day it is manageable; at fifty, it is a part-time job.

The n8n pattern: an orders/create webhook feeds a workflow that routes each order by status and amount (IF or Switch node), writes to your management tool, notifies the team on Slack and triggers an enriched confirmation email. Every node is covered in our guide to automating e-commerce orders with n8n.

Project 2 — Abandoned carts

The problem: a significant share of shoppers fill a cart without checking out — an expressed purchase intent that dies silently if nobody follows up.

The n8n pattern: detect the abandonment (a checkouts/update webhook on Shopify, polling of "pending" orders on WooCommerce), wait the right amount of time with a Wait node, re-check that the order was not paid in the meantime, then generate an AI-personalized recovery email from the cart contents. The full sequence — delays, re-checks, message writing — is in our guide to recovering abandoned carts with AI and n8n.

Project 3 — Inventory synchronization

The problem: as soon as you sell on several channels or your stock lives outside the store (ERP, supplier, spreadsheet), discrepancies creep in — and they are expensive. A study by DeHoratius and Raman published in 2008 in Management Science, covering nearly 370,000 inventory records from one retailer, found that 65% of stock records were inaccurate (study on Google Scholar). Manual synchronization does not hold up over time.

The n8n pattern: a two-way flow — sales decrement the source of truth, restocks flow back to the store through the API — with careful conflict handling and low-stock alert thresholds. Our guide to synchronizing Shopify inventory with n8n covers the full architecture.

Project 4 — Failed payments and dunning

The problem: expired cards on subscriptions, declined payments, disputes: every unhandled payment failure is revenue evaporating, and chasing it manually is as painful for you as it is for the customer.

The n8n pattern: Stripe webhooks (invoice.payment_failed, charge.dispute.created…) trigger dunning sequences whose tone and content are adapted by AI to each customer's context. The setup is described in our guide to Stripe webhooks and AI-driven payment recovery.

Project 5 — Customer reviews

The problem: reviews pile up across several channels and nobody reads them systematically — even though they directly move sales. A study by Chevalier and Mayzlin published in 2006 in the Journal of Marketing Research showed, using Amazon and Barnes & Noble data, that an improvement in a product's reviews increases its relative sales, and that a 1-star review carries more weight than a 5-star one (study on Google Scholar). Leaving a negative review unanswered costs more than you think.

The n8n pattern: collect reviews via API or email, classify them by sentiment and topic with an AI node, alert immediately on negative reviews and draft a suggested reply. The full workflow is in our guide to analyzing customer reviews with AI.

Project 6 — Customer support

The problem: "where is my order?", return requests, product questions: e-commerce support is 80% repetitive, but the remaining 20% (a furious customer, a dispute) demand a fast reaction that an untriaged ticket queue makes you miss.

The n8n pattern: every incoming ticket goes through an AI classification node scoring urgency, sentiment and category, then routes to the right person — or even drafts a reply for standard cases. The scoring method is detailed in our guide to AI-based support ticket scoring.

Project 7 — Quotes and invoices

The problem: B2B or quote-based billing often stays manual: re-typing order lines, generating the PDF, sending, filing.

The n8n pattern: order data feeds a template, a node generates the PDF, and the document goes out by email before being archived automatically. Our guide to generating quotes and invoices as PDFs with n8n shows both approaches (dedicated API or HTML → PDF rendering).

Project 8 — Reporting

The problem: revenue lives in the platform, traffic in Analytics, ad spend in Ads Manager — and on Monday morning, nobody has the full picture.

The n8n pattern: a weekly Schedule Trigger aggregates sales (store API), joins them with the other sources, has an AI node write a readable summary and posts it to Slack or email. The same pattern as our existing automated reports, applied to sales data.

Where to start: an order that works

Do not launch all eight projects at once. The sequence that works for most stores:

1. The connection + one read-only workflow (enriched order notification): zero risk, hands-on practice with webhooks.
2. Abandoned carts: the best effort-to-revenue ratio, measurable within the first week.
3. Order processing, then inventory — the projects that write into your systems, to tackle once the basics are solid.
4. Reviews, support, invoicing, reporting depending on your current pain point.

Two cross-cutting habits before wiring anything into production: handle webhook duplicates (a platform can deliver the same event twice) and give every workflow that writes data an error path. Our ready-made templates in the workflows library make good starting points.

Key takeaways

• n8n covers the whole e-commerce cycle: orders, abandoned carts, inventory, payments, reviews, support, invoicing, reporting — on Shopify, WooCommerce and PrestaShop.
• Everything rests on the same foundation: API credentials + webhooks, set up once per platform.
• Every project has its own detailed guide on this site; this hub gives you the map, the guides give you the terrain.
• Start with a read-only workflow, then work your way up to workflows that write into your systems.