Hosting in Vietnam

Vietnamese WordPress hosting where payment happens at the door.

Cash on delivery means the order is not paid when it ships and may never be paid at all. The customer decides at the doorstep, days later.

Orders open until deliveryRefusals recordedStock held meanwhile
COD lifecycleCourier updatesStock holdingDaily backupsFree SSL24/7 support
Built for cash on delivery

The sale finishes at the door.

Every ecommerce assumption about payment preceding fulfilment is inverted here.

Orders that stay open for days

An order ships unpaid and settles when the courier collects cash. Its lifecycle is measured in days with several intermediate states rather than paid or unpaid.

Multi-day states

Refusals recorded as outcomes

A meaningful share of COD orders are declined at the door. That is a normal outcome needing a state and a stock return, not an error.

Return to stock

Courier status updates absorbed

Delivery progress arrives as callbacks from the courier. Those have to be reachable and idempotent, since the same update often arrives twice.

Stock committed before payment

Inventory is held for goods that may come back, so availability reflects what is genuinely sellable rather than what has been paid for.

An origin in the region

Checkout and account pages always reach the origin, and Vietnam is well served from within Asia.

Unpaid orders

Fulfilled, not yet sold.

A store treating shipment as completion overstates revenue and understates stock. Neither is visible until somebody reconciles the courier's remittance against the order list.

  • Order states covering the full COD lifecycle
  • Refusals recorded with stock returned
  • Courier callbacks reachable and idempotent
  • Stock reflecting genuinely sellable goods
Order states
COD lifecycle
modelled
Refusals
Recorded
with returns
Courier callbacks
Idempotent
yes
Reconciliation
Remittance
running
Reconciliation

Revenue is what was collected.

The number that matters is not orders placed but cash remitted, and the gap between them is the entire operational challenge.

Modelled
full COD lifecycle
Idempotent
courier callbacks
Asia
origin region
MagicWP115 ms
Typical shared host1180 ms
European origin serving Vietnam490 ms

Illustrative comparison of a checkout request from a Vietnamese connection. Your numbers depend on origin placement and payment flow.

Configuration

What we change for Vietnamese stores

Payment arriving after delivery rather than before it changes what an order means at every stage.

SettingWhat we doWhy
Order lifecycleStates covering shipped, delivered, refused and remittedCash on delivery means an order can be fulfilled and never paid, so paid-or-unpaid cannot describe where it actually is.
Refusal handlingRecorded as an outcome with stock returnedDoorstep refusals are a routine share of COD volume, and treating them as failures leaves inventory committed to goods sitting in a warehouse.
Courier callbacksReachable and idempotentDelivery updates arrive as machine requests and frequently arrive twice, so a non-idempotent handler double-counts or double-returns stock.
Stock commitmentReflecting sellable rather than paid goodsInventory is held against orders that may come back, so availability has to account for goods in transit both ways.
Origin regionAsia rather than a distant originCheckout and account pages always reach the origin, and those are the requests where distance is felt.
Plans

Simple, transparent pricing.

Every plan includes free migration, daily backups, SSL and 24/7 support.

MonthlyYearly 2 months free
Starter
For personal sites, blogs, and portfolios.
$20/mo
  • 1 WordPress site
  • 10 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Support tickets
Start free trial
Pro★ Most popular
For growing businesses and busy stores.
$80/mo
  • 5 WordPress sites
  • 50 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Priority support tickets
Start free trial
Enterprise
For agencies and high-traffic platforms.
$250/mo
  • 20 WordPress sites
  • 200 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Dedicated support
Start free trial
FAQ

Questions, answered.

Why is paid-or-unpaid not enough for COD?
Because an order can be shipped, delivered and still unpaid, or refused at the door and coming back. The lifecycle needs states for each of those, not a boolean.
What happens when a customer refuses delivery?
It is recorded as an outcome and the stock returns to sellable. Treated as an error instead, inventory stays committed to goods sitting in a warehouse.
Do courier updates arrive twice?
Regularly, which is why the handler is idempotent. A non-idempotent one double-counts a delivery or returns the same stock twice.
How should I read revenue on a COD store?
As cash remitted rather than orders placed. The gap between the two is the operational reality, and treating shipment as completion overstates both revenue and availability.

Count the cash, not the shipment.

Move the store to an Asia origin — migration is free, order states modelled.