MERSO IT

Automation · Vietnam e-commerce

The end-to-end e-commerce automation stack for Vietnam

MERSO IT Insights · Updated July 2026 · 9 min read

Diagram of a fully automated e-commerce pipeline from storefront to delivery and invoicing

The goal: you decide what to sell and keep goods stocked at one registered pickup address. Everything else — listing products, writing content, answering customers, booking the courier, issuing compliant e-invoices, even producing marketing videos — runs as software. This article maps the complete architecture we build for Vietnamese sellers, and the traps that only show up in production.

The seven layers of a self-running shop

  1. Storefront — Shopify (or Haravan/Sapo for domestic-first shops), the system of record for products and orders.
  2. Listing & content engine — AI generates titles, bilingual descriptions, variant tables and images from a photo and a few facts.
  3. Customer service bot — one brain answering webchat, Zalo OA and Facebook Messenger, with human escalation.
  4. Fulfilment — new order → automatic ViettelPost pickup booking at your registered address, label generation, tracking webhooks back to the customer.
  5. Finance — every order becomes a legal e-invoice in MISA AMIS or an alternative provider, and COD remittances are reconciled automatically.
  6. Marketing factory — AI-generated product videos, images, ad copy and Vietnamese voiceovers on a content calendar that posts itself.
  7. Observability — a daily AI briefing: sales, ad spend, stuck shipments, unanswered chats, invoice failures.

What "automated" actually means, order by order

Follow one order through the stack. A customer sees a TikTok video (generated last Tuesday by the marketing factory), clicks through, and asks the chat widget whether the 250 ml size ships to Đà Nẵng. The bot answers from your shipping-rate table, and the customer orders with COD.

Within a minute: the order webhook fires; the fulfilment service checks inventory, books a ViettelPost pickup for the next collection window at your registered kho (warehouse/pickup point), and prints a label to your thermal printer via a print agent. The customer gets a Zalo ZNS message with the tracking number. When ViettelPost's webhook reports delivered, the finance service issues the e-invoice through the MISA AMIS API and files it with the tax authority. At 07:00 the next day, your phone shows the AI briefing: 41 orders, 2 failed pickups (both rebooked), 1 invoice rejected for a malformed tax code (flagged for review).

You touched nothing.

The real-world traps (the reason this is an engineering project)

1. Carrier APIs fail quietly

ViettelPost's booking API occasionally accepts a pickup that no courier ever attends. The fix is not hope — it is a reconciliation job that compares "bookings made" with "status changes received" and rebooks or alerts after a timeout. Every carrier integration needs this shadow-audit pattern.

2. E-invoice rejections are data-quality problems

Under Decree 123 and its successors, e-invoices are validated on submission. Buyer tax codes, unit names and VAT rates must match exactly. Automation must include a pre-validation step and a human review queue for rejects — never silently drop them, because missing invoices are a compliance liability.

3. COD money is not revenue until reconciled

Carriers remit COD in batches with their own reference formats. An automated đối soát (reconciliation) job matches remittance lines to orders and surfaces the ones that never arrive — typically 0.5–2% of shipments, which is real money at scale.

4. Anything involving video needs redundancy in Vietnam

If your marketing relies on hosted video, serve it through at least two CDNs (for example Cloudflare and Bunny) with automatic failover. Domestic routing to individual CDN edges degrades unpredictably per ISP — a single-CDN setup will look broken to some fraction of your customers while working perfectly for you. We wrote a full deep dive on this.

5. Platform policies change under you

Zalo OA message templates need approval; TikTok API scopes get re-reviewed; Meta deprecates endpoints on a schedule. The architecture must isolate each platform behind an adapter so one policy change never halts the whole pipeline.

Build order that de-risks the project

PhaseScopePayoff
1Order → ViettelPost booking + tracking messagesHours saved daily; fewer missed pickups
2Order → e-invoice with review queueCompliance with zero typing
3Customer service bot with escalation24/7 answers; humans only on hard cases
4AI listing & content engineNew products live in minutes
5Marketing factory + daily briefingConsistent presence without a content team
Rule of thumbAutomate the flows that fire on every order first (shipping, invoices), then the flows that fire on every customer (chat), and only then the flows that fire on every campaign (marketing). Frequency determines return.

What stays human

Product selection, pricing strategy, supplier relationships and the creative direction of your brand. Automation removes the typing, not the judgement. That is exactly why it works: the machine does the 400 repetitive actions a day, and your attention goes where it compounds.

Want this running for your shop?

MERSO IT designs and builds exactly this stack — and for suitable projects we demonstrate the core workflow before any payment.

Talk to Mersoid, our AI consultant