Separate formatting from destination verification
A formatted address is a representation of a destination, not proof that the destination exists or that a selected service can deliver there. UPU’s Postal Addressing Systems guidance points users to destination-country practices. Formatting, reference verification and carrier eligibility therefore need separate decisions.
CEP Insight recommends agreeing the receiving party’s address components first, then producing a channel-specific representation. A renderer should change the arrangement of confirmed information without silently changing the intended recipient, building or unit.
Read China’s address hierarchy with its date
The September 2013 UPU China sheet describes six-digit postcodes, Chinese large-to-small geographical order and reversed Latin-script order. It is historical guidance, not a current address register.
For a China-bound order, ask the recipient to confirm province, city, district or county, locality, street or village, building and room where applicable. Preserve distinctions between a street number, a building number and a room number. Do not copy a named place or postcode from a historical example into a live shipment.
Distinguish translation, transliteration and channel rules
USPS’s preparation page asks for English address text. International Mail Manual 122 also specifies Roman-character rendering when an English translation is unknown. These are USPS rules, not universal carrier requirements.
Translation explains meaning; transliteration represents words in another script. Treat both as derived views of the confirmed address. Do not translate a building’s proper name into an unconfirmed new identity. Check which view the contracted channel accepts and retain the confirmed original within permitted data retention. Where the channel supports both scripts, test their mapping and presentation together.
Map components before composing label lines
The following is a CEP Insight proposal for checking transformations. Field names and available lengths depend on the actual carrier interface; the table does not specify a universal API schema.
Separate recipient and return addresses. Keep contact and entrance instructions in their agreed fields. If a field limit cannot accommodate an essential component, route the case for review instead of silently deleting the component.
| Record or view | Purpose | Review point |
|---|---|---|
| Original input | Preserve the customer’s submitted text | Do not overwrite it with a generated label |
| Confirmed components | Identify the intended recipient and destination | Separate building, unit, street and locality |
| Derived script view | Support the agreed language or character set | Keep a traceable link to confirmed components |
| Carrier request | Populate the selected interface | Check field mapping, length and required data |
| Rendered label | Present the shipment address | Inspect characters, line breaks and retained detail |
CEP Insight proposed review method; not a certified implementation or carrier specification.
Test what survives the complete label process
Use fictional cases for functional tests and authorized examples for operational review. Include a leading-zero postcode, a non-Latin place name, a building-and-room combination, an unusually long address and a change made after a label was created. These are test categories, not observed failure rates.
Compare the confirmed record, outbound request, returned label and actual printed output. Check character encoding, glyph availability, line breaks, clipping and component loss. An accepted API request alone does not establish that the printed address remains complete. Recheck the affected documents and handoff after a material edit; keep the carrier’s acceptance decision separate.
Record the source and limits of each rule
Record source URL, market, channel, edition, review date and the transformation it supports. A current access date does not make a historical document a current postcode or street database. For live orders, verify the address and service through current recipient and carrier evidence.
The four sources were reviewed on 12 October 2026. The UPU China sheet bears September 2013; the other cited pages do not state a single publication date for all their content. This article reviews the cited addressing sections, not every linked standard or contract. Mapping and test proposals are CEP Insight analysis; no carrier integration, printer test, shipment trial or delivery guarantee is reported.
Conclusions
Preserve the confirmed address, derive the representation required by the selected channel, and inspect the full printed label before release. Formatting alone does not establish deliverability.
Sources & further reading
Industry knowledge and interpretation; carrier terms and local requirements vary.
Sources reviewed:
- UPU — Postal Addressing Systems: destination-country guidance; addressing overview
- UPU — China address sheet; September 2013; historical format examples, not a current address register
- USPS — Preparing international shipments, Step 4: Write the Address; U.S. outbound postal channel
- USPS — International Mail Manual 122: addressing and Roman-character alternative; U.S. outbound postal channel
Enquiries related to this article
This article can provide background for an industry, research or cooperation enquiry. Review and edit the brief before contacting the team.
Prepare a brief with this readingContact CEP Insight
WhatsApp and Telegram inquiries are received through the Jeton Express account.