E-commerce
July 1, 2026
"I cannot save my new address." "Wrong default address on every order." "My saved addresses do not appear at checkout." Three tickets where a poorly managed address book generates delivery errors and cart abandonment.
The e-commerce saved address support covers addition, deletion, default address, format validation, and customer account checkout sync. Distinct from post-order changes (#183): here, it is the profile address book before or outside of an active order.
This guide #831 covers policy SAVEDADDR-SUP, flows SA-1 to SA-8, and matrix SAVEDADDR-MAP. Customer service duo of the future address book bot (#832).
Summary
Why does the address book generate tickets?
The customer manages their address book: addition, default, deletion. Validation error, ghost address at checkout, or obsolete default after relocation. The agent redirects to checkout without checking the admin profile.
Five typical frictions with saved addresses
Addition blocked: postal code, special characters, PO box refused
Incorrect default: old address pre-selected at checkout
Addresses missing at checkout: logged-in account, empty address book UI
Duplicates in address book: same address 3 times, customer confused
Billing shipping confusion: wrong address saved as default shipping
Shopify stores customer addresses on the profile; the new accounts checkout can pre-fill from the address book (Shopify, customer accounts 2026).
DTC Example
Maison DTC, 34 savedaddr_ tickets/month. After SAVEDADDR-MAP: savedaddr_resolution_rate 90%, delivery errors related to default address -22%.
SAVEDADDR #831 vs ADDR-CHANGE #183, MADDR #409, reduce errors, business #biz and bot #832
Seven contents, seven distinct customer address angles.
Quick Matrix
#831 SAVEDADDR: account address book default add delete
ADDR-CHANGE #183: modify delivery of already paid order distinct from profile address book
MADDR #409: multiple addresses one order distinct from customer address book
Reduce errors: cross-functional checkout error prevention distinct from address book support
Business delivery: B2B business delivery distinct from personal address book addresses
ACCT #293: guest without address book distinct from registered account
Bot #832: help choose correct address tier 1
#831 = my account address book is not working. #183 = change the address of my order #1234.
Promise #831
Policy SAVEDADDR-SUP, tree SAVEDADDR-GATE, 8 macros, account self-service guide, KPI savedaddr_resolution_rate.
Which savedaddr_* typologies should be classified?
Classify avoids macro change order when the problem is address book profile.
Eight SAVEDADDR-MAP typologies
savedaddr_add_fail: unable to add address form
savedaddr_wrong_default: incorrect delivery default
savedaddr_delete_fail: address deletion blocked
savedaddr_checkout_missing: address book not visible in logged-in checkout
savedaddr_duplicate: duplicates of the same address in address book
savedaddr_format_error: ZIP code street country validation rejected
savedaddr_moved_update: relocation address book update
savedaddr_billing_confused: confuses billing and delivery in address book
Active order in progress + wrong address: reroute #183 ADDR-CHANGE, not SA-5 edit address book alone.
Policy SAVEDADDR-SUP: agent and escalation rules
The SAVEDADDR-SUP policy defines what the agent can modify on the customer profile.
Six SAVEDADDR-SUP rules
L2 Verification: account email + recent order or postal code match before admin edit
Self-service first: guide customer account before admin edit
Documented admin edit: note address before/after in ticket
No editing shipped orders: address book ≠ changing package in transit (#183)
Country format: respect Shopify validation rules per market
Dev escalation: recurring savedaddr_checkout_missing on the same browser
Escalation
Dev/theme: broken UI address book on mobile. Ops: PO box forbidden zones delivery policy.
Flow SA-1 to SA-8: standard resolution
Eight sequential steps, backlog SLA P3 < 8 h.
Flow SA-1 to SA-8
SA-1 Triage: backlog vs active order, tag savedaddr_*
SA-2 Customer lookup: profile, Shopify admin address list
SA-3 Classify: savedaddr_* via SAVEDADDR-MAP
SA-4 Self-service: macro SAVEDADDR-GUIDE account link
SA-5 Admin fix: edit default, delete duplicate, add if blocked
SA-6 Verify checkout: ask for add-to-cart test or screenshot
SA-7 Macro confirm: SAVEDADDR-DONE default address OK
SA-8 Close: KPI savedaddr_resolution_rate
Eight SAVEDADDR-* macros ready to paste
Short macros, account link {{account_link}} to be filled in.
SAVEDADDR-* Library
SAVEDADDR-GUIDE: "Manage your addresses: {{account_link}} → Addresses. Add, set as default, or delete."
SAVEDADDR-DEFAULT-FIX: "Default address updated: {{address}}. Next checkout pre-filled."
SAVEDADDR-FORMAT: "Check postal code {{cp}} and country {{country}}. Number and street required. No special characters @#."
SAVEDADDR-DUPLICATE-CLEAN: "Duplicates deleted. {{count}} unique addresses kept."
SAVEDADDR-CHECKOUT-TIP: "Log in before checkout to see the address book. Guest mode: manual entry."
SAVEDADDR-MOVED: "Update address book then set new default address. Delete old one if no longer used."
SAVEDADDR-BILLING-NOTE: "Address book = delivery. Billing = checkout entry or existing order."
SAVEDADDR-DONE: "Address book updated. Try a test order or verify on next purchase."
SAVEDADDR-GATE tree and common format errors
Decision tree before admin edit or dev escalation.
SAVEDADDR-GATE
Active order wrong address? → #183 ADDR-CHANGE
savedaddr_format_error? → SAVEDADDR-FORMAT + valid country example
savedaddr_checkout_missing + logged in? → logout login cache, escalate dev if recurring
savedaddr_wrong_default? → SA-5 set default admin + SAVEDADDR-DEFAULT-FIX
savedaddr_duplicate? → delete admin duplicates + SAVEDADDR-DUPLICATE-CLEAN
Frequent FR/EU format errors
FR 5-digit postal code, no PO Box alone if carrier prohibited, optional phone depending on theme. Align theme error message with SAVEDADDR-FORMAT macro.
KPI, QA and handoff to bot #832
Measuring SAVEDADDR distinguishes between address book and order changes.
Four SAVEDADDR KPIs
savedaddr_resolution_rate: address book OK via self-service or admin / total
savedaddr_selfservice_first_rate: % of SAVEDADDR-GUIDE before admin edit
savedaddr_wrong_default_fix_rate: % of savedaddr_wrong_default resolved
savedaddr_reroute_addr_change_rate: % correctly routed #183
Bot Handoff #832
Export SAVEDADDR-MAP to intents bot_savedaddr_guide, bot_savedaddr_format. SAVEDADDR-NO-ORDER-EDIT-BOT guardrail: address book only, not shipped orders.
Edge cases: guest, PO box, French overseas territories (DOM-TOM)
Three cases outside the standard flow.
Guest customer
No address book: SAVEDADDR-CHECKOUT-TIP + guide account creation #821 if recurrence is desired.
PO box declined
Carrier policy: explain the restriction, offer a drop-off address or pickup point if available.
Specific French overseas territories (DOM-TOM) postal code
Postal code 97xxx validation: SAVEDADDR-FORMAT with French overseas territory example. Check if the Shopify market is active.
Agent training: 20 minutes SAVEDADDR
Short module: address book ≠ current order.
Exercises
Ticket A: package already shipped to wrong address → #183 not SA-5 alone
Ticket B: obsolete default → SAVEDADDR-DEFAULT-FIX
Ticket C: guest no address book → SAVEDADDR-CHECKOUT-TIP
How Qstomy structures SAVEDADDR in your stack
Qstomy route savedaddr_*, displays admin profile addresses and suggests address book macros.
Three building blocks
Routing: saved_address intent vs addr_change_order
Profile sync: Shopify address list in ticket sidebar
Bot #832: tier 1 format guide before human
FAQ and SAVEDADDR deployment checklist
FAQ
Address book = modify paid order?
No. Address book = future purchases. Active order → #183 ADDR-CHANGE.
Addresses not at checkout?
Verify account login. Guest = no address book. SAVEDADDR-CHECKOUT-TIP.
Multiple addresses same order?
Address book ≠ multi-ship. See MADDR #409.
7-Day Checklist
D1: SAVEDADDR-SUP + SAVEDADDR-MAP
D2: 8 helpdesk macros
D3: SAVEDADDR-GATE + account address link
D4: 20 min training + address book vs #183 quiz
D5: savedaddr_* tags + KPIs
D6: iOS mobile test adding address
D7: bot brief #832
Linking
Enzo
July 1, 2026
