InPost Parcel Lockers are a standard in Polish e-commerce that cannot be skipped: for most stores it is the most frequently chosen delivery method, and a missing locker map in the cart means genuinely lost orders. The InPost integration with PrestaShop lets customers pick a locker on a map directly in the checkout, and lets the store generate labels, pickup protocols and track shipments from the panel — without manually copying data into a courier manager. Implementation usually costs 500–2,000 PLN net (commercial module plus configuration) and pays back at a few dozen shipments per month.
Najważniejsze: The InPost integration with PrestaShop runs through the ShipX API and covers: a Parcel Locker map in the checkout, locker size selection (A/B/C), label and pickup protocol generation from the store panel, shipment tracking, InPost Courier parcels and cash on delivery (COD). Implementation costs 500–2,000 PLN net, the module itself 200–600 PLN. An alternative for multichannel stores: integration through Baselinker when orders also come from Allegro and other marketplaces.
How does the InPost integration work?
InPost provides the ShipX API — that is how the store communicates with the carrier's system. A correct integration covers several elements that must work together:
- Locker map in the checkout — the customer picks a point on a map (the InPost widget or a module map), and the choice is saved with the order as delivery data.
- Locker size selection — size A, B or C; a well-configured module shows available sizes and prices the shipment accordingly.
- Creating shipments from the panel — from the order list you create a parcel, generate a label and a pickup protocol; the courier collects parcels in bulk.
- Tracking — the shipment number goes into the order and the customer email, and statuses update through ShipX webhooks.
- InPost Courier — alongside Parcel Lockers, enable courier parcels; customers often choose one or the other.
- Cash on delivery (COD) — for both lockers and courier; requires correct configuration in the module and gateway.
All of this works on PrestaShop 1.7, 8.x and 9.x — the key is matching the module version to your store version and PHP.
Custom module or ready-made?
There are three integration routes, with different trade-offs.
| Solution | Pros | Cons | Cost |
|---|---|---|---|
| Official InPost module | Direct carrier support, updates | Basic scope | 0 PLN |
| Commercial modules (Polish vendors) | Extended: locker sizes, COD, Baselinker, multi-courier | Cost, vendor dependency | 200–600 PLN one-off |
| Custom module | Fit for unusual processes (WMS, ERP, own panel) | Higher implementation cost | 1,500–4,000 PLN |
| Baselinker integration | One hub for stores and marketplaces | Linker subscription | within the subscription |
For most stores the best choice is a proven commercial module with Polish support — it works out of the box, gets updates for API changes and requires no own code maintenance. A custom module makes sense when the shipping process is unusual (own warehouse system, B2B pallet orders, oversized products). On custom module development see PrestaShop modules and customisations.
Implementation step by step
- InPost business account and contract — access to the ShipX API (token) and the carrier's price list.
- Choose and buy a module — compatible with your PrestaShop and PHP version.
- Configuration in the panel — delivery methods (Parcel Lockers, Courier), locker sizes, zones and prices, COD.
- Map in the checkout — test point selection on desktop and mobile; this is the most common source of integration bugs.
- Labels and protocols — a test shipment, label printing, courier pickup order.
- Tracking and emails — shipment number in the email, statuses via webhooks, tracking link.
- End-to-end tests — test orders: locker + courier + COD, verifying delivery costs and the invoice.
The whole implementation usually takes 1–3 business days; problems appear mostly with conflicts between delivery modules or old checkout templates.
How much does it cost and how much does it save?
| Item | Cost (net) |
|---|---|
| Commercial module | 200–600 PLN one-off |
| Implementation and configuration | 300–1,000 PLN |
| Checkout modifications (map, size selection) | 500–2,000 PLN |
| Maintenance and updates | within store care |
- The saving is in work: manually issuing labels takes 2–5 minutes per shipment — at 500 shipments a month that is over a dozen hours. Automation pays back almost immediately, and the number of address and locker-number mistakes drops too.
Frequently asked questions
Does InPost have an official PrestaShop module?
Yes — InPost provides official PrestaShop plugins (with implementation documentation for 1.7+). The scope is basic; stores needing locker sizes, COD, Baselinker integration and multi-courier support often choose extended commercial modules.
Does the integration require the ShipX API?
Yes — the store communicates through the ShipX API (an API token from the InPost panel). Modules "working without an API" are usually overlays for manual data entry; full label and status automation requires ShipX.
Does the customer pick a locker on a map in the checkout?
In a well-implemented integration — yes: the Parcel Locker map appears when choosing the delivery method (the InPost widget), and the selected point is saved with the order and on the label. It is the most important UX element of the integration; test it on mobile.
Can Parcel Lockers be combined with courier and COD?
Yes — modules support Parcel Lockers (Standard and Allegro), InPost Courier, COD shipments and oversized parcels. In the configuration you set up separate delivery methods with their own prices and zones.
What about Allegro orders — integrate separately?
If you sell on Allegro and in your own store, the simplest approach is to connect everything through Baselinker or a similar linker: orders from marketplaces and the store land in one panel, from which you generate InPost labels. See Allegro + PrestaShop.
Does the InPost module survive PrestaShop updates?
Well-maintained modules get updates for new PrestaShop versions (8.x, 9.x) and PHP. Before updating the store, check module compatibility — and test a shipment afterwards. It is a standard part of any update plan: PrestaShop support.
Sources and tools
- InPost — integrations for online stores
- InPost — ShipX documentation for PrestaShop
- PrestaShop Addons — carrier modules
- PrestaShop DevDocs — modules
- Baselinker — integration documentation
👉 Want to automate InPost shipping in your store? See e-commerce integrations and PrestaShop store development in my offer: InPost modules, locker maps, labels, tracking and marketplace integration. Get in touch via the contact form or at kontakt@informatix.com.pl.
👉 Tidying up shipping and payments? Check Przelewy24 in PrestaShop, Allegro + PrestaShop and PrestaShop API.
📖 See also: PrestaShop online store, PrestaShop modules and customisations and resilient API and webhook integrations.