Four Digits in a Five-Digit Field: Bangladeshi Post Codes in Online Forms

You are checking out on an international site. The address fields are labelled Street, City, State and ZIP code, and the ZIP field will not accept your four-digit post code. The page says it must be five digits.

The form is not describing a rule about your address. It is describing a rule about US addresses, applied to everyone, and it is the form that is wrong. That does not help you finish the order, so this guide covers both halves of the problem: what to do as the person filling it in, and what to do if you are the one who built it.

Why the field is five digits

A US ZIP code is five digits, so a form built for US customers validates five digits, and the validation often survives the day the business starts shipping internationally. Nobody removes it, because nothing in the US flow ever fails.

A Bangladeshi post code is four digits — Dhaka GPO is 1000 — and it is not a shortened version of anything. What the four digits name covers the format properly, but for form purposes the relevant fact is simply that four is the correct length and there is no fifth digit to supply.

The workarounds, and what each one breaks

When a field refuses a valid value, people improvise. Each of the usual improvisations produces a record that looks complete and is not.

• Adding a leading zero, turning 1000 into 01000. The value now belongs to no post office in Bangladesh, and any system that trims it back is guessing.
• Adding a trailing zero, turning 1000 into 10000. Worse, because the result looks like a plausible code and may collide with a real one elsewhere.
• Entering 0000 or 00000. An obviously empty value that still passes validation, so nobody downstream is warned.
• Copying a number from a search result, which attaches someone else’s delivery area to your address.
• Leaving the field blank where the form allows it, which is the least harmful of the five but loses the only structured routing data in the address.

The common thread is that all of them pass. Validation is satisfied, the order is placed, and the error surfaces at the point where somebody is trying to deliver a parcel — which is the most expensive place for it to surface and the furthest from anyone who could have fixed it.

The cost of a wrong code, in order of severity

Not every bad value costs the same. A missing code is the mildest case: the address still reads correctly, and in Bangladesh a complete written address with a mobile number is what carries most deliveries anyway.

A padded code is worse, because it is wrong rather than absent, and automated steps will act on it confidently. An outright borrowed code — one copied from a search result for somewhere else — is worst, since it points at a real office that has no reason to expect the item, and it can send a parcel into a sorting path that leads away from the destination before any person reads the address.

That ordering is useful when you have to choose. If a form will not take four digits and will not let you leave the field blank, the least damaging option is the one that is obviously empty rather than the one that looks plausible.

What to do as a customer

Look for a country selector before the address fields and set it first. Many forms switch their validation and their field labels when the country changes, and a form that looked broken simply had not been told where you are.

If there is no country selector, or the fields do not change, the form genuinely cannot handle a Bangladeshi address. At that point the honest options are to look for another route to the purchase, or to contact the seller and ask them to take the address another way.

Whatever you do, write the rest of the address completely: area, thana, district, and a mobile number. In practice that is what gets an item delivered in Bangladesh, and it is what gives a courier something to work from when the code is missing or wrong.

What to do if you built the form

The fix is not a longer regular expression. It is to stop treating one country’s format as the default.

• Ask for the country first, and choose the label and the validation from it. The field is a post code in Bangladesh, a postcode in Australia and a ZIP code in the United States, and the three are different lengths.
• Validate per country, or validate loosely. Four to ten characters of digits, letters and spaces accepts nearly every real format in the world and still rejects an empty field.
• Store the value as text. A post code is a label, not a quantity, and a numeric column is how leading zeros disappear in the countries that have them.
• Use a text input with a numeric keypad hint rather than an input of type number, which strips leading zeros and offers increment arrows nobody wants.
• Do not make the field required for every country. Several postal systems do not use codes at all, and a required field forces a fabricated value.
• Keep the thana and district fields separate and do not try to derive them from the code.

That last point deserves its own sentence. A form that fills in a district from a post code will be right often enough to look correct and wrong often enough to generate complaints, and the complaints will come from the customers whose addresses are already hardest to get right. Post code, thana and district covers why the two do not line up.

What a form that works looks like

The shape of a form that handles Bangladeshi addresses properly is not complicated. Country first. Then a street or area line with room for a village or holding number, a thana field, a district field, a post code field labelled with the local term, and a mobile number.

The post code field accepts four digits, is not marked required with a red asterisk that implies the order will fail without it, and is stored exactly as typed. The thana and district fields are independent of it. Nothing is autofilled silently; if you offer a suggestion, offer it as a suggestion the customer can reject.

Test it with a real address rather than a generated one. The quickest honest test is to take three addresses from different parts of the country, including one rural, and check that each can be entered without the customer having to lie to any field. If any of the three cannot, the form does not support Bangladesh, whatever the country dropdown claims.

Checking the code before you type it

If you are not sure of the post code for where you are, the detection tool returns the code covering the position your device reports, with the district beside it so you can sanity check the answer. It is a quick way to fill in a form correctly rather than from memory.

For anything consequential, confirm the code against the Bangladesh Post Office post code list. A location lookup answers which code covers a point; the Post Office answers which office delivers to an address, and on the edge of a delivery area those can differ.