Courier Label Software for E-commerce — What Should It Handle?

couriersautomation

When you ship a few parcels a day, you click each label by hand in the carrier’s panel and nobody counts it. When there are dozens — across several carriers and several sales channels — packing turns into a window-clicking marathon: copy the address, pick the service, type in the locker code, print, and start over. Good courier label software is supposed to remove that bottleneck — but only if it handles the right things.

This article is a checklist: which features a labelling tool should have and what to actually look at when choosing one, if you sell on marketplaces and your own store and ship with several carriers. No marketing — point by point.

Multi-carrier — one panel instead of five logins

The baseline: the tool should handle multiple carriers from one place. In European e-commerce that usually means InPost, DPD, DHL, Orlen Paczka, plus GLS, national post services or UPS. If you have to log into a separate panel for each carrier, you’ve gained nothing — you’ve just moved the address-copying somewhere else.

What to look at:

List of supported carriers — check for exactly the ones you use, not “popular in general”. A missing key carrier breaks the whole point.
One dispatch queue — every parcel, regardless of carrier, on a single “ship today” list, with the carrier chosen automatically from the order’s delivery method.
Accounts and contracts — the tool should work on your own carrier contracts (your rates), not force you to ship through a broker at its rates unless you want to.

Multi-carrier isn’t a bonus, it’s a precondition. Without it, every other feature only covers half your parcels.

Delivery-method mapping — the most important, most underrated feature

The heart of any labelling tool is delivery-method mapping from the sales channel to a specific carrier service. Marketplaces, WooCommerce, PrestaShop and Shopify all name deliveries their own way (“InPost Locker”, “DPD courier cash-on-delivery”), and each carrier has its own service catalogue. Without correct translation the parcel goes to the wrong service, or the label won’t generate at all.

What good mapping must handle:

Channel method name → carrier service — you set it once per delivery method, then it works for every following order from that channel.
Cash-on-delivery (COD) vs prepaid — the COD amount and how it’s settled must carry through to the label, otherwise the courier won’t collect the money.
Default rule (fallback) — if a method can’t be mapped unambiguously, the system flags the order for a manual decision instead of creating a wrong shipment.
Conditional rules — it helps to set logic like “parcel over 30 kg → pallet courier” or “international → different service”.

This is where the rollout is won or lost. A pretty interface without solid mapping is a calculator with a printer attached.

Parcel lockers and pickup points — separate data, not part of the address

A large share of parcels goes to lockers and pickup points (InPost, Orlen Paczka, DPD Pickup, DHL POP). That introduces a piece of data that door delivery doesn’t have: the identifier of the chosen point (e.g. KRA010). The customer picks it at checkout and it has to reach the label intact.

Common traps the software must handle correctly:

Point code as a separate field — if the tool pulls the address but drops the locker-code field, the label is created with no destination or with an error.
Customer changing the point — if the buyer edited the locker after ordering, the system must take the current value, not the original one.
Locker size (A/B/C dimensions) — it helps if the order carries the parcel size, or a default size assigned to the product.
Point-picker map — if the tool handles checkout itself, an up-to-date map of a carrier’s points is useful.

Rule of thumb: treat the locker identifier as first-class data — as important as the address. If it flows correctly, the rest of the label falls into place.

Tracking and statuses — the shipment number must close the loop

Generating the label is half the job. The other half is closing the loop: the tracking number has to return to the order and trigger the rest of the process. A tool that only prints a PDF and forgets the parcel leaves you clicking statuses by hand in every channel.

What to expect:

Shipment number saved on the order — you don’t hunt for it in the carrier panel; it sits with the customer.
Automatic status change to “shipped” once the label is created.
Customer notification — email or SMS with the number and a tracking link, sent automatically after dispatch.
Status pushed back to the channel — ideally the shipping status returns to the marketplace or store, so the buyer sees the current info where they bought.
Delivery monitoring — a consolidated view of which parcels are in transit, delivered, or stuck.

Batch printing and packing throughput

At higher volume, batch printing matters: you select the whole “ship today” list and generate all labels at once, in a single print-ready file. That’s the difference between packing 200 parcels in an hour and in half a day.

Features that genuinely speed up the floor:

Batch generation of labels for many orders in one click.
ZPL format / thermal printers — not just PDF; support for label printers (Zebra and similar).
Handover protocol / manifest — a consolidated end-of-day document handing parcels to the carrier.
Scan and check — it helps if a scan can confirm you’re packing the right parcel for the right label.
Return labels — handling returns without clicking each one from scratch.

What else to look at when choosing

Beyond the labelling features themselves, a few things decide whether a tool lasts:

Where order data comes from — does the tool pull orders from your channels itself, or do you upload them by hand? The label should be built from order data, not from re-typing.
Pricing model — per-parcel commission, subscription, or a package with a limit. Do the maths at your real volume, not at the headline price.
Your contracts vs broker rates — can you ship on your own carrier rates?
API and automation — can labels be wired into the rest of the process (statuses, notifications, webhooks), or is it a closed island?
Honesty about feature status — does the vendor say clearly what works today versus what’s “planned”? That saves disappointment after rollout.

We cover designing “if this, do that” rules around shipping in more depth in the guide on e-commerce order automation, and how a label is built from order data without re-typing the address — in the piece on automatic InPost labels for marketplace and WooCommerce orders.

Where Sellaro fits in (honestly, about status)

Sellaro is a central OMS — it collects orders and products from all connected channels into one normalised view and has an automation engine that reacts to domain events (new order, status change) with actions: email, SMS, webhook, log entry. That’s the foundation on which courier labels make sense at all — because the order data (recipient, address, delivery method, chosen point) is already organised in one place, ready to hand to the carrier.

We should be clear about where we are, though:

Ready today: store modules PrestaShop, Sylius, WooCommerce (connect a store as a channel, READ-ONLY — Sellaro does not write back to the store).
On the roadmap / added on request: marketplaces and courier integrations — InPost, DPD, DHL, Orlen Paczka and others — plus accounting.

In other words: label generation and batch printing are a direction we’re heading as a module added to the platform, not a ready “print” button in the panel today. We work on the principle that we add a missing integration for free within your plan — if InPost or DPD is your main carrier, flag it at onboarding and we’ll set it up as a priority.

Frequently asked questions

How many carriers should courier label software handle?

Exactly as many as you actually use — from one panel. In European e-commerce that usually means InPost, DPD, DHL and Orlen Paczka, often plus GLS or a national post service. A missing key carrier breaks the whole point, because you’d still ship part of your parcels separately.

What is delivery-method mapping and why does it matter so much?

It’s the rule that translates a channel’s delivery name (e.g. “InPost Locker”) into a specific carrier service plus the COD or prepaid variant. You set it once and it works for every order. Without correct mapping the parcel goes to the wrong service or the label won’t generate.

Does Sellaro generate courier labels today?

That’s a roadmap feature added as a module on request — not a ready button in the panel today. The foundation (normalised orders and the automation engine) already works, so once we connect a given carrier, the label is built from order data without re-typing the address. Flag your carrier at onboarding and we’ll prioritise it.

Should a labelling tool work on my own carrier contracts?

Ideally it gives you a choice: ship on your own carrier rates, or through a broker. If you have negotiated rates, being forced onto a broker’s price list can cost more — so it’s worth checking before rollout.

Summary

Good courier label software comes down to a few hard features: multi-carrier from one panel, correct delivery-method mapping, handling lockers as separate data, closed-loop tracking and batch printing — all fed by order data, not by re-typing addresses. Get that right and you stop clicking through windows and eliminate the most common shipping errors.

At Sellaro we’re building the foundation for it — normalised orders and the automation engine work today, while courier integrations (InPost, DPD, DHL, Orlen) and marketplaces are on the roadmap and added on request (a missing integration free within your plan). Work out your cost on the pricing page and tell us which carriers and channels you need — we’ll prioritise them.