A customer taps a saved address and their surname lands in the company box. Or they choose a delivery address and the billing details change too. They can correct the fields, but the next step changes them back.
If your website behaves like this, start by finding where the wrong value appears: in the browser suggestion, in the form after selection, or in the record your team receives. Each points to a different investigation. Replacing the whole checkout or switching off autofill is a large response to a problem that may sit in a few fields.
First, identify which feature is filling the form
Browser autofill uses saved personal details. A postcode lookup searches an address service. A signed-in customer account can supply another set of details. These can appear on the same checkout, so record the exact action that introduces the mistake.
Use a controlled test with details you have permission to use. Try the form once by typing, then again by choosing a saved browser suggestion. For a checkout, repeat with the account signed out and signed in. Keep the basket and delivery option consistent so you can compare the same journey.
- The suggestion already contains an old address: inspect the saved browser profile before changing the website.
- The suggestion is correct but lands in the wrong box: investigate how the website identifies and groups its fields.
- The fields look correct but the order or enquiry is wrong: compare the submitted values with the receiving system.
These are starting points, rather than proof of a cause. A useful fault report includes the page URL, device, browser version, chosen suggestion and first moment the result differs from what was expected.
Check the saved details before changing the website
MDN’s autocomplete reference explains that suggestions can come from previous entries or information configured in the browser. The website provides guidance about the expected information; it does not own every saved suggestion.
Check whether the selected profile actually contains the intended name, email and address. Work and home profiles are particularly worth separating during testing. Compare a second known profile on the same form: does the wrong field receive both sets of details, or does only one saved profile produce the problem?
If correcting an outdated saved address resolves one person’s issue, record that outcome. If different people can reproduce the same misplaced value, give the developer that evidence. Avoid asking customers to delete all their saved information as the routine workaround.
Give each field a clear purpose in the code
A visible label tells the customer what to enter. The underlying field also needs a meaningful identity. Google’s payment and address form guidance recommends appropriate autocomplete values and stable field name and id attributes that do not change between page loads or deployments.
Ask your developer to inspect the form actually delivered to the browser, including any fields inserted by a checkout extension. A sensible setting in the website editor is only useful if the resulting page contains the intended attributes.
The HTML standard’s autofill definitions include specific values for common details:
namefor a full name, orgiven-nameandfamily-namewhen those parts are genuinely separate.organizationfor the company name.emailandtelfor email addresses and telephone numbers.address-line1andaddress-line2for separate street-address lines.street-addressfor a field accepting the street address across multiple lines.postal-codefor the postcode.
The customer-facing label can still say “Postcode”. The standardised value in the code remains postal-code. Do not invent a token such as uk-postcode to match the wording on the page.
Keep delivery and billing details separate
The same standard defines shipping and billing grouping tokens. A delivery postcode can use autocomplete="shipping postal-code", while the billing postcode uses autocomplete="billing postal-code". Named groups beginning with section- can distinguish repeated address groups.
For your business, the acceptance test is straightforward: a customer must be able to choose a delivery address different from their billing address and keep both correct through checkout. Include the recipient’s name in that test when customers buy gifts or order for colleagues.
Investigate values that change after autofill
Sometimes the right details appear initially, then disappear when the customer changes country, opens another checkout step or selects a delivery method. Record that sequence. Ask the developer to compare the visible fields, the website’s stored form values and the eventual submission at each step.
For an address problem in Chrome, its DevTools Autofill panel shows the relationship between detected fields, predicted autofill values and inserted data. It also provides test address data. The panel is specifically for address information; it is not a complete test of every browser or every kind of autofill.
Ask for a finding that names the failing step. For example: “The address fills correctly, but returning from delivery options restores the earlier address.” That gives a developer a repeatable problem to trace. “Autofill is unreliable” leaves too much unexplained.
Follow the details into the order or CRM
If the customer sees the correct company name but your CRM receives their surname in that property, inspect the handover. Compare a controlled submission with the website’s received data and the destination record. Check which field each integration uses before editing the CRM’s existing records.
For an online shop, inspect both the saved order addresses and the information passed to fulfilment. A checkout screenshot alone cannot establish that the warehouse received the intended recipient and destination. Keep test orders clearly identifiable to your team and out of normal dispatch.
Keep autofill support and manual correction usable
Autofill also has an accessibility role. W3C’s explanation of WCAG 2.2 criterion 1.3.5 covers identifying the purpose of specified fields collecting information about the user. Appropriate autocomplete attributes are one way to provide that meaning and can reduce typing and memory demands.
W3C also distinguishes correct field identification from whether a browser actually fills the field. A successful autofill demonstration alone does not establish conformance with that criterion, let alone the accessibility of the whole form.
Keep labels visible and let customers inspect and correct their details. Include manual entry in the repair checks, alongside browser suggestions. A customer with no saved address still needs a usable route, and a customer sending a gift needs to change the recipient without fighting repeated replacements.
Verify the complete journey before closing the issue
Agree a small test set based on the browsers and devices your customers use. Include the device where the fault was reported and at least one other relevant browser. For each route, check:
- Initial entry: type the details manually, then repeat using a saved suggestion.
- Correction: change an autofilled value and confirm it survives the next step.
- Separate addresses: use different billing and delivery details where supported.
- Error recovery: trigger a normal validation error and confirm the corrected details remain usable.
- Completion: inspect the received enquiry or saved order, including its destination system.
Save the expected and actual outcomes with the browser versions tested. If a route still fails, name it explicitly so the issue stays visible. Avoid treating a single successful desktop submission as evidence that the mobile problem has gone.
If you need help tracing the fault, BuzzBoost’s web development and integration work covers the website and the systems behind it. Send us the affected page and the steps that reproduce the problem so we can assess a focused repair.
Featured image: AI-generated editorial artwork, not a photograph of a real BuzzBoost office, client or result.


