Automation

WooCommerce & eCommerce Automation

Store automation is where a small team stops answering "where is my order" all day. Orders confirm themselves, delivery updates go out on WhatsApp, low stock raises an alert before you sell something you do not have, and cash-on-delivery orders get confirmed before they are dispatched.

  • WooCommerce, Shopify and sheet-based stores
  • COD confirmation built for Nepal delivery
  • Setup quoted on request

Who this is for

Online stores in Nepal and abroad where the order volume has passed what one person can watch: WooCommerce and Shopify shops, Instagram-first sellers who take orders in DMs, and businesses selling through a website and a marketplace at the same time. It sits under marketing and business automation services, and the biggest wins here are usually delivery communication and cash-on-delivery confirmation rather than anything marketing-shaped.

It is not for a store still deciding what it sells. Automation multiplies whatever your fulfilment process already is, including its mistakes, so the process has to work manually first.

What gets automated

  • Order lifecycle messages. Placed, confirmed, packed, dispatched and delivered, sent on WhatsApp, SMS or email as approved utility templates, with the courier’s tracking reference included. This is the single change customers notice most.
  • Cash on delivery confirmation. A COD order triggers a confirmation message and, if unanswered, a call task, before anything is packed. For stores where most orders are COD, cutting the refused-delivery rate matters more than any campaign.
  • Abandoned cart and abandoned checkout recovery, by email and, where the customer opted in, WhatsApp, with a limit on how many attempts and a hard stop on anyone who has bought or said no.
  • Stock alerts and reorder triggers. Low-stock notifications to the person who buys, back-in-stock notifications to the customers who asked, and automatic hiding of products that cannot be fulfilled.
  • Courier and delivery integration. Order details pushed to your delivery partner and status pulled back, so the store, the sheet and the customer say the same thing.
  • Post-purchase flows. Review requests timed to actual delivery rather than to dispatch, replenishment reminders for consumables, and win-back sequences, built in Klaviyo or your existing email tool as described on email automation.
  • Reporting. Daily sales, COD refusal rate, delivery times by courier and product margin pulled into one sheet or dashboard.

What I deliberately do not automate

  • Refunds and returns approval. The message flow around a return can be automatic; the decision and the money are not.
  • Pricing changes by rule. Automatic repricing against competitors goes wrong in ways that are expensive and slow to notice.
  • Marketing messages to customers who only ever placed an order. A purchase is not an opt-in to promotions, and treating it as one is how a WhatsApp number loses its quality rating.
  • Fake urgency. Countdown timers that reset and stock counters that are not real damage trust and, in several markets, breach consumer law.
  • Review generation of any kind that is not a genuine request to a real customer after a real delivery.

How a build runs

  1. Follow one order end to end, from placement to delivery to the accounting entry, noting every message sent, every sheet updated and every person involved. Most stores discover two steps nobody knew were manual.
  2. Fix the order statuses. The automation depends on statuses meaning one thing each. Stores that use a status to mean two things get unpredictable messages, so this is agreed before any build.
  3. Get the messaging channel ready. WhatsApp Business Platform access, templates written in Nepali and English and submitted for approval, opt-in capture at checkout, as covered on WhatsApp Business automation.
  4. Build against a staging store with real product data, testing partial orders, cancelled orders, duplicate submissions and customers who enter a phone number in five different formats.
  5. Go live on one flow first, usually order status, then add recovery, stock and reporting once the first is quiet.
  6. Review after a month on message delivery rates, COD refusals and the questions customers still ask, and adjust the sequence to answer them.

What you receive

  • Workflows in your own automation account, connected to your own store, messaging and courier accounts.
  • Approved message templates in Nepali and English, with the send rules and frequency caps documented.
  • An order-status map showing exactly which status triggers which message, so nothing sends twice.
  • Stock, failure and delivery-exception alerts, plus a daily operations summary.
  • Documentation, a pause switch and training for whoever handles orders, with optional monthly maintenance for API and plugin changes.

Pricing pointer

Setup is quoted on request; order status messaging plus stock alerts sits at the lower end of the range. Adding COD confirmation, courier integration, recovery flows and reporting moves it toward the top. Maintenance is quoted on request and matters more for stores because plugin and platform updates are frequent. WhatsApp conversation charges and email platform subscriptions are paid in your own name. Store marketing itself sits under eCommerce ads and WooCommerce SEO, and the industry view is on automation for eCommerce and retail.

Next step

Tell me your platform, your average daily orders, your courier and what share of orders are cash on delivery. I will come back within four business hours with the flows worth building first and a fixed price.

Frequently asked questions

Does this work with WooCommerce, or only with Shopify?

Both, and with sheet-based or Instagram-first stores that have no platform at all. WooCommerce is the most common case in Nepal and integrates through its REST API or webhooks, which is more flexible than most plugin-based automations. Where a store runs on a spreadsheet, the first step is usually giving orders a proper structure.

Can it reduce cash-on-delivery refusals?

Confirming the order and the address before dispatch, and telling the customer when the courier is coming, removes the two most common reasons a COD package is refused: the customer forgot, or nobody is home. I will not quote a percentage, because it depends on your products and audience, but the confirmation rate and refusal rate are both measured from day one so you can see your own numbers.

Can we send order updates on WhatsApp in Nepal?

Yes, through the WhatsApp Business Platform with approved utility templates. Order updates fall under the utility category rather than marketing, which is the important distinction: they can be sent to a customer without a marketing opt-in. Setup, verification and template approval are handled inside the project with the account in your name.

How do abandoned cart messages avoid annoying people?

Limits, mostly. A maximum of two attempts, a hard stop once someone buys or replies negatively, no messaging outside reasonable hours, and no promotional messaging on WhatsApp without an explicit opt-in captured at checkout. Recovery flows that ignore these rules cost more in unsubscribes and spam reports than they recover.

Will it slow down my store?

No, because the workflows run outside your site. Order events are sent to the automation platform by webhook and everything else happens there, so the customer's checkout is unaffected. This is a deliberate choice over plugin-heavy setups, which add load to the site and tend to conflict with each other.

What happens when my courier changes?

The courier integration is built as a separate step so it can be swapped without touching the rest. Under maintenance, changing or adding a delivery partner is a small piece of work; without maintenance, it is quoted individually. Stores in Nepal change couriers often enough that this is designed for from the start.

Ready to talk about your project?

A free 30-minute call, a straight answer about what would move the numbers, and a written proposal within 48 hours if we are a fit.