Skip to main content

· 2 min read
Daniel K.

The need for carrier integration

One of the critical determinants of Amazon’s success is their access to a network of logistics carriers combined with their investment in strategic warehouse establishment. As your shipping volume and your product selection grow, a multi-carrier strategy becomes a smarter choice. Integrating your platform to a network of carriers will allow your shoppers to get the best experience and value for shipments with different weights, dimensions and expected services.

Developer experience and time-to-value

Developers often face two challenges when integrating with a shipping carrier Webservice. First, the integration is tedious and long as most of the major carriers use arcane technologies that do not blend easily with modern software development practices. Added to that, documentations are either non-existent, long and complex and simply not up to modern dev standards. Secondly, there is a fragmentation and no ruling standard across the logistics industry for data exchange. Meaning, web services do not share a unified data exchange protocol but rather each company offers its own Interface. The consequence is that for any integration needed, you will have to go through a new learning and discovery curve with each carrier individually.

Why is it still unsolved?

Most of the saas platforms offering shipping APIs are exclusively tailored to work with their implementation which creates a vendor lockin and reliance on their servers. Our first goal is to lower the barrier of entry for shipping carrier services integration. To accomplish that, we have opted to adopt the open-core model for simple distribution and additionally offer teams control over the roadmap with the freedom to develop additional features without restriction.

A modern toolbox

Karrio is more than a black box multi-carrier Saas API. It is a toolbox that proposes a unified API to communicate with all supported carriers and an open-source abstraction that serves as a framework for additional carrier integration.

Karrio is written in Python with a Django REST app layer and a React web app. Join the community today and contribute to making shipping service integration accessible to businesses of all sizes.

To learn more:

· 2 min read
Daniel K.

Handling the logistics pertaining to your business or organization in this modern age calls for leverage of technology and automation. The different parties involved in the supply chain lifecycle of a product enjoy the peace of mind and a sense of control when there is visibility. And that can only be achieved when the logistics parties are connected and in sync.

Integrating with a shipping carrier can be very challenging because of their technology choices and long and complex documentations. Added to that, the multi-carrier strategy becomes expensive to adopt as it requires a higher development and maintenance cost.

Karrio is an Open Source platform focused on making it easier for you to integrate with one or multiple shipping carrier services to your existing application.

Modern API

Businesses who need to integrate directly with their carriers without third parties Saas are left with the pain of integrating with every single carrier. Karrio modernizes under a single interface the shipping APIs when Saas is not the preferred way

Specialized lightweight documentation

Carrier’s web service docs are long and complex because of all the various shipping service requirements and use cases. Karrio breaks down into simple modules, freight, packages and document APIs to present specialized lightweight documentation that only covers your needs.

Complete control with Open-core

Saas providers offer limited integrations of the carrier’s capabilities. Karrio lets you build whatever you need–and keep your data on-premises.

We are very enthusiastic at the opportunity to empower software developers for a digitally connected supply chain. We are looking forward to your comments, feature requests, votes and contributions. If you find bugs, please let us know in the issue tracker.

To learn more:

Thank you so much for reading all the way here,

Best regards,

Team Karrio