Risk analysis
Different Customers, One Delivery Address: How to Review Linked Orders
Several customers shipping to the same address should be reviewed as a possible relationship, not rejected as a group. Households, offices, apartment buildings, and shared receiving locations can legitimately receive orders from different people. The useful question is whether the common destination, together with independent order facts, creates an unresolved concern.
Start by confirming that the addresses are actually the same destination. A shared street line with different apartment or suite numbers may represent separate recipients. Poor normalization can make a busy building look like one coordinated buyer, while inconsistent abbreviations can hide a true common destination.
Establish the relationship you can support
Use the order records to compare delivery details, timing, items, payment status, and the available review context. Preserve meaningful unit numbers and recipient distinctions. Do not merge customers solely because a spreadsheet strips punctuation or drops the second address line.
Shopify identifies common destinations as review context in its fraud-prevention guidance. The merchant still needs to establish what the observed relationship means for the actual orders.
Write the relationship precisely: “same building, separate units,” “same complete destination, different customer records,” or “shared receiving desk.” Avoid “same person” unless evidence actually supports that conclusion. A common destination is a link between orders, not proof of a common identity.
Keep the review limited to operationally relevant records. Do not investigate unrelated residents or assemble personal profiles of everyone associated with a building. The store needs a decision about its orders, and the record should reflect that purpose.
Review the cluster without erasing individual facts
Create a cluster reference that points to each order. For every order, retain its own payment status, risk recommendation where available, fulfillment state, and required decision. Group context can reveal an issue, but it should not overwrite differences between the purchases.
A useful comparison looks like this:
| Order field | Why it matters in the group |
|---|---|
| Full destination including unit | Confirms whether the receiving point is actually shared |
| Order time | Shows whether purchases are close together or simply historical |
| Items and quantities | Helps explain a household, office, or unusual repeated purchase |
| Current payment status | Prevents unpaid and paid orders being treated identically |
| Independent review concerns | Distinguishes common address from additional unresolved facts |
| Fulfillment state | Identifies which goods remain within merchant control |
Do not invent a shared risk score by averaging recommendations or counting red flags across unrelated individuals. Instead, state the group-level concern and the order-level facts that support or weaken it.
Compare two hypothetical receiving locations
At a hypothetical apartment building, three customer records use the same street address but different units. Their orders occur over several weeks and contain different ordinary purchases. Once unit numbers are preserved, the apparent single destination becomes several delivery points. The review should correct the grouping rather than continue treating the building as one buyer.
At a hypothetical office, several employees buy gifts for an event and use a common reception desk. The shared location has a plausible operational explanation, but each order still needs its normal payment and release checks. A receptionist's confirmation that the office receives parcels does not prove that every payment is authorized.
Now consider an invented cluster where the full destination matches, orders arrive close together, and several contain independent unresolved payment changes. The reviewer should document that combination and escalate the relevant orders. The concern is the supported pattern, not merely that multiple people share a location.
These examples do not establish a universal threshold for how many orders an address may receive. Such a threshold would need a defined business purpose and an exception route for ordinary shared premises.
Clarify without disclosing other customers
If contact is needed, discuss only the customer's own purchase. Ask whether the named destination is the intended receiving point and whether any delivery instructions are missing. Do not reveal the names, items, payment details, or existence of other customers' orders as a way to test the response.
Use the order's established contact route. Record the response as context, including its limits. The customer may reasonably know nothing about other orders at a shared address, and that lack of knowledge should not automatically count against them.
Consult Shopify's order-review documentation for the individual order information available to the authorized reviewer. The cluster worksheet supplements that context; it should not replace the original records.
Assign decisions at the right level
If a shared concern affects several orders, one reviewer can coordinate the investigation, but each order still needs a clear disposition. State which orders are held, released, or escalated and why. Fulfillment should never infer that every parcel at an address is approved because one was reviewed.
Close the cluster when the relationship is understood and the relevant decisions are recorded. Retain the explanation for future reviews, but avoid turning one unresolved incident into a permanent blanket block on a whole building. Shared destinations require careful context, limited disclosure, and individual accountability.
Explore how Lower Chargeback presents Shopify risk signals for merchant review.
Related reading in this collection:
- Shopify Fraud Analysis: Reading the Recommendation and the Individual Signals
- Previous Undisputed Orders as Evidence: Build a Reliable Purchase History
- An Address Change After Payment: When to Reopen the Fraud Review