E-commerce
July 1, 2026
"I ordered 3 gifts to 3 addresses, only one arrived." "Why pay 3 times the shipping fees if it's a single order?" "The checkout only accepted one address, how do I send to my mother and sister?" Three messages where a poorly managed multi-address order generates CS tickets, partial refunds, and negative Christmas reviews.
The e-commerce multi-address shipping order support covers multiple gifts, multi-site B2B orders, Shopify Multi Ship apps, and post-purchase disputes when addresses, fees, or fulfillments do not match expectations.
This guide #409 covers policy MADDR-SUP, flow MADDR-FLOW, and KPI multi_addr. No existing content on this topic. Distinct from split shipment (#356) (multiple packages, same address) and gifts (#gift): here, we cover multiple delivery addresses per order or multi-ship flows.
Summary
Why do multi-address orders generate tickets?
A multi-address order ticket concerns an order where the customer expects multiple distinct recipients or delivery addresses, via the Multi Ship app, linked orders, or multi-site B2B flows.
Five typical customer pain points
One checkout address: customer thought they could enter 3 native Shopify addresses
Shipping fees x N: surprise 3x shipping fee unexplained on PDP
Missing parcel: 2/3 addresses delivered, 1 forgotten by operations
Wrong address line: Item A → address B by warehouse error
Single invoice, multiple deliveries: B2B accounting vs operations
Native Shopify supports one shipping address per order; Multi Ship apps or multi-order flows extend this behavior (Shopify, checkout 2026). Gorgias observes that gift-giving periods (Christmas, Mother's Day) see 18-28% of delivery tickets related to multi-recipients when the option is not documented at checkout (Gorgias, support stats 2026).
Angle #409 vs related content
Split shipment #356: multiple parcels, one address. #409 = multiple recipient addresses.
Gifts #gift: gift message, wrapping. #409 = routing multiple addresses.
Corporate bulk: B2B bulk orders. #409 = B2B multi-sites + DTC gifts.
Address change: post-order modification. #409 = multiple addresses from the start.
Split bot #357: future automation multi-parcels. #409 = agent policy for multi-addresses.
DTC Example
Candle brand, Christmas Multi Ship app, 340 orders with 2+ addresses/peak week. Without MADDR-SUP: 89 multi_addr tickets, wrong_address_rate 6%. After playbook: multi_addr_ticket_rate -44%, line_address_accuracy 98%, multi_addr_csat 4.1/5.
Multi-address vs split
Split = 1 address, N parcels (warehouse stock). Multi-addr = N addresses, N fulfillments (often N shipping fees).
Ticket seasonality
Nov-Dec: 3-5x multi_addr volume vs rest of the year. Temporary staffing + pinned chat macros recommended.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
How does multi-address differ from split shipment #356?
Two logistical complexities, two distinct support playbooks.
Scenario → guide matrix
#409 MADDR-SUP: N addresses, line → address mapping
#356 SPLIT-SHIP: 1 address, N parcel tracking
#184 WISMO: tracking by fulfillment/address
Wrong recipient #wrong: gift recipient error
Three DTC multi-address models
App Multi Ship checkout: line item → address + rate per dest
Linked multi-orders: parent order + child orders per address
B2B CSV upload: address file → batch fulfillments
Shopify native limit
1 shipping_address per order. Multi-addr = app or split into multiple orders. Support must know stack model to explain to customer.
Promise #409
MADDR-SUP policy, LINE-ADDR matrix, 12 multi_addr_* typologies, MADDR-FLOW flow, MADDR-* macros, KPIs.
Which multi_addr_* typologies should be mapped?
Twelve multi-address ticket typologies for support routing.
Twelve multi_addr scenarios
multi_addr_pre_purchase: "can I send to 3 addresses?"
multi_addr_fee_question: shipping fees per address, checkout total
multi_addr_partial_delivery: 2/3 addresses received
multi_addr_wrong_address: package delivered to incorrect address line
multi_addr_missing_shipment: 1 fulfillment never created
multi_addr_tracking_confusion: N tracking numbers, lost customer
multi_addr_gift_message: gift message per recipient
multi_addr_post_change: modify 1 address post-order
multi_addr_b2b_invoice: 1 invoice, N delivery sites
multi_addr_cancel_partial: cancel 1 line/1 address only
multi_addr_international_mix: FR + BE + CH same cart
multi_addr_app_bug: Multi Ship app did not save address
Helpdesk tags
multi_addr, multi_addr_2plus, multi_addr_b2b, multi_addr_gift, multi_addr_wrong, multi_addr_resolved. Distinct split_ship, gift_wrap.
Prioritization
P1: wrong_address, missing_shipment, partial_delivery. P2: tracking_confusion, post_change. P3: pre_purchase, fee_question.
Which LINE-ADDR matrix to map lines and addresses?
The LINE-ADDR row-address matrix documents mapping ops and support.
Four LINE-ADDR columns
order_id / child_order_id: parent or split order
line_item SKU + qty: item concerned
shipping_address_id: hash or Dest A/B/C label
fulfillment_id + tracking: package linked to address
Data source
Multi Ship metafields line_item.ship_to_address app, or 3PL export, or Shopify child orders linked parent_order metafield.
Agent MA-1 lookup
"Missing package mom" ticket → LINE-ADDR filter Dest B → fulfillment status unfulfilled → escalate ops missing_shipment.
Customer manifest
Multi-addr confirmation email: SKU | Recipient | City | Tracking table. Reduces multi_addr_tracking_confusion by 40%.
Split #356 distinction
Split: same address_id, multiple fulfillments. Multi-addr: different address_id per line or order.
Example LINE-ADDR 3 dest
Order #1042: SKU-Candle-A qty1 → Dest Marie Lyon FUL-881 · SKU-Candle-B qty1 → Dest Paul Paris FUL
How to draft the MADDR-SUP policy in eight rules?
The MADDR-SUP multi-address policy documents the stack model and promises.
Eight MADDR-SUP rules
Stack model: Multi Ship app | multi-order | B2B CSV (documented)
Shipping fees: 1 rate per address, explained on the PDP/FAQ before checkout
LINE-ADDR mandatory: each line mapped to an address before pick
Confirmation manifest: email table of recipients + tracking
Post-change window: modify 1 address within 2 hours if unfulfilled (#change)
Wrong address: reship or line refund if brand/ops error
Partial cancel: possible per line/child order if unfulfilled
B2B SLA: batch ship 48-72 hrs, dedicated pro contact if > 10 addresses
Publication /pages/multi-ship
FAQ: how many addresses, fees, delivery times, gifts, international, how checkout works. Link on PDP during Christmas period.
Checkout copy
"Ship to multiple addresses: shipping fees calculated per recipient" visible before the Multi Ship app step.
Pre-peak Christmas review
Ops + support: test of 5 multi-addr orders in staging, LINE-ADDR accuracy, macro refresh.
of refresh.
How to apply the MADDR-FLOW flow in eight steps?
The MADDR-FLOW framework structures multi-address ticket processing.
Eight steps MA-1 to MA-8
MA-1 Identify order: parent/child, multi_addr tag, app metafields
MA-2 Classify: typology multi_addr_* section 3
MA-3 Load LINE-ADDR: mapping line → address → fulfillment
MA-4 Diagnose: missing | wrong | delay | tracking | fee
MA-5 Respond: macro MADDR-* grounded MA-3
MA-6 Execute: reship, refund line, address fix, ops alert
MA-7 Tag outcome: resolved | reship | refund_partial | escalated_ops
MA-8 Document: LINE-ADDR gap if mapping error
MA-4 partial_delivery
Compare fulfillments count vs address count expected. Missing = ops create fulfillment urgent. Delay = WISMO per address #184.
MA-4 wrong_address
Verify LINE-ADDR vs label carrier. Mark error → reship + gesture. Client typo checkout → policy #change window expired, limited options.
MA-6 cancel_partial
Unfulfilled line Dest C only: cancel line + refund shipping portion. Child order model: cancel child order intact.
Ops escalation
missing_shipment > 24 h post SLA: Slack #multi-addr-ops P1.
MA-3 child order lookup
Parent metafield child_order_ids [104
Which MADDR-* macros and touchpoints should be configured?
Eight multi-address agent macros and checkout touchpoints.
MADDR-PRE-01 (pre-purchase multi-addr)
"Yes, ship to multiple addresses via [app/flow]. Shipping fees calculated per recipient. Guide: [link /pages/multi-ship]."
MADDR-FEE-01 (shipping fees explained)
"Your order #[X]: 3 recipients = 3 separate shipments. Fees: [A] €4.90 + [B] €4.90 + [C] €6.90 (international). Total shipping checkout."
MADDR-MANIFEST-01 (multi-addr confirmation)
"Delivery summary: [SKU1] → Marie, Lyon · [SKU2] → Paul, Paris · Separate tracking numbers via shipping email."
MADDR-PARTIAL-01 (2/3 delivered)
"Recipients A and B delivered. Recipient C in preparation · shipping [date]. Tracking: [link]. We apologize for the wait."
MADDR-WRONG-01 (incorrect address brand error)
"Internal address error confirmed for Recipient B. Free replacement sent within 48h. New parcel tracking will be sent by email."
MADDR-TRACK-01 (N tracking numbers explained)
"3 parcels = 3 standard multi-address tracking numbers. Recipient A: [track1] · Recipient B: [track2] · Recipient C: [track3]."
Touchpoints
PDP badge "Multi-recipient available"
/pages/multi-ship FAQ
Checkout app step addresses by line item
Email confirmation manifest LINE-ADDR
Customer account: fulfillments grouped by address
Gifting Period
Website banner + chat macro MADDR-PRE-01 pinned Nov-Dec. Align last-minute gift.
How to manage B2B and multi-site corporate gifting?
Multi-address B2B orders and corporate gifts amplify volume and invoicing requirements.
B2B CSV workflow
Customer upload CSV: name, address, SKU, qty, gift_message
Ops validate within 24 hours → create child orders or batch fulfillments
1 parent invoice, N ship confirmations
Pro contact: account manager or B2B tier support
Policy B2B vs DTC
B2B: 48-72 hour batch SLA, different FRT compared to DTC. CSV line 47 error: fix single line, do not refund full order.
Corporate link #corp
See corporate gifts bulk for volume quotes. #409 = post-order multi-address execution.
Gift message per recipient
Line property gift_message + address_id. Ops pick list must show per recipient. Confusion → #gift macro, not MADDR alone.
International mix
multi_addr_international_mix: duties vary per country (#65 customs). Explain 3 rates checkout, not flat fee.
CSV B2B validation
Ops checklist: postal code format, country match SKU ship zone, duplicate address merge before fulfill batch.
Which multi_addr KPIs should we measure?
Multi-address support KPIs drive ops and checkout clarity.
Eight key metrics
multi_addr_ticket_rate: multi_addr tickets / multi_addr orders
line_address_accuracy: correct address fulfillments / total lines
multi_addr_wrong_rate: wrong_address tickets / multi_addr orders
missing_shipment_rate: dest without fulfillment / expected dest
multi_addr_fee_complaint_rate: fee_question / multi_addr tickets
multi_addr_fcr: resolved MADDR-FLOW without escalation / tickets
multi_addr_csat: multi_addr tag satisfaction
pre_purchase_multi_addr_share: pre-purchase questions / total (checkout clarity)
DTC peak gifting benchmark
line_address_accuracy > 97%, wrong_rate < 2%, missing_shipment < 1%, multi_addr_fcr > 68%, fee_complaint < 15% post FAQ /pages/multi-ship.
Christmas peak Dashboard
Daily multi_addr volume, typology breakdown, LINE-ADDR errors ops, manifest correlation email vs tracking_confusion tickets.
Ops alert
missing_shipment > 3 same day: review Multi Ship sync app + warehouse pick list.
Pre-purchase FAQ ROI
/pages/multi-ship live: pre_purchase_multi_addr_share -35-50%. Checkout clarity = fewer fee_complaint tickets.
Which multi-address anti-patterns should be avoided?
Ten multi-address order anti-patterns to banish.
1. Promising multi-addr without app/flow
Shopify is native 1 address. MADDR-PRE-01 cites real stack.
2. Surprise shipping fees at checkout
fee_complaint spike. PDP + checkout disclosure.
3. Confusing split #356 and multi-addr
Macros SPLIT-* vs MADDR-*. Router MA-2 classifier.
4. Pick list without LINE-ADDR
Warehouse ships all to address A. wrong_rate explosion.
5. 1 tracking email for 3 destinations
Customer thinks 1/3 delivered. Manifest + per-fulfillment emails.
6. Ignoring child order model
Agent searches 1 order, misses child unfulfilled.
7. Refunding full order for partial issue
1 wrong dest ≠ refund all. Line/child cancel policy.
8. Post-change all addresses
Modifying 1 dest OK during 2 h window. Do not reorder 3 addresses for free.
9. B2B CSV without validation
Address typo x50 lines. Ops validate step mandatory.
10. No FAQ /pages/multi-ship
30%+ pre_purchase tickets avoidable.
11. App bug not escalated
multi_addr_app_bug → dev + ops workaround manual fulfill.
How does Qstomy help with multi-address orders?
Qstomy on Shopify: multi_addr intent detect, LINE-ADDR lookup assist, manifest explain, per-address tracking routing #184, priority queue wrong/missing P1.
Qstomy multi_addr capabilities
multi_addr_order_detect: parent-child tag/metafield
multi_addr_line_lookup: MA-3 LINE-ADDR assist
multi_addr_tracking_map: N trackings per dest
multi_addr_pre_faq: bot quotes /pages/multi-ship
multi_addr_escalate_ops: missing_shipment alert
multi_addr_split_reroute: distinguish #356 vs #409
Split #356 and gift #gift complement
Upstream classifier: same address multi-package → SPLIT. Multi dest → MADDR. Gift wrap message → gift playbook.
Quantified DTC scenario
Christmas candles, Multi Ship app, 280 multi-addr orders/week peak.
After MADDR-SUP + Qstomy: multi_addr_ticket_rate -46%, line_address_accuracy 98.5%, multi_addr_fcr 71%, multi_addr_csat 4.2/5.
Explore customer support and request a demo.
What checklist is needed to deploy MADDR-SUP?
MADDR-SUP Checklist (12 steps)
Document stack model (app / multi-order / B2B CSV)
Draft MADDR-SUP 8-rule policy
Configure LINE-ADDR export ops + agent lookup
Publish /pages/multi-ship FAQ + shipping fees
Checkout copy fees per shipping address
Email manifest multi-addr template confirmation
Create MADDR-* helpdesk macros
Train agents on MADDR-FLOW 30 min + test 3 dest staging
Warehouse pick list LINE-ADDR columns
Tags multi_addr + priority queue P1 wrong/missing
KPI Dashboard multi_addr (peak + annual)
Post-Christmas review LINE-ADDR errors + policy update
In brief
#409 = N addresses, no split parcel (#356)
LINE-ADDR: line → address → fulfillment mapping
MADDR-FLOW: lookup → diagnose → macro → execute
Shipping fees: transparent per recipient checkout
KPI line_address_accuracy: ops target > 97%
FAQ
Shopify native multi-address?
No, 1 shipping address/order. Multi Ship App or multiple linked orders.
Difference split shipment #356?
#356 = multiple parcels, 1 address. #409 = multiple recipient addresses.
Modify 1 address post-order?
Within 2 hours unfulfilled if policy #change. Otherwise limited or paid reship.
Relationship with #gift?
#gift = wrapping, message. #409 = multi-address routing.
B2B 50+ addresses?
CSV batch + SLA 48-72 h. Pro contact. See corporate bulk #corp.
Go further
This week: document multi-ship stack model, publish /pages/multi-ship, configure LINE-ADDR pick list, test 3-address order staging.
Share this guide #409 with ops and e-com before gift peak: multi-recipient is a selling point if customer service is ready.
International mix in same cart?
Possible depending on app/markets. Fees and delivery times by country. macro MADDR-FEE-01 details breakdown.
Enzo
July 1, 2026
