¶ InPost - parcel lockers and courier

InPost in Hummerce is an integration with the Parcel Locker network and InPost courier: the customer picks a pickup point on the map in the cart, and the store creates the shipment itself, generates the label and tracks its delivery status. This is about delivery - a different mechanism from the InPost Pay payment ("Buy with InPost" in the cart and on the product page) and selling through InPost Buy (the InPost marketplace).

Last updated: 2026-09-29.

¶ Benefits and use cases

The customer picks a Parcel Locker on the map in the cart (the InPost widget) instead of hunting for a point code manually - ready-made in the BS5 template.
Automatic shipment and label creation after the order status changes to "ready to ship" - no manual re-typing of the address into the InPost system.
Automatic shipment statuses (in transit, ready for pickup, delivered, returned to sender), updated periodically - fewer "where's my parcel" questions to store staff.
The tracking link can be emailed to the customer along with the tracking number.
Support for cash on delivery and shipment insurance.
An extra weekend delivery option (Parcel on Weekend).

¶ How it works

¶ Two InPost integrations

InPost (older integration) - based on the Parcel Locker XML API with separate login (login, password); marked as deprecated.
InPost ShipX (current, recommended) - based on the ShipX REST API, token authorization (Bearer token) and an organization ID from the InPost Parcel Manager.
Both integrations can run in parallel during a migration period - only ShipX remains in the end.

¶ Choosing a Parcel Locker in the cart

In the BS5 template, the customer picks a point on the map (the InPost widget) in the delivery-choice window.
The chosen point is saved on the order, and for a logged-in customer also on their account, so the last chosen point is suggested on the next order.
The list of points (Parcel Lockers and customer service points) is periodically imported into the store, to verify the chosen point and its capabilities (e.g. whether it accepts cash on delivery).

¶ Creating a shipment and the label

After the order's delivery status changes to "ready to ship," the store automatically creates the shipment in the ShipX API (unless sending data to InPost is disabled in the configuration).
The shipment can be handed over directly at a Parcel Locker or by ordering a courier pickup from the sender's address - both options are configurable.
The label is available in PDF or thermal format (EPL2), in A4 or A6 size.
The parcel size (A/B/C by dimensions) is set as a default for the delivery method, or chosen manually by the person handling the order.

¶ Shipment status and the weight limit

The store periodically polls InPost for the shipment status and sets the matching order delivery status (including in transit, ready for pickup, delivered, returned to sender).
The maximum weight for a single parcel is 25 kg by default - the store can check this before the order is placed, if items have weight filled in.
Weekend delivery and shipment insurance are options enabled separately for a given delivery method.

¶ Version

The InPost integration (Parcel Lockers and courier) has worked in the platform for a long time - the exact version both plugins were introduced isn't stated in the available sources.
The current ShipX (REST) integration replaces the older, XML-based one - for customers still using it, both may run in parallel during a transition period.

¶ Dependencies

A contract with InPost and access data for the ShipX API (organization ID, API token, map widget token) - the store gets these on its own from the InPost Parcel Manager.
Store template: the Parcel Locker selection widget is ready-made in BS5; older templates need adjustments.
Weight on items - to verify the parcel weight limit.
Linking with payments (cash on delivery) - Payments overview.
General rules for delivery methods - Delivery methods overview.

¶ Implementation

Requires implementation - the integration doesn't work without configuration. Scope:
- enabling the ShipX integration and filling in access data from the Parcel Manager,
- setting up a delivery method flagged for InPost,
- testing in the InPost test environment and switching to production,
- checking the point-selection widget in the template (ready-made in BS5, needs adjustment in older templates),
- an email template with the shipment tracking link.
Minimum estimated time:
- configuring the ShipX integration in the panel and testing - from 4 h,
- with adjusting the Parcel Locker selection widget in a template older than BS5 - from 8 h,
- migrating from the older XML integration to ShipX - an additional 4 h.
What the time depends on: the store template (BS5 has a ready-made widget), whether only the Parcel Locker or also the pickup courier is enabled, the number of views and countries, whether migration from the older integration is needed.

¶ Limitations

The maximum weight for a single parcel is 25 kg - an InPost limit, not configurable upward.
The older integration (XML) is marked as deprecated - new deployments should use ShipX.
The Parcel Locker selection widget in the cart is ready-made only in the BS5 template - older templates need adjustments.
Importing the point list is needed to verify the chosen point, even if sending data to InPost is disabled.
No management of the InPost integration through the REST API and MCP - configuration only in the panel.
We do not verify the task for legal compliance (e.g. licenses of submitted materials, GDPR, store terms of service).

¶ Future development

Fully retiring the older XML integration in favor of ShipX.
Managing the courier integration's settings through the API and MCP.
Extending automatic shipment statuses to further carriers in a single mechanism.

¶ Frequently asked questions

Does the customer choose a Parcel Locker on the map in the cart?
Yes, in the BS5 template through the InPost map widget. Older templates need adjustments.

Does the store generate the label and tracking number on its own?
Yes. After the order status changes to "ready to ship," the ShipX integration creates the shipment and label (PDF or thermal format).

Does the customer see the parcel's status without contacting store staff?
Yes. The store periodically fetches the status from InPost and updates the order's delivery status; the customer can get a tracking link by email.

Does InPost support cash on delivery?
Yes, if the chosen payment is marked as cash-on-delivery and the chosen pickup point supports it.

How long does implementing the InPost integration take?
From 4 h in the BS5 template. From 8 h if the Parcel Locker selection needs adjusting in an older template.

Can parcels heavier than 25 kg be shipped?
No - that's InPost's limit for a single parcel.

Delivery methods overview - general pricing and configuration rules for delivery methods.
InPost Pay - the "Buy with InPost" payment, a separate mechanism from the delivery described here.
InPost Buy - selling offers through the InPost marketplace.
On hummerce.com: InPost integration (in Polish).

Want to see how the InPost integration could work in your store? Contact the Hummerce team (in Polish).

¶ Configuration details

¶ Access in the admin panel

ShipX integration configuration: Configuration -> the InPostShipX tab - Organization ID, Bearer token, Geowidget token, Base connection URL, URL of the service providing the available Parcel Locker list, Fetch the list of pickup points (Parcel Lockers), Default parcel type/size (A/B/C), Automatically order a courier, Send data to InPost, Import shipment statuses only.
Older integration (if still active for the customer): a separate configuration tab with access data for the XML API and the backup FTP.
Editing a delivery method: the InPost delivery property, optionally InPost: Insurance and weekend delivery.
Order: tracking number, chosen Parcel Locker, InPost status, integration error code and message - in the order details.

¶ REST API and MCP

The REST API and MCP have no dedicated methods for the InPost integration - the delivery method, delivery status and tracking number are visible through the general REST API and MCP for deliveries (Delivery methods overview); the integration itself updates this data on the order.

¶ Store messages

The point-selection message in the cart - in the message editor; the content of the point-selection window itself comes from the InPost widget and isn't translated by the store.
Shipment status descriptions shown to the customer (e.g. "parcel in transit," "ready for pickup") come from the InPost integration - fixed content shipped with the module.

¶ Parameters

Symbol	Object	Label
`_inPostDelivery`	delivery	InPost delivery
`_inPostInsurance`	delivery, order	Insurance
`_inPostPackageType`	order	Parcel type/size (A/B/C)
`_inPostBoxMachineName`	order, customer	Chosen Parcel Locker
`_inPostPackCode`	order	Tracking number
`_inPostStatus`	order	InPost status (internal identifier)
`_inPostErrorCode`, `_inPostErrorMessage`	order	Integration error code and message
`end_of_week_collection`	delivery	Weekend delivery