Custom multicarrier shipping software development
If you ship with more than one carrier, you usually make the choice by hand or let a shipping platform choose. As volumes grow, that starts to chafe: one destination is only served by one carrier, one product may only go with another, cut-off times differ and statuses arrive in five different formats. Appfront builds shipping software that selects the carrier for each shipment itself, based on rules you know, creates the label and the accompanying documents, and brings all events together in a status model your organisation can explain.
What makes multicarrier shipping different
With a single carrier, shipping is an action: pick the order, stick on the label, done. The software only needs to do one thing, and almost any package can do that. With several carriers side by side, the nature of the problem changes, because a decision is added. That decision is made per shipment: the contents, weight, dimensions, destination, the promise to the customer and the time of day together determine which carrier and which product fit. Two orders from the same customer on the same day can therefore belong with different carriers.
Are you in the right place? This page is about the routing itself and about several carriers working side by side in one process. If you mainly want to check afterwards whether the carrier's invoice is correct, including weight corrections and surcharges, you want parcel audit software. If it is about an integration with a shipping platform, a MyParcel integration is the shorter route. Here the focus is on the question that comes before that: which carrier gets this shipment, and why.
The second difference lies in aftercare. Each carrier delivers its own events, with its own codes, its own timestamps and its own idea of what delivered means. If you pass those codes on one to one to customer service, the webshop and the finance department, you build the differences between carriers into your entire organisation. A model of your own on top is therefore not a luxury but the foundation everything else rests on.
Shipping with multiple carriers is rarely a choice made out of ambition. It starts with a limit: a carrier that does not accept parcels above a certain size, a country where your regular partner is expensive or slow, a business customer who prescribes their own carrier, or a peak period in which a carrier caps its pickup capacity. From that moment on, two or three portals sit side by side and the logic moves into people's heads. You notice it from the symptoms: a spreadsheet showing who ships what where, a packing station where the experienced employee is faster than the new one because they know the rules, and a customer service team with three tabs open. Those symptoms are not sloppiness, but the result of logic that is not recorded anywhere.
The choice is made per shipment
Not per customer and not per webshop. Two orders from the same customer can belong with different carriers.
Every carrier has its own language
Different fields, different product names, different status codes. Without a model of your own, you inherit those differences throughout your entire process.
The exception takes the most time
Shipments that simply arrive need no attention. The work lies in the shipments that get stuck.
Carrier selection per shipment, based on rules you know yourself
A rule set sounds simple until you write it down. In practice, the choice consists of two steps that you need to keep separate: first exclude what is not possible, then rank what is. That separation prevents the most common mistake, which is a list of preferences in which a hard constraint has been included as a preference. Excluding is about the limits of the product: the country or postcode lies outside the delivery area, the weight or longest side falls outside the permitted dimensions, the girth is too large, the contents require handling that this carrier does not offer, or the booking time falls after today's cut-off. What remains after that step is the set of valid options, and only then does the trade-off begin.
You rank on more than the freight price. The promise to the customer often comes first: if a delivery day or time slot was chosen with the order, everything that cannot make that day drops out. Next come your own price agreements, where the comparison has to be fair. Carriers do not calculate with the same weight. Besides the actual weight there is the volumetric weight, where length, width and height are converted using the carrier's divisor and the higher of the two forms the basis. Two carriers with a comparable price list can therefore turn out very differently for the same small box of air. If your software only calculates with the actual weight, the choice looks right and then turns out differently on the invoice.
There are also agreements that have nothing to do with the individual shipment. If you have divided your volume across carriers, you have usually agreed quantities, and those quantities are a constraint on the choice. A system that optimises each shipment in isolation may discover at the end of the period that a carrier has not reached its agreed volume. So you need a counter, per carrier and per period, that is factored into the ranking. The same applies to capacity on the day: if a carrier has a maximum per pickup round, or the roll containers are full, the remaining shipments have to go elsewhere, without anyone having to adjust rules by hand.
A question that is often skipped: at what moment is the choice made? At order intake you know the destination and the promise, but not the actual weight and not which box it will fit in. When packing you do know that, but by then the customer has already been informed. Most shippers therefore need two moments. A provisional choice at the order determines what you tell the customer and what you charge. A final choice at booking uses the actual box and the actual weight. If the second differs from the first, that difference should become visible, because it is precisely the difference between what you expected and what the carrier will invoice.
Finally, the outcome must be explainable. For every shipment it should be recorded which options were available, which dropped out and for what reason, and which rule picked the winner. That seems like a detail, until the first time someone on the shop floor says the system is behaving strangely. Without a record, that conversation cannot be settled and the rule set gets loosened as a precaution until it no longer means anything. With a record, you can reconstruct a decision, even much later, and you can see which rule decides most often in practice. That last one is surprisingly often a rule that nobody chose deliberately any more.
When the cheapest choice turns out to be the most expensive
The temptation when comparing carriers is to sort on freight price alone. That works fine for shipments that arrive without a hitch. But the total cost of a shipment also includes what happens when things go wrong: a failed first delivery attempt, a customer who calls, a parcel that goes to a service point the recipient never visits, a shipment that goes back to sender. Part of that cost sits with the carrier and part with you, in customer contact and re-shipping. It differs by carrier, by destination and by type of address, and those are exactly the differences you can't see in a comparison that stops at freight price.
You can factor that in without getting lost in models. For each carrier and each zone layout, track how often the first delivery attempt succeeds, how often a shipment ends up at a service point and how often a return follows. Those figures come from your own status model, so you have them as soon as that model is in place. Translate them into a surcharge on the freight price in the ranking and the choice shifts in exactly the places where it is warranted. If you sell to business recipients and consumers alike, you'll see that the same carrier is strong in one segment and weak in the other.
If shipments leave the Union, or enter it under a special regime, there is a licensing side to it. See software for customs procedures and registration.
What multicarrier shipping software needs to do
These components are interdependent. A selection rule without a traceable outcome leads to arguments, a label without an address check leads to failed deliveries, and a status model without the raw messages behind it leaves you helpless as soon as a carrier changes its codes.
What isn't included matters just as much. This is not a scheduling system for your own transport, nor a freight module for pallets with a haulier. If you deliver yourself, or your volume moves on consignment notes rather than parcel labels, you need different tooling, with routes and load capacity at its core: see custom transport software development.
Rule set with a traceable outcome
Conditions that you manage yourself, with the recorded reason for each shipment explaining why this carrier was chosen.
Labels in your printer's format
Thermal or as a document, in the right size, with a queue that can handle reprinting and cancelling.
Customs data per line
Commodity code, country of origin, value and weight for each item line, plus the shipment's delivery terms.
Own status model with raw source
Events from all carriers mapped to your own steps, with the unprocessed message stored alongside the mapping.
Return as a separate shipment
A return gets its own number, its own carrier and its own status, linked to the order and to the receipt at the premises.
An integration layer per carrier
Each carrier sits behind its own translation layer with its own tests, so a change at one party doesn't affect the rest.
Labels and documents that are right first time
The label is the point where all the preparation comes together, and where errors are most expensive. A shipment that leaves with the wrong address or the wrong product comes back as customer contact, a second shipment and a correction to the invoice. Most of these errors can be spotted in advance. An address check that validates postcode, house number and suffix against a source catches the typos and missing suffixes that would otherwise surface at the courier. For destinations outside the Netherlands, this includes a check on the address structure, because not every country uses the same pattern of street, number and postcode.
Then comes the technology of printing, which is less trivial than it looks. Carriers supply labels either as a document or as printer language. A thermal printer wants the latter, at that device's resolution, and a label that looks fine on an office printer can come off the roll unreadable on the shop floor. In a packing station, the print queue should run per workstation, with reprinting that doesn't require registering a new shipment, because every new registration creates a new shipment number. Unused numbers must be cancelled within the carrier's window, otherwise they turn up later in the invoicing.
A label should carry more than the address. The carrier reads its own barcode containing the shipment number, and there is also data that drives its sorting, such as a routing or depot code that comes from its system and so can't be something you make up yourself. That is why you have labels formatted by the carrier rather than rebuilding them, even if the layout looks simple. What you do add is your own identifier: an order number or a reference to the pick list that your staff can scan, so that a box can be traced in your own process without first opening the carrier's portal.
Just as important is retaining what has been registered. The moment the carrier returns a shipment number, the shipment exists in the outside world. From then on, your system should know which number belongs to which order, which box and which contents, even if items are repacked afterwards. Splitting is a topic in its own right here: multiple boxes under one order, each with its own number, and a status view that is only complete once the last piece has arrived.
Registering shipments also involves the end-of-day close. Carriers want to know which shipments are in the collection round, and that declaration is more than a formality. Shipments that are not on it may be treated as unknown at the sorting centre, and shipments that are on it but don't go with the driver remain open items. A daily close per carrier, with a list you can look back on, prevents the discussion the next morning from going on gut feeling. If you ship from several premises or under several brands, that close should run per site and per contract, because carriers tie their collection round to a specific address and a specific customer number.
Shipments that cross the border
As soon as a shipment leaves or enters the European Union, the work shifts to the data. For customs, the subject is not the box but its contents, per item line: a description an outsider can understand, the commodity code, the country of origin, the quantity, the weight and the value. The shipment also needs the delivery terms, meaning whether the recipient pays the import duties or you do, and the registration number under which your company is known to customs. The carrier usually files the declaration, but it does so with your data, and an incomplete line only becomes its problem once the parcel is stuck.
That means this data has to be right much earlier in your chain than at packing. A commodity code belongs to the item and not to the shipment, so it should live in item management, with a check that blocks new items without a code from being sold internationally. For the shipment itself, carriers need the data electronically in advance, in the format their declaration process requires, and a missing field there leads to a rejection rather than a warning. Keep the generated documents with the shipment, so that a customer or an inspector can get a copy later without a new label being created.
- Address verified before the label is created
- Label in the format the printer actually speaks
- Shipment number recorded at the moment of registration
- Cancellation within the carrier's window
- Commodity code and origin per item line
- Documents can be requested again without a new label
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Track and trace for five carriers, one status model
Ask any shipper where their shipments are and the answer is usually that you can look it up per carrier. That is exactly the problem. As long as statuses stay in the carrier's own language, there is no overview, customer service cannot work from a task list, and nobody can say how many shipments are stuck right now. The solution is not a nicer display but a model of your own: a limited, fixed series of steps describing what happens to a shipment, to which each carrier's codes are mapped. Registered, collected, in transit, out for delivery, delivered, ready at a service point, failed attempt, refused, returned, lost: most organisations need little more than that.
That mapping comes with three agreements you cannot leave until later. First, alongside the mapped step you also store the carrier's raw message, with its own code and its own text. If a carrier changes a code, or your mapping turns out to be wrong, you can remap without losing the history. Second, you record two timestamps: when the event happened according to the carrier and when you received the message. The two diverge, sometimes considerably, and only with both can you tell sequence and delay apart. Third, every event gets a key that lets you recognise duplicate messages.
Messages, after all, arrive in a jumble. One carrier pushes events to an endpoint on your side, another makes you fetch them, and a third does both with different content. A message can arrive twice, or in the wrong order, with the delivery arriving before the scan at the sorting centre. Your model must not be thrown by this: the state of the shipment follows from the event with the latest carrier timestamp, not from the last message received. And delivered is not the end of the line, because a refusal or a return can still follow.
The final step is that someone does something with it. A status model that only fills a timeline per shipment is a reference book. It becomes a tool once you put thresholds on it: shipments not collected within that carrier's window, shipments in delivery for too long, parcels at a service point whose holding period is running out, returns that have been registered but have not arrived. Each of those groups is a task list with an owner, and the size of those lists is also your quality measure. If you do not build them, customer service does the same work reactively, call by call, without seeing that fifty other shipments have the same problem.
What you get from this is more than a tidy overview. Once all carriers speak the same steps, you can compare: which carrier gets what share of shipments stuck, where the first scan takes longest, which destinations produce the most second attempts. Those same steps feed the page your customer sees, and that only works if the texts are yours and do not come from five different sources. You can read what that side looks like in building a track and trace system.
Failures, exceptions and the day a carrier changes
A shipment that arrives needs no attention. The work lies in everything else, and that is bigger than most companies think. Failures often start with silence: a label has been created, but no first scan follows, because the box ended up behind a roll cage or never went out with the collection round. Without detection of absence, you only find out when the customer calls. The rule itself is simple: if a shipment has no intake scan after that carrier's expected window, it belongs on a work list, with the reason alongside it.
Then comes the series of familiar exceptions: wrong address, recipient not at home, parcel damaged, shipment held by customs, parcel not collected from the service point, and the case nobody wants, lost. Each of these situations has its own follow-up step, and that step is more than a phone call. Wrong address means passing on a correction, which for one carrier goes through a portal and for another through a message in the integration. Damage and loss mean a claim, with a deadline that differs per carrier and with evidence that you only have if you kept it with the shipment.
For business shipments, proof of delivery comes into play. If you deliver under terms in which receipt can be disputed, you want to be able to show the sign-off: the name, the time and, where the carrier records it, the signature or the photo of the handover. These proofs can only be requested from the carrier for a limited period, and not afterwards. If you retrieve them as soon as a shipment has been delivered and keep them with the shipment, a dispute over a delivery that was supposedly not received becomes a matter of looking it up rather than searching through two portals.
Returns belong in this list because in practice they involve the same exceptions, but in reverse. A return is a shipment in its own right, with its own number, its own carrier and its own status, not a flag on the original order. Only then can you handle the cases that really matter: a return that has been registered but never arrives, a customer who ships with their own label, a parcel that comes back without being registered, or a refusal that the carrier sends back as a return. How to set up that process further is covered under returns management software.
And then something changes on the carrier's side. This happens regularly, in three forms. A technical change: a new version of the integration, a field that becomes mandatory, authentication that works differently. A commercial change: new price lists, different zones, different surcharges, a fuel surcharge that moves with each period. And a product change: a service that is discontinued, a new delivery option, different maximum dimensions. All three affect your software, but only the first produces an error message. The other two let your system carry on working with outdated assumptions, and that is the most dangerous of the three.
There is a way of building for this. Each carrier sits behind its own translation layer that converts your shipment model into its format and brings its responses back into your model, so that the rest of the system knows nothing of any carrier's internals. Each layer comes with tests that run against that carrier's test environment, so that an announced version change is noticed before the effective date passes. Rate agreements, zones, surcharges and maximum dimensions are stored as data in the system, with an effective date, rather than hidden in the code. A new price list is then an import with a date, not a change that has to go through acceptance.
Adding a carrier is also more than entering a key. There is a contract with a customer number per site or per brand, a test environment where you register shipments, and with most carriers an approval of your labels before you can go live: they check that the barcode is readable and that the layout does not get in the way of their sorting. Each carrier also sets its own requirements for the data, such as a phone number or email address for the recipient once you start using delivery notifications. Factor that in for the first carrier you add. The second and third go faster, but not because their integration is simpler.
That raises the honest question: should you build this yourself? For many shippers, no. Mature multicarrier platforms exist that offer dozens of carriers out of the box, maintain the integrations and come with a rules screen, and Dutch providers are well represented there. If your selection logic fits that screen and your volume is made up of standard products, you buy it in and your effort shifts from building to configuring. Custom development pays off when the choice depends on data that only exists in your own processes, when a shipment only takes its final shape during packing, or when you need to split orders across carriers according to rules the platform does not know. Often the middle route is the answer: a platform for the integrations, your own logic in front of it. You can read how we weigh that up under automating logistics processes.
If you are specifically interested in the carrier integration and generating labels, see carrier integration and shipping label software.
- Platform if your rules fit their rules screen
- Platform if you mainly need integrations, not logic
- Custom if the selection rules come from your own processes
- Custom if the shipment only takes shape during packing
- Middle route: a platform for the integrations, your own selection logic in front of it
Frequently asked questions about multicarrier shipping software
An integration sends your shipments to a provider and uses that provider's selection logic. Multicarrier shipping software makes the choice itself: the system decides per shipment which carrier and which product fit, keeps track of what has been registered and which events followed, and keeps working when a carrier is added or drops out. If you are looking for that one integration, a MyParcel integration is the shorter route. If you work with several contracts side by side, the selection logic itself is the subject.
Based on rules you define yourself, applied in a fixed order. First it rules out what is not possible: a destination outside the carrier's coverage area, weight or dimensions outside the limits of the product, a shipment requiring age verification or containing dangerous goods, a registration after that day's cut-off time. What remains, the system ranks by the promise made to the customer, the freight cost under your own price agreements and the capacity still available within a volume agreement. The outcome should be readable back per shipment, including the rule that made the choice.
By defining your own status model and mapping each carrier's codes to it, rather than showing the codes of all carriers side by side. That model describes what is happening to the shipment: registered, collected, in transit, out for delivery, delivered, ready at a service point, failed attempt, refused, returned, lost. You also store every event unprocessed, with the carrier's timestamp and the time of receipt, so you can revise a mapping later without losing the source.
That is not an incident but recurring maintenance, and the system should be built for it. Each carrier gets its own layer that translates your shipment model into that carrier's format, so a change at one carrier does not affect the rest. Each layer comes with tests that run against the carrier's test environment, so an announced version change is caught before the effective date passes. Rate agreements, zones and surcharges are stored as data in the system, with an effective date, rather than hidden in the code.
That is a different subject. This page is about the choice up front and about execution: which carrier, which label, which documents, which status. Matching the carrier's invoice against the shipments you actually booked, including weight corrections and surcharges, is work done after the fact, with its own data model and its own dispute process. Parcel audit software is the right starting point for that. The two do fit together, because the expected costs from the selection logic form the benchmark for that check.
Often it can, and for many shippers that is the wiser route. Mature multicarrier platforms exist that offer dozens of carriers out of the box and maintain the integrations themselves. If your selection logic fits within their rules screen and your volume consists of common products, you buy that. Custom software becomes interesting when the choice depends on data that only exists in your own processes, when a shipment only takes its final shape during order picking, or when you need to split shipments across carriers according to rules the platform does not know.
Related services
Parcel audit software
Does the carrier's invoice match the shipments you actually booked? Weight corrections, surcharges and labels that were never shipped are checked after the fact, with a dispute process of their own. That is the subject of building parcel audit software.
MyParcel integration
If you work with a shipping platform and mainly need that one integration, with labels and statuses fed back into your own system, building a MyParcel integration is a shorter route than a selection layer of your own.
Track and trace for the customer
You will also want to show the statuses you bring together to the recipient, in your own words and with your own messages instead of ten different carrier pages. That calls for a status page and notifications of your own: building a track and trace system.
Returns management and warehouse
Returns that go beyond a label, with inspection, restocking and crediting, are covered under building returns management software. If the bottleneck is in the building itself, at receiving, locations and order picking, then a custom WMS is the place to start.
Your shipping process across carriers
Tell us which carriers you work with, which selection rules currently live in someone's head or in a spreadsheet, and what happens today when a shipment is never scanned after it has been booked. Those three answers usually show whether a platform, custom software or a combination fits best, and which part you should tackle first.