A parcel that comes back because of an incomplete address costs postage, staff time and often the customer’s trust as well. Some of these errors do not happen on the road but minutes earlier, in the checkout address form: a four-digit postal code, a house number in the wrong field, a rear building nobody could enter. With Shopware 6.7.15.0, the browser now checks the postal code against the pattern stored for the respective country (Shopware). This guide shows how checkout address fields should be built so customers enter their address quickly and correctly: with autocomplete values for autofill, the right on-screen keyboard, an address line 2 that is there when it is needed, and error messages that help customers fix their input.
What delivery errors cost a store
How much trouble is tied to delivery shows in the activity report of the postal arbitration board at Germany’s Federal Network Agency: in 2025 it received 5,861 arbitration requests and other submissions (Bundesnetzagentur). The number of formal requests rose by 25.7% over the previous year to 4,804 (Bundesnetzagentur); 3,035 of them, a good 63%, concerned the loss or theft of a shipment (Bundesnetzagentur). The report does not say how many cases go back to a wrong address, and it only covers disputes that reach arbitration. It does show the scale, though, and cases that go back to a faulty entry in the store can be tackled in the form itself.
For customers, delivery is not a side issue. 53% of online shoppers say shipping and delivery are very important when choosing an online store (Bitkom). The survey covers 1,072 online shoppers aged 16 and over in Germany, interviewed in fall 2025 (Bitkom).
For merchants selling to consumers in Germany, there is also a legal side. When goods are shipped to a consumer, the risk of accidental loss passes to the buyer on handover to the carrier under § 475(2) of the German Civil Code (BGB) only if the buyer commissioned the carrier and the merchant did not name that carrier beforehand (gesetze-im-internet.de). In the usual case, where the store organizes shipping, the risk therefore stays with the merchant until the goods are handed over to the customer. Who is liable when a customer entered a wrong address is a question for the individual case and for legal advice. In practice, the effort for the return, the follow-up and the new shipment usually stays with the store.
Data protection also asks for correct data. Under Art. 5(1)(d) GDPR, personal data must be accurate and, where necessary, kept up to date (EUR-Lex). A form that catches obvious typos while they are being entered therefore serves both delivery and data quality.
First, less typing: autofill with the right autocomplete values. Second, correct typing: the right keyboard, a check against the pattern of the delivery country, clear messages. Third, room for special cases: an address line 2 that opens when needed and a hint for Packstation customers.
What Shopware 6.7.15 changes for the postal code
With version 6.7.15.0, Shopware has brought a small but effective change to the storefront. In the release news for October 2026, it appears in the section on further storefront improvements:
Shopware now uses the postal code patterns configured for each country for browser-side validation.
Shopware, Release News October 2026
According to Shopware, the form detects invalid entries when the form is submitted, and customers can correct them directly (Shopware).
The patterns themselves are stored per country in the administration as regular expressions; the documentation gives a pattern of exactly five digits and one of four digits and two letters as examples (Shopware). The storefront only applies a stored pattern to the form if postal code validation is switched on for the selected country, and when the country changes, it re-checks a postal code that has already been entered (Shopware).
It matters what the check does not do. A pattern determines whether an entry has the form of a postal code, not whether it exists and matches the city: “12345” and “12354” both have five digits. Catching transposed digits takes a comparison of postal code and city, for example as a list of city suggestions after the postal code has been entered. And the browser check does not replace the check on the server, more on that below.
If you use your own theme or a customized address form, check after the update to 6.7.15.0 whether the new check arrives there. Overridden templates do not pick up changes to the default form in every case. One test order per delivery country shows whether pattern and message work. For stores with many customizations, we handle this as a Shopware agency as part of the update review.
Autofill: fields the browser understands
The fastest address entry is the one the customer does not have to type. Browsers offer to fill in saved addresses, and the autocomplete attribute tells them which field expects what. The HTML specification describes the purpose like this: the attribute can hint to the browser how, or whether, it should help users fill in forms (WHATWG). Without the value, the browser has to guess which field is which, and that does not work in every form.
For accessibility, this is not optional polish. Success criterion 1.3.5 of WCAG 2.2 (level AA) requires that the purpose of input fields collecting information about the user can be programmatically determined when the field serves one of the purposes listed in the guideline (W3C). The list includes name, street address, postal code, city, country, phone and email, among others (W3C). People shopping with motor or cognitive impairments then do not have to type their address letter by letter. Which other criteria affect stores is summarized in our article on the new success criteria in WCAG 2.2.
The address fields at a glance
| Field | Value for autocomplete | Input and keyboard | Required |
|---|---|---|---|
| First name | given-name | Text | yes |
| Last name | family-name | Text | yes |
| Company | organization | Text | no, optional for consumers |
| Street and house number | address-line1 | Text | yes |
| Address line 2 | address-line2 | Text | no, behind a toggle |
| Postal code | postal-code | Text field, numeric keyboard only for purely numeric patterns | yes |
| City | address-level2 | Text | yes |
| Country | country | Select list | yes |
| Input type email | yes, for confirmation and shipping notice | ||
| Phone | tel | Input type tel | only if the delivery method requires it |
Two details decide whether autofill works cleanly. First, the assignment to the address block: with the prefix token shipping or billing, the form marks whether a field belongs to the shipping or the billing address (WHATWG). Without this token in a form with both addresses, the browser cannot tell the blocks apart. Second, the field layout: the specification knows both street-address for a multi-line address in one field and address-line1 to address-line3 for an address spread over several single-line fields (WHATWG). Which variant fits depends on the form; what matters is that field and value match.
<label for="ship-name">Full name</label>
<input id="ship-name" name="shipping[name]" autocomplete="shipping name">
<label for="ship-street">Street and house number</label>
<input id="ship-street" name="shipping[street]" autocomplete="shipping address-line1">
<!-- inputmode and pattern only while the selected country has a purely numeric pattern -->
<label for="ship-zip">Postal code</label>
<input id="ship-zip" name="shipping[zipcode]" autocomplete="shipping postal-code"
inputmode="numeric" pattern="[0-9]{5}" aria-describedby="ship-zip-hint">
<p id="ship-zip-hint">Five digits, for example 12345</p>
<label for="ship-city">City</label>
<input id="ship-city" name="shipping[city]" autocomplete="shipping address-level2"> The right on-screen keyboard
On a smartphone, the on-screen keyboard has a say in how many typos happen. And the smartphone is the device used most for online shopping: 73% of online shoppers use a smartphone for shopping, more than any other device (Bitkom). Multiple answers were possible in the survey, so many shop on several devices. What mobile first means beyond that is covered in our article on mobile commerce.
There are two tools for the right keyboard. The inputmode attribute sets which input aid is shown; according to the specification, the value numeric stands for a keyboard for entering digits (WHATWG). The input types email and tel bring suitable keyboards with an @ key or a dial pad for email address and phone number.
For the postal code, type=number seems obvious and is still wrong. The HTML specification makes clear that this type is not meant for input that merely happens to consist of digits, and it names US postal codes as an example (WHATWG). A number field shows arrows for counting up and down on the desktop, can lose a leading zero depending on further processing and does not accept letters.
Stores with several delivery countries need to be careful: inputmode=numeric only fits while the selected country has purely numeric postal codes. Germany’s current postal code system was introduced on July 1, 1993, and the first two digits denote the routing region (Bundesregierung). It uses no letters, so a numeric keyboard fits there. For a format with letters, such as the pattern of four digits and two letters from the Shopware documentation, a digits-only keyboard effectively blocks the input. A clean form ties pattern, keyboard and hint text to the country selection and therefore asks for the country before the postal code or re-evaluates on a change.
Many stores ship mostly to one country. Then a preselected country with a visible way to change it above the postal code is a good compromise: the keyboard fits for most customers, and anyone ordering from abroad sees right away where to change the country. When the country changes, pattern, keyboard and hint change with it.
Name, street and house number
For the name, stores usually stick with two fields for first and last name, because salutation, invoice and shipping label need them separately. What matters is that both fields accept characters that occur in real names, such as hyphens, apostrophes and accents. For stores selling to consumers, a company field belongs in the optional part, with the value organization.
For street and house number, there are two common designs: one combined field or two separate ones. The combined field is faster to fill in and also fits addresses with additions such as “12a” or “12–14”. Separate fields, on the other hand, make the handover to shipping interfaces that expect street and house number individually easier, and they make a missing house number visible right away.
If you stick with the combined field, you can still catch a missing house number: with a friendly hint when the field contains no digit, instead of a hard block. There are addresses without a house number, for example on farms, in some business parks or abroad. A hint such as “Please check the house number” with the option to continue anyway catches typos and locks nobody out.
Address line 2: optional and easy to find
With address line 2, stores easily fall into one of two traps. Either the field is missing altogether, and “c/o”, “rear building” or “side entrance” end up in the street line or not in the form at all. Or it appears as an equally weighted required field, and customers type in anything just to move on.
The middle ground: the field is optional and sits behind a toggle such as “Add address line 2” directly below the street line. Customers who need it find it where they look for it; everyone else sees one field fewer. Two conditions apply. The expanded field gets a visible label and the value address-line2. And if a value is already saved, for example in the customer account or via autofill, the field is open from the start, because a filled but hidden line can no longer be checked by the customer.
Technically, the toggle is a button with aria-expanded, not a link to nowhere, and it needs a size that can be hit on a smartphone. WCAG 2.2 requires in criterion 2.5.8 that pointer targets be at least 24 by 24 CSS pixels unless one of the exceptions listed there applies (W3C).
In Shopware, two additional address lines can be shown in the login and registration settings and each marked as required (Shopware). As a required field, the extra line is usually the wrong choice for consumers. For B2B stores, where department or receiving dock are needed regularly, a visible field can make sense. Expanding the field behind a toggle can be added in the theme.
Packstation in the address form
Some customers do not want delivery to their front door at all. Offering the pickup point as a separate delivery method with a location search solves this cleanly; how to set that up is described in our article on parcel shops and pickup lockers in checkout. The Packstation still ends up in the regular address form, because customers type it in there by hand.
DHL describes a fixed scheme for this: after the name, the personal post number goes into the address suffix field (DHL). The street field takes “Packstation”, the house number field the number of the chosen station, plus postal code and city of the station (DHL). If there is no address suffix field, DHL says customers should add the post number after the last name, separated by a space (DHL). A form without address line 2 therefore forces Packstation customers to write their customer number into the name field, and from there it travels into every document that shows the name of the delivery address.
The form can help here without being patronizing. If it detects the word “Packstation” in the street line, it shows a hint that the post number belongs in address line 2 and opens that field. Automatically rewriting the input, on the other hand, is risky: the customer should see and confirm what will be printed on the label.
The scheme is about to change: DHL announces that recipients will be able to choose a DHL Packstation directly as their delivery address, even without registration and a post number (DHL). According to DHL, they receive the pickup code via the email address provided (DHL). For use without a post number, DHL names a business customer contract as a prerequisite (DHL). The store should also make sure that the email address may be used for shipment-related communication and for providing the pickup code (DHL); this belongs in the checkout’s privacy information.
For the form, this means the post number becomes optional, and the email address has to go to the carrier with the shipment data. How your shipping integration maps this is something we clarify when connecting the shipping interface.
Error messages that help with corrections
The check in the browser is only as good as its message. WCAG 2.2 requires in criterion 3.3.1 that an automatically detected input error identifies the item in error and describes the error to the user in text (W3C). Criterion 3.3.3 goes further: if suggestions for correction are known, they are provided, unless this would jeopardize the security or purpose of the content (W3C). For a postal code, the suggestion is known in practically every case, namely the format the selected country expects.
- Specific rather than general: “Postal codes for Germany have five digits” instead of “Invalid input”.
- At the field, not only at the top of the page: the message appears directly below the field and is linked with
aria-describedby; a summary above the form can also point to the fields. - Not by color alone: a red border on its own is not enough, an icon and text belong with it.
- At the right moment: checks run when the field is left or the form is submitted, not on every keystroke.
- Input stays put: after an error, the rest of the form stays filled in, and the focus moves to the first field in error.
This includes a visible label above every field. WCAG 2.2 requires in criterion 3.3.2 that labels or instructions are provided when content requires user input (W3C). A placeholder in the field that disappears while typing does not replace a label: at the latest during the correction, the customer no longer knows what belonged in which field. How forms across the whole store can be tested with keyboard and screen reader is shown on our page on accessibility under the BFSG.
Delivery address and billing address
Many consumers order to their own address. Then a preselected option “billing address is the same as delivery address” is the simplest solution, and the second address only opens when needed. WCAG 2.2 puts the idea into criterion 3.3.7: information previously entered in the same process is either auto-populated or available for selection instead of being asked for again (W3C).
For regular customers, the same applies beyond the single process: saved addresses from the customer account appear as a selection, the most recently used one first. Whether an account is needed for the purchase at all is discussed in our article on guest checkout without a mandatory account.
On the invoice, the billing address counts. If you switch to the new document generation in Shopware, take the opportunity to check which address fields end up on the documents, including address line 2; what changes there is described in our article on document generation v2 in Shopware.
What is checked after submission
A check in the browser improves input, it does not protect the data. After submission, the server checks the same rules again, for every path by which addresses reach the store: checkout, customer account, marketplace interfaces and imports from the ERP system. Whether this holds for all input paths in your own store belongs in the test before going live.
If you want to go a step further, you compare postal code, city and street against a street directory. That catches transposed digits no pattern sees and allows suggestions such as “Did you mean …?”. Three rules apply. The comparison suggests and does not overwrite. The customer has the final say, because directories often know new streets only with a delay. And if the comparison runs through an external service, passing on the address needs a data protection review, including data minimization under Art. 5(1)(c) GDPR (EUR-Lex).
In the end, the checked address has to arrive unchanged where the label is created. How store, ERP system and shipping software hand over address data is described in our article on shipping interfaces and logistics APIs.
Measuring where addresses fail
Whether the changes work is not shown by a single test but by an evaluation over several weeks. Three sources already exist in many stores:
- Carrier returns: shipments with return reasons such as “recipient unknown” or “address incomplete”, counted per month and related to the number of shipments.
- Address corrections in customer service: how often customers ask for an address change after ordering, and for which fields.
- Messages in the form: which check fires how often, without storing the input itself. A cluster at the postal code of one country points to a wrong pattern or an unsuitable keyboard.
What matters is the comparison before and after a change, not the absolute value. The arbitration board’s report shows the scale of the topic; for your own store, your own rate counts. When the form is adjusted, the date belongs in the evaluation so the effect can be separated from seasonal swings such as Black Week.
Checklist for the address form
- Every field has a visible label and a suitable
autocompletevalue; the shipping and billing blocks carryshippingandbilling. - The country comes before the postal code or is preselected; pattern, keyboard and hint follow it.
- The postal code is a text field, not a number field;
inputmode=numericonly for purely numeric patterns. - From Shopware 6.7.15.0: browser check verified with one test order per delivery country, including in your own theme.
- Address line 2 optional behind a toggle, open from the start when a value is saved.
- Hint for “Packstation” in the street line; post number in address line 2, optional once the announced direct addressing arrives.
- Error messages specific, right at the field, as text and with a suggestion.
- Billing address preselected as identical to the delivery address.
- The server checks the same rules for checkout, customer account, interfaces and imports.
- Carrier returns and address corrections are counted monthly.
How we review address forms in your store
We go through your store’s address form field by field: labels, autocomplete values, keyboards on smartphone and tablet, error messages and the behavior for delivery countries with their own postal code formats. For Shopware stores, we check after the update to 6.7.15.0 whether the new check arrives in your own theme, and we implement adjustments such as the expandable address line 2 or the Packstation hint in the theme.
Form review
Fields, labels, autocomplete values and keyboards, tested on real devices and with the keyboard.
Implementation in the theme
Expandable address line 2, hints for Packstation and house number, messages per delivery country, built through custom programming.
Delivery countries and handover
Postal code patterns per country and the handover of the address to ERP system and shipping integration all the way to the label.
It starts with a short review using test orders for each delivery country. After that, you know which spots in the form encourage delivery errors and how much effort the changes take.
This article is based on Shopware’s release news for October 2026 (version 6.7.15.0), the Shopware documentation on country settings and the login and registration configuration and the storefront country selection in the Shopware source code, the WHATWG HTML specification (autofill, inputmode, input type number), the W3C Web Content Accessibility Guidelines 2.2, the 2025 activity report of the postal arbitration board at the Bundesnetzagentur (as of January 2026), the Bitkom study report “Digitaler Handel in Deutschland” (survey of 1,120 people aged 16 and over, including 1,072 online shoppers, fall 2025), DHL’s pages on receiving parcels at a Packstation and on direct addressing without a post number, a German federal government answer on the postal code system (Bundestag printed paper 14/1027), as well as § 475 BGB on gesetze-im-internet.de and the GDPR on EUR-Lex. All information retrieved on November 3, 2026.
From version 6.7.15.0, Shopware also uses the postal code patterns stored in the country settings for a check in the browser (Shopware). As a rule, this requires that a pattern is maintained for the country and the check is enabled. For stores with their own theme, it is worth testing whether the check arrives in the customized form.
Only if the entry does not match the pattern. A postal code with the right number of digits that belongs to another city is not caught by a pattern. That takes a comparison of postal code and city, for example as a list of city suggestions.
Common ones are given-name and family-name or name, address-line1 or street-address, postal-code, address-level2 for the city and country, plus email and, if needed, tel (WHATWG). With separate shipping and billing addresses, shipping or billing goes in front.
For stores selling to consumers, usually not. A good fit is an optional field behind a toggle such as “Add address line 2” that opens by itself when a value is saved. In B2B stores where department or receiving dock are needed regularly, a visible field can make more sense.
Most cleanly through a separate delivery method with a location search. In the regular address form, DHL describes the scheme like this: post number in the address suffix, “Packstation” in the street field and the station number as the house number (DHL). According to DHL, delivery to a Packstation is to become possible without a post number as well (DHL).
No. It helps during input but can be bypassed, and addresses also reach the store through customer accounts, interfaces and imports. The server checks the same rules again. If you want to know where your form stands, write to us via the contact page.