InPost
ShipX, Geowidget, status webhooksLocker shipments created in ShipX in batches, with labels, a pickup order and a validation error to fix.
InPost, DPD and Furgonetka integration in your store
The customer picks a pickup point at checkout, the warehouse prints a label in one click, and the parcel status flows back to the order by itself. Directly to the carrier or through an aggregator, depending on your volume and couriers.
The carriers and aggregators we connect to
Each has its own page with its API, sample code and pitfalls.
DPD
SOAP service: numbers, labels, protocolsA 10 x 15 cm label for a thermal printer, one per parcel, fetched right after the parcel numbers.
Furgonetka
Many couriers, one point mapPickup points of several networks on one map at checkout, with a price at each point.
Apaczka
Pricing, labels, handover documentCourier prices at checkout worked out for the weight and size of this order's parcel.
Carriers from the integration side
Each talks differently. That decides rollout time more than the feature count. "Per arrangement" marks a detail we have not confirmed in public documentation. We check it for your agreement before quoting.
| From the integration side | InPost ShipXcarrier, its own API | DPD Polandcarrier, its own API | Furgonetkaaggregator | Apaczkaaggregator |
|---|---|---|---|---|
| API style | REST | SOAP with versioned operations | REST | REST with signed requests |
| Authentication | organisation token, OAuth 2.0 | login, password and customer number | OAuth2 | HMAC-SHA256 with the App Secret |
| Test environment | a separate sandbox account | a demo service | per arrangement | per arrangement |
| Point map for checkout | Geowidget | per DPD arrangement | a multi-carrier map | points via API |
| Shipment statuses | webhooks | per DPD arrangement | via API | a tracking endpoint |
Shipping without retyping
Every carrier names statuses its own way. In your system we fold them into one list that customers and support understand.
One list of statuses
The customer and support see the same five statuses whichever carrier has the parcel.
Label readyDispatchedIn transitReady for pickupDeliveredProblemFailed deliveryThe status comes back to the order by itself
The integration records every change on the order and in the store's messages, so nobody retypes it from the carrier's panel.
- InPost ShipXWebhooks
- DPD PolandPer DPD arrangement
- FurgonetkaVia API
- ApaczkaA tracking endpoint
The status on the orderthe same for every carrierA tracking link
Once the parcel is in transit, the customer gets the carrier's tracking link. Support sees a failed delivery, a return or damage in the panel at once.
An aggregator or the carrier directly
The most common shipping question. The answer depends on parcel volume and couriers.
- Your system
- Furgonetka, Apaczka
- Many carriers
An aggregator: Furgonetka or Apaczka
Pick it when
Choice at checkout
You want to offer customers several couriers.
Parcel volume
You ship a moderate number of parcels.
Agreement and billing
You prefer one integration and one bill.
Features
What the aggregator passes on is enough.
What you get
One API for many carriers, with a point map and labels.
- Your system
- InPost ShipX, DPD Poland
The carrier directly
Pick it when
Choice at checkout
One carrier at checkout is enough.
Parcel volume
One carrier handles most parcels.
Agreement and billing
You have your own agreement with it.
Features
You need features the aggregator does not pass through.
What you get
An integration with the carrier's API, e.g. InPost ShipX or the DPD service.
Common questions about courier integrations
Shipping, labels and parcel statuses
Read next
Where the orders to ship come from.
How do you ship parcels today?
Tell us which couriers you use and how many parcels you ship a day. We will reply within an hour with a proposal and a quote.