The Hummerce integration with IFS ERP connects a B2B store to IFS through the company's data bus - the integration layer that sits between the ERP and other systems. Orders flow from Hummerce to IFS automatically, while items with base prices, stock levels, customers, order statuses and invoices come back to the store without manual re-entry.
Last updated: 2026-10-09.
¶ Benefits and use cases
- The store fits the company's architecture - Hummerce uses the same data bus as the company's other systems instead of a separate, direct connection to the ERP. The IT department stays in control of what is exposed and how.
- Orders in IFS without re-typing - an order placed in the store reaches the ERP within minutes.
- Up-to-date stock levels - item availability is refreshed every 5 minutes, so business customers order what is actually in the warehouse.
- Customers can follow their orders - statuses, details and order confirmations from IFS are available in the store.
- ERP invoices in the store - invoices from IFS reach the store automatically, every 5 minutes.
- Base prices from the ERP, promotions in the store - item base prices come from IFS, and the store applies its own product promotions and cart promotions on top of them.
- Business customers from the ERP - customer (account) data is imported from IFS; a single customer can also be fetched from the ERP by tax ID (NIP).
- Hummerce does not connect to the IFS database directly. It calls methods exposed by the company's data bus, in JSON format, over HTTP.
- Each type of exchange is a separate scheduled task with its own schedule.
- Imports of items, stock, customers and invoices are incremental - the store fetches only records changed since the previous import. A full item import can be run on demand.
| Data |
Direction |
Frequency |
| Orders |
store -> IFS |
every 5 minutes |
| Stock levels |
IFS -> store |
every 5 minutes |
| Order statuses |
IFS -> store |
every 5 minutes |
| Order details |
IFS -> store |
every 5 minutes |
| Order confirmations (files) |
IFS -> store |
every 5 minutes |
| Invoices |
IFS -> store |
every 5 minutes |
| Customers (accounts) |
IFS -> store |
every hour |
| Items with base prices |
IFS -> store |
every 6 hours |
- Customer accounts from IFS are imported into the store on a schedule.
- Store staff can fetch a specific customer's data from IFS on demand - a lookup by tax ID (NIP).
- Item base prices come from IFS. The store applies product and cart promotion rules on top of them - see B2B sales in Hummerce.
- Access to the data bus is protected by an access key configured in the admin panel; the key is masked in the integration logs.
- A company data bus with methods exposing IFS data (items, stock, customers, orders, statuses, invoices) - prepared by the customer's IT department or their IFS partner.
- Access to the data bus for the store - service address and credentials.
- Business accounts and B2B pricing rules in Hummerce - B2B sales, price lists.
- The integration requires implementation - it does not start by itself after an update. A typical rollout covers:
- agreeing the list of methods and the data format with the data bus team,
- configuring access to the data bus in the admin panel,
- mapping order statuses, units and customer groups between IFS and the store,
- the first full import of items and customers, end-to-end order tests.
- Implementation time is agreed individually after analysing the scope.
- What the time depends on:
- which methods the data bus exposes and whether they need extending on the customer's side,
- the number of exchange areas and the data volume,
- the scope of mappings between IFS and the store.
- The scope of the exchange is defined by the methods the data bus exposes - a new type of data requires changes on both the data bus side and the store side.
- Item base prices come from IFS; product and cart promotions are set up in the store.
- Credit limits, payment terms and delivery addresses are not synchronised with IFS.
- The store polls the data bus on a schedule - the delay ranges from 5 minutes (orders, stock) to 6 hours (full item data).
- We do not verify the task for legal compliance (e.g. licences for supplied materials, GDPR, store terms and conditions).
- Importing individual prices and customer trade terms from IFS, if the data bus exposes them.
- Customer credit limits and payment terms from the ERP.
- Shorter import periods, or exchange initiated by the data bus instead of scheduled polling.
Does Hummerce integrate with IFS ERP?
Yes. The integration works through the company's data bus and covers orders, items, stock levels, customers, order statuses and details, confirmations and invoices.
Does the store have to connect directly to the IFS database?
No. Hummerce uses methods exposed by the company's data bus - the IT department decides which data is available to the store.
How quickly does a store order reach IFS?
Orders are sent to IFS every 5 minutes; statuses, stock levels and invoices come back at the same frequency.
Do prices come from IFS?
Yes, item base prices. The store applies product and cart promotion rules on top of them, set up in the Hummerce admin panel.
Will the IFS integration work in any company running IFS?
Partly. The integration needs a data bus with methods for the store; if the company does not have one, it has to be prepared, or the integration adapted to the available interface.
How long does it take to launch the IFS integration?
Implementation time is agreed individually after analysing the scope - it depends mainly on which methods the data bus exposes.
Want to see how IFS can work with your B2B store? Contact the Hummerce team (in Polish).
- IFS integration screen - on-demand import of a customer's data from IFS.
- The integration's scheduled tasks - on the scheduled tasks list, each with its own schedule.
¶ REST API and MCP
The integration works through scheduled tasks and the admin panel - it has no store REST API endpoints or MCP tools of its own.
Integration settings in the admin panel: data bus service address, access key and login credentials. The values are provided by the data bus team during implementation.