Understand location selection states

Customer App can present saved addresses and, in some contexts, address entry, map, or device-location surfaces. These surfaces are related, but they do not represent one state or one completed transaction.

:::warning Location information is private

Do not copy an address, coordinates, account information, map-provider response, or delivery context into support notes or documentation. A visible location is not proof of ownership, serviceability, or successful cart settlement.

:::

Entry depends on the caller

The saved-address list can appear when the main Customer App experience has no active address. Related address selection can also be reached from business discovery, checkout, account, or sign-up contexts. The control used to return from the screen can therefore vary.

Caller information is navigation context, not authority. A route that says a selection came from checkout or business discovery does not prove that the current account, address, cart, or destination is still the same when an asynchronous result returns.

Read the visible list conservatively

The pinned source defines loading placeholders, saved-address rows, an empty or error presentation, address-tag filtering, add/edit/delete controls, and a Continue action in eligible contexts. It does not establish a visible text search field on this list.

A row can look selected because its address fields match the active ordering address. That presentation does not establish that the row is the saved default, that the server accepted a default change, or that every cart now uses it.

Keep location state layers separate

State layer	What it can represent	What it does not prove
Typed location	Text entered or selected as a candidate	Precise coordinates, ownership, saved address, or delivery coverage
Device-provided location	Coordinates returned after an available permission flow	Postal address, saved default, serviceability, or continuing permission
Saved address	An address record associated with an eligible account context	Current default, active order address, or cart settlement
Saved default	The account's intended default address	That the active ordering context or every cart has refreshed
Active order location	Address and city held by the current ordering context	Saved-default identity or acceptance by a specific cart
Cart delivery context	Address and delivery options held for one cart	Global account state or successful order placement

Matching text or coordinates do not collapse these layers into one transaction.

Map and current-location boundaries

Business maps, address forms, and current-location controls are separate surfaces. When a device-location action is available, the operating system owns the permission decision. A map or address provider may receive the minimum location input needed for the requested lookup.

A permission prompt, map marker, address suggestion, or returned coordinates do not prove that an address was saved or selected. They also do not prove that a business delivers there. Declining or losing device permission should leave a manual or saved-address path when the configured experience supports one.

Selection and settlement are separate

In the pinned source, choosing a different saved row can begin default-address and active-order-context work while navigation continues. Those effects are not presented as one awaited, authoritative receipt. A destination screen, changed row style, or closed selector therefore cannot confirm that the saved default, active order address, order options, and cart all settled.

A future accepted implementation must bind every mutation to the current account, project, session, address owner, caller, and cart where applicable. It must return versioned results for each changed layer, reject stale callbacks, and preserve an unknown outcome when a response is lost. Navigation must wait for the required settlement or disclose what remains pending; it must never silently replay an unknown write.

Guest and account boundaries

Guest, signed-in, and changed-account address state must remain partitioned. A guest-visible address or a cached selection is not authority to attach it to a later account. After logout, account change, or project change, the app must not reuse an earlier address, precise location, callback, or cart context without a fresh owner-scoped result.

Partial and unknown outcomes

Treat these events as incomplete evidence:

• the list closes before a default or ordering-context update settles;
• a saved default changes while the active order location or cart remains old;
• an order location changes while delivery options or totals remain stale;
• a provider returns an address after the caller, account, project, or session changed;
• navigation succeeds but the underlying write fails or its response is lost;
• the list refreshes from cache while server authority is unavailable.

Do not repeatedly select, edit, delete, or request current location to diagnose an unknown result. Reopen the relevant summary, confirm the current account and order context, and use a non-sensitive support channel if the state remains unclear.

Accessibility and safe troubleshooting

Buttons, address rows, selected state, loading and error messages, permission handoffs, and map alternatives require independent iOS and Android validation. Do not infer equivalent focus order, screen-reader labels, large-text behavior, keyboard handling, or Back behavior from source structure alone.

For safe troubleshooting:

• confirm which surface and caller are visible without sharing the location;
• confirm whether the app shows a saved row, typed candidate, device location, active order location, or cart summary;
• wait for the current state to settle before taking another action;
• use manual entry or a saved-address alternative when device location is unavailable and that alternative is offered;
• re-certify after changes to navigation, address ownership, order options, cart settlement, permission handling, map providers, or session cleanup.

This page is a source-safe state reference. It does not certify current deployment behavior, provider behavior, delivery coverage, or a successful location change.

Related guides: Add or edit an address · Location permission and unavailable-location states · Explore businesses on a map · Choose order type and time · Manage saved addresses · Review customer and delivery details