InPost
Parcel locker and courier delivery for an online store: choice at checkout, labels and statuses via API.
IntegrationsUsing since 2025 · Featured project: The Travelling Cows
- Category
- Integrations
- Using since
- 2025
- Featured project
- The Travelling Cows
In practice
I add InPost to an online store when customers should be able to choose delivery to a parcel locker or by courier. At The Travelling Cows a physical-product store on Shopify got that delivery, and the orders also reach the client account.
What is InPost?
InPost is a parcel operator with a network of Paczkomat lockers and courier delivery. For a store it matters that the customer picks where to collect the parcel at checkout, and the store has to pass that place on and create the shipment.
For integration there is the ShipX API, through which a store creates parcels and pulls labels and statuses, and the Geowidget, an element for choosing a locker in the checkout. API access is protected by OAuth 2.0 with a Bearer token.
- Collection
- A Paczkomat locker or a courier
- API
- ShipX, OAuth 2.0 authorization
- Locker choice
- Geowidget in the checkout
- Labels
- PDF, EPL2 or ZPL
How I work with InPost
I start with what the customer picks at checkout and what the store does with the parcel afterwards: creates it, prints the label, shows the status. That decides how much of the integration I write as custom code.
Choice at checkout
I settle whether the customer picks a locker or a courier. For the locker I use the InPost Geowidget embedded in the checkout, so I do not build a map myself. I did it that way on The Travelling Cows.
Parcel and label
After an order the store sends the data to the ShipX API, which lets it create the parcel and fetch the label. I keep credentials on the server, in environment variables. On The Travelling Cows I used exactly the ShipX API.
Statuses and orders
Parcel statuses can be pulled from the API or received through webhooks, so the store knows what happens to a parcel. On The Travelling Cows the store orders show up in the client account.
When it fits, and when it doesn't
InPost fits when customers want to collect parcels from a locker or get them by courier.
A good fit when
- A physical-product store whose customers buy in Poland.
- A checkout where the customer picks a locker instead of typing an address.
- A store that should pull labels and statuses through the API, not by hand.
- A platform of services that adds sales of physical products.
Not a fit when
- A store with digital products or services, with no shipping.
- Sales mostly abroad that need a different carrier.
- A team that will not maintain an API integration through changes on the carrier side.
I do not compare other couriers and parcel aggregators from experience, because I used InPost in my project. I pick the carrier by where your customers live and how they prefer to collect parcels.
Frequently asked questions
Should your store ship with InPost?
Tell me which platform the store runs on and whether customers should pick a locker. I will say what a ready integration can cover, and what needs custom code.