How We Use AI Agents to Automate Post-Launch Ecommerce Operations (Real Workflow Inside)

Most Shopify agencies stop at launch. Deploy the store, hand over the keys, wish the client good luck. We think that's where the real work begins.

Post-launch operations — order communications, inventory management, review generation, supplier coordination — consume 15–20 hours a week for a mid-sized D2C brand. Most of that time is repetitive decision-making: has this order been delivered? Should we ask for a review? Is this SKU about to run out? These are decisions that follow rules — rules that can be automated.

Here's exactly how we built the post-launch automation layer for Baby Forest India, and what we learned about where AI agents add value — and where they break in production.

---

The Starting Point: Baby Forest's Post-Launch Reality

Baby Forest is an Ayurvedic baby care brand we launched on Shopify. In their first month they hit ₹4.2L in revenue with a -22% cart abandonment rate improvement from their previous setup. The store performed well. The operations behind it were still largely manual.

The founder was handling:

• Customer "where is my order?" messages manually via WhatsApp and email
• Restocking decisions based on end-of-day stock checks (sometimes missed)
• Review requests sent ad hoc, no systematic process
• Supplier coordination via WhatsApp forwards from Shopify email notifications

Each of these tasks took about 10–20 minutes per day in isolation. Combined, they were consuming 2–3 hours daily — time that should have gone into product development and marketing.

We proposed automating all four. Here's what we built.

---

Workflow 1: WhatsApp Order Status + Post-Delivery Review Request

The trigger: Shopify's orders/fulfilled webhook

When an order is marked fulfilled in Shopify, the webhook fires to our n8n instance. n8n receives the payload, extracts the customer's name, order number, and tracking details, then immediately sends a WhatsApp message via the Business API with a tracking link.

This sounds simple. It nearly broke production twice.

What actually goes wrong:

WhatsApp Business API doesn't let you send arbitrary messages to customers. You need pre-approved message templates. If your template isn't approved — even if it looks totally innocuous — the message silently fails. No error thrown in n8n. The workflow marks success. The customer gets nothing.

We learned this the hard way during testing. The solution: test every template approval before a single order goes live, and build a fallback that sends an email if the WhatsApp delivery status isn't confirmed within 2 minutes.

// n8n workflow node: Check WhatsApp delivery status
{
  "operation": "getMessageStatus",
  "messageId": "{{ $json.messageId }}",
  "timeout": 120,
  "onFailure": "triggerEmailFallback"
}

The review request sequence:

Three days after the orders/fulfilled webhook, a second n8n workflow checks if the order tracking status is "delivered." If yes, it fires a review request WhatsApp message with a direct link to the Shopify product page review section.

The key decision in this workflow: who made this decision before automation? The founder — and they forgot to do it about 40% of the time.

After 90 days, Baby Forest had collected 180+ verified product reviews. Those reviews contributed directly to a measurable lift in conversion on product pages — social proof that compounds every month.

---

Workflow 2: Inventory Restock Alert with Velocity Context

The trigger: Shopify's inventory_levels/update webhook

Every time inventory changes in Shopify, this webhook fires. Our n8n workflow checks if the current stock level for any SKU has dropped below the predefined threshold (set per product based on supplier lead time).

If it has, n8n doesn't just send "Product X is low." That's what Shopify Flow does. We send something more useful:

# AI agent step in n8n (Python function node)
def generate_restock_alert(sku_data):
    current_stock = sku_data['inventory_quantity']
    avg_daily_sales = sku_data['avg_daily_velocity_30d']  # Pulled from Analytics API
    lead_time_days = sku_data['supplier_lead_time']
    
    days_of_stock_remaining = current_stock / avg_daily_sales
    reorder_quantity = (lead_time_days * avg_daily_sales * 1.3)  # 30% buffer
    
    return {
        "sku": sku_data['variant_id'],
        "current_stock": current_stock,
        "days_remaining": round(days_of_stock_remaining, 1),
        "suggested_reorder_qty": round(reorder_quantity),
        "urgency": "HIGH" if days_of_stock_remaining < lead_time_days else "NORMAL"
    }

The WhatsApp message to the supplier includes the SKU, current stock, days of stock remaining at current velocity, and the suggested reorder quantity. The supplier confirms via WhatsApp reply, which n8n logs to a Google Sheet.

What can go wrong: Velocity calculations break during promotional periods. A flash sale spikes daily velocity 5x and the system panics, suggesting a massive reorder. We now include a flag for active discount codes in the calculation — velocity data from heavy promo windows is excluded from the 30-day average.

---

What These Workflows Saved

Across both workflows, Baby Forest recovered 12–15 hours per week of founder time. The review collection system generated social proof that directly impacts conversion — a compounding asset, not a one-time gain.

For context: similar post-operation AI workflows we built for a service business client save over 130 hours per month in manual coordination. The ROI calculus isn't complicated.

As an Official Shopify Partner, we have early access to Shopify's webhook and API capabilities, which means we can build these integrations faster and more reliably than working through third-party middleware.

---

What We Still Don't Automate (And Why)

Returns processing decisions. A return request involves judgment: Is the claim valid? Is the photo evidence sufficient? Replacement or refund? We automate the intake form and ticket creation, but a human makes every final decision. The cost of a wrong automated decision — customer churn, social media complaints — outweighs the time saved.

Complaint handling. An angry customer message requires empathy calibration that LLMs still get wrong under pressure. We route complaints to a human immediately, with the AI summarising the issue and order history in the ticket so the human has full context upfront.

Pricing decisions. Never. Business context — a competitor running a loss-leader campaign, a supplier price hike being absorbed — requires human judgment that no current model reliably provides.

---

The Architecture in Plain English

Shopify (webhook) 
  → n8n (orchestration layer)
    → Shopify API (fetch order/inventory details)
    → AI Agent (decision logic + message formatting)
    → WhatsApp Business API (customer communication)
    → Google Sheets (audit log)
    → Email (fallback)

The entire stack costs approximately ₹3,000–5,000/month to run (n8n self-hosted on a VPS + WhatsApp API call costs). For a brand doing 300+ orders per month, the ROI is clear within the first week.

Want to see what a post-launch automation layer would look like for your store? Explore our AI automation services or see our Shopify case studies.

---