InPost Folds Yodel Into Its Carrier API Network
Yodel's brand and systems shut down 17 July 2026. Here's what UK shippers must update in carrier API/EDI integrations before InPost's cutover.
On 17 July 2026, InPost permanently retired the Yodel brand in the UK. The Yodel website and app went dark, and every function, tracking, delivery preferences, parcel management, moved onto InPost's own platform. If you're a European shipper running a carrier integration that still points at Yodel endpoints or hard-codes Yodel service rules, this is the point where things start breaking quietly rather than loudly.
This didn't come out of nowhere. InPost bought Yodel's parent company, Judge Logistics, for £106 million in April 2025, taking 95.5% of the share capital with PayPoint keeping a 4.5% minority stake. The deal got stuck in a UK court dispute for months, with rival claimants arguing they held warrants to more than 75% of Yodel's shares. The High Court eventually ruled those claims were likely built on forged signatures, clearing the way for InPost to finish what it started. The brand went through an intermediate "Yodel by InPost" phase before being switched off entirely in July 2026.
Key dates for this migration
| Date | What happened |
|---|---|
| April 2025 | InPost acquires 95.5% of Judge Logistics (Yodel's parent) for £106m; PayPoint retains 4.5% |
| September 2025 | Yodel rebrands to "Yodel by InPost" across web, app and communications |
| June 2026 | Phased account migration to InPost begins |
| 17 July 2026 | Yodel and "Yodel by InPost" brands retired; yodel.co.uk and the app shut down; Yodel Direct continues separately as its own offering |
| Through 2027 | Retailers expected to still show "Yodel" at checkout while backend systems catch up |
What actually breaks in your integration
The headline change nobody flags loudly enough: the weight ceiling has moved. The 30 kg Yodel limit has gone with it: nothing in the InPost network takes more than 15 kg. If your rate engine or service-selection logic still routes anything up to 30kg to Yodel, those bookings for parcels in the 15-30kg band will start failing, often without a clear error message pointing at the real cause.
Location data doesn't survive the move cleanly either. Delivery preferences carry over automatically from the old app, but any delivery preferences previously set in the Yodel by InPost app have carried over automatically, with one exception: what3words locations will need to be re-entered in the InPost app. If you pass what3words codes via API for last-mile delivery instructions, you need a plan to recapture that data for repeat customers.
Then there's the branding mismatch your support team will live with for a year. You may still see the Yodel name on some retailers' websites for a period, this is expected to continue through 2027 as those retailers update their systems. Regardless, your parcel is moving through the same network. Your tracking and status-mapping tables need to decouple the checkout-facing "Yodel" label from the backend carrier actually fulfilling the shipment, or your customer service team will be chasing a carrier that no longer answers.
Finally, the basics: tracking, account management, and customer support are now handled through InPost rather than Yodel. Webhook URLs, API credentials and tracking-number formats tied to legacy Yodel systems all need revalidation against InPost's endpoints.
How multi-carrier platforms have already reacted
Some integration layers didn't wait for the dust to settle. ShipStation's carrier list already shows the rename baked directly into the carrier code: for UK-based ShipStation API accounts, you have immediate access to GlobalPost, EVRi, DPD, Royal Mail, and InPost (FKA Yodel) services with ShipStation API Carriers. That's a telling detail. One major abstraction layer has already absorbed the rename so its users never had to touch their own code.
That's the real argument for not building point-to-point carrier connections in the first place. Platforms like ShipStation, EasyPost, Sendcloud, nShift and ShippyPro exist precisely to absorb this kind of carrier churn centrally. Cargoson takes the same approach on the TMS side, maintaining the carrier connections itself so a brand retirement like this is a backend update on their end, not a fire drill on yours.
This isn't an isolated event either. The market is also consolidating rapidly. In May 2025, DHL eCommerce UK merged with Evri, creating a carrier capable of processing 1 billion parcels per year. Two separate brand mergers, Evri/DHL eCommerce and InPost/Yodel, reshaped UK carrier integrations in the same twelve-month window. If you ship into the UK, this pattern is worth building a response plan for rather than treating each one as a one-off.
What to check before 2027
- Audit hard-coded Yodel service codes, weight and dimension rules, and webhook endpoints across your TMS, OMS or custom integration
- Re-test parcels in the 15-30kg band that used to route to Yodel, and confirm they now route correctly rather than failing silently
- Recapture what3words or other delivery-location metadata for repeat customers previously served through the Yodel app
- Separate customer-facing carrier branding from the backend API carrier on tracking and status pages, since "Yodel" may persist at checkout into 2027
- Confirm API keys, account credentials or EDI interchange details have been reissued under InPost rather than legacy Yodel systems
The pattern to watch
Brand retirements like this one are becoming a recurring category of carrier API news in a consolidating European last-mile market. Shippers running their own point-to-point Yodel integration are the ones doing firefighting right now. Those sitting behind a carrier connectivity layer, whether in-house or a platform like Cargoson, nShift or ShipStation, absorbed this rename with a configuration update instead of a support ticket spike.