Connect Commercetools to InPost so shoppers can choose lockers or pickup points at checkout, while your team automates labels, tracking updates, order status sync, and returns.
• InPost delivery methods are exposed in Commercetools checkout, with pickup-point selection persisted as custom fields on the Cart and Order objects.
• Pickup point availability is requested from InPost APIs based on shopper location and mapped to a store-friendly pickup point ID plus human-readable address details.
• Shipment creation triggers InPost label generation, and returned label IDs, tracking numbers, and carrier services are stored on the related Commercetools shipment.
• Tracking webhooks or polling updates are translated into Commercetools order and shipment state transitions, with timestamped status history kept for support use.
• Validation handles missing or incompatible pickup-point data before fulfillment is released, and exceptions are logged with request and response payload references.
• Returns flow events map RMA identifiers and return shipment updates between Commercetools Returns and InPost return shipments, keeping statuses aligned across systems.
.png)
We pass the chosen InPost location into Commercetools as shipping method data and validate pickup point availability before the order is placed.
The integration syncs shipment creation, label IDs, tracking numbers, tracking events, and delivery status so each update maps back to the right Commercetools order.
Yes, we trigger InPost label creation from the fulfillment step, store the label reference on the order, and support printing and reprints for the warehouse team.
Yes, we can configure InPost methods per market, currency, and store, while keeping pickup point rules and availability checks consistent across locales.
We connect the InPost return flow to Commercetools returns so return labels, statuses, and tracking updates stay visible for support and operations.














