contact ↗

← all posts

blog / e-commerce

e-commerce shipping integration: carriers, labels, tracking and pickup points

the carrier turns an order into a parcel.  from the shop's side that means four jobs: show delivery options and prices at checkout, create a shipment and label when the order is ready, tell the customer where the parcel is, and handle what goes wrong.  each carrier does these with different apis, field names and rules.

delivery options at checkout

what the checkout promises must match what the warehouse can do.  if the cut-off for next-day delivery is 2 pm, the checkout needs to know that.  delivery options should come from rules the warehouse owns: cut-off times, working days, weight limits, restricted destinations.

shipping prices come either from a fixed table, which is simple and predictable, or live from the carrier's rate api, which is accurate and adds a dependency to every checkout.  most shops start with tables by weight and zone and move to live rates only when the difference matters.

labels and shipment data

creating a label requires clean data: a valid address, weight, dimensions, and for international parcels customs details.  bad addresses are the most common source of failed shipments, so validate them in checkout instead of discovering the problem at the packing bench.

check which label formats the carrier returns (pdf for office printers, zpl for thermal printers) and whether your warehouse printers can use them.  check how returns work too: a return label is a separate flow, often with separate rules, and customers expect it to be easy.

pickup points and parcel lockers

in many european markets, pickup points and lockers are a major delivery choice.  in poland, inpost lockers are the obvious example.  integrating them means embedding a point selector in checkout and storing the chosen point id on the order.  point lists change, so use the carrier's live widget or api instead of a copied list that goes stale.

tracking and customer messages

customers ask "where is my parcel" more than any other question.  pull tracking events by webhook where the carrier supports it, and by polling where it does not.  map the carrier's many statuses to a short list you control: shipped, in transit, out for delivery, ready for pickup, delivered, problem.  then send messages from your own system with your own wording.

direct integration or an aggregator

integrating each carrier directly gives you full control and the carrier's own contract rates, at the price of one integration per carrier.  a shipping aggregator such as sendcloud, shippo or easypost puts many carriers behind one api, which saves build time and adds a fee and another vendor.  for two carriers with high volume, go direct.  for many carriers or low volume, an aggregator is often cheaper overall.

whichever route you take, test with real labels and real addresses before launch.  sandbox labels do not scan at the depot.

example tools and docs

← all posts