The Hummerce integration with BPSC (Impuls EVO) ERP connects a store to the ERP via REST API, without manual re-entry of data. It works in two variants: for B2B sales - items, customer price lists, customer accounts, delivery addresses, sales representatives and orders - and for retail stores - items, stock levels, orders and invoices customers can download.
Last updated: 2026-10-09. The integration is being extended - we keep adding further areas to its scope.
¶ Benefits and use cases
- B2B customer accounts created from the ERP - a BPSC customer gets a store account with an assigned sales representative, coordinator and payment method, with no manual registration.
- Individual customer prices from the ERP - price lists and customer-to-price-list assignments are imported from BPSC; a changed assignment in the ERP shows up in the store within a minute.
- An offer matched to the customer - the customer group in the ERP decides which store views (offer scope) the business customer sees.
- Orders in the ERP without re-typing - a store order reaches BPSC automatically, with the customer's delivery address and payment method; the sales team works in the ERP.
- Several companies in one ERP - an order goes to the right company and organisational unit in the ERP based on the order type.
- Product attributes from the ERP - item features from BPSC feed the store's attributes, so filtering and technical descriptions do not require double work.
- Stock levels and invoices in a retail store - stock refreshed every 5 minutes, and customers download ERP invoices and receipts as PDF from their account, without contacting staff.
- B2B variant - full exchange of business customer data: customer accounts, individual price lists, addresses, sales representatives, orders. Described in the sections from "How the store connects to BPSC" to "Monitoring and diagnostics".
- Retail store variant - items, stock levels, orders and invoices for customers. Described in the "Retail store variant" section.
The variant is chosen during implementation, depending on the sales model and on the interface the ERP exposes.
- Hummerce connects to the ERP via the BPSC REST API, in JSON format. No intermediate database or file exchange is needed.
- The store fetches data from the ERP incrementally - each run picks up only records changed since the previous import. The import starting point can be set manually in the admin panel, e.g. to force data to be fetched again from a given date.
- Each type of exchange is a separate scheduled task with its own on/off switch in the settings - the integration can be launched step by step.
| Data |
Direction |
Frequency |
| Items |
ERP -> store |
every 5 minutes |
| Item features (attributes, item group) |
ERP -> store |
every 10 minutes |
| Price lists |
ERP -> store |
once a day |
| Customer-to-price-list assignments |
ERP -> store |
every minute |
| Customers (B2B accounts) |
ERP -> store |
every 10 minutes |
| Customer activity status |
ERP -> store |
every 10 minutes |
| Delivery addresses |
ERP -> store |
every 10 minutes |
| Sales representatives and coordinators |
ERP -> store |
every 6 hours |
| Orders |
store -> ERP |
every minute |
| Order statuses |
ERP -> store |
on a schedule |
- A BPSC customer becomes a customer account in the store. The account is matched by e-mail address, or - if there is none - by the customer ID in the ERP. A repeated import updates the data without creating a duplicate.
- The account receives the sales representative, coordinator, payment method and delivery addresses from the ERP.
- The customer group in the ERP determines the store views (offer scope) the customer sees after logging in.
- The store can send imported customers a welcome e-mail - a feature enabled in the settings.
¶ Items and prices
- The item import sets whether a new item is immediately available and purchasable - depending on the store settings.
- Item features from the ERP are mapped to store attributes.
- Price lists are imported in full: when a price list changes in the ERP, the store refreshes it in full, so after the import store prices match the ERP price list.
- An order placed in the store is sent to BPSC automatically, with the delivery address, payment method and additional services.
- Each order has a sending flag in the admin panel: not ready, ready to send, sent, error, do not send.
- When the ERP rejects an order, the store retries every minute up to the configured attempt limit, then flags the order as an error for staff to check.
- Orders from a selected store view can be excluded from sending to the ERP.
¶ Monitoring and diagnostics
- The integration has its own BPSC section in the admin panel.
- Request logging and extended logging are switched on in the settings - for the launch period or for diagnosis.
- Test mode lets the integration run without a connection to the ERP - for testing the store before BPSC is connected.
The store connects to a REST API exposed for the Impuls ERP by the ERP implementation partner. Access is protected by a token and restricted to trusted IP addresses.
| Data |
Direction |
Frequency |
| Items (new and changed) |
ERP -> store |
every 15 minutes |
| Stock levels |
ERP -> store |
every 5 minutes |
| Orders |
store -> ERP |
every 5 minutes |
| Invoices and receipts (PDF) |
ERP -> store customer |
on customer request |
- Items - incremental import; new items from the ERP are created in the store automatically.
- Stock levels - incremental import, into one store warehouse.
- Orders - sent to the ERP with the payment status; delivery and payment costs can be passed to the ERP as a separate line. When the ERP rejects an order, the store retries up to the configured number of attempts.
- Invoices and receipts - the customer downloads the document issued in the ERP as a PDF from the order list in their account. Only the logged-in customer has access, and only to their own orders.
- Each exchange type has its own switch in the settings; there is also a test mode without a connection to the ERP.
- B2B variant: access to the BPSC REST API - service address and API key from the ERP administrator.
- Retail store variant: a REST API for the Impuls ERP exposed by the ERP implementation partner, with the store server on the trusted IP list, and access to the invoice PDF files issued by the ERP.
- Store views, customer groups, order statuses and item features prepared in Hummerce and mapped to the ERP data.
- Business customer accounts - B2B sales in Hummerce.
- The integration requires implementation - it does not start by itself after an update. A typical rollout covers:
- configuring access to the BPSC REST API,
- mapping customer groups to store views, item features to attributes, ERP order statuses to store statuses,
- switching on further exchange types and the first data import,
- end-to-end tests: customer and price list import, a test order, checking the order and its status in the ERP.
- Implementation time is agreed individually after analysing the scope.
- What the time depends on:
- the number of exchange areas and the data volume,
- the number of companies and organisational units in the ERP,
- the number of customer groups and store views to map,
- the scope of additional services in the order.
- B2B variant: a full price list import overwrites prices added manually in the store - permanent price changes are made in the ERP.
- B2B variant: a customer has one group in the ERP, and that group defines their offer scope in the store.
- Retail store variant: prices are set in the store, stock goes into one warehouse, and order statuses do not come back from the ERP to the store.
- Data is exchanged by scheduled tasks, with a delay from one minute to one day depending on the data type.
- We do not verify the task for legal compliance (e.g. licences for supplied materials, GDPR, store terms and conditions).
In progress in the B2B variant:
- importing invoices from the ERP,
- importing credit limits,
- importing stock levels,
- importing customer payment terms,
- importing delivery routes from the ERP,
- a new import of the customer's address book,
- splitting made-to-measure items (e.g. elements cut from a configurator) into ERP document lines,
- complaint orders passed to the ERP with a priority code.
Does Hummerce integrate with BPSC (Impuls EVO) ERP?
Yes, in two variants. The B2B variant covers items, price lists, customer accounts, delivery addresses, sales representatives, and orders with their statuses. The retail store variant covers items, stock levels, orders and invoices customers can download.
How quickly does a store order reach the ERP?
In the B2B variant orders are sent to BPSC every minute, in the retail store variant every 5 minutes. When the ERP rejects an order, the store retries up to the configured attempt limit.
Do business customers see their ERP prices in the store?
Yes. The store imports price lists and customer-to-price-list assignments; a changed assignment in the ERP shows up in the store within a minute.
Does the integration fetch invoices and stock levels?
Partly. In the retail store variant stock levels are imported every 5 minutes, and customers download invoices and receipts as PDF from their account. In the B2B variant, importing invoices, credit limits, stock levels and payment terms is in progress.
Can a price be changed in the store rather than in the ERP?
Partly. A price can be added in the store, but a full price list import from the ERP will overwrite it - permanent price changes are made in the ERP.
How long does it take to launch the BPSC integration?
Implementation time is agreed individually after analysing the scope - it depends on the variant, the number of exchange areas, companies in the ERP, and customer groups and views to map.
Want to see how BPSC can work with your store? Contact the Hummerce team (in Polish).
- BPSC - the integration section in the admin panel menu.
- BPSC timestamps - manually setting the starting point of the incremental import (Update button).
- The BPSC Plugin settings group - switches for each import and the export, the order sending error limit, logging, test mode.
- The integration's scheduled tasks (names start with "BPSC -") - on the scheduled tasks list.
- On the order - the ERP sending flag.
- Retail store variant: the Impuls settings group (switches for item, stock and order exchange, maximum number of order sending attempts) and scheduled tasks with names starting with "Impuls -".
¶ REST API and MCP
The integration works through scheduled tasks and the admin panel.
The main settings of the BPSC Plugin group (B2B variant):
| Setting |
Purpose |
| Enable ... import task / Enable order export task |
A separate switch for each type of exchange |
| Error limit for sending orders |
How many times the store retries sending an order before flagging an error |
| Default delivery country |
Country assumed for addresses without a country |
| Send welcome email to imported customers |
Welcome e-mail for accounts created from the ERP |
| Set item as buyable while importing, Set item as available while importing |
Whether a new item from the ERP goes on sale immediately |
| Enable request logging, extended logging |
Diagnostics of the ERP exchange |
| Use mock |
Test mode without a connection to the ERP |