¶ Sage Symfonia - ERP integration via REST API

The Hummerce integration with Sage Symfonia connects the shop to the ERP through the platform REST API: Symfonia sends items, prices and stock levels to the shop, and fetches orders from it and updates their statuses. The sales team works in the ERP, while the shop shows customers current offers and availability without manual data re-entry.

Last updated: 2026-10-16.

¶ Benefits and use cases

Items and prices straight from the ERP - the catalog and prices in several types (e.g. regular and wholesale) and currencies are maintained in Symfonia and flow to the shop.
Current stock levels - the ERP sends stock per warehouse, and the shop shows customers availability consistent with the warehouse.
Orders in the ERP without re-keying - Symfonia fetches new and changed orders from the shop together with customer and delivery data.
Statuses return to the shop - the ERP changes order, payment and delivery statuses, and the customer sees the change in the shop.
One API for many tasks - the same interface handles items, orders and stock, so there are no separate exchange channels for each kind of data.
A common model for ERP systems without a ready-made module - Symfonia connects the same way as other systems using the Hummerce REST API.

¶ How it works

¶ Who does what

Hummerce does not call Symfonia on its own. The ERP is the active party: an application on the Symfonia side queries the shop REST API and sends changes to it. The Symfonia side of the integration is built by the ERP implementation partner - on the Hummerce side we configure API access and the scope of visible data.

¶ What is exchanged

Data	Direction	How it works
Items and variants	ERP -> shop	Symfonia creates and updates items, including variants, producer, parameters and prices with a tax group
Prices	ERP -> shop	Prices in several types and currencies passed as item parameters
Stock levels	ERP -> shop	Symfonia sends the current stock per warehouse, not a stock change, through the warehouse and warehouse entries API
Orders	shop -> ERP	Symfonia fetches orders, also incrementally - only those changed since a given date and time
Order, payment and delivery statuses	ERP -> shop	Symfonia changes statuses, and the shop reacts as it does to a manual change in the panel, e.g. it sends a notification to the customer

¶ Frequency

The exchange frequency depends on the schedule of the application on the Symfonia side. Stock levels become visible in the shop from a few seconds to several dozen minutes after sending, depending on the shop's scheduled tasks - item availability updates when the task runs, not instantly.

¶ Which data the ERP sees

The scope of data the shop exposes through the API is set in the panel - separately for items and for orders. A parameter that has not been selected is not visible to the ERP. For an order, you can expose, among other things, customer data and the delivery address.

¶ Older XML file exchange

Hummerce also has an older Symfonia integration based on XML file exchange (items, warehouse, orders and statuses). It remains available for existing deployments, while new deployments are built on the REST API.

¶ Version

The REST API for items and orders is available from Hummerce version 2.29, and the warehouse and warehouse entries API from version 2.32.

¶ Dependencies

REST API enabled in the shop, with a dedicated role and an API user account with access to the shop views.
An integration application on the Symfonia side - built by the ERP implementation partner, not part of Hummerce.
Matching item symbols - the item symbol in the shop must match the Symfonia item master, because data is linked by it.
Warehouses and tax groups set up in the shop that the ERP refers to.

¶ Implementation

The integration requires implementation - it does not work after a shop update alone.
On the Hummerce side:
- enabling the REST API and creating the API role and account,
- selecting the item and order parameters visible in the API,
- preparing warehouses and tax groups,
- end-to-end tests: item, price, stock, order and status change.
On the ERP side: the integration application of the Symfonia implementation partner, coordinated with its scope of work.
We set the implementation time individually after analyzing the scope - it depends on the amount of exchanged data, the price types and currencies, and the readiness of the application on the ERP side.

¶ Limitations

The shop sends nothing to Symfonia on its own - no application on the ERP side, or an API outage, means no orders and stock in the ERP.
Parameters not selected in the API configuration are not visible to the ERP.
Saving an item through the API covers the full set of fields to keep - a field sent empty removes the value, e.g. the producer.
The ERP sends the stock level, not its change. Warehouse entries cannot be given custom symbols.
An order without complete customer or delivery address data may not be fetched by the ERP.
Every order edit, including through the API, may send a notification to the customer unless the parameter is excluded from notifications.
The exchange is not real-time - it depends on the schedule on the ERP side and the shop's scheduled tasks.
We do not verify the task for legal compliance (e.g. accounting and VAT in the ERP, shop terms and conditions).

¶ Frequently asked questions

Does Hummerce have a ready-made module for Sage Symfonia?
Partly. Hummerce connects to Symfonia through the REST API, and the application on the ERP side is built by the Symfonia implementation partner. An older XML file exchange also exists for existing deployments.

Does the shop send orders to Symfonia on its own?
No. Symfonia fetches orders from the shop REST API, also incrementally, only those changed since a given date.

Can the ERP change stock levels and order statuses?
Yes. Symfonia sends stock per warehouse and changes order, payment and delivery statuses, and the shop reacts as it does to a change in the panel.

How quickly do changes from Symfonia appear in the shop?
From a few seconds to several dozen minutes - it depends on the schedule on the ERP side and the shop's scheduled tasks. Item availability updates when the task runs.

How long does it take to launch the Symfonia integration?
We set the time individually after analyzing the scope. It depends on the amount of exchanged data, price types and currencies, and the readiness of the application on the ERP side.

What should I watch out for when matching items?
The item symbol in the shop must match the Symfonia item master. Changing a symbol in the shop panel breaks the data link.

REST API - integration with external systems - data scope, permissions and API diagnostics.
Integrations - catalog - other ERP, payment, delivery and marketplace integrations.
Subiekt GT - orders and invoices integration (e-mo) - another example of an ERP connected through the REST API.
Comarch ERP XL - an ERP integration with a ready-made module.
B2B and B2C in one shop - selling to businesses and individual customers on one platform.
On hummerce.com: Sage Symfonia integration, Integrations.

Would you like to see how the Sage Symfonia integration can work in your shop? Book a free demo.

¶ Configuration details

¶ Access in the admin panel

API role and user - an account with permissions for items, orders and views, with access to all views the ERP is to read from. The REST API module must be enabled in the shop.
Parameter locations - item parameters visible in the API are assigned to the itemApi location, and order parameters to the orderApi location (Parameters and locations).
Warehouses - stock from the ERP goes to warehouses set up in the shop (Warehouses).
Diagnostics - the Status -> REST API diagnostics screen shows what the ERP sent and what the shop replied.

¶ REST API and MCP

The integration uses the REST API. Incremental order retrieval relies on a modification date filter, and results can be filtered by any parameter. The shop API address and credentials are set during implementation.

¶ Parameters

Data type	Object	Purpose
Prices in several types and currencies	Item	Price types from the ERP passed as item price parameters
Producer	Item	Producer assigned by the ERP; an empty value removes the producer
Customer and delivery data	Order	Email, address, country and delivery data exposed to the ERP together with the order
Additional information	Order	Seller notes passed to the ERP