Elena Navarro
We started Uniship with a simple observation. Integrating with European shipping carriers is painful, fragmented, and way harder than it should be. One API to handle them all - that was the pitch. And honestly? We have come a long way since those early days.
Over 400 merchants now route shipments through our platform. We process north of 2 million labels a month. Our Shipment API and Tracking API are production-stable and handling real volume. The Printing API and PUDO Map came out of beta last year and adoption has been strong.
But we are not done. Not even close. I want to walk you through what is on the roadmap for 2026 and share some of the thinking behind these decisions.
New carrier integrations
This is always the top request from merchants, and rightfully so. Every market has its local champions, and if we do not support them, merchants have to maintain a side integration. That is exactly the problem we are trying to eliminate.
In the first half of 2026 we are adding Mondial Relay - essential for France and Belgium with over 40,000 pickup points. We have had this on the backlog for too long and I am personally relieved it is finally happening. Colissimo from La Poste is coming too, completing our French market coverage. Austrian Post fills the gap in our DACH region support alongside DHL and DPD. And Correos for Spain, which is growing fast as an e-commerce market and where I happen to have a lot of personal connections from my years in Madrid.
In the second half of the year we are targeting PostNord for proper Nordic coverage across Sweden, Denmark, and Norway. Zasilkovna - also known as Packeta - is massive in Czech Republic and Slovakia with a growing pickup point network across Central and Eastern Europe. And Royal Mail plus Evri for the UK, because merchants shipping post-Brexit need proper coverage and our current continental Hermes integration only goes so far.
By the end of 2026 we are targeting 25 or more carrier integrations across 15 European markets. That is up from 12 carriers today.
Smarter carrier selection powered by machine learning
This is the one I am personally most excited about.
Right now our rate comparison returns options sorted by price or speed, and merchants either pick manually or set static rules. That works, but it leaves value on the table. Static rules do not account for carrier performance patterns that shift over time.
We are building a recommendation engine that considers historical delivery performance per carrier per route - not just what the carrier promises but what actually happens. It factors in current carrier load because during peak season some carriers degrade significantly. It looks at return rates by carrier - if a carrier has a three times higher damage rate on a specific lane, maybe do not use them for fragile goods. And it considers total cost including the customer support burden from delivery failures, not just the label price.
The system will include a score and reasoning for each recommendation so you can understand why a particular carrier was suggested. No black boxes. If you disagree you override it. We are already training on anonymized shipment data from opt-in merchants and targeting launch in the second quarter of 2026.
A proper analytics dashboard
We have had basic analytics since day one - shipment volume, carrier breakdown, cost per shipment. Useful but not enough. The new dashboard launching in the first quarter adds delivery performance benchmarks so you can see how your carrier mix compares to similar merchants in your market. Cost trend analysis shows whether your shipping costs per order are rising or falling and which carriers are driving the change. Geographic heatmaps reveal where your shipments go and where delivery failures concentrate. SLA compliance tracking shows what percentage of shipments met the carrier's promised delivery window.
All of this data will also be available through the API for merchants who want to pull it into their own business intelligence tools. We are not trying to be your analytics platform. We just want to give you shipping-specific insights that are genuinely hard to get elsewhere.
Mobile SDK for app-first merchants
This has been requested repeatedly by marketplace and app-first merchants. If your customers interact with your brand primarily through a mobile app, embedding shipping features should not require wrapping our dashboard in a WebView.
The Uniship Mobile SDK - iOS, Android, and React Native - will support native PUDO point selection with map integration that is faster and smoother than a WebView. In-app tracking lets you show the delivery timeline natively. And shipping option selection at checkout gives customers a native experience for choosing carrier, speed, and pickup versus home delivery.
We are targeting a beta in the third quarter of 2026. If you are a mobile-first merchant and want early access, reach out. We are looking for design partners to help us get the experience right.
Expanding PUDO coverage dramatically
PUDO - Pick Up and Drop Off - is one of the strongest trends in European logistics right now. Consumers like the flexibility. Merchants like the lower cost. Carriers like the route density. Everyone wins.
Today our PUDO Map covers around 120,000 points across 8 countries. By end of 2026 we are targeting over 200,000 points across 15 countries. The biggest additions will be France through Mondial Relay and Colissimo points, the Nordics through PostNord service points, Spain through Correos pickup locations, and Czech Republic and Slovakia through the Zasilkovna and Packeta network.
We are also improving search and filtering. Consumers will be able to filter by opening hours, locker versus staffed location, and accessibility features. Small things that make a real difference in checkout conversion.
Address API getting smarter
The Address API is quietly one of our most-used products. Validating addresses before label creation prevents failed deliveries, and each failed delivery costs 5 to 15 euros in carrier return fees and customer support time.
In 2026 we are adding autocomplete suggestions for type-ahead address completion in checkout forms. Delivery point validation will confirm that a specific PUDO point is active and accepting parcels before you route there. And we are expanding address normalization to cover over 20 European countries, up from 10 today.
Where we stand
A year ago we were a team of 8 with 80 merchants. Now we are 22 people and growing. The core thesis has not changed. European shipping is fragmented and developers should not have to deal with 15 different carrier APIs with 15 different data formats and 15 different error handling patterns.
We are not trying to be a logistics company. We are not trying to be a fulfilment provider. We are building the infrastructure layer - the API that makes shipping work so you can focus on your actual product.
If any of this roadmap resonates with what you are building, I would love to hear from you. Check out our use cases to see if Uniship fits your stack, or just drop us a line at hello@uniship.io.
Here is to a big 2026.