DEV Community

Cover image for Shipment Exception Management: From Package Status to a Closed Ticket
EveryInfra for EveryInfra

Posted on Originally published at everyinfra.com

Shipment Exception Management: From Package Status to a Closed Ticket

On November 21, 2026, from 00:15 to 00:22 Singapore time (SGT), we used the EveryInfra trustpilot/reviews capability. We pulled the 20 newest one- and two-star reviews for each of five carriers: FedEx, UPS, DHL, USPS and Evri. That gave us 100 complaints. We sorted them with a set of keyword rules. The rules matched only 52 reviews to an exception type that a carrier event code can express. The other 48 were about customer service only, or the rules did not recognize them.

We then read the 34 unmatched reviews by hand. Three problem types came out of them. Ten were delays written as durations, such as "seven days for a three-hour trip". Five were parcels left in the rain, over a fence or in a bin.

Six were about a counter or pickup point that refused a parcel. The last two types have almost no match in standard carrier statuses. A shipment exception product must handle both halves: the events that carriers send, and the problems that carriers never report.

Key points

  • Of 100 carrier complaints, keyword rules mapped 52 to an operational exception type. After manual reading of the 34 unmatched reviews, delays went from 13 to 24.
  • "Left in an unsafe place" (5) and "counter or pickup point" (6) have no matching value in the Shopify or EasyPost status lists.
  • The newest 20 negative reviews covered 1.1 hours for Evri, 23.7 hours for FedEx and 238.8 hours for USPS.
  • Evri has a TrustScore of 4.1 from 5,809,104 reviews. FedEx, DHL and USPS each have 1.2, and UPS has 1.1. Evri replied to all 20 of its newest negative reviews. The other four replied to none.
  • With the public FedEx default quota, polling 10,000 active packages every 30 minutes takes 480,000 calls per day. That is 4.8 times the default Track quota of 100,000 per project per day.
  • The complaint types, arrival speeds and costs come from live calls on November 21. The data model, push and polling, quotas and status lists come from public carrier and platform documents. We did not call carrier APIs.

What "exception" means in 100 real complaints

The trustpilot/reviews capability takes a company domain in company. We also set stars to one and two, and date to last30days. One call returns 20 reviews and costs $0.001389, per the EveryInfra catalog that we read at 00:13 SGT on November 21, 2026. We made one call per carrier.

The reviews were posted between November 10 and November 20, 2026. The country field showed 44 from the United States and 40 from the United Kingdom. Ninety-seven had one star.

Each review has an experience_at date, which the reviewer enters, and a posted_at timestamp. The median gap between them was zero days. Most people write the complaint on the same day that the problem happens. That makes public reviews a fast signal, often faster than a support ticket that waits in a queue.

We fixed the keyword rules at 00:17 SGT. At that time the FedEx batch (pulled at 00:15) was already saved, and the other four carriers were not yet pulled. We did not change the rules after that. A review can match more than one type. For example, "lost parcel, called three times, nobody answered" counts as both "lost" and "customer service". All 100 reviews in this batch were in English, which the rules require.

# Fixed on Nov 21, 2026 at 00:17 SGT (FedEx batch saved, other four not pulled); not changed after
RULES = {
    "delivered_not_received": r"(marked|shows?|showing|said|says|status)\s+(as\s+)?delivered|never (received|got) (it|my|the)|not delivered",
    "lost_missing": r"\blost\b|missing|disappear|never (arrived|came|showed)|stolen",
    "delay_no_scan": r"\bdelay|late\b|stuck|no update|hasn'?t moved|still in transit|on hold",
    "failed_attempt_address": r"attempt(ed)?|nobody (was )?home|left a (card|note)|missed (delivery|you)|address|redeliver",
    "damaged": r"damaged|broken|smashed|crushed|torn|opened",
    "customs_duties": r"customs|dut(y|ies)|import (fee|tax)|brokerage|clearance|\bvat\b",
    "return_to_sender": r"return(ed)? to sender|sent back|returning to",
    "tracking_inaccurate": r"tracking (is |was )?(wrong|inaccurate|useless|incorrect)|tracking (said|says|showed)|lied",
    "customer_service": r"customer service|support|call(ed)?\b|chat|agent|hung up|claim",
}
Enter fullscreen mode Exit fullscreen mode

Here are the results. Fifty-two reviews matched at least one operational type. Fourteen matched only "customer service". Thirty-four matched nothing.

"Failed attempt or address" had the most matches with 25. "Lost or missing" had 15, "delay" had 13 and "damaged" had 5. Thirty-eight reviews mentioned customer service, calls, chat or claims. That is more than any single operational type.

The UK regulator Ofcom found a similar pattern in its annual parcel survey of October 27, 2026. Satisfaction with contacting a parcel firm fell from 47% to 43% across all operators (Ofcom, Oct 27, 2026). In other words, the contact step fails often, and the complaint about the contact step can hide the delivery problem behind it.

Horizontal stacked bar chart of 100 one- and two-star carrier reviews by problem type. Grey shows matches from keyword rules and teal shows reviews that the rules missed and that we added by manual reading. Delay or no movement: 13 from rules plus 11 manual, 24 in total. Failed attempt or address: 25, all from rules. Lost or missing: 15. Left in unsafe place: 5, all manual. Counter or pickup point: 6, all manual. Damaged: 5. Delivered, not received: 1 plus 2, 3 in total. Extra fees: 2, manual. Customs or duties: 2. Wrong tracking: 2. Returned to sender: 1.

At 00:32 SGT we read the 34 unmatched reviews one by one and gave each a label. One person did the labels and nobody checked them a second time. That is a limit of this data. The largest missed group was delay.

Ten reviews described a delay with a duration and did not use "delay" or "late". One reviewer wrote that a parcel from a seller three hours away took seven days. Another wrote that a parcel sat six days in the Indianapolis distribution center and took ten days in total. One more parcel showed "out for delivery" and then appeared in another state the next day.

The second missed group was counters and pickup points, with six reviews. A UPS store did not print a return label. A USPS window refused prepaid parcels. An Evri partner shop did not release a parcel against a valid code.

The third group was "left in an unsafe place", with five reviews. Parcels were left by a garage door in the rain, thrown over a fence, put in a bin or left at a care home door. The rest were extra fees (2), a "delivery" photo without a knock (2) and no way to reach anyone (3). There were also four insults with no detail and one positive review that the author rated two stars.

With the manual labels added back, delay goes from 13 to 24. That is almost equal to "failed attempt or address" at 25. The lesson for product design is direct. If you classify free text with keywords only, you miss almost half of the most common exception type. A delay check must compare the promised date with the days already spent. It cannot wait for the word "delay" to appear in a text field.

The half that carrier event codes do not cover

Next, we compared these types with three common status lists. Shopify FulfillmentEventStatus has 11 values. They are ATTEMPTED_DELIVERY, CARRIER_PICKED_UP, CONFIRMED, DELAYED, DELIVERED, FAILURE, IN_TRANSIT, LABEL_PRINTED, LABEL_PURCHASED, OUT_FOR_DELIVERY and READY_FOR_PICKUP (Shopify docs, read Nov 21, 2026). EasyPost trackers have 10 statuses, from unknown and pre_transit to failure, cancelled and error (EasyPost support, updated Nov 3, 2026).

AfterShip adds sub-statuses under its 9 main statuses (AfterShip delivery statuses). Examples are Exception_007 for an incorrect address, Exception_013 for a lost shipment and Exception_018 for missing documents. Delivered_004 means delivery to a neighbor (AfterShip sub-statuses). The table maps our complaint types to these lists.

Complaint type Count in 100 Shopify status EasyPost status AfterShip sub-status example
Delay / no movement 24 DELAYED No specific value; stays in_transit Exception_016 processing delay, Pending_005 no update in 120 days
Failed attempt / address 25 ATTEMPTED_DELIVERY No specific value AttemptFail_002 addressee not available, Exception_007 incorrect address
Lost / missing 15 No specific value failure or error Exception_013 shipment lost
Damaged 5 No specific value None Exception_012 shipment damaged
Delivered, not received 3 Shows only DELIVERED Shows only delivered Shows only a delivered sub-status such as Delivered_004
Left in unsafe place 5 None None None
Counter / pickup point 6 None (READY_FOR_PICKUP only means ready) None (available_for_pickup only means ready) Exception_008 covers only a missed pickup by the recipient
Extra fees 2 None None Exception_005 held for payment

The rows that match show that standard statuses are a good start. The three rows that do not match are the extra work for an exception product. "Delivered, not received" is the hardest row. In the event stream it is a normal delivered event, so the system never marks it as an exception by itself.

The USPS Office of Inspector General audited this problem in the Chicago District. The audit covered October 1, 2014, to July 31, 2015. In that time, 10,181 packages at 30 delivery units got a "delivered" scan before the carrier left the office. It also found 296,219 delivery scans with no location data (USPS OIG audit DR-AR-16-003).

The report is old, but its main point still holds. A "delivered" status is one scan. It is not a confirmation from the recipient.

Carriers also work on this gap. UPS started Protected Delivery on November 16, 2026. The recipient gives a PIN to the driver to release the package. The service costs $10.70 per shipment (Supply Chain Dive on the UPS Q3 call). For a merchant, this service can reduce "delivered, not received" cases. But it adds a cost and it works only for packages that use it.

A more practical approach is to treat "customer says not received" as a separate event source. Three signals should move a delivered package back into the exception queue. They are a "not received" click on the order page, a support ticket with those words and a spike of similar public complaints.

Separate the order from the physical package

The first point of the original version stays the same. An order, a shipment, a physical package and a tracking number are four different objects. The Shopify Fulfillment object describes "a shipment of one or more items from an order". It records which line items and quantities shipped, and which tracking data goes with them (Shopify Fulfillment docs).

One order can have many shipments. One shipment can have many packages. A package can get a new number when a last-mile carrier takes it. If your database keeps one tracking_number column on the order table, the status of the second package overwrites the first one. Then the order page shows "delivered" while two items are still on a truck.

Diagram with four columns from left to right: Order, Shipment, Package and Tracking ID. Order 1042 splits into Shipment A, which left on Nov 18, and Shipment B, which left on Nov 19. Shipment A holds Package 1 and Package 2. Shipment B holds Package 3. Package 1 has a FedEx number with 9 events. Package 2 has a DHL number with 6 events. Package 3 has a UPS number with 4 events, and a dashed arrow links it to a last-mile number marked replaced_by. A note at the bottom says the order page shows 1 of 3 delivered, 2 in transit and 1 exception.

Each of the four layers needs its own fields:

Layer What it represents Required fields Who changes it
Order Commercial promise to the customer Promised delivery date, sales channel, contact preference Merchant system
Shipment One fulfillment run Warehouse, ship time, carrier and service level, line items Warehouse or 3PL
Package One physical item Weight, size, high-value flag, restricted items such as batteries Packing step
Tracking ID Carrier plus number Carrier code, number, replaced_by, last-mile number, first and latest event time Events only

Events attach only to the tracking ID. They roll up to the package, the shipment and the order. When an order splits, the customer sees one order-level line, such as "1 of 3 delivered, the other two due tomorrow and the day after". The customer does not get three emails that disagree.

When a carrier merges or relabels a parcel, the old number may stay active. FedEx lets you track by a door tag number, which starts with "DT" and has 12 digits. FedEx links it back to the original number (FedEx Track API docs). So one package must be able to hold more than one number, with the relation between them.

Isometric illustration. An open cardboard box in the center stands for one order. Three conveyor belts carry three small parcels to three different grey vans. One belt is stopped, and a teal warning light sits above its parcel, which shows that only one of three parcels has an exception.

After an order splits, an exception usually affects one physical parcel. The order page must say which one. Generated illustration (gpt-image-2.5), drawn for EveryInfra

This structure also helps outside split orders. A return is another tracking ID that moves the other way. A replacement is a new shipment under the same order. A refused parcel gets a new event on its original tracking ID. When all of these live in one relation table, support can answer "how many items of this order are on the road now". Finance can answer "which package does this refund belong to".

Normalize statuses, but keep the raw carrier event

You can reduce your internal stages to a short list: label created, picked up, in transit, out for delivery, delivered, exception, returning and unknown. Each event must still keep the carrier's raw code, raw description, location, event time, receive time and a reference to the raw payload. The normalized stage drives the workflow. The raw event supports review and reconciliation.

Keep raw events because carrier APIs change, and the changes often affect format, not business fields. On April 8, 2026, DHL sent a notice to subscribers of Unified Tracking, both pull and push. After its platform upgrade, DHL would send all HTTP header names in lower case. It would also accept only TLS 1.3 and a short list of TLS 1.2 cipher suites. The switch took place from April 27 to April 30 (DHL Unified Push page). Code that read headers by exact case failed silently that week.

USPS retired its old Web Tools APIs on January 25, 2026. The new APIs run on apis.usps.com, and tracking push uses Subscriptions - Tracking 3.2 (USPS Web Tools migration page; USPS developer portal). FedEx returns the error code TRACKING.AUTHENTICATEDDELIVERY.ERROR from its basic Track API for packages with Authenticated Delivery. For those, you must use account-based subscriptions (FedEx Track API docs).

Source Change in 2026 Risk without raw events
DHL Unified Tracking Header names in lower case and fewer cipher suites, April 27–30 A parse error leaves no payload to replay
USPS Web Tools retired on January 25; new host apis.usps.com No record to map old status codes to new ones
FedEx Authenticated Delivery packages return a special error code The error looks like "unknown" and the package drops out of the queue
EasyPost Event time zone comes from geocoding, else UTC (marked beta) One package mixes local time and UTC, so sorting fails

Store the three kinds of time apart. Event time is when the package was scanned. Receive time is when your system got the event. Record time is when you wrote it to storage.

EasyPost explains that some carriers send a full time zone offset and others send only local time. When it can resolve the location, it adds the local zone. When it cannot, the timestamp defaults to UTC (EasyPost support; EasyPost Tracking Guide).

So one tracker can mix local time and UTC. Store every timestamp as RFC 3339 with an offset (RFC 3339). Convert to the recipient's time zone only for display. The GS1 EPCIS standard keeps eventTime and recordTime as two fields (GS1 EPCIS standard). You do not need the full standard to copy that split.

Map stable codes first, and use description text only as a fallback. The complaint data gives a parallel example: ten delays used durations and thirteen used keywords. Carrier description text also changes its words and its language. Do not map an unknown code to "in transit" by default. Send it to a review queue. A person confirms the mapping once, and then the system applies it.

Expected date changes: measure delay by date, not by keyword

In the first section, ten delay complaints did not use the word "delay". They said "seven days", "ten days" or "over a week". Carrier events have the same gap. Many delays never produce an event called "delay". They show up only as a later expected date, or as a long time without a new scan. So a delay check must use dates, not status names.

Use three dates. The first is the date that you promised the customer, which lives on the order. The second is the current carrier estimate or window, which lives on the tracking ID. The third is the time of the latest scan. The FedEx basic Track API returns whether a package is on time, early or late, with a reason.

Its documentation also says that not every tracking number returns an estimated delivery (FedEx Track API docs). DHL Unified Tracking returns an estimated delivery time "where available" (DHL Shipment Tracking - Unified). If the source gives no estimate, compute a reference value from service standards and your own history. Mark it as an estimate on the card.

Case Rule Goes to the exception queue?
Carrier estimate moves later but stays before the promised date Update the order page only No
Carrier estimate moves past the promised date Log "expected delay" and notify the customer Yes, owner is support
No carrier estimate, and the service standard has passed Use the standard plus 2 days as a reference; log "possible delay" after that Yes, a logistics specialist traces it first
No new scan for more than 48 hours Log "no movement" whatever the estimate says Yes, poll once more before you decide
Many packages of one carrier in one region move late together Merge them into one incident Yes, once, not one ticket per package

USPS gives a number that you can use. In the 2025 peak season, its average delivery took 2.5 days (USPS news release, Oct 22, 2026). In our data, 9 of the 20 USPS complaints were delays, and they described 7 days, 10 days and "over a week". Use the average plus 2 days as a reference line. Then these packages enter the queue on day 4.5, or about day 5. That is two to five days before the customer wrote the complaint. This is how you measure lead time: the time the system flags an exception minus the time of the first customer complaint.

In peak season, when one sorting center has a backlog, or one airport cuts capacity, hundreds of packages move late on the same day. One ticket per package floods the support team. One incident with a list of affected packages needs only one date update and one notice.

An exception is not a red label

Two events can both say "exception" and need completely different actions. An address problem needs contact with the recipient. A customs hold needs a commercial invoice or a product identifier. A weather delay first needs a new expected date. A failed attempt can allow a new delivery date.

A long gap without scans needs a carrier trace. "Delivered, not received" needs a proof of delivery and a location check before you decide on a replacement or a claim. So your product must describe each exception as "cause + owner + due time". One generic delay email is not enough.

Cause Suggested owner First action Due time guide Who approves money actions
Wrong address / recipient away Support Confirm the address or a new date with the recipient Within the carrier hold period, often a few business days Not applicable
Customs / missing documents Cross-border operations Add invoice, product identifiers, tax ID Per destination customs Finance approves prepaid duties
No scans for a long time Logistics specialist Open a carrier trace Per carrier trace rules Not applicable
Delivered, not received Support and risk Get proof of delivery and location, then decide Within the carrier claim window A manager approves replacement or refund
Damaged Support Collect photos and file a claim Within the carrier claim window A manager approves refund
Unsafe place / counter problem Support Log it and report it to the carrier; change last-mile service if needed Next business day Not applicable

From November 1, 2026, the European Union requires product identifiers in customs declarations for imported goods sold at a distance to EU consumers. There are three: the merchant product identifier (M-PID), the non-standardized manufacturer identifier (NS-PID) and the standardized identifier (S-PID), such as an EAN or UPC. The identifiers were voluntary from July 1 to October 31 and became mandatory on November 1 (EC DG TAXUD, Nov 3, 2026).

FedEx and Shippo both tell shippers to add PIDs to the commercial invoice (FedEx EU customs changes; Shippo support). For your queue, this creates a new type of customs exception after November 1. The owner is not support. The owner is the person who maintains product master data. The missing barcode lives in the product record, so one fix solves every later parcel of that product.

Isometric illustration. A long table holds a neat row of grey cards that stand for package events. At the right end, three cards sit in a small tray, and one of them is teal. Next to the tray are three small desks with a magnifying glass, a telephone and a stack of forms. Dotted lines link the tray to each desk, which shows that each exception goes to a different owner.

An exception queue picks out the few events that need a person, then routes them by cause to tracing, customer contact or document work. Generated illustration (gpt-image-2.5), drawn for EveryInfra

Exception rules also need order context. High-value goods, cold chain items, holiday gifts and orders with a fixed delivery date need different wait limits. In the United States, delays also connect to a federal rule. The FTC Mail, Internet, or Telephone Order Merchandise Rule sets the shipping time. A seller must have a reasonable basis to ship within the stated time, or within 30 days if it states no time. A late seller gets the buyer's consent or refunds the money (FTC rule; FTC guide).

On October 6, 2026, the FTC said it was sending more than $100,000 to consumers. The money is redress for the shipping and refund practices of GOAT (FTC press release). On October 23, Reuters reported that Shein agreed to pay $100 million to settle an FTC investigation (Reuters, Oct 23, 2026). The investigation was about delivery delays and customer complaints. Check the rule text yourself and ask your own counsel about your duties. In the product, make three fields mandatory on each exception card: delay notice sent, customer consent, and refund status, each with a timestamp.

A workable exception card holds at least the following data. It shows the order, all related packages, and how many are done. It shows the current event, the raw carrier text, the event time, the receive time and the data age. It shows the original and the new expected date, with the cause of the change.

If the source gives no window, the field stays empty. It shows the suggested action, the owner team, whether the customer got a notice, and the next check time. It also shows which approvals a refund, replacement, address change or claim needs, so support staff do not trigger a real payment by mistake.

Check push and polling against each other

All major carriers offer push updates. DHL Unified Push, version 1.2.5, lets you subscribe by tracking number (DHL Unified Push). USPS Subscriptions - Tracking 3.2 sends tracking events to a server URL that you register (USPS developer portal). UPS has the Track Alert API (UPS Developer Portal).

FedEx offers account-based subscriptions in its advanced tier (FedEx Track API docs). Push removes most polling. But push messages can repeat, arrive out of order, or get lost when your receiver is down. So you still need polling to fill gaps.

Push options differ by carrier. This table shows what the public documents said when we read them on November 21, 2026.

Carrier Push method Gaps and limits
DHL Unified Push 1.2.5, subscribe by number Header names in lower case after the April upgrade
USPS Subscriptions - Tracking 3.2, register a server URL Web Tools retired on January 25
UPS Track Alert API Details need a portal login
FedEx Account-based subscriptions in the advanced tier Basic Track takes up to 30 numbers per call; Track quota defaults to 100,000 per day

Quotas set the cost of polling. FedEx publishes three limits (FedEx quotas and rate limits guide). First, each organization has a daily request quota; the guide uses 500,000 as an example. Second, each project has a quota per capability, and Track defaults to 100,000 requests per day across its six endpoints. Third, each project has a rate limit of 1,400 requests per 10 seconds. The OAuth endpoint also has per-IP thresholds, and a breach gives a 10-minute 403 penalty.

One Track request can carry up to 30 tracking numbers (FedEx Track API docs). Batching numbers can cut calls by a factor of 30. Many systems still query one package per call, and the chart uses that case.

Bar chart with our estimate of daily tracking calls for 10,000 active packages at different polling intervals. Every 30 minutes gives 480,000 calls. Every hour gives 240,000. Every 4 hours gives 60,000. Every 12 hours gives 20,000. A dashed line marks the FedEx default Track quota of 100,000 per project per day. The first two bars are above the quota and are teal.

Polling 10,000 packages every 30 minutes needs 480,000 calls per day, which is 4.8 times the default quota. Hourly polling still needs 240,000. EasyPost shows a better pattern. It polls every few hours early in transit and more often near delivery.

It stops at once when a tracker reaches delivered, cancelled or error. An outbound tracker that stays in pre_transit or unknown stops after 7 weeks. An in-transit tracker with no new data stops after 3 months. A failure status that does not change for 2 weeks also stops (EasyPost support).

EasyPost also returns the original tracker when you create the same carrier and number again within 3 months, which prevents double billing. Poll by status and stop at a final state. Then polling cost follows the number of active packages, not the size of your order history.

Flow diagram. Two inputs on the left, carrier push by webhook and backfill polling by status, both go to a raw event store with fingerprint dedupe. Next come normalize, with a queue for unknown codes, and order roll-up, which shows n of N delivered. From there an arrow goes down to exception rules, which hold cause, owner and due time and are highlighted in teal. A dashed input from public signals, which are reviews, forums and news, also enters the exception rules. Two outputs leave the rules: a ticket for support, warehouse or finance, and a customer notice grouped by action.

Give every event an idempotency key. If the source sends a stable event ID, use it. If not, compute a fingerprint from carrier, tracking number, event code, event time and location. Write the raw event to storage first and process it later. An HTTP 200 reply means "received". It does not mean that the business action is done.

The IETF Idempotency-Key header draft reached version 08 on October 22, 2026. It defines a separate error for a repeated key with a different request body (IETF draft-ietf-httpapi-idempotency-key-header-08). Standard Webhooks 1.0.0 asks each message to carry a unique ID and a timestamp, so the receiver can drop duplicates (Standard Webhooks spec). CloudEvents uses source plus id to identify one event (CloudEvents spec). Our idempotency key test covers the caller side of the same problem: how retries avoid a double charge.

import hashlib, json

def event_fingerprint(carrier: str, tracking: str, ev: dict) -> str:
    """Use these fields when the source has no event ID. Push and polling share this function."""
    key = {
        "carrier": carrier.lower(),
        "tracking": tracking.strip().upper(),
        "code": ev.get("code") or ev.get("status"),
        "event_time": ev["event_time"],          # RFC 3339 with offset
        "location": (ev.get("postal_code") or ev.get("city") or "").upper(),
    }
    return hashlib.sha256(json.dumps(key, sort_keys=True).encode()).hexdigest()

# On insert: INSERT ... ON CONFLICT (fingerprint) DO NOTHING
# Same fingerprint, different payload: log "payload_mismatch" for a person; do not overwrite
Enter fullscreen mode Exit fullscreen mode

The cross-check between push and polling can stay simple. Each day, take a random 1% of active packages that got a push in the last 24 hours. Poll them once and compare the latest event. Then poll every active package that got no push for 48 hours. The first check finds lost push messages. The second check finds stuck parcels.

Add public signals to the exception queue

Carrier events tell you what happened to one package. Public reviews, forums and news tell you what is happening to a group of packages. The 100 complaints in the first section are this kind of signal. Suppose complaints about "left in an unsafe place" for one carrier jump in one city in one day. Your event stream has no code for that. But your support team will see the same tickets the next day.

EveryInfra can return public carrier reviews (Trustpilot data API), forum posts (Reddit data API) and news (Google News API). These are public page data, not carrier tracking data. EveryInfra has no carrier tracking capability. For tracking, you still connect to the carriers or to a tracking aggregator.

One request looks like this:

curl -s https://api.everyinfra.com/api/v1/social \
  -H "Authorization: Bearer ${EVERYINFRA_API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{"platform":"trustpilot","action":"reviews",
       "params":{"company":"dhl.com","stars":["1","2"],"date":"last30days"}}'
Enter fullscreen mode Exit fullscreen mode

Each review in the response has 24 fields (trustpilot/reviews capability page). For exception work, use title and text for classification, rating, and country for the market. Use experience_at and posted_at for signal delay, reply_text and reply_at for the carrier's reply, and company_domain. The fields author_name, author_id and author_image hold personal data. Your exception analysis does not need them, so drop them before you store anything.

Screenshot of a real EveryInfra API response. The top line shows the POST URL, the trustpilot/reviews capability, the parameters company=dhl.com, stars=1,2 and date=last30days, and the time Nov 21, 2026 00:17 SGT. The JSON below shows count 20 and one expanded DHL one-star review. Teal boxes mark rating 1, experience_at Nov 19, posted_at Nov 20 at 03:14:36 and charged_usd 0.001389 in billing. The reviewer name and ID are masked.

Part of a real trustpilot/reviews response. The reviewer name and ID are masked, and the other 19 reviews are not shown. Screenshot of a real EveryInfra API response, Nov 21, 2026 00:17 SGT

If a request is slow, add "mode":"async" to the request body. The API returns a job ID at once, and you poll GET /api/v1/jobs/{job_id} for the result. Failed calls, timeouts and empty results are not charged. Our API error self-healing guide explains how to retry each error code. We fetched the UPS reviews and the UPS profile in async mode.

Filter Reddit and news results for relevance first. Four reddit/search calls returned 14 posts, and only 5 were about parcels. The 3 newest posts for "tracking stuck in transit" were about astrology and multiple sclerosis. In astrology, a "transit" is the movement of a planet. The query "lost package claim carrier" returned 7 posts, and 3 of them were silver coin sales.

Two of the 5 useful posts came from the community of UniUni, a North American last-mile carrier. Both said the order showed "delivered" with a photo, but the item was not there. This is the same "delivered, not received" type that we found in the reviews.

The google_news/search call for "parcel delivery delays" in the past week returned 10 articles. Five reported specific delays or backlogs, 2 covered UK courier league tables, 1 warned about parcel text scams and 2 were off topic. On November 14, 2026, Better Retailing reported on a UK partner store of Relay. It held more than 100 parcels for days before a driver came (Better Retailing, 2026-11-14). This matches the "counter or pickup point" group that we found by hand. Put the carrier name or words such as "parcel" or "package" in each query. Then run the results through the same rules as the reviews before they go to the queue.

Horizontal stacked bar chart of 6 keyword searches, showing how many results were about a specific delivery problem. Reddit "tracking stuck in transit": 0 of 3. "package marked delivered but not received": 1 of 1. "package says delivered but not received": 2 of 3. "lost package claim carrier": 2 of 7. News "parcel delivery delays": 5 of 10. "Correos retrasos paquetes": 5 of 10. In total, 15 of 34 results were relevant.

The first use of public signals is to set how often you check them. The chart shows how much time the newest 20 one- and two-star reviews covered for each carrier. Evri's 20 reviews arrived within 1.1 hours. FedEx took 23.7 hours, DHL 27.3 hours, UPS 46.7 hours and USPS 238.8 hours, or about 10 days.

Horizontal bar chart on a log scale showing the hours covered by the newest 20 one- and two-star reviews per carrier. Evri 1.1 hours, in teal. FedEx 23.7 hours. DHL 27.3 hours. UPS 46.7 hours. USPS 238.8 hours. A shorter span means the same public signal needs more frequent checks.

The spans differ by more than 200 times. One polling interval for all sources wastes calls. Hourly checks can still miss Evri complaints, while one check per day is enough for USPS. At 00:47 SGT we pulled FedEx again with date: last7days. Of the 20 reviews, 19 matched the 00:15 batch and 1 was new, posted at 00:30 SGT. At 20 reviews in 23.7 hours, the expected count for 32 minutes is about 0.45, so 1 new review is the same order of magnitude.

The second use is to see the structure of problems for each carrier. The heat map splits the 100 complaints by carrier, with the manual labels included. USPS had 9 delays out of 20. DHL and FedEx each had 7 "failed attempt or address" cases. Evri had the widest spread and the most "left in an unsafe place" cases, with 4. UPS had 11 reviews that mentioned customer service.

Heat map with five carriers as rows and eight problem types as columns. Each cell holds a count, and each carrier has 20 reviews. Evri: delay 4, failed attempt 3, lost 4, unsafe place 4, counter 1, damaged 3, delivered not received 1, support 8. USPS: delay 9, failed attempt 1, lost 4, counter 3, support 3, all others 0. DHL: delay 6, failed attempt 7, lost 2, support 9. UPS: delay 4, failed attempt 7, lost 4, counter 1, damaged 1, delivered not received 1, support 11. FedEx: delay 1, failed attempt 7, lost 1, unsafe place 1, counter 1, damaged 1, delivered not received 1, support 10.

The third use is a warning: do not rank carriers by stars. The trustpilot/profile capability returned these TrustScores. FedEx had 1.2 from 55,710 reviews, DHL 1.2 from 30,043, USPS 1.2 from 9,645, UPS 1.1 from 51,762 and Evri 4.1 from 5,809,104. Evri has more than 100 times as many reviews as FedEx. It also replied to all 20 of its newest negative reviews, and the other four carriers replied to none.

On November 18, 2026, the UK consumer charity Citizens Advice published its sixth yearly Parcels League Table. It scores the five largest parcel companies on delivery and collection, accessibility, customer service and trust. Royal Mail was first with 3 stars out of 5, and Evri was last with 2 stars (Citizens Advice press release, Nov 18, 2026).

The survey ran from September 17 to 29 with 10,000 UK adults who got a parcel in the past month. Of them, 30% had a delivery problem in that month. Of the people with a problem, 35% had more trouble when they tried to fix it. Two results of our 00:46 SGT news search covered this table.

Source Measure Evri Comparison
Trustpilot (read Nov 21, 2026) TrustScore (out of 5) 4.1 from 5,809,104 reviews FedEx, DHL and USPS 1.2; UPS 1.1
Ofcom yearly survey (Oct 27, 2026) Satisfaction with contact and complaints 26%, last Amazon and FedEx 56%, joint first
Citizens Advice league table (Nov 18, 2026) Overall score (out of 5 stars) 2, last Royal Mail 3, first

In the Ofcom survey of the same period, Evri came last for contact and complaint handling at 26%. Amazon and FedEx shared first place at 56% (Ofcom, Oct 27, 2026). Trustpilot's business guidelines, version 7.3 from September 2026, allow companies to invite customers to review (Trustpilot Guidelines for businesses). The invitations must be fair and have no incentives.

Its "Action We Take" policy also bans inviting only happy customers (Trustpilot Action We Take). Public sources do not show how much each carrier invites reviews or how much that moves the score. The TrustScore points one way, and the Ofcom and Citizens Advice rankings point the other way. So do not choose a carrier by stars alone. For an exception queue, the content and the arrival speed of complaints are the useful parts.

Bar chart of Trustpilot TrustScore out of 5. FedEx 1.2 with 55,710 reviews and 0 of 20 negative reviews replied. UPS 1.1 with 51,762 reviews and 0 replied. DHL 1.2 with 30,043 reviews and 0 replied. USPS 1.2 with 9,645 reviews and 0 replied. Evri 4.1 with 5,809,104 reviews and 20 of 20 replied, in teal.

Public signals cost little to add. Set a check rate for each carrier from the speeds we measured. Check Evri every hour, which is 24 calls per day. Check FedEx and DHL every 6 hours, UPS every 12 hours and USPS once per day. That is 35 trustpilot/reviews calls per day at $0.001389 each, or $0.048615. Add 4 daily calls to reddit/search and 4 to google_news/search, at $0.000792 each, for $0.006336. The total is $0.054951 per day, or about $1.65 for 30 days. See the trustpilot/profile capability page and the pricing page for current prices. Failed calls, timeouts and empty results are not charged.

Source Rate Calls per day Cost per day (USD)
Evri reviews Every hour 24 0.033336
FedEx reviews Every 6 hours 4 0.005556
DHL reviews Every 6 hours 4 0.005556
UPS reviews Every 12 hours 2 0.002778
USPS reviews Once a day 1 0.001389
reddit/search Every 6 hours 4 0.003168
google_news/search Every 6 hours 4 0.003168
Total — 43 0.054951 (about 1.65 per 30 days)

If your support team works in Claude or another MCP client, the same capabilities are also available as a remote MCP server. See the MCP server page for setup and tool names. Give the model counts and examples of complaints for one carrier and one type in the last 24 hours. Do not let it change package status. Public signals feed only the exception rules, as one input to the question "should we contact the customer early".

Notify customers about actions, not scans

A notice for every hub scan only adds noise. Customers care about a few moments. The carrier has the parcel, the expected date moves a lot or they must do something. The parcel is out for delivery, part of the order arrived or all of it arrived. Group notices at the order level. When two packages update in the same minute, send one message.

Trigger Send? Content
Each hub scan No Update the order page only
Expected date moves by more than 1 day Yes New date, cause if the source gives one, what the customer can do
Customer action needed (address, duties, pickup) Yes The exact task; link only to your order page
Partial delivery Yes Items delivered, items left, expected date for the rest
"Delivered" but customer clicked "not received" Send to support, not to the customer Proof of delivery, location, next step time

An exception notice states the known facts, the unknown parts and the next step. "One item is on hold because of an address problem; please confirm the address on your order page" helps more than "Your order has an exception". Link only to your own order page. Do not use carrier short links, and never ask for payment by text message.

The FCC lists "missed delivery, click to reschedule" as a common start of delivery scams. It also says that USPS sends tracking texts only to people who signed up. Those texts do not contain links (FCC package scam guide). The US Postal Inspection Service and the FTC give the same warning (USPIS smishing notice; FTC consumer alert). The more your notice looks like a scam text, the fewer customers click it.

Internal support can see more data, but limit personal data. Article 5 of the EU GDPR says personal data must be kept in an identifiable form no longer than the purpose needs (GDPR text). A product can mask the recipient's phone and address after delivery and after the after-sales period ends. Check the regulation and ask your own counsel about the retention period. The same applies to public reviews. Your analysis needs the text and the time, not the reviewer's name or photo. Before you use Reddit posts, check its terms for user content yourself (Reddit Data API Terms).

What peak season adds to the queue this month

These changes from October 22 to November 21, 2026, affect exception work directly.

Date (2026) Change What it adds to your queue
Oct 22 USPS expects about 40% more volume from Oct 1 to Dec 31 Shorter USPS event delay; long delays point to your own pipeline
Oct 26 Q4 ground prices up 5.8%, express up 13.8%; fuel surcharges near 29% More "extra fees" complaints
Oct 27 Ofcom: 71% of UK recipients had a delivery problem "Left in an unsafe place" needs its own type
Nov 1 EU product identifiers become mandatory New customs document exceptions
Nov 16–20 Shenzhen airport cargo limits during APEC Grouped late first scans from South China

On October 22, USPS said that mail and package volume rises about 40% from October 1 to December 31. In the 2025 peak, the average delivery took 2.5 days, down from 2.8 days the year before. Its new tracking platform is almost four times faster than the old one. An update often appears within one minute of a scan (USPS news release, Oct 22, 2026). For you: USPS event delay should be short. If you see a much longer delay, check your own push or polling first.

For delivery before December 25, USPS recommends sending by December 17 for Ground Advantage and First-Class. The dates are December 18 for Priority and December 19 for Priority Mail Express (Postal Bulletin 22714). For you: gift orders that ship by Ground Advantage after December 17 should show a warning on the order page.

On October 26, Reuters reported that US ground parcel prices would rise 5.8% year over year in the fourth quarter. Express prices would rise 13.8%.

At a diesel price of $6.28 per gallon on October 19, the UPS fuel surcharge was 29.5% and the FedEx surcharge was 29%. USPS has charged an 8% fuel surcharge on most packages since April (Reuters, Oct 26, 2026. Diesel prices come from the US Energy Information Administration. For you: "extra fees" complaints may grow in peak season. The exception card must separate carrier surcharges from customs duties.

On October 27, Ofcom published its annual parcel survey. UK parcel volume reached a record 4.6 billion last year, up 8.6%. In the past six months, 71% of recipients had a delivery problem, up from 68%. The most common problems were delays (32%) and parcels left in an unsuitable place (28%).

Next came drivers who did not knock loudly enough (25%) and not enough time to answer the door (20%) (Ofcom, Oct 27, 2026). For you: "left in an unsafe place", which our rules missed, ranks second in the UK survey. A queue for UK customers needs a separate type for it.

From November 1, EU product identifiers became mandatory, as described above. For you: parcels to the EU get a new document exception, owned by whoever maintains product data.

From November 16 to 20, during the APEC summit, Shenzhen airport did not allow cargo on international passenger flights, and domestic capacity fell by 80%. Some freighters moved to other airports or paused (Air Cargo News, November 2026). For you: cross-border parcels flown out of South China in those days will show late first scans together. Merge those delays into one incident.

Attach the list of affected orders, update the expected date once and send one notice. Our weather alert operations method uses the same "one incident, many orders" pattern for regional alerts. Also on November 16, UPS started selling Protected Delivery, as described above.

Start the MVP with an exception queue, not a map

The first version can cover one store, two carriers and the latest batch of active orders. First prove these parts: links between orders and many packages, event dedupe, status mapping, changes to the expected date, and three frequent exception types. Then connect support tickets. Maps, prediction models and full carrier coverage can come later.

Stock and reorder alerts before shipment are a different product; see our inventory replenishment method. Exception work starts with the first event after the parcel leaves the warehouse. From the complaint data, a good first set of three types is delay (including long gaps), failed attempt or address, and lost. Together they cover most operational problems in our 100 complaints.

Write the metrics before you build. Track source event delay as the median and 95th percentile from event time to receive time. Track the share of unknown statuses. Track lead time, which is how many hours the system finds an exception before the customer complains. Also track duplicate notice rate, first human response time, support contacts per order, and who approves replacements and refunds. Check samples of "delivered" orders to confirm that all packages arrived, not just any one tracking number.

How we got the data

We made all live calls on November 21, 2026, in Singapore time (SGT). Prices come from the capability catalog, read at 00:13 SGT. trustpilot/reviews and trustpilot/profile cost $0.001389 per call. reddit/search and google_news/search cost $0.000792 per call. The successful calls are 19 charged calls, $0.022809 in total at catalog prices.

Time (SGT) Capability Parameters Result Charged (USD)
00:15:21 trustpilot/reviews fedex.com, 1–2 stars, last 30 days 20 reviews 0.001389
00:17:56 trustpilot/reviews dhl.com, same 20 reviews 0.001389
00:18:45 trustpilot/reviews usps.com, same 20 reviews 0.001389
00:21:52 trustpilot/reviews evri.com, same 20 reviews 0.001389
00:22:05 / 00:23:07 trustpilot/reviews ups.com, same, "mode":"async" Job ID, then 20 reviews from the job 0.001389
00:25:14–00:27:51 trustpilot/profile fedex, dhl, usps, evri, once each 4 profiles 4 × 0.001389
00:28:13 reddit/search "package marked delivered but not received", newest 1 post, relevant 0.000792
00:28:22 reddit/search "tracking stuck in transit", newest 3 posts, none relevant 0.000792
00:46:00 reddit/search "package says delivered but not received", relevance 3 posts, 2 relevant 0.000792
00:46:09 reddit/search "lost package claim carrier", relevance 7 posts, 2 relevant 0.000792
00:46:19 google_news/search "parcel delivery delays", past week 10 articles 0.000792
00:47:00 trustpilot/reviews fedex.com, 1–2 stars, last 7 days 20 reviews, 1 new 0.001389
00:49:11 / 00:50 trustpilot/profile ups.com, "mode":"async" Job ID, then the profile 0.001389
00:50:06 trustpilot/reviews correos.es (Spanish post), 1–2 stars, last 30 days 3 reviews 0.001389
00:52:22 google_news/search "Correos retrasos paquetes", Spain, Spanish, past month 10 articles 0.000792
00:52:55 trustpilot/profile correos.es 1 profile 0.001389

We fixed the rules at 00:17 SGT and finished the manual labels at 00:32 SGT. Every chart number comes from these responses. We dropped reviewer names, IDs and photos before the analysis, so they are in no count.

Limits of this data

One hundred complaints is a small sample. It shows what public negative reviews looked like for these five carriers, on this platform, over about ten days. The 20 reviews per carrier come from one API call; we did not pick them. But Trustpilot users are mostly in the US and UK, and those two countries gave 84 of the 100 reviews. Do not move these results to other markets without new data.

One- and two-star reviews come from people who had a problem. They show the type of problem. They do not show the rate of problems. For rates, use a survey with a sample design, such as the Ofcom survey of 4,179 people online in January and July 2026.

One person wrote the rules and the same person read the unmatched reviews, with no second check. The "failed attempt or address" rule includes the word address. It can count sentences such as "I changed my address and it did not help", so that type may be too high. The arrival speed comes from one moment and the latest 20 reviews. Evri's 1.1 hours may reflect a short peak.

The FedEx recheck came only 32 minutes later and found 1 new review, which is too little to set a check rate. Correos, the Spanish postal service, had only 3 reviews of 1 or 2 stars in 30 days. In markets with few reviews, this method gets almost no signal, so use local news and your own tickets there. Use these numbers to design check rates and types, not to rank carriers.

Signal Correos (Spain) FedEx (US)
1–2 star reviews returned 3 in 30 days 20 in 23.7 hours
TrustScore and total reviews 1.2 from 5,029 1.2 from 55,710
Company replies to those reviews 0 of 3 0 of 20

FAQ

What does "shipment exception" mean?

It is a carrier tracking status. It means that the package left the normal flow because of a problem such as an address issue, customs, weather or a failed attempt. The status alone does not tell you the cause. Read the event text or the sub-status. AfterShip, for example, splits exceptions into more than twenty sub-statuses, such as incorrect address, missing documents and lost (AfterShip sub-statuses).

FedEx shows a shipment exception. Will my package still arrive?

In most cases, yes. The FedEx basic Track API returns delay status and cause, and some packages get a new delivery window. The documentation says that not every tracking number returns an estimated delivery (FedEx Track API docs). As a merchant, act on the cause: contact the recipient for an address problem, and add documents for a customs problem.

What does "held, cleared regulatory agency(s) after aircraft/truck departed" mean?

Customs or another agency released the package, but the planned flight or truck had already left. So the package waits for the next one. This usually adds one or two days and needs no action from the recipient. In your queue, label it "cleared, waiting for transfer". Update the expected date and do not send an exception notice.

My package says delivered but I did not receive it. How can a system find this?

In the carrier event stream, this is a normal delivery event, so the system cannot find it alone. It needs outside signals. Examples are a "not received" click on the order page, a support ticket, or a delivery photo and location that do not match the address. A USPS OIG audit found 10,181 packages scanned as delivered before the carrier left the office (USPS OIG). Our reddit/search call at 00:28 SGT also returned a post with the same topic in a merchant disputes forum.

Should I use webhooks or polling for tracking?

Use both. Push removes most polling, but you still need polling to fill gaps. The FedEx default Track quota is 100,000 calls per project per day. Hourly polling of 10,000 packages already needs 240,000 calls (FedEx quotas guide). Push plus polling by status is the safer balance.

Can I rank carriers by their Trustpilot score?

We do not recommend it. In our data, Evri had a TrustScore of 4.1 and FedEx had 1.2. But Ofcom put Evri last for complaint handling at 26%, and FedEx first at 56% (Ofcom, Oct 27, 2026). Use the content and speed of complaints instead.

Get started

  1. Sign up in the EveryInfra quickstart and get an API key. Put it in the environment variable EVERYINFRA_API_KEY.
  2. Read the free capability catalog once. Check the parameters and the price of trustpilot/reviews.
  3. Run the curl request above for one carrier and the last 30 days of one- and two-star reviews. Read 20 reviews by hand and write rules for your own market.
  4. Set a check rate for each source from its arrival speed. Write the results to an "external signal" field on the exception card. Use them as alerts only, and do not change package status.

References

  1. Shopify, FulfillmentEventStatus (GraphQL Admin), read Nov 21, 2026, https://shopify.dev/docs/api/admin-graphql/latest/enums/FulfillmentEventStatus
  2. Shopify, Fulfillment object (GraphQL Admin), read Nov 21, 2026, https://shopify.dev/docs/api/admin-graphql/latest/objects/Fulfillment
  3. EasyPost, Understanding Trackers, updated Nov 3, 2026, https://support.easypost.com/hc/en-us/articles/360044353091-Understanding-Trackers
  4. EasyPost, Tracking Guide, read Nov 21, 2026, https://docs.easypost.com/guides/tracking-guide
  5. AfterShip, Delivery Sub-statuses, read Nov 21, 2026, https://www.aftership.com/docs/tracking/enum/delivery-sub-statuses
  6. AfterShip, Delivery Statuses, read Nov 21, 2026, https://www.aftership.com/docs/tracking/enum/delivery-statuses
  7. FedEx, Basic Integrated Visibility (Track API) documentation, read Nov 21, 2026, https://developer.fedex.com/api/en-us/catalog/track/v1/docs.html
  8. FedEx, Quotas and rate limits guide, read Nov 21, 2026, https://developer.fedex.com/api/en-us/guides/ratelimits.html
  9. DHL, Shipment Tracking - Unified (1.5.8), read Nov 21, 2026, https://developer.dhl.com/api-reference/shipment-tracking
  10. DHL, Shipment Tracking - Unified - Push (1.2.5) and platform notice of Apr 8, 2026, https://developer.dhl.com/api-reference/shipment-tracking-unified-push
  11. UPS, Developer Portal: Track Alert API, read Nov 21, 2026, https://developer.ups.com/api/reference?loc=en_US&api=trackalert
  12. USPS, Subscriptions - Tracking 3.2, read Nov 21, 2026, https://developers.usps.com/subscriptions-trackingv3r2
  13. USPS, Web Tools APIs Retired January 25, 2026, read Nov 21, 2026, https://www.usps.com/business/web-tools-apis/
  14. USPS, Postal Service Prepped To Deliver for 2026 Holiday Season, Oct 22, 2026, https://about.usps.com/newsroom/national-releases/2026/1022-postal-service-prepped-to-deliver-for-2026-holiday-season.htm
  15. USPS, Postal Bulletin 22714: 2026 Holiday Mailing and Shipping Dates, Oct 29, 2026, https://about.usps.com/postal-bulletin/2026/pb22714/html/cover.htm
  16. USPS OIG, Package Delivery Scanning: Chicago District (DR-AR-16-003), https://www.uspsoig.gov/reports/audit-reports/package-delivery-scanning-chicago-district
  17. GS1, EPCIS Standard, https://ref.gs1.org/standards/epcis/2.0.1/
  18. IETF, RFC 3339: Date and Time on the Internet: Timestamps, https://www.rfc-editor.org/rfc/rfc3339
  19. IETF, The Idempotency-Key HTTP Header Field (draft-08), Oct 22, 2026, https://datatracker.ietf.org/doc/draft-ietf-httpapi-idempotency-key-header/
  20. Standard Webhooks, Specification 1.0.0, https://github.com/standard-webhooks/standard-webhooks/blob/main/spec/standard-webhooks.md
  21. CloudEvents, Specification, https://github.com/cloudevents/spec
  22. FTC, Mail, Internet, or Telephone Order Merchandise Rule, https://www.ftc.gov/legal-library/browse/rules/mail-internet-or-telephone-order-merchandise-rule
  23. FTC, Business Guide to the Mail, Internet, or Telephone Order Merchandise Rule, https://www.ftc.gov/business-guidance/resources/business-guide-ftcs-mail-internet-or-telephone-order-merchandise-rule
  24. FTC, Redress Payments to Consumers Impacted by GOAT's Deceptive Shipping, Refund Policies, Oct 6, 2026, https://www.ftc.gov/news-events/news/press-releases/2026/10/ftc-issues-redress-payments-consumers-impacted-goats-deceptive-shipping-refund-policies
  25. FTC, Fake shipping notification emails and text messages, Dec 14, 2023, https://consumer.ftc.gov/consumer-alerts/2023/12/fake-shipping-notification-emails-text-messages-what-you-need-know-holiday-season
  26. FCC, How to Avoid Package Delivery Scams, read Nov 21, 2026, https://www.fcc.gov/how-identify-and-avoid-package-delivery-scams
  27. USPIS, Smishing: Package Tracking Text Scams, read Nov 21, 2026, https://www.uspis.gov/news/scam-article/smishing-package-tracking-text-scams
  28. European Commission DG TAXUD, Product identifiers for e-commerce imports mandatory from 1 November 2026, Nov 3, 2026, https://taxation-customs.ec.europa.eu/news/product-identifiers-e-commerce-imports-mandatory-1-november-2026-2026-11-03_en
  29. FedEx, EU customs changes, read Nov 21, 2026, https://www.fedex.com/en-se/support/clearance/customs-changes.html
  30. Shippo, EU customs update: new product identifier requirements starting November 1, 2026, https://support.goshippo.com/hc/en-us/articles/56535213758619-EU-customs-update-new-product-identifier-requirements-starting-November-1-2026
  31. EUR-Lex, Regulation (EU) 2016/679 (GDPR), https://eur-lex.europa.eu/eli/reg/2016/679/oj
  32. Reddit, Data API Terms, https://redditinc.com/policies/data-api-terms
  33. Trustpilot, Guidelines for businesses (version 7.3, September 2026), https://corporate.trustpilot.com/legal/for-businesses/guidelines-for-businesses/sep-2026
  34. Trustpilot, Action We Take (March 2026), https://corporate.trustpilot.com/legal/for-everyone/action-we-take/mar-2026
  35. Ofcom, Ofcom demands improvements from parcel firms as satisfaction declines, Oct 27, 2026, https://www.ofcom.org.uk/post/market-performance/ofcom-demands-improvements-from-parcel-firms-as-satisfaction-declines
  36. US EIA, Gasoline and Diesel Fuel Update, read Nov 21, 2026, https://www.eia.gov/petroleum/gasdiesel/
  37. Reuters, US retailers face record holiday delivery prices from surcharges tied to costlier diesel, Oct 26, 2026, https://www.reuters.com/business/retail-consumer/us-retailers-face-record-holiday-delivery-prices-surcharges-tied-costlier-diesel-2026-10-26/
  38. Reuters, Fast-fashion group Shein agrees to pay $100 million to settle US FTC probe, Oct 23, 2026, https://www.reuters.com/business/retail-consumer/fast-fashion-group-shein-agrees-pay-100-million-settle-us-ftc-probe-2026-10-23/
  39. Supply Chain Dive, UPS gears up for peak season with less Amazon volume in tow, October 2026, https://www.supplychaindive.com/news/ups-gears-up-for-peak-season-with-less-amazon-volume-in-tow/872845/
  40. Air Cargo News, Shenzhen air cargo operations face delays during APEC summit, November 2026, https://www.aircargonews.net/editorial/2026/11/shenzhen-air-cargo-operations-face-delays-during-apec-summit/
  41. EveryInfra, capability catalog, read Nov 21, 2026 00:13 SGT, https://api.everyinfra.com/api/v1/social/catalog
  42. Trustpilot, FedEx review page, read Nov 21, 2026, https://www.trustpilot.com/review/www.fedex.com
  43. Trustpilot, Evri review page, read Nov 21, 2026, https://www.trustpilot.com/review/www.evri.com
  44. Trustpilot, DHL review page, read Nov 21, 2026, https://www.trustpilot.com/review/www.dhl.com
  45. Trustpilot, USPS review page, read Nov 21, 2026, https://www.trustpilot.com/review/www.usps.com
  46. Trustpilot, UPS review page, read Nov 21, 2026, https://www.trustpilot.com/review/www.ups.com
  47. Better Retailing, Retailers report Relay parcel collection delays, 2026-11-14, https://www.betterretailing.com/retailers-report-relay-parcel-collection-delays/
  48. Citizens Advice, Almost a third of consumers faced recent parcel delivery problems (sixth Parcels League Table), Nov 18, 2026, https://www.citizensadvice.org.uk/about-us/media-centre/press-releases/almost-a-third-of-consumers-faced-recent-parcel-delivery-problems-citizens-advice-reveals/
  49. Trustpilot, Correos review page, read Nov 21, 2026, https://www.trustpilot.com/review/www.correos.es

Originally published on the EveryInfra blog: Shipment Exception Management: From Package Status to a Closed Ticket. This article was written with AI assistance; the numbers come from the API calls and sources linked above, and were checked before publishing.

EveryInfra is a pay-per-call data API for AI agents and developers: everyinfra.com.

Top comments (0)