DLVX Academy · Guide preview

Extract Thai delivery addresses without inventing the missing parts

Preserve original address text, separate landmarks from postal fields, and use maps as evidence rather than proof of delivery.

A starting point

A fictional customer sends an address in Thai, a building name in English and a map pin in a separate message. Another line says to use the rear entrance. AI translates everything into one polished English address, drops the unit number and picks the first map result with the building name. The output looks easier to read, but it is...

A tidy address can be the wrong address

Address extraction should preserve evidence before improving presentation. Keep the original text intact, including number separators, floor and unit details. Create structured fields beside it rather than replacing it. A translated version is a convenience for a reader, not the master record for the delivery.

The worked examples below use invented building details and deliberately incomplete addresses. They are not valid delivery destinations. Any Thai wording used in your actual operation needs a native reviewer, particularly when the request mixes abbreviations, romanised names and instructions that a literal translation could misread.

Split destination, contact and access instructions

A delivery record needs different kinds of information that don't belong in the same field. The postal address identifies the destination. A unit or floor identifies the recipient's place inside it. A pin suggests a geographic point. An entrance instruction tells a driver how to approach. A phone number provides a contact route under your service process. Keep those separate so later steps don't discard useful detail as irrelevant text.

For an illustrative message, suppose the customer writes “River Court, building B, unit 12/34, floor 8, use rear entrance,” attaches Thai street text, and sends a pin. Extract unit “12/34” as a string. Do not turn it into a fraction, remove the slash, or assume it means building twelve and apartment thirty-four. Preserve the wording when the interpretation is uncertain.

Likewise, “near the station” is a landmark, not a district. A missing postcode remains missing. Don't complete a postcode from a remembered association with a neighbourhood. The destination may span administrative boundaries, the building name may be duplicated, or the customer may have sent an old address. Ask for the missing detail that the actual carrier or delivery process requires.

Use geocoding to find discrepancies

Google's Geocoding documentation, checked 20 October 2026, describes results with different location types and a possible partial_match flag. A returned coordinate is not a universal certificate that a complete, deliverable address was supplied. Inspect the match and the parts of the address it actually resolved.

In the fictional case, the map result points to the front of a similarly named building, while the customer's pin points to a rear access road elsewhere. The assistant should report a conflict, not average the coordinates or choose the more confident-looking result. The next question can be specific: “Your pin and the written building name appear to indicate different locations. Which should the driver use, and is building B at that location?”

Even a correct building location doesn't identify the right tower, loading point or recipient. Use the customer's confirmation and the delivery team's current operating information to settle those details. If the service only needs a verified pin and a local phone contact, don't demand unnecessary postal fields simply because the model's schema has them.

Inside this guide: what comes next

  • Copy an extraction prompt that allows blanks
  • Show the customer what matters before dispatch
  • Test with messy addresses, not perfect forms
  • Sources and dates

Read the full guide

A free Academy account opens the full guide and practice lessons.

Create a free account Already a member? Sign in

No newsletter subscription. We use your email for sign-in and account messages.