Carrier APIs Label and returns Track and trace

Custom carrier integration and shipping label software development

Appfront builds the integration between your own system and the carriers you use: PostNL, DHL, DPD, GLS, UPS or a combination of them. Your order is booked, the label comes back in the format your printer expects, and the carrier's status updates flow automatically back into your system. No retyping, no separate portals.

What is carrier integration and shipping label software?

A carrier integration is the link between your own system and a carrier's API. Your system registers the shipment with the address, weight, dimensions and chosen service. The carrier returns a tracking number and the shipping label, usually as a ZPL file for a label printer or as an A6 PDF. The carrier then sends status updates: registered, sorted, in transit, delivered or recipient not at home.

If you work without an integration, you do all of this by hand. Addresses are retyped into the carrier's portal, tracking numbers are typed back into the order system, and a customer who calls about their parcel means searching across two screens. An integration removes those steps and makes the shipment status part of the order record.

We build that integration to your requirements, because the difference lies in your process. Which service belongs to which order type, when can shipments be combined into a multi-parcel consignment, what happens with a non-standard address, and which exceptions can an employee resolve themselves. These are choices that an off-the-shelf package makes for you and that we would rather define together with you.

Booking and labelling

The shipment goes to the carrier's API and the label comes back in ZPL for a Zebra printer or as a PDF for a regular printer.

Returns and customs

Return labels, pick-up points and, for shipments outside the EU, the customs data for CN22 or CN23, including commodity code and EORI number.

Status back in your system

Webhooks or status files from the carrier are written back to the order, so your customer service team doesn't have to check the carrier's portal.

How we build your carrier integration and shipping label software

We start with your shipping process as it runs now, including the exceptions nobody writes down. Then we build the integration carrier by carrier, with that carrier's test environment as the first step.

1
Mapping the shipping process

Which carriers, which services, which order types and which exceptions. We walk the packing table with you and note what goes wrong: addresses without a house number addition, shipments that don't fit on a single pallet, customers with their own pick-up arrangement.

2
Integration per carrier

Every carrier has its own API, its own service codes and its own way of returning labels. We build and test per carrier in their test environment, so an error doesn't come to light on a real shipment.

3
Label line and printers

The label has to come out of the right printer, at the right point in the packing process. We handle the control of label printers and make sure a reprint remains possible without booking a second shipment.

4
Statuses and exceptions

Status updates come back to the order and exceptions get their own work queue: failed bookings, addresses the carrier rejects and shipments that get stuck. After that, we take over maintenance of the integration.

What carrier integration and shipping label software actually does

The functionality depends on what you ship and to whom. These are the components that appear in almost every carrier integration.

Booking a shipment

Address, weight, dimensions and service go to the carrier. If an address is non-standard or incomplete, the employee gets an alert before the label is printed.

Labels in the right format

ZPL for label printers, PDF for office printers, and multiple labels per shipment for multi-parcel consignments. The label layout follows the carrier's requirements.

Return labels

Include a return label with the shipment or create it only when the customer registers a return, with your own returns portal if you want one.

Customs documents

For shipments outside the EU, the integration completes the customs data: commodity code, value, country of origin and your EORI number.

Track and trace

Status updates arrive via webhook or retrieval file and are written back to the order, with a tracking page for the customer in your own branding.

Exceptions list

Failed submissions, rejected addresses and shipments with no status update go into a work queue instead of a log file nobody reads.

Who we build carrier integration and shipping label software for

This integration becomes worthwhile once your shipment volume outgrows what someone can comfortably submit by hand, or as soon as you use more than one carrier.

Webshops and D2C brands

You send parcels every day and want an order to get a shipment number automatically after packing, including a tracking page in your own branding.

Wholesalers and manufacturers

Your shipments are heavier and more often multi-parcel or pallet. The integration has to handle parcel allocation, packing slips and per-customer agreements.

Fulfilment companies

You ship on behalf of several clients, each with their own carrier contracts. The integration has to work with the right account and service for each client.

Companies with their own WMS

Your warehouse system decides when a shipment is ready. The integration connects to it rather than putting a separate portal alongside it.

Technology and integrations

We build directly on the carrier's API, using your own contract numbers and services. If you are looking for a broader shipping platform that compares and manages rates from multiple carriers, see our page on multi-carrier shipping software. This page is about the integration and the label line itself. For the stock side, we connect to warehouse management software.

For the shop floor, with scanning and printing at the packing station, there is our shipping label and carrier app.

PostNL API DHL eCommerce API DPD GLS UPS ZPL and EPL PDF A6 labels Zebra label printers Webhooks REST and JSON GS1 SSCC EDI CN22 and CN23 EORI

Why Appfront for your carrier integration and shipping label software?

A carrier integration is rarely complicated when everything goes right. The work is in the exceptions, and that is where we look first.

Exceptions first

An integration that only works with a complete address and a two-kilo parcel is not finished. We build the error paths together with the people who currently fix them.

Your contracts, your rates

You connect using your own carrier accounts. We do not sit between you and your carrier contract.

Your own code, no lock-in

The integration runs in your own environment and the code is yours. Adding a carrier means an extension, not a migration.

Security and privacy in carrier integration and shipping label software

Recipients' address details are personal data. The integration sends only what the carrier needs to deliver and stores no more than your own administration and handling of follow-up queries require.

Access to the carrier accounts runs through keys held in a managed environment rather than in the code. All calls are logged with shipment number and timestamp, so that in a dispute with a carrier you can show what was submitted and when.

Frequently asked questions about carrier integration and shipping label software

The questions that come up most often with a carrier integration.

A carrier integration is the link between your own system and a carrier's API. Your system registers the shipment with the address, weight and service, the carrier returns a tracking number and a shipping label, and then sends status updates on the delivery. That removes the need to retype data in a portal and to look up tracking numbers by hand.

In the Netherlands, PostNL, DHL, DPD, GLS and UPS are the most common, and we integrate these directly with their APIs using your own contract number. If you work with a carrier not listed here, we will review their documentation before promising anything. The set-up is the same for each carrier; only the service codes and label formats differ.

Usually ZPL, the format that Zebra and comparable label printers process directly. It gives the sharpest result on a thermal label. If you do not have a label printer, carriers also supply the label as a PDF in A6 format, which you can print on an ordinary printer.

Yes. You can include a return label in the parcel, or have it created only once the customer registers a return, which can save on costs. For shipments outside the EU, the integration completes the customs data: commodity code, value, country of origin and your EORI number, in the format the carrier requires for CN22 or CN23.

The shipment then lands on an exceptions list instead of quietly stalling. The employee sees what the carrier reports back, corrects the address and resubmits the shipment. We deliberately make this work queue visible, because otherwise failed submissions only come to light when the customer calls.

Yes, that is usually the starting point. The integration hooks in at the moment your system says a shipment is ready and writes the shipment number and status back to the order. We connect to what you already have, even if that is an older package with a limited API.

Yes. We regularly take over the maintenance of existing integrations, even when another party built them. We first look at how error handling and logging are set up, because that is usually where the overdue maintenance sits, and on that basis we propose what to tackle first.

Want to connect your carriers to your own system?

Tell us which carriers you use and where the shipping process currently gets stuck. We will look at how you work today and show what an integration would concretely deliver in your situation.

Edit content