Your account
HOL-D108Story implementation: Planned

Manage my delivery addresses

commerce · Proposed launch phase 4

Start from Home

Review as Registered user · Full workflow planned

User story

As a registered member, I want to save and update my own delivery addresses so I can reuse the correct address for supported physical purchases.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • Provide Delivery addresses under Payments & purchases with list/add/edit/remove and default choice when implemented; keep a truthful empty state beforehand.
  • Validate recipient, street, locality/region, postal code and country according to supported destinations; exact shipping coverage/rules remain to be defined.
  • Keep addresses private and distinct from broad profile home region and public organization location. Do not infer an address from a region or professional affiliation.
  • Changing or removing an address must not silently rewrite a historical order/shipment address snapshot. Explain default selection without promising an unimplemented shipping workflow.

What to check in the demo

Follow these steps from the role’s landing page through navigation and feature checks.

Review asStart here: Home

Begin on this account’s permitted Home. For a local review use Sign in → Try a demo account → Alex Morgan → Free Member Home. Settings belong to this same personal account; keep Professional/organization/staff authority separate.

Navigation from sign-in

  1. 01Open the fictional Registered user account through the connected sign-in service. Seeded Home review opens directly. Real HOL staff access and protected actions require an authenticator check.
  2. 02Begin at this role’s Home, open its account/workspace menu, then Profile & settings when that navigation is delivered. Follow the section named in the checks; stop if a planned destination is unavailable.

Feature checks start here

Manage my delivery addresses · Full workflow planned

Planned follow-up. Requirements are recorded; the dedicated settings page and backend workflow are not implemented. Current navigation/editor work does not implement this outcome.

  1. 03From the role Home open Profile & settings → Payments & purchases → Delivery addresses when delivered; this workflow is currently planned.
  2. 04With an approved fictional address save/reload/edit a dedicated record, then check default and validation when connected.
  3. 05Compare private profile/public pages and an existing order snapshot; no exact address appears publicly or retroactively changes a placed order.

Backend work for this feature

Requirements only · Backend implementation on hold

What needs to be supported

  • Future private owner address records need stable IDs, fields, default constraints and validated country/region semantics; historical orders retain an explicit address snapshot.
  • Use verified-owner mutations, bounded validation, conflict handling and safe removal/default behavior. Organization grants do not authorize personal-address reads.
  • No address seed, shipping provider, actual shipment or new address/order schema is part of the first editor slice.

How to verify when implementation is approved

  1. Test owner/other-user/anonymous/unverified boundaries and repeated/default/conflicting edits.
  2. Verify old order address snapshots survive address edits/removal; no exact address in public projections.

Before this can work

  • Use an existing fictional account; keep its current role/entitlement and selected Home. No profile/preference reset is required to review requirements.
  • Dev only. No real card/address/recipient data, provider setup, outbound delivery or publication is part of this review.

Connected stories