An address does not always have a street and a postcode. Forms for different countries
Design address forms for supported countries, with local fields, manual entry and safe corrections when formats change.
Article language: English

In this article
A customer has known their address for twenty years. Five seconds into a form, they are told it is wrong. There is no postcode, the building number contains a letter, and the building name does not fit in the “Street” field. International sales stop at the edge of a Polish template.
Imagine a fictional studio that frames archival photographs. Customers in different markets request a quote and, once they accept it, provide an address for the return of the originals. The studio needs information for a specific task. It does not need a complete address when someone merely asks about a frame. For the return, however, it must retain the information that the person preparing the parcel will use.
Make that decision before drawing the fields. Start designing a form with Aeneia Design by asking what happens next to each part of the stored address. “We have always had that field” describes a habit, not a need.
Country changes the question, not just the label
If the format depends on a country or territory, let people choose it before entering the address details. Do not infer a Polish location from the language of the page, though. A Polish speaker may be ordering for an office outside Poland. An English version of a site does not tell you where the parcel should go either. The language used for the service does not determine the photographs' return address.
The official Macao Post FAQ is a useful reminder: Macao does not use postcodes. A required field that accepts only five Polish digits and a hyphen therefore does not verify every international address. It tests an assumption that is too narrow.
Do not fix this with “make one up if you do not have a postcode”. The studio's form should know that a postcode may not apply to a supported format. The database needs to distinguish “not applicable” from a missing answer. Six zeros imposed by the site do not become the customer's verified postcode.
Selecting a country does not settle the address structure on its own. The official Korean address guide describes a structure with a road name, building number and additions such as floor and unit. It also explains how to write addresses in English. This is a specific local model; translating Polish labels is not enough to reconstruct it.
When someone changes the country, do not silently erase everything they have entered. They changed a selection, perhaps by mistake; they did not decide to delete the address. Show which fields need checking again. If values cannot be moved without guessing, keep the previous entry available to copy or restore. A unit number should not disappear because its position in the layout changed.
Consider one correction. A customer selected Poland, pasted the address of a branch abroad, then noticed the wrong country. After changing it, they see new labels. The design should show the previous text and ask them to assign it to the right places if an automatic split would be uncertain. Moving the third line into the third field simply because both are numbered three is not enough.
If the user changes the country back, check whether they get the earlier address or the corrected version. Decide this in the design, then walk through the scenario with the implementer. Without that decision, two implementers may interpret the preservation rule differently. The studio may not notice until it prepares the return, rather late to experiment with the form's memory.
Separate fields make sense when you use them separately
At the studio, the first proposal sounds convenient: one large box into which the customer pastes the whole address. It is easy to copy from a message. Trouble starts if the next tool requires the town, postcode and remaining lines separately. Someone then has to split the text. The interface has not removed the work; it has handed it to the person packing the parcel.
The GOV.UK Design System distinguishes address lookup, multiple fields and a larger text area. The last option accommodates a wide range of formats when precisely separated parts are not needed. Its guidance warns against using it where that separation is necessary.
Start with whoever receives the data. If a team reads the address and writes it on an envelope by hand, free text may be enough. If it is passed automatically to another service, check that service's actual requirements for the places you support. A tidy form alone does not show that the data will make it through the whole process.
Leave room for a building name, branch and internal recipient too. In our example, the photographs must return to a conservation workshop within a larger institution. An address without the department name may be formally complete for one system but not very helpful to the person sorting incoming mail. Check where that information ends up in the saved result.
Do not make every part a separate question for everyone. A “voivodeship” field shown in every market asks the recipient to solve a Polish administrative puzzle. Labels and required fields must follow the model supported for the location. If the team cannot justify a field for a place, it should not demand an answer under threat of a red border.
Distinguish an address identifier from a quantity. “12B” identifies a place, and “0012” may need its leading zeros preserved in a particular address. Do not automatically apply the rules for entering numbers and decimal separators (in Polish) (article in Polish). A field containing digits does not necessarily contain a number for calculation.

The Scottish design system, updated 24 June 2026, recommends identifying the purpose of manual fields with the autocomplete attribute. A browser can then fill an address provided earlier. That helps with entry; it does not verify the data or justify taking away the user's ability to change it.
Check a browser-filled address too. Does the institution name land on the right line? Does the selected country match the other information? If fields hidden for the previous format become relevant, the interface must show what needs completing. Nobody should discover a missing unit number only after submitting. Manual entry and autofill lead to the same saved address, so both paths belong in acceptance testing.
When lookup does not know the customer's door
Address suggestions can be convenient: type a fragment, choose a result and receive completed lines. The design must also cover an address that the service cannot find. A new building is not imaginary simply because it has not reached someone's database. No result describes a search; it does not prove that the user's home is fictional.
On the results screen, offer a visible route to manual entry. Keep it available when suggestions are similar but wrong, too. A user may not want any of them. Distinguish no match from a service failure: in the latter case, explain that lookup is unavailable now and that the address can still be entered manually.
Do not make people repeat data when they take that route. If the customer has already typed a town, preserve it as their own text. Do not automatically treat the first suggestion as an accepted address, however. A highlighted result and a deliberate choice are different states. In the prototype, test Enter as well, so an attempt to choose a suggestion does not submit the form.
After selection, show the address in readable form and allow corrections. An external service's identifier is not enough for someone checking a unit number. Editing should preserve what the user confirmed. If another lookup will replace manual additions, say so before replacing them and let the person keep their own entry.
Define the supported area as well. If the studio really accepts returns only to selected places, say so before asking for a long address. That is a different restriction from an address being absent from suggestions. The article on delivery and collection (in Polish) (in Polish) helps decide which method is available; here the question is whether the selected address can be stored correctly.
Aeneia Design
We will design an address form for the agreed markets: its data structure, manual entry, corrections and unavailable-lookup states. With the implementer, we will check whether the saved result retains the information needed for the next step. Design a form that accepts your customers' addresses
Corrections should help find the place
Validation, the checking of entered data, should point to a problem a person can fix. “Invalid address” does not say what to do. If a town required by the selected format is missing, name it. If a limit comes from the line length in the next tool, explain the limit and leave the text available for correction. Do not automatically cut off the end of a building name.
Consider which changes merely tidy the entry and which change the data. Removing an accidental trailing space is not the same as replacing a town name with a suggested alternative. For a substantive correction, show the difference and offer a choice. Do not present a suggestion as an established fact merely because it came from an external service.
Allow suitable scripts where the process supports them. If a specific service needs an additional Latin-script version, ask for it separately and explain why. Translating page labels does not convert the characters in the address itself into Latin script. Combining fragments with different reading directions needs extra care, described in the article on names, codes and addresses in two directions (in Polish) (in Polish).
On the confirmation screen, show the exact address that was saved. Then check its appearance in the message to the customer. Lines should not run together into an unreadable string. That is a separate requirement for email template design (in Polish) (article in Polish), because a good display in the form does not guarantee a good one in email.
Before acceptance, prepare examples for the formats actually supported. Enter a long building and unit name, an address without a postcode where none is used, a search with no result, and a country change after completing the fields. Save and return to read the result. Compare the contents, not just green ticks. They are polite, but they do not deliver parcels.
In that test, compare the address after reopening the saved request as well. The success screen may have shown text from the page's memory while the server stored a different version. Reading the request again shows whether the conservation workshop detail actually survived. Use data prepared for the test; a random customer's private address is not needed to check wrapping and line preservation.
If a real address still cannot be entered, provide a way to contact support and the number of the request already started. The person helping should see where the problem arose without asking the customer to repeat the whole conversation. Do not automatically announce that the address has been accepted for the return, though. Someone must first resolve the missing information and confirm the next step with the customer.
At the beginning of the journey, leave a short B2B contact form (in Polish) (article in Polish). Someone merely asking whether a family photograph can be framed does not need to prove that their staircase exists straight away.







