Carrier Integration & Logistics Systems
Get the carrier integration specified, built and live
Labels, manifests, tracking events, customs data and returns: I turn carrier and logistics requirements into working integrations. You choose whether I specify it, lead your developers, or deliver it with developers I contract.
When to use it
Integrations fail on operations, not on the API call
Connecting to a carrier API is the easy part. Projects stall on the details nobody wrote down: which services and options you actually need, how labels must look for the sorter, when manifests close, how tracking events map to what your customers see, which customs fields are mandatory on which lanes, and what happens when something goes wrong.
Three options
Pick how much of the work you want me to own
| Option | From | Who writes the code | What you get |
|---|---|---|---|
| A · Integration Blueprint | €2,250 | Your team, later | One interface or carrier workflow specified: current-state review, data-flow diagram, label/manifest/tracking/customs field mapping, error handling, security and an acceptance-test plan your engineers can estimate. 1–2 weeks. |
| B · Leadership with your developers | €4,750 | Your developers | I lead discovery, requirements, interface decisions, carrier coordination, the backlog, data-mapping reviews, UAT and launch readiness. Up to 6 consultant days over roughly 3–5 weeks. |
| C · Delivered with contracted developers | €18,500 | Developers I contract and manage | A scoped integration built and handed over. I lead architecture, scope, carrier coordination, quality and testing. You own the code and the repository. |
Extra leadership time beyond the agreed scope is €850/day, always agreed in writing before it is used. Option C's entry price assumes one bounded integration with reasonable carrier documentation and accessible systems; multiple carriers, missing APIs, heavy ERP work, hosting and long-term support are quoted separately.
What it covers
Everything a parcel integration needs to work in production
- Shipment creation and service options, labels and label-format checks.
- Manifests, cut-off times and handover references.
- Tracking-event mapping into your own statuses and customer notifications.
- Customs and item-level data for cross-border lanes.
- Returns labels and return tracking.
- Error handling, retries, monitoring and exception processes.
- Security, credentials and access ownership.
- Test cases, carrier certification steps where needed, go-live and handover.
Not included
Where the scope stops
Carrier approval timelines and partner response times are outside my control. Software unrelated to delivery and returns, 24/7 on-call support and open-ended maintenance aren't included. For option C, developer IP assignment, repository and credential ownership, warranty and optional support are written into the statement of work before we start. Prices exclude VAT and third-party licences or hosting.
Why me
Operator, product lead and builder
I have worked across 18+ carrier and API integrations in my career, including European network and PUDO integrations during my time in international product development at Hermes, where I also led a seven-person product team. Separately, I designed and run predictapp, a production software platform with APIs, data pipelines, authentication and payments. I understand both the parcel operation and the software that has to support it.
Related answers: What a carrier API integration project involves · Build direct or buy a multi-carrier platform
Questions
Before we start
Will you write the code yourself?
It depends on the option. In A, I specify and your team builds. In B, your developers build and I lead. In C, developers I contract build it under my lead, and you own the result.
Should we build directly or use a multi-carrier platform?
It depends on volumes, the number of carriers, the special services you need and your engineering capacity. The blueprint answers that question before you commit money to either.
Can you work with our existing platform or ERP?
Yes, as long as we can access documentation and a test environment. Heavy ERP customisation is scoped separately.
Do you guarantee carrier approval or go-live dates?
No. Carriers control their own certification and timelines. I manage the plan, the dependencies and the risks so there are no surprises.
Next integration