When autofill gives two address groups the same values

Establish whether the duplication was actually unwanted

Begin with the affected checkout path and the buyer’s reported action. Record whether the customer intended one address for both purposes or selected separate billing and shipping details. Note the state of any same-address control before the values became equal. Two equal addresses alone do not demonstrate a failure; the question is whether the page preserved the customer’s intended distinction.

Keep the sequence specific: which field received focus, whether the buyer selected a browser suggestion, which group changed immediately and whether the second group changed only after another checkout action. Record the browser and version from the actual report. Do not attribute a later address copy to browser autofill merely because an autocomplete attribute exists.

Compare native hints field by field

MDN describes autocomplete as a hint about the expected purpose or value. The browser chooses the source of the data. A visible heading that says billing does not by itself tell you what hints the inputs underneath it carry. Have the maintainer inspect the rendered native controls on the affected path and record the actual autocomplete value for corresponding fields in both groups.

The billing and shipping tokens let the markup distinguish those purposes. A section-* token provides another grouping distinction when a purpose repeats in the same form. Compare the complete token lists, including the token describing the particular address component. Identical lists can receive the same data, so inspect all corresponding fields rather than checking only the street input.

If a field has no autocomplete setting of its own, MDN says it inherits the owning form’s setting. Record that inheritance explicitly. An absent field attribute is not evidence that the page has supplied a distinct billing or shipping group. Browser prerequisites and behavior vary, so correct hints are evidence about markup, not a guarantee of identical results across browsers.

Find where the second value was copied

Compare the grouping evidence with the observed sequence. If the corresponding fields have identical hints and fill together after an autofill selection, there is a supported grouping issue to investigate. That observation still does not prove the hints are the only cause. If values become equal only after a same-address choice or another page update, inspect the checkout logic responsible for that change as a separate candidate.

The page may contain browser autofill, a store-controlled address selector and logic that copies one address to the other. Determine which of those the actual checkout uses instead of treating every address suggestion as native autofill. Keep each candidate linked to the point where the values changed. Where the sequence was not observed, say that the cause remains unresolved.

An address-correctness question is separate. Autocomplete hints do not prove the destination exists, that the buyer intended it, or that billing details will satisfy a payment provider. Preserve address validation and the buyer’s opportunity to review the values while the grouping issue is investigated.

Define the correction by the buyer’s choice

Give the maintainer the visible field purposes, complete rendered hint lists, affected browser and exact action that preceded the unwanted copy. The correction should make the hints agree with the intended grouping and preserve the explicit choice between shared and separate addresses. Do not impose different addresses when the buyer selected the same one, or overwrite a separately chosen address just to make the form look consistent.

The acceptance observation is whether the intended billing and shipping values remain distinct when separate addresses are selected, and remain shared only when that is the intended choice. Record this from the authorized real checkout investigation without placing an unnecessary order or collecting customer address values in a public worksheet. Browser-specific uncertainty should remain stated until that browser’s behavior has been observed.

For a Prism checkout-review consultation, describe the grouping mismatch and the affected step. Request a scope that covers the observed behavior and clarify who will implement any correction. Responsibilities, fees and terms are agreed before work; a working form is not payment-provider approval.

Autofill address-group map

Use the actual rendered checkout and the reported sequence. Compare corresponding fields across both groups. Record whether values matched the intended choice without copying full customer addresses. Matching values are a defect only when the evidence shows a distinction was intended and lost.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.