David Chen

DHL has launched significant changes across their API portfolio that every European shipper needs to address immediately. On January 1, 2025, the new product DHL Kleinpaket was introduced, replacing the previous Warenpost product, and changes will only apply to shipments created after 11:00 CET on January 30, 2025 for

Your European manufacturing company faces a complex choice: how do you connect with 50+ carriers across air, sea, and road freight without drowning in API maintenance? Multi-carrier APIs allow you to compare shipping rates from multiple carriers in real time, but the technical architecture decision you make today will determine

Your transport department is managing EDI connections with 50+ carriers, and procurement has just asked about migrating to "modern APIs" to get real-time tracking. The IT director warns about disrupting existing workflows that process 200,000 shipments annually. Sound familiar? Despite predictions that APIs would replace EDI entirely,

Most European manufacturers spend 12-16 weeks implementing a single carrier API integration. Your procurement team negotiates rates, your IT team builds the connection, then three months later you're finally shipping. Meanwhile, your competitors are already onboarding their next carrier partner. The problem isn't technical complexity -

The USPS Web Tools API platform will be retired on January 25, 2026, marking the end of an era for European shippers who rely on USPS for cross-border shipping. Continued use of this API is subject to disruptions starting in July 2025, meaning you have less than a year to

Beginning September 1, 2025, the U.S. Postal Service will require all international commercial shipments to include a six-digit Harmonized System (HS) code on customs declarations. For European manufacturers and retailers shipping to the US, this means your existing TMS workflows need immediate updates. The clock is ticking, but you