Cash on Delivery in Vietnam: Ward-Level Logistics

Vietnamese addresses have three levels and carriers want all of them

Vietnam is administratively divided into provinces, then districts, then wards. Carriers route on the lower two levels, and they identify them by code rather than by name.

This is the single most common integration failure for sellers entering the market. A parcel addressed to Ho Chi Minh City is not addressable. The carrier needs the district and the ward beneath it, and it will not infer them from a street address.

Vietnamese district names also collide in ways that punish naive matching. A system searching an address for a district called District 1 will happily match inside District 10, and the parcel goes to the wrong side of the city. Matching has to prefer the longest name, not the first one found.

• Capture province, district and ward as three separate fields
• Resolve them against the carrier's own list rather than free text
• Prefer the longest matching district name to avoid District 1 and District 10 collisions
• Fail loudly at confirmation rather than guessing at dispatch

Vietnamese COD is driven by social and live commerce

A large share of Vietnamese online selling happens inside social platforms and live sessions rather than on a conventional storefront. Orders arrive as messages, often in bursts during and immediately after a broadcast.

That shapes the operation more than the payment method does. Demand is spiky, the buyer's intent decays quickly once the session ends, and the seller who replies during the burst captures orders that a seller replying an hour later does not.

It also means order details arrive conversationally and incompletely. The address is rarely given in one clean message, so assembling a routable three-level address from a scattered chat is core work, not an edge case.

Confirm fast, because intent decays with the broadcast

In markets where orders come from a checkout page, a confirmation delay of a few hours is survivable. In a live-commerce market it is not. The buyer's enthusiasm was generated by a moment, and the moment has passed.

The practical target is a reply inside the session or immediately after it, with the address resolved before the buyer disengages. Every hour after that measurably reduces the share of orders that ever ship.

Decide who pays the shipping before the buyer does

Vietnamese COD carries a convention that surprises sellers from other markets: the shipping fee is frequently collected from the buyer by the courier, on top of the goods, rather than absorbed into the advertised price.

That convention is workable, but only if the buyer knows about it before the courier arrives. A buyer who agreed a price in a live session and is then asked for an additional freight charge at the door has been given a reason to refuse.

Whichever model you choose, state the total the buyer will hand over as a single number during confirmation. The refusals in this market cluster tightly around buyers being asked for more than they expected.

Frequently Asked Questions

Why does my Vietnamese carrier reject the city name? Because Vietnamese carriers route on district and ward codes rather than city names. A province alone, or a city name alone, is not a routable destination.

What is a ward code? It is the identifier for the smallest administrative level in a Vietnamese address, sitting beneath the district. Carriers require it, and it must come from the carrier's own reference data rather than from free text.

Why do my parcels for District 1 end up in District 10? Because naive text matching finds District 1 inside District 10. Matching should always prefer the longest candidate name.

How quickly should I confirm orders from a live session? Inside the session or immediately after. Live-commerce intent decays fast, and orders confirmed hours later convert far less often.