E-commerce automation in 2026: 14 workflows that run your store while you sleep

Why E-Commerce Automation Is No Longer Optional

The median e-commerce operator in 2026 is competing against brands with fully automated operations: cart recovery sequences that fire within minutes, inventory reorder alerts that trigger before stock-outs occur, VIP customer programmes that respond to purchase behaviour in real time, and shipping delay communications that reach the customer before they open a support ticket. If your store still runs on manual processes for any of these, you are competing at a structural disadvantage.

The good news is that the tooling to close that gap has never been more accessible. Shopify's webhook API and WooCommerce's REST API expose every significant store event order created, cart abandoned, product inventory updated, customer tagged, refund processed as automation triggers. Combined with n8n or Make as the orchestration layer, you can build a fully automated operations stack for a fraction of what enterprise e-commerce platforms charge for comparable functionality.

This guide documents the 14 workflows we deploy most consistently across e-commerce clients, with specific implementation notes for both Shopify and WooCommerce. Every workflow described here is running in production across real stores.

The Shopify and WooCommerce Integration Setup

Shopify

Shopify exposes webhooks for every major store event. Configure your n8n webhook receiver URL in Shopify Admin under Settings, Notifications, Webhooks. For each workflow below, you will create a webhook subscription for the relevant event type (orders/create, checkouts/update, inventory_levels/update, refunds/create, etc.).

For read operations (querying orders, customers, products), use the Shopify REST API with a private app API key and secret. In n8n, the native Shopify node handles authentication; for advanced queries, the HTTP Request node with your private app credentials gives more flexibility.

WooCommerce

WooCommerce webhooks are configured in WooCommerce Settings, Advanced, Webhooks. The WooCommerce REST API uses Basic Auth with consumer key and consumer secret generated in WooCommerce Settings, Advanced, REST API. In n8n, the WooCommerce node handles native operations; for bulk queries or custom filters, the HTTP Request node gives full flexibility against the WooCommerce REST API.

Workflow 1 Abandoned Cart Recovery (3-Touch Sequence)

Abandoned cart is the highest-ROI e-commerce automation for the majority of stores. Industry benchmarks show 15-20% of abandoned cart emails result in a recovered order revenue that is otherwise permanently lost.

Architecture

Trigger: Shopify fires a checkouts/update webhook when a checkout is created with contact information but no completed order within 1 hour.

Touch 1 (1 hour after abandonment): a short, direct email with the cart contents and a single "Complete your purchase" CTA. No discount. Urgency based on product availability, not artificial scarcity.

Touch 2 (24 hours after abandonment): if no order placed, a second email with social proof reviews for the abandoned products, a trust signal, and optionally a 10% discount code generated via the Shopify API (configurable not all stores want to train customers to abandon for discounts).

Touch 3 (72 hours after abandonment): final recovery email acknowledging that they may have decided not to purchase, offering a customer service contact for any questions, and presenting one alternative product recommendation based on the abandoned item's category.

When an order is placed at any point, a conditional node checks for a pending recovery sequence and cancels the remaining touches.

WooCommerce Note

WooCommerce's abandoned cart detection requires either the WooCommerce Abandoned Cart plugin (which fires webhooks on cart abandonment) or a custom query against the wp_woocommerce_sessions table via the WooCommerce REST API. We recommend the plugin approach for simplicity.

Workflow 2 Post-Purchase Upsell

The moment immediately after a completed purchase is the highest-intent moment in a customer's relationship with your store. Post-purchase upsell converts at 2-5x the rate of pre-purchase offers because the customer has already made the buying decision.

Architecture

Trigger: Shopify orders/paid webhook.

The workflow reads the completed order products purchased, order value, customer tags, purchase history. A conditional routing node determines the appropriate upsell offer: customers who purchased product category A receive an offer for category A accessories; customers above a threshold order value receive an invitation to the loyalty programme; first-time customers receive a "complete the set" offer.

The upsell email sends 2 hours after order confirmation (allowing the confirmation email to arrive first, avoiding message collision). For high-value customers, the upsell triggers a Slack notification to the account manager to personally follow up by email or phone.

Workflow 3 Review Requests (Timing Strategy)

Review request timing is the single biggest determinant of review rate more important than the incentive, the copy, or the platform. Send too early and the customer has not had time to use the product. Send too late and the enthusiasm of a positive experience has faded.

Architecture

Trigger: Shopify fulfilments/create webhook (fires when order is marked as fulfilled/shipped).

The workflow calculates the review request send time based on the shipping carrier and destination: standard UK domestic delivery (2-3 days) triggers a review request 5 days after fulfilment. Next-day delivery triggers a review request 3 days after fulfilment. International orders trigger a review request 10 days after fulfilment.

A personalised review request email sends at the calculated time, containing the specific products from the order and a direct link to the review platform (Trustpilot, Google, or Shopify's native product reviews). For customers who received a discount or loyalty reward on their order, a gentle "sharing helps us keep prices competitive" message is included.

For orders flagged as returns or refunds (queried against Shopify before the review email sends), the review request is suppressed. Requesting a review from a customer who returned your product is one of the fastest ways to generate a public 1-star review.

Workflow 4 Low Stock Alerts

Stock-outs cost UK e-commerce operators an estimated 4-8% of potential annual revenue in lost sales and lost customers (who purchase from a competitor and do not return). Low stock alerts prevent stockouts when paired with a reorder process.

Architecture

Trigger: Shopify inventory_levels/update webhook fires whenever inventory is adjusted.

For each SKU with inventory below the configured reorder threshold (typically 2-3 weeks of average daily sales volume), the workflow sends a Slack alert to the operations team and an email to the buying manager. The alert includes: SKU, product name, current stock level, average daily sales over the last 30 days, and the estimated days-to-stockout at current sales velocity.

For Shopify stores using Shopify inventory management natively, the n8n workflow can also create a draft purchase order in the connected accounting system (Xero, QuickBooks) automatically when stock falls below threshold.

Workflow 5 Supplier Reorder Trigger

Building on the low stock alert, the supplier reorder trigger automates the purchase order creation and supplier notification, reducing the time from stock alert to order placed from days to minutes.

Architecture

Trigger: same inventory webhook as Workflow 4, with a second branch for items with a configured auto-reorder rule.

For SKUs with auto-reorder enabled, the workflow calculates the reorder quantity (based on economic order quantity formula: safety stock plus lead-time demand at average daily sales), generates a purchase order document from a Google Docs template, and sends it to the configured supplier email address. The sent order is logged in a Google Sheet (order date, supplier, SKU, quantity, expected delivery date) and a Slack notification confirms the automated order to the operations team.

A human approval step is configurable for orders above a value threshold the workflow sends the draft order to Slack with Approve/Reject buttons before sending to the supplier.

Workflow 6 Price Monitoring

For stores in competitive categories, competitor price monitoring prevents the scenario where your product is 20% more expensive than the same item on a competitor's site without anyone noticing for weeks.

Architecture

Trigger: scheduled n8n workflow, runs daily.

The workflow iterates through a monitored product list (stored in a Google Sheet with SKU, competitor URL, and alert threshold). For each product, an HTTP Request node fetches the competitor page and a Claude AI extraction step reads the price from the page HTML using a prompt that handles variations in HTML structure and currency formatting. The extracted price is compared against your Shopify price for the same product.

When a competitor's price falls more than the configured threshold (e.g., 5%) below yours, a Slack alert fires to the merchandising team with the specific product, your price, the competitor's price, and the delta. The team decides whether to match, and if they do, the Shopify product price update can be executed directly from an n8n workflow triggered by a Slack button click.

Workflow 7 Loyalty Points

Loyalty programmes that run on spreadsheets and manual point allocation are loyalty programmes in name only. Automated loyalty point allocation makes the programme feel responsive and keeps customers engaged with their balance.

Architecture

Trigger: Shopify orders/paid webhook.

For every completed order, the workflow calculates the points earned (typically 1 point per £1 spent, with multipliers for specific product categories or loyalty tiers). The points are written to a customer tag in Shopify (e.g., points_1240) that can be read by Shopify's discount code system or a loyalty app. Simultaneously, an email goes to the customer with their points earned on this order and their running total.

Point redemption events (discount codes applied) trigger a corresponding deduction workflow that updates the customer tag balance. For customers reaching a loyalty tier threshold (Bronze/Silver/Gold), a tier upgrade email fires automatically with the benefits of their new tier.

Workflow 8 VIP Customer Triggers

VIP customers your top 10% by lifetime value deserve service that reflects their status. VIP triggers ensure they receive it automatically.

Architecture

Trigger: Shopify orders/paid webhook, with a conditional branch for orders from customers whose total lifetime spend has crossed the VIP threshold (configurable typically the value that puts a customer in the top 10%).

When a customer crosses the VIP threshold, the workflow tags them as VIP in Shopify, sends a personalised email from the founder or store owner welcoming them to the VIP tier with their specific benefits, and creates a task in the CRM for the customer success team to personally reach out within 48 hours.

For existing VIP customers, every new order triggers a Slack notification to the account manager not for action, just awareness. Knowing your best customers are shopping keeps the relationship front of mind.

Workflow 9 Refund Processing

Refund processing is a reliable source of customer service friction. Slow refunds, unclear timelines, and zero proactive communication turn a neutral experience (a return) into an actively negative one.

Architecture

Trigger: Shopify refunds/create webhook.

Immediately on refund creation: the workflow sends a proactive refund confirmation email to the customer with the refund amount, the payment method being refunded, and the expected timeline (typically 3-5 business days for card refunds). This single email reduces refund-related support tickets by 40-60% by setting accurate expectations before the customer has time to worry.

At the 5-business-day mark: if the refund has not yet been processed by the payment gateway (detectable via Shopify's refund status API), the workflow sends an apology email with an update and escalates internally to the operations team.

Workflow 10 Return Logistics

For stores with a physical return process, the return logistics workflow automates the label generation and return tracking.

Architecture

Trigger: customer submits a return request via a Typeform or custom return form (linked from the post-purchase email).

The workflow receives the return request, validates the order number and return reason, generates a prepaid return label via the Royal Mail or DPD API, sends the label to the customer by email, and creates a return record in the inventory management system. When the return is scanned as received at the warehouse, a webhook triggers the refund initiation workflow (connecting to Workflow 9) and sends the customer a "we've received your return" notification.

Workflow 11 Shipping Delay Proactive Alerts

The most expensive customer service interaction is the one where a customer asks "where is my order?" before you have had a chance to tell them there is a delay. Proactive delay communication costs nothing and earns disproportionate goodwill.

Architecture

Trigger: scheduled n8n workflow, runs every 2 hours. Queries Shopify for all fulfilled orders with expected delivery in the next 24 hours, then checks the carrier tracking API (Royal Mail, DPD, Evri) for each order's current tracking status.

For orders where the tracking status indicates a delay (not yet out for delivery and expected delivery is today), the workflow sends a proactive delay notification to the customer: apologetic in tone, honest about the revised timeline, and including the tracking link. A discount code for 10% off the next order is optionally included (configurable by store worth testing whether goodwill from transparency alone is sufficient).

Workflow 12 Win-Back at 90 Days

Customers who have not purchased in 90 days are at risk of permanent churn. A targeted win-back sequence recovers a meaningful percentage.

Architecture

Trigger: scheduled n8n workflow, runs weekly. Queries Shopify for customers whose last_order_date was exactly 90 days ago (plus or minus 3 days).

Touch 1: a "we miss you" email with a personalised product recommendation based on their purchase history and a time-limited 15% discount code. Touch 2 (7 days later, if no purchase): a "your discount expires soon" reminder. Touch 3 (3 days before expiry): final reminder.

Customers who purchase at any point exit the sequence. Customers who do not purchase after Touch 3 are tagged as "lapsed" in Shopify and moved to a lower-frequency engagement cadence (quarterly rather than monthly email).

Workflow 13 Seasonal Campaign Scheduler

Seasonal campaigns Black Friday, Valentine's Day, summer sale require consistent execution across email, SMS, and sometimes social. The campaign scheduler ensures nothing is missed and timing is precise.

Architecture

Configuration: a Google Sheet containing the campaign calendar for the year campaign name, send date, send time, email template ID, discount code, and target customer segment (all customers, VIP only, lapsed customers, first-time buyers).

The scheduled n8n workflow checks the campaign calendar daily. On campaign send days, it queries the Shopify customer database filtered by the target segment tag, generates personalised emails from the configured template using SendGrid or Klaviyo's API, and sends at the configured time. Discount codes are generated via the Shopify API immediately before send to ensure they are fresh and valid.

Post-campaign, the workflow queries Shopify 48 hours after send for orders with the campaign discount code applied and writes the revenue attributed to the campaign back to the Google Sheet row, creating an automatic campaign ROI record.

Workflow 14 Fraud Flagging

Fraud costs UK e-commerce operators an estimated £1.3 billion annually. Automated fraud flagging catches high-risk orders before they ship, preventing chargeback losses.

Architecture

Trigger: Shopify orders/create webhook.

The workflow runs each new order against a risk scoring model: high-order-value with a new account (created within the last 24 hours), billing and shipping addresses that do not match, shipping address in a high-fraud-rate postcode (maintained in a reference table), an email address matching a known fraud pattern (disposable email domains, sequential variations), or a failed payment retry pattern before a successful charge.

Orders scoring above the risk threshold are tagged "fraud-review" in Shopify, which puts them in a manual review hold. A Slack alert fires to the operations team with the order details and the specific risk signals that triggered the flag. The team reviews and either releases the order or cancels and refunds. For orders matching the most extreme risk patterns, the workflow can trigger an automatic cancellation and refund.

For a broader look at how automation connects across the entire e-commerce operation, see our guide on workflow automation for small businesses. And for calculating the ROI of deploying this full stack, see our automation ROI guide.

Frequently Asked Questions

Which of the 14 workflows should I build first?

Abandoned cart recovery (Workflow 1) delivers the highest ROI for most stores and has the clearest measurable impact. Build it first, measure the recovery rate for 30 days, then use the recovered revenue to fund subsequent workflows. The second priority depends on your biggest operational pain: if stockouts are a problem, build Workflow 4 next; if customer retention is the challenge, build Workflow 12.

Do these workflows work with Shopify Plus, standard Shopify, and WooCommerce?

Yes. All 14 workflows use Shopify's standard REST API and webhook system, which is available on all Shopify plans. WooCommerce implementation notes are included for the workflows most commonly deployed on WordPress stores. The n8n orchestration layer and the logic are identical across both platforms.

How do I prevent automated emails from ending up in spam?

Send from a warmed domain with SPF, DKIM, and DMARC configured. Use an established email delivery service (SendGrid, Mailgun, or Klaviyo) rather than sending directly from your domain. Keep list hygiene current by suppressing bounced and unsubscribed addresses. Start new automations with low volume and scale up gradually. For transactional emails (order confirmations, shipping notifications), deliverability is typically high. For marketing emails (win-back, upsell), list hygiene matters more.

What is the typical implementation time for all 14 workflows?

For a Shopify store with an existing n8n instance, all 14 workflows take 3-4 weeks to build with proper error handling, testing, and documentation. Prioritising the highest-value five workflows (abandoned cart, post-purchase upsell, low stock alert, fraud flagging, win-back) reduces the timeline to 1.5-2 weeks for the first production deployment.