“Arrived” and “delivered” are not synonyms in logistics. One signals presence at a hub; the other confirms the customer’s possession.
Misreading these statuses triggers refund requests, chargebacks, and churn. This article maps the exact moment each term applies, how carriers calculate them, and how retailers can protect revenue.
Status Definitions: Where Carriers Draw the Line
“Arrived” means the parcel has reached a physical scan point—dock, container, or belt—inside the destination facility. It does not promise last-mile hand-off.
“Delivered” requires a timestamped scan at the consignee’s address or an authorized alternate location. The carrier’s liability shifts to the recipient at this event.
UPS, FedEx, and DHL embed these triggers in their service guides. Retailers who override the wording risk policy violations and chargeback losses.
Scan Hierarchy Inside a Sort Facility
Arrival scans fire when the pallet crosses the geo-fence of the final sorting center. The package still sits inside a gaylord or tote, untouched by the delivery van.
Departed scans follow once the carton is loaded onto the route truck. If weather delays the van, the parcel remains “arrived” until a successful doorstep scan occurs.
Proof of Delivery vs. Proof of Arrival
Proof of arrival is a warehouse receipt. Proof of delivery is a photo, signature, or GPS ping within 10 m of the delivery address.
Chargeback teams accept only the latter. Issuers reject warehouse receipts because the package could still be lost in the cage.
Customer Psychology: Why “Arrived” Feels Like “Delivered”
Mobile tracking apps collapse both events into the same green checkmark. Shoppers stop reading after the emoji.
A 2022 Narvar study found 62 % of consumers open the tracking page once and never return. If the first update says “arrived,” they assume the box is at the door and panic when it is not.
Retailers that add a one-line caption—“Package still in transit to your address”—cut WISMO tickets by 28 % within 30 days.
Push Notification Wording That Prevents Tickets
Replace “Your order has arrived” with “Your order has reached our local facility and will be delivered tomorrow.” The extra clause resets expectations.
Split the final mile into two pings: “Out for delivery” at 07:00 and “Delivered” only after the geo-located scan. Ticket volume drops 19 %.
Chargeback Reason Codes: How Banks Interpret Each Status
Visa reason code 13.1—“Merchandise not received”—is filed when the tracking stub shows “arrived” but no “delivered” scan exists. The bank auto-debits the merchant.
Mastercard 4855 applies the same logic. Providing a warehouse receipt is useless; the issuer demands a signed POD or GPS image.
Amazon’s A-to-Z guarantee goes further. It refunds the buyer instantly if the courier’s photo is blurry, even when the status reads “delivered.”
Compelling Evidence Checklist
Submit the POD PDF, the GPS map, and a timestamp-adjusted screenshot. Add the courier’s SLA clause that defines “delivered.”
Match the shipping label address to the AVS address. A mismatch voids your evidence.
Inventory Reconciliation: Arrived Quantity vs. Delivered Quantity
Large retailers often receive 1 % fewer cartons than the ASN shows. The discrepancy is flagged as “arrived short.”
If the warehouse signs for 1 000 units but only 990 are physically shelved, the 10-unit gap is written off as shrink. The supplier is debited only when the shortage is caught before the carton leaves the dock.
Once the warehouse ships the 990 units to stores, each store’s “delivered” file must equal the outbound quantity. Any variance becomes a store-level loss.
Blind Receipt Protocol
Staff scan each inner carton without seeing the ASN quantity. The WMS records the delta in real time.
Disputes drop by 40 % because the vendor receives objective data instead of a manually adjusted figure.
International Shipments: Customs “Arrived” Does Not Equal Cleared
Parcels land at CDG or JFK and immediately receive “arrived” scans. They still sit in bonded warehouses awaiting customs release.
Duty-paid DDP shipments can show “delivered” only after the last-mile agent completes customs formalities and hands the box to the buyer. Importers who confuse the two statuses accrue storage fees.
FedEx International consolidates both events into one line: “International shipment release—Delivered.” The wording hides the customs delay, so merchants should parse the raw XML feed.
DDP vs. DAP Risk Allocation
Under DDP, the seller pays demurrage if customs clearance lags. Under DAP, the buyer pays once the goods “arrive” at the port.
Choose Incoterms that match your tracking vocabulary to avoid surprise invoices.
Same-Day Courier Loopholes: When “Delivered” Is Reversible
Regional couriers often batch-swipe “delivered” at the restaurant pickup point to meet on-time metrics. The driver still has 90 min to reach the customer.
If the food arrives cold, the customer disputes the charge. The courier’s pre-scan gives the merchant zero proof.
Insist on courier APIs that lock the “delivered” trigger to customer GPS or a barcode on the door.
Geo-Fence Radius Settings
Set the acceptable radius to 50 m in dense cities and 200 m in rural zones. Tighter radii force drivers to approach the door, raising photo evidence quality.
Looser settings reduce false negatives but increase reversible deliveries. A/B test for 14 days to find the sweet spot.
Marketplace Requirements: Amazon, eBay, and Shopify Filters
Amazon’s Buy Shipping requires a “delivered” scan by 23:59 on the promised date. An “arrived” scan at the local facility at 22:00 still counts as late.
eBay’s Money Back Guarantee accepts either status for domestic shipments but demands “delivered” for global ones. Shopify merchants set their own rules, yet payment processors override with card-network policies.
Listings that promise “overnight” must therefore trigger “delivered,” not “arrived,” within 24 hours.
Automated Rule Engines
Build a lookup table that maps each sales channel to the required status code. Your OMS can then auto-select the service level that satisfies every platform.
This prevents overspending on premium speed when standard service already meets the marketplace threshold.
API Webhooks: Real-Time Status Deltas
Carriers POST JSON payloads every time the label hits a new node. Parse the “status” field and watch for the jump from “arrived” to “delivered.”
Trigger customer emails only on the final hop to avoid spam. Segment the audience so that high-value customers receive SMS plus email.
Cache the previous state in Redis to prevent duplicate events. A single duplicate “delivered” email can generate a support ticket asking about a second phantom package.
Webhook Security Checklist
Verify the carrier’s signing certificate against a pinned public key. Replay attacks can spoof “delivered” events and unlock digital products.
Log every payload with HMAC validation results. Forensic teams need immutable logs to refute friendly fraud.
Post-Purchase Platforms: How Narvar, Route, and AfterShip Translate Events
These vendors normalize carrier jargon into branded language. Narvar maps “arrived” to “Your package is at a nearby facility.” Route collapses both events into a single map pin.
AfterShip lets merchants rename statuses, but payment dispute teams still see the raw carrier code. Custom wording helps CX yet offers zero legal value.
Choose a platform that surfaces both the customer-friendly text and the raw scan code for internal dashboards.
Branded Tracking Page A/B Test
Display an animated truck driving from the hub to the home when status equals “arrived.” Conversion to repurchase rises 11 % because shoppers trust visual progress.
Keep the raw code in a hidden div so that customer service can inspect it during live chats.
Reverse Logistics: “Delivered” Does Not Close the Loop
A box marked “delivered” can still bounce back through retail returns. The original delivery scan remains untouched, creating a data orphan.
Retailers must create a new return tracking ID. If they reuse the outbound label, the carrier’s system overwrites the POD and voids chargeback evidence.
Always generate a reverse label with a unique ID. Archive the original POD PDF for 18 months to match issuer retrieval limits.
Return Status Glossary
“Return received” means the warehouse signed for the carton. “Return processed” means items are graded and restocked.
Do not refund until “processed” to avoid double crediting the customer.
Subscription Boxes: When “Arrived” Triggers Billing
Some meal-kit firms bill the customer the instant the weekly box “arrives” at the regional depot. Customers revolt because they have not tasted the food.
Chargebacks soar above 2 % for these brands. Switch the trigger to “delivered” plus a 24-hour buffer to allow for theft claims.
Revenue recognition auditors also prefer the later trigger, keeping deferred liability accurate.
Prorated Refund Logic
If the customer cancels after “arrived” but before “delivered,” issue a full refund. Once “delivered,” offer 50 % credit to cover ingredient spoilage.
Spell this rule in the subscription FAQ to reduce disputes.
Blockchain Pilot Programs: Immutable Status Hashes
Maersk’s TradeLens writes both “arrived” and “delivered” events to a shared ledger. Each hash includes GPS, temperature, and container seal ID.
Importers can grant bank access to the ledger, eliminating paper PODs. Letter-of-credit funds release automatically when the blockchain sees “delivered.”
Retail pilots are smaller: a fashion house mints an NFT for each luxury handbag. The token transfers to the buyer’s wallet only when the courier’s API returns “delivered.”
Smart Contract Sample Clause
“Release escrow if and only if status equals delivered, gps_accuracy < 25 m, and photo_hash is not null.”
Code the oracle call in Solidity to avoid manual disputes.
Carrier Scorecards: SLA Penalties Hinge on Final Status
Retailers fine carriers 3 % of shipping cost for every parcel that stays “arrived” beyond the SLA window. The penalty jumps to 10 % if the event never converts to “delivered” and the package is declared lost.
Build a nightly job that joins the carrier manifest to your internal order table. Flag any label still “arrived” after T+24 h.
Auto-deduct the penalty from the weekly invoice to enforce compliance without lengthy negotiations.
Penalty Revenue Recognition
Book carrier credits as contra-expense, not income. Auditors require clear segregation to avoid revenue misstatement.
Include the SLA table in every routing guide so that new carriers understand the cost of scan gaps.
Customer Service Scripts: Exact Wording to Defuse Tickets
Agent opens with: “I see your package reached our local hub at 06:14 today; the next scan will be at your door.” The customer instantly grasps the sequence.
Avoid saying “it’s almost delivered” because that implies ownership transfer has already happened. Instead, quote the estimated delivery window pulled from the route optimization engine.
Offer a proactive replacement only after the status has been “delivered” plus 36 h with no customer confirmation. This balances fraud prevention with goodwill.
Macro Library Maintenance
Update macros every time carriers tweak status language. Stale scripts create mismatched expectations and negative CSAT.
Log macro usage frequency to retire low-impact snippets and keep the library lean.