InPost Buy in Hummerce is a direct integration with the InPost marketplace: the store lists offers based on its own items, retrieves orders from there, and continuously syncs prices and stock levels - similarly to the Allegro integration. Sales through InPost Buy go to the same panel and the same order handling as the store's other sales channels. This is a different mechanism from the InPost Pay payment method ("Buy with InPost" in the cart and on the product page) and from InPost Parcel Locker and courier delivery - InPost Buy is a separate sales channel (marketplace), not a payment or delivery method.
As of Hummerce 2.35.43, updated 2026-10-07.
¶ Benefits and use cases
- A new sales channel without an integration broker - the store connects to InPost Buy directly through the API, just like with Allegro.
- Offer prices and stock levels follow the store automatically - no manual re-entry after every change.
- One panel tab to manage InPost Buy accounts, offers and orders.
- Orders land on the same list and go to the same order handling as the store's other orders.
- Integration diagnostics in the panel (recent errors, account status) - no need to contact technical support for every issue.
- Bulk offer listing - a single InPost category mapping for a store category covers the entire product subtree.
- An offer is a separate object linked to one item and one InPost Buy seller account - it has its own name, description, InPost category, features, price, stock and package dimensions.
- Offer data can be pulled automatically from the item (name, description, brand, EAN, manufacturer code, category with features, dimensions, price and stock) - anything the operator entered manually is not overwritten, unless they deliberately use the option to fully re-pull data from the item.
- The price and stock can be fixed on the offer, or, by default, calculated automatically from the price list and warehouse pinned to the seller account.
- The InPost category is chosen manually or automatically based on the store category the item belongs to (with the option to override it for a single product) - only leaf categories can be selected.
- Offer photos come from the item image properties specified in the integration settings - main ones and fallback ones (used only when the main ones yield no photo). The order of the properties determines the offer's main photo. The number of photos can be capped in the settings (0 = no cap); InPost accepts at most 20 photos per offer.
- Photos can be refreshed in bulk from the item's current gallery: on the offer list, the bulk operation Update photos (from item gallery) rebuilds the photos of the selected offers (from version 2.35.43).
- In the offer editor you can fetch the current offer from InPost (Fetch the current offer from InPost): the store overwrites the name, description, brand, category, attributes, GPSR data, dimensions, photos, shipping time and quantity with the data held by InPost, while the item link and the price settings of the offer stay unchanged (from version 2.35.43). Unsent changes entered in the offer are lost - the store asks for confirmation before overwriting.
- The store caches InPost categories and their attributes for an hour. In the offer editor you can fetch them from InPost again without waiting for the cache to expire (from version 2.35.31).
- Manufacturer data and product safety information (GPSR) can be filled in on the offer or copied from the item's manufacturer database.
- An offer missing required data (name, description, brand, category, price greater than zero, stock) will not be sent to InPost - the store shows what's missing before the InPost interface is called.
- The store retrieves orders from InPost Buy on a cycle and saves them as regular orders, in the view set for the integration.
- The order status and shipment information are sent back to InPost Buy as the order is handled in the store.
- The payment method chosen by the buyer in InPost Buy (e.g. card, BLIK, Google Pay, Apple Pay, deferred payment, cash on delivery) is mapped to a payment method in the store.
¶ Price and stock sync
- Changing an item's price or stock level in the store automatically queues the linked offers for an update in InPost Buy - no manual push after every change.
- Price and stock updates are sent in batches, per InPost's recommendation - this limits the number of requests to the InPost interface.
The integration's diagnostics panel shows recent communication errors with InPost Buy, lets you check the account connection, and forces a re-sync.
Introduced in version 2.35 as an integration analogous to Allegro.
- From version 2.35.31: manual refresh of InPost categories and category attributes in the offer editor.
- From version 2.35.43: configurable photo sources and photo limit, the bulk operation Update photos (from item gallery), and fetching the current offer from InPost.
- A seller account in InPost Buy (Merchant Portal) and an API application registered on the InPost side, with access credentials - set up by the store or by us as part of the implementation.
- Store delivery methods matching the deliveries offered in InPost Buy.
- Items with a completed category, photos, dimensions and package weight - without this data, InPost will not accept the offer.
- Up-to-date stock levels in the store (Warehouse) - offer stock depends on them.
- The store's task schedule - the integration's tasks must be running.
- The integration works only in the panel - it doesn't require changes to the store template.
- Requires implementation - the module doesn't turn on by itself after an update. Scope:
- registering an application in InPost Buy (test and production environment) and entering the access credentials in the panel,
- configuring the seller account and authorization,
- setting the offer and order view, payment mapping and product data sources (description, photos, dimensions),
- importing or creating the first offers and linking them to items,
- testing in the InPost test environment, switching to production and checking the first orders.
- Minimum estimated time: one seller account, items with complete data (category, photos, dimensions) - from 12 h.
- The time for a specific implementation depends on its scope - we quote it individually.
- What the time depends on: the number of seller accounts, how complete the product data is (photos, dimensions, GPSR), the number of categories to map, migrating from another marketplace integration without duplicating orders, the store version.
- The integration supports InPost Buy only - other marketplaces (e.g. Allegro) have a separate integration.
- An offer without a photo will not be accepted by InPost - the store doesn't enforce this itself; InPost rejects it.
- An offer without package dimensions won't get a valid delivery method on the InPost side.
- Changing an offer's category clears previously filled features that don't belong to the new category - they need to be filled in again.
- A newly added InPost category, or a changed list of its features, appears in the store with a delay of up to an hour - the delay can be bypassed by refreshing categories and attributes manually in the offer editor.
- No InPost Buy operations in the store's REST API; only a read of the integration's status is available through MCP.
- We do not verify the configuration for legal compliance with InPost Buy's terms - offer content, GPSR data and VAT rates are set by the seller.
- InPost Buy write operations in REST API and MCP tools (today only a read of the integration status).
- Handling of returns and complaints filed in InPost Buy within the store's returns module.
Is InPost Buy the same as the InPost Pay payment method?
No. InPost Pay is the "Buy with InPost" payment option in the cart and on the product page. InPost Buy is a separate sales channel - a marketplace where the store lists offers.
Is InPost Buy the same as Parcel Locker delivery?
No. Parcel Locker and InPost courier delivery are a delivery method for the order, available regardless of whether the store sells through InPost Buy.
Do offer prices and stock levels need to be updated manually?
No. Changing an item's price or stock in the store automatically queues the linked offers for an update in InPost Buy.
Will an offer without a photo be published?
No. InPost rejects offers without a photo - worth checking before sending, since the store doesn't block it itself.
How long does the InPost Buy integration take to implement?
From 12 h at minimum - one seller account, items with complete data. More accounts and gaps in product data extend the time.
Does the integration have REST API operations?
No. REST API has no InPost Buy operations; only a read of the integration status is available through MCP.
Want to see how selling through InPost Buy could work in your store? Contact the Hummerce team (in Polish).
- InPostBuy menu (Configuration): Configurations (application data for authorization), Accounts (seller authorization, connection test), Offers (offer list and editing, bulk operations including Update photos (from item gallery)), Imported orders (order import preview, retry on error), Diagnostics panel (recent errors, connection test, forced sync).
- Panel configuration: Configuration -> Settings, InPostBuy group - environment (test/production), offer and order view, description and photo sources, Offer photo properties, Fallback photo properties, Maximum photos per offer (0 = no cap), payment mapping, package dimension and weight settings.
- Order: the "inPostBuy" source on the order list.
¶ REST API and MCP
- REST API: no InPost Buy operations in the store's REST API.
- MCP (AI assistant - MCP server):
ec2_inpostbuy_status - whether the integration is enabled, which views it uses for offers and orders, the scope of the published stock level, and the state of the integration's scheduled tasks. The tool only reads data.
The integration has no store messages - offer descriptions are built from item data and the offer form's fields. Email templates and alerts are changed separately; by default the store doesn't send its own emails to InPost Buy buyers, since InPost notifies them.
| Symbol |
Object |
Purpose |
_inPostBuyCategoryId |
item |
InPost category assigned to the item (overrides the category inherited from the store category) |
_inPostBuyOfferImages |
offer |
offer photos overriding the item's gallery |
_inPostBuyOfferDescriptionOverride |
offer |
offer description overriding the description taken from the item |