Google updated its package tracking documentation on July 14, 2026, confirming that the early adopters program behind the feature is no longer accepting new partners. Shipping companies not already integrated have no route in.

The change appeared in the Search Central changelog under a single line entry dated July 14: the feature availability and eligibility requirements sections of the package tracking early adopters program documentation had been revised. The stated reason was blunt. According to Google, the package tracking early adopters program is no longer accepting new partners.

A banner now sits at the top of the developer page carrying the same message. The documentation page itself was last updated on July 14, 2026, matching the changelog date.

For shipping companies, logistics providers, and the retailers who depend on them, the practical effect is a closed door. Carriers with an existing integration continue to appear. Everyone else is outside a surface that intercepts a specific, high-intent query type before the user reaches a carrier website at all.

What the feature does

Package tracking displays shipment status information directly on Google. When someone searches for a package shipped with a participating company, they can enter a package ID into a panel that appears in results. Google then calls the carrier's API, retrieves the tracking information, and renders it inside Search.

The documentation includes screenshots of two states. The first shows an entry field labelled for tracking number input, with a button to submit. The second shows the populated result: a tracking number, an expected delivery city and date, a vertical progress list running from tracking number creation through in transit, out for delivery, and delivered, plus links to view details on the carrier site, contact support, call a listed phone number, or track another package.

Google attaches a caveat to the images, noting that the actual appearance in search results might be different.

Availability is broad. According to the documentation, package tracking is available in all languages and countries where Google Search is available. There is no country-by-country rollout schedule and no market restriction. The constraint is not geographic. It is who holds an integration.

The 700ms requirement

The technical bar for participating carriers is unusually explicit for a Google Search feature, and it has not moved.

Google expects almost no downtime from a partner's API and requires that the API respond within 700ms on average, with the 95th percentile not exceeding 1,000ms. The consequence for missing those numbers is stated in the documentation: if a partner's API does not meet the requirements, Google may stop displaying that partner's package tracking information.

That is a performance service level attached to organic search visibility, enforced by removal rather than by ranking adjustment. It applies continuously, not at onboarding. A carrier whose infrastructure degrades over time can lose the display without a policy change, a manual action, or an algorithm update.

The 95th percentile figure is the operationally demanding half of the pair. An average of 700ms tolerates occasional slow responses. A 1,000ms ceiling on the 95th percentile constrains tail latency, which is where API performance typically breaks under load - during peak shipping windows, when tracking query volume is highest and carrier systems are under the most pressure.

The integration has exactly one required field. CurrentStatus carries the current status of the package, including the date and time that status became valid and any error states.

Everything else is recommended. Google lists eleven additional fields it strongly recommends the API return:

DeliveredDate covers the day and time the package was delivered, if it has been. PromisedDate covers the date the package is expected to be delivered. TrackingNumber is the tracking number itself. TrackingURL points to the website URL where a user can view tracking information and possible additional details.

SupportPhoneNumbers is a list of support phone numbers available per region. TransitEvents covers the set of events denoting interim progress on the journey to the recipient, including day, time, city, state, and country where applicable. CreateDate records when the tracking number was created. PickupDate records when the carrier picked up the package.

TimestampEvent and LocationEvent capture the timestamp and location of an event associated with a given package. CanReschedule indicates whether the package can be re-scheduled.

The minimal requirement combined with an extensive recommended set tells its own story about display quality. A carrier supplying only CurrentStatus satisfies the integration. A carrier supplying the full recommended set populates the richer panel shown in Google's own screenshots, with the transit event list, the delivery estimate, and the support contact row.

What Google refuses to accept

Two categories are explicitly excluded. According to the documentation, Google does not accept any personal data about the recipient or sender of the package, and does not accept any geographical information about the recipient or sender.

The second exclusion is the more interesting one, because it appears to sit in tension with what the interface displays. The screenshot shows an expected delivery destination and city-level locations attached to transit events. The distinction Google draws is between the package's own journey - the transit events and their locations, which are recommended fields - and information about the people at either end of it. Sender and recipient geography stays out of the payload.

For carriers, this shapes the engineering work. The tracking API feeding Google cannot simply be the same endpoint that serves an authenticated customer portal, where recipient address data is routinely present. It has to be a filtered surface.

Why closing the program matters now

The immediate consequence is competitive asymmetry inside a query category that has commercial weight.

Tracking queries are navigational and repeated. A single shipment can generate several searches across its transit window. When those searches resolve inside Google, the carrier's own site loses the session, along with whatever the carrier had planned to do with it - upsell, account creation, delivery preference capture, advertising inventory on its tracking page.

Carriers already in the program have that traffic intercepted but also have brand presence in the panel, which the screenshots show carries the company name. Carriers outside it have neither. As search behaviour continues shifting toward answers rendered in place, a permanently closed feature functions as a moat around whoever was inside it when the gate shut.

There is no stated appeal path in the documentation and no indication that the program will reopen. The banner language is present tense and unqualified.

A pattern of narrowing surfaces

The July 14 entry is the fourth documentation change Google published in the first two weeks of July 2026, and it fits a wider direction visible across the changelog.

Three days earlier, on July 10, Google updated its canonicalization troubleshooting guide with clarifications on re-evaluation time, stated as improving expectations about how long canonicalization changes take to register.

On July 7, Google added the CategoryCode type to Merchant listing structured data and published a new section on sale duration covering the validFrom, validThrough, and priceValidUntil properties. On July 1, it simplified its AMP documentation by removing references to the AMP viewer, AMP Cache, and signed exchange, alongside a change routing Search users directly to publisher-hosted AMP pages.

Read together, the July batch shows Google tightening structured data alignment with Merchant Center on one side while withdrawing or freezing older feature programs on the other.

The freeze is the more consistent recent pattern. Google ended FAQ rich results on May 7, 2026, with Search Console reporting removed in June 2026 and API support scheduled to end in August 2026. Documentation for the feature was removed entirely on June 15, 2026. Earlier, Google removed practice problem structured data documentation on January 6, 2026, following a November 2025 announcement. In June 2025, seven structured data types were deprecated in a single action, including Book Actions, Course Info, Claim Review, Estimated Salary, Learning Video, Special Announcement, and Vehicle Listing.

Package tracking differs from those cases in a way that matters. The others were deprecations: the feature stopped appearing for everyone. This one keeps running for incumbents. It is a partner list frozen in place rather than a feature switched off.

That distinction has been used before. The Google Business Profile Q&A API was discontinued on November 3, 2025after a September 17 notice, but the underlying Q&A functionality kept operating inside Search and Maps interfaces. The mechanism was access restriction rather than feature removal. Package tracking applies the same logic at the partner tier.

Context for retail and logistics marketers

The closure lands in a period of continued Google investment in merchant-facing shipping infrastructure - which sharpens rather than softens the contrast.

Google expanded shipping policy configuration on November 12, 2025, extending the shipping and returns settings in Search Console to all websites its classification systems identify as online merchants, rather than only those with active Merchant Center accounts. That expansion moved in the opposite direction from the package tracking freeze: it widened eligibility rather than narrowing it.

The difference is instructive. Shipping and returns policy data is declarative. A merchant states its terms, and Google renders them. Package tracking requires a live API, a latency guarantee, and an ongoing operational relationship. The first scales without Google carrying cost or risk. The second does not.

Other merchant surfaces have followed the scalable model. The store widget launched September 18, 2025 displays ratings, shipping information, return policies, and reviews on merchant sites. Brand profile management tools let eligible retailers claim and manage the display of business descriptions, images, shipping information, and promotions in Search. Both draw from data merchants already supply.

For retail media teams and e-commerce operators, the sequence points to a rough rule about which Google Search surfaces stay open: those fed by feeds and markup tend to widen, and those requiring bespoke carrier integrations tend to close.

The package tracking freeze also arrives as Google builds out transactional commerce infrastructure through the Universal Commerce Protocol, which launched January 11, 2026 with Shopify, Etsy, Wayfair, Target, and Walmart as co-developers, and has since extended into hotels, food delivery, and additional countries. Post-purchase tracking would be a natural endpoint for a protocol covering the purchase itself. That Google chose this moment to stop admitting tracking partners suggests the fulfilment layer is not being solved through the early adopters program.

What remains unknown

The documentation does not say how many partners are in the program, when it stopped accepting applications in practice, or whether existing partners can be removed for reasons other than latency. It does not indicate whether a replacement mechanism is planned.

It also does not clarify the status of applications submitted before July 14. The banner speaks only to the present state.

For companies that had integration on a roadmap, the July 14 update converts a planned project into a closed option, with no published timeline for reconsideration.

Timeline

Summary

Who: Google, shipping carriers and logistics providers with existing package tracking integrations, and companies that had planned to join the early adopters program but have not yet integrated. Retailers and e-commerce operators dependent on carrier tracking visibility are affected indirectly.

What: Google updated the feature availability and eligibility requirements sections of its package tracking early adopters program documentation, confirming that the program is no longer accepting new partners. Existing technical requirements remain: a single required CurrentStatus field, eleven recommended fields, an average API response time of 700ms with the 95th percentile not exceeding 1,000ms, and exclusion of personal or geographical data about senders and recipients.

When: July 14, 2026, recorded in the Search Central changelog and reflected in the last updated stamp on the documentation page.

Where: Google Search Central documentation for the package tracking early adopters program. The feature itself is available in all languages and countries where Google Search is available.

Why: Google's stated reason in the changelog is that the program is no longer accepting new partners. The company did not publish further explanation, a reopening timeline, or an alternative mechanism for carriers seeking the same visibility.