The Baselinker integration in Hummerce connects the store with Baselinker - an external broker that lists offers and receives orders from Allegro, eBay, Amazon and many other sales channels in one place. The store shares items, stock levels and orders with Baselinker, and day-to-day channel management stays in the Baselinker panel (an external service, requiring its own subscription).
As of Hummerce 2.20 onward (latest module changes: 2.35.68), updated 2026-10-07.
¶ Benefits and use cases
- Single data source for multiple marketplaces - items, stock and prices from the store reach Allegro, eBay, Amazon and other channels supported by Baselinker, without manually entering data in each one separately.
- Orders from every channel return to one store - staff handle them exactly like orders placed directly in the store.
- Statuses and tracking numbers update automatically - a change to an order's or delivery's status in the store reaches Baselinker, and from there the buyer on the given marketplace.
- Waybills return to the marketplace - for orders from selected sources (e.g. Empik) the store itself passes the waybill number to Baselinker and, optionally, the "shipped" status, so the buyer gets the parcel number without manual work (from version 2.35.68).
- Flexible choice of the price exported to Baselinker - the price can come from any price list rule, not just the item's base price.
- Separate view for integration items and orders - the store's catalog and customer base stay shared, while marketplaces get a dedicated data scope (Views - several stores in one panel).
Baselinker receives from the store:
- the list of categories,
- the list of items and item details, optionally with variants and properties,
- stock levels,
- delivery and payment methods configured in the store.
The store accepts from Baselinker:
- new orders,
- order status changes - by default Baselinker updates the fulfillment status every hour and the payment status every 4 hours.
The store sends to Baselinker (from version 2.35.68):
- waybill numbers of orders from selected sources (e.g. Empik - a marketplace name; the sources are set in the configuration),
- optionally, the order status (e.g. "shipped") right after the waybill number is passed.
The integration does not support:
- sorting items by warehouse stock quantity (a store with multiple warehouses calculates availability differently than Baselinker assumes),
- sharing orders placed directly in the store back to Baselinker,
- more than one main category per item (Baselinker assigns one category per product).
From version 2.35.68 the store can itself send waybill numbers to Baselinker for orders from selected order sources (e.g. from Empik), instead of waiting for Baselinker to ask for them.
- The export task runs in the store's schedule every 5 minutes and handles orders that have a waybill number and a courier code. It can be switched on and off in the settings, without restarting the store.
- The order sources covered by the export, the number of orders per run, the maximum number of send attempts and the minimum gap between sending the waybill number and the status are integration settings. The gap gives Baselinker time to register the parcel before the status changes.
- After the waybill number is passed, the store can set the order status in Baselinker (e.g. "Shipped"). Once the number of attempts is exceeded, the order drops out of the queue and waits for staff to react.
- The Diagnostics panel in the Baselinker menu shows the module state (token, sources, task, Baselinker availability), orders waiting for export, available courier codes, recent exchange attempts and errors, and lets you test the connection and clear the panel's buffers.
- The export requires a Baselinker API token and a courier code on the order. While the configuration is incomplete the task does not start, and the Diagnostics panel shows what is missing.
Baselinker and the store keep separate status dictionaries. The integration maps the combination of the store's order and delivery status to a single Baselinker status (e.g. an order placed and not yet shipped in the store corresponds to "New" in Baselinker; an order in progress with a shipped delivery corresponds to "Shipped"). Payment mapping is optional - without it, the order gets the default payment from the integration configuration.
- An order from Baselinker reaches the store without thorough validation of the buyer's data - the store calculates any missing totals itself.
- The store splits the buyer's first and last name at the first space in the data from Baselinker.
- Delivery and payment are set from the mapping in Baselinker, and when it's missing - from the default delivery and payment in the integration configuration (separately for orders paid in advance and cash on delivery).
- Resending the same order from Baselinker (an update) creates a new order in the store instead of updating the existing one.
- The store shares selected item properties with Baselinker from two groups: properties also visible in the store panel (sent as features with a name and value) and properties dedicated only to the integration (sent as additional data, symbol and value).
- Multi-value properties send only the first value.
- Mapping the store's properties to Allegro properties (when Baselinker lists an offer on Allegro) is set in the Baselinker panel, not in the store.
- Baselinker integration available since Hummerce 2.20.
- Since version 2.35.68 - passing waybill numbers (and optionally the order status) to Baselinker for orders from selected sources, plus an integration diagnostic panel.
- Pagination of the item, price and variant list (a page parameter and a configurable number of items per page) - introduced in a later module version, useful for large catalogs.
- An active Baselinker subscription (external, outside Hummerce) and a configured "own store" integration in the Baselinker panel.
- Views - the integration uses an item view (what to export) and an order view (which view receives orders from Baselinker); these can be the same views used by other integrations, or dedicated ones.
- Delivery and payment methods in the store, to which Baselinker's deliveries and payments are mapped.
- Requires implementation - the module doesn't work on its own after an update. Scope of a typical setup:
- enabling the module and generating a communication password,
- configuring the "own store" integration in the Baselinker panel (data exchange file address, communication password),
- assigning the integration's item view and order view, and the default delivery and payment,
- testing the connection and the first item and order retrieval,
- optionally: passing waybills to Baselinker - the Baselinker API token, order sources, courier code, the shipped status, enabling the export task and trial runs in mock mode, which only logs requests,
- optionally: mapping properties to Allegro attributes in the Baselinker panel (on the Baselinker side, not the store).
- Minimum estimated time: a basic setup (one item view, standard properties, no variants) - from 8 h; we always add: analysis - +1 h, testing - +2 h, production deployment - +1 h.
- The time for a specific implementation depends on its scope - we quote it individually.
- What the time depends on:
- the number of views and marketplaces handled by Baselinker,
- support for item variants and additional properties,
- mapping of non-standard statuses and payments,
- the store version - an older version requires an update first (quoted separately).
- The integration doesn't sort items by warehouse stock quantity - this limitation comes from the store's support for multiple warehouses.
- Orders placed directly in the store don't reach Baselinker. Passing waybills applies only to orders from selected sources that originate from Baselinker.
- Passing waybills requires a Baselinker API token and a courier code on the order, and Baselinker allows 100 requests per minute, so the store sends orders in batches.
- One item - one main category on the Baselinker side, regardless of how many categories it's assigned to in the store.
- Mapping the store's properties to Allegro attributes (in the Baselinker panel) only works in Allegro category fields, not in the offer description - yes/no properties in the description show up exactly as saved in the store.
- Resending the same order from Baselinker creates a new order instead of updating the existing one.
- Status updates happen on Baselinker's initiative, on its own cycle (by default every hour for delivery, every 4 hours for payment), not immediately after a change in the store. The exception is the waybill number (and optionally the shipped status) of orders from selected sources - the store sends these itself, every 5 minutes.
- We do not verify the task for legal compliance (e.g. licenses of submitted materials, GDPR, store terms of service).
- Sorting items by warehouse stock quantity with multiple warehouses.
- Passing orders placed in the store back to Baselinker.
- More than one main category per item on the integration side.
Can Baselinker list offers on several marketplaces at once?
Yes - that's Baselinker's core role as a broker; the store shares items and stock with it, and listing on Allegro, eBay, Amazon and other channels is configured in the Baselinker panel.
Do orders from Baselinker reach the same store as orders placed directly?
Yes. Staff handle them exactly like other orders, in the order view specified in the integration configuration.
Does the integration update order statuses in real time?
Not instantly - Baselinker polls the store for statuses on its own cycle (by default every hour for delivery, every 4 hours for payment).
Does the store pass parcel numbers to Baselinker itself?
Yes, from version 2.35.68, for orders from selected sources (e.g. Empik). The export task runs every 5 minutes and requires a Baselinker API token and a courier code. For other orders Baselinker fetches the data on its own cycle.
Do you have to pay for Baselinker separately?
Yes. Baselinker is an external service with its own subscription, independent of Hummerce.
How long does setting up the Baselinker integration take?
A basic setup with one item view - from 8 h. The time for a specific implementation depends on the number of views, marketplaces and non-standard mappings.
Want to see how the Baselinker integration could work in your store? Contact the Hummerce team (in Polish).
- Configuration -> Settings, Baselinker section: communication password (pasted from the Baselinker panel), criteria for orders retrieved from Baselinker (e.g. source), default delivery and payment (separately for cash-on-delivery orders), the item view exported to Baselinker, the order view, pagination settings for the item, price and variant list.
- Baselinker -> Diagnostics (from version 2.35.68): waybill export state, order queue, courier codes, recent requests and errors, Test connection, Clear buffers.
- Waybill export settings (from version 2.35.68): Base API URL, Base API token, Run waybill export task, Order sources with waybill export, Waybill export batch limit, Max send attempts, Min gap between waybill and status sending (ms), Base sent status id, Send order status after waybill, Use mock API client (only logs requests), Per-message logging. The courier code is read from the order property named in the module configuration.
- In the Baselinker panel: an "own store" integration type with the data exchange file address (the store panel address with the integration endpoint) and the pasted communication password; Orders, Products, Statuses and Shipments tabs on the Baselinker side.
¶ REST API and MCP
The integration works through its own data exchange file and tasks called by Baselinker - independent of REST API and the AI assistant (MCP).
- Item properties shared with Baselinker are set in two locations: one shared with the store panel (sent as features with a name and value), and one dedicated only to the integration (sent as additional data, symbol and value) - changed in Properties and locations.
- Mapping of item fields (price, VAT, EAN, name, weight, description, manufacturer data, category) and order fields (delivery data, invoice data, contact, comment) between Baselinker and the store is set by default in the module configuration; changing it requires editing the module's configuration file by an implementation engineer.
- The order property
_baselinkerWaybillSendStatus stores the progress of the waybill export (queued, package sent, status sent, error); _baselinkerWaybillErrorCount is the failed-attempt counter.
- The price exported to Baselinker can come from any price list rule assigned to the integration's item view, instead of only the base price.