A Shipping Promise and Shipping Performance Are Different Evidence

A merchant’s stated carrier or regional shipping policy is not the same thing as proof that every order was delivered on time or handled without issue. A published shipping policy or FAQ tells you what a merchant promises or intends; to assess actual fulfilment performance you need separate kinds of evidence: the merchant’s policy statements, records tied to specific orders, carrier records that document physical movement, and aggregated performance data that show patterns over time. Treat merchant policies as dated statements of intent, not independent proof of delivery or legal enforceability; for individual order problems contact the merchant directly [1] [3].

Why the distinction matters

• A policy or FAQ describes options, typical timeframes, and partners the merchant says it uses. It does not by itself show the merchant complied with that policy for a particular shipment.
• Individual orders can fail to meet the stated policy for many reasons — inventory errors, label mistakes, customs holds, carrier delays — and those causes are revealed only by order-level and carrier-level records.
• Aggregated data provide evidence about how often the merchant meets its stated policy, but aggregated claims need clear methodology and cannot substitute for documentation of a specific order.

Four evidence types and what each can (and cannot) show Use these categories to read claims critically.

1) Merchant policy statements (what the merchant says)

• What it is: public webpages such as FAQs and shipping pages, where merchants describe carriers used, regional coverage, shipping options, and estimated transit windows. These are merchant-authored statements of process or intent [1] [2] [3].
• What it shows: the merchant’s declared practices at a point in time — e.g., which carriers it typically uses, or that it offers expedited shipping to certain regions. These are useful for expectation-setting.
• What it does not show: that any particular order was shipped as promised, that the merchant’s statement has been independently verified, or that the policy is enforceable as legal proof. Treat the policy as a dated merchant statement, not as standalone evidence of fulfilment [3].

2) Individual order evidence (what happened to a specific purchase)

• What it is: order confirmations, dispatch notices, tracking numbers, and timestamped customer communications the merchant or customer holds.
• What it shows: whether the merchant issued a shipping label, when the order left the merchant’s facility, and what the merchant recorded about the transaction. Paired with carrier tracking this can strongly support whether an item entered the carrier network.
• What it does not show on its own: whether the package physically arrived unless corroborated with carrier scans or recipient confirmation. The existence of a label or a merchant note that an order “shipped” is not identical to carrier acceptance and movement.

3) Carrier records (what the carrier documents)

• What it is: tracking scans, pickup/acceptance timestamps, scan-location histories, and delivery confirmations maintained by a carrier.
• What it shows: where and when a package was scanned in carrier facilities, transfers between hubs, and delivery attempts or confirmations. These are the primary evidence for the package’s physical movement.
• What it does not show: internal merchant intent or that the merchant’s policies were followed for every item. Discrepancies can exist between merchant-recorded status and carrier scans; both records are needed to resolve those gaps.

4) Aggregated performance data (patterns across many orders)

• What it is: compiled statistics such as on-time delivery rates, average transit times, claim rates, and customer-service metrics derived from many orders.
• What it shows: systemic performance — for example, whether the merchant meets its stated shipping timeframes for 95% of shipments during a quarter. Aggregates are useful for assessing reliability over time.
• What they do not show: the outcome of a particular order. Aggregated success rates do not guarantee any single shipment’s performance and depend on how the data were collected and processed.

A practical approach to reading shipping evidence

• Start with the merchant’s published policy to know what the merchant says it does. Treat that as a dated declaration of intent [1] [3].
• For concerns about a specific purchase, ask for order-level documents: confirmation, shipping label details, and the tracking number. If the merchant points only to its general policy, that does not prove the specific order complied.
• Compare merchant-provided tracking or status with carrier scans. Carrier records are the most direct evidence of physical movement and delivery attempts.
• If you want to evaluate overall reliability, look for aggregated performance statistics and ask how they were calculated: sample size, period covered, and definitions (e.g., what counts as “on time”). Aggregates can indicate patterns, but methodology matters.
• Keep timelines and copies: timestamps from order systems and carrier scans are central when trying to reconcile conflicting statements.

Limitations you should expect

• Merchant policies are snapshots: they can change and should be read with their publication or last-update date in mind [3]. Policies alone do not demonstrate fulfilment.
• Records can conflict: a merchant’s system may show “shipped” while carrier scans start later or show exceptions. Resolving those conflicts requires both sets of records.
• Aggregated data can hide edge cases: even a high overall on-time percentage allows for individual failures that matter to affected customers.

When to escalate or seek support

• For individual order issues, contact the merchant’s customer support directly and request the specific order and carrier records; merchant policy pages are not a substitute for order-level evidence [1] [3].
• If the merchant is unhelpful and a significant financial or legal issue is at stake, document all communications and consider the consumer protection resources available in your jurisdiction.

In short: read a shipping promise as a starting claim, not as complete proof. Confirm with order-level documentation and carrier scans to establish what actually occurred for a specific shipment, and consult aggregated data (with attention to methodology) to understand broader reliability patterns [1] [2] [3].