¶ Subiekt GT - orders and invoices integration (e-mo)

The Hummerce integration with InsERT Subiekt GT passes orders from the shop to the ERP through the e-mo S2S connector and sends the sales invoice back as a PDF, which the customer downloads in the order details. Staff do not re-key orders into Subiekt, and the customer gets the invoice without it being emailed.

Last updated: 2026-10-16.

¶ Benefits and use cases

Orders in Subiekt without re-keying - an order from the shop goes to Subiekt GT together with customer and delivery data, and the contractor is created in the ERP automatically.
The invoice returns to the customer - the sales invoice issued in Subiekt is available in the shop, in the order details, to download as a PDF.
Control over the moment of transfer - orders reach the ERP in a chosen status, e.g. after confirmation by staff.
A ready-made connector instead of custom programming - the connection to Subiekt is provided by the S2S application from e-mo, while Hummerce exposes the standard REST API.
Sales from many points - in a shop with several views, the connector fetches orders from each of them.

¶ How it works

¶ Who does what

The shop does not send anything to Subiekt on its own. e-mo S2S is an intermediary program installed on the customer's side, on the computer or server running Subiekt GT. It queries the Hummerce REST API itself, fetches orders in the chosen status, creates them in Subiekt, and then sends the invoice back to the order. S2S is a product of an external vendor - e-mo, not Hummerce.

¶ Order flow

The customer places an order in the shop.
Staff set the order to the status from which orders go to the ERP (e.g. "In progress").
The connector fetches the order through the REST API and creates the documents in Subiekt GT.
Subiekt issues a sales invoice, and the connector sends it back to the order in the shop as a PDF file.
The customer downloads the invoice in the order details in their account.

¶ Item matching

Items are matched by EAN code or by symbol:

if the item symbol in the shop is a valid EAN-13 code (with a check digit), Subiekt looks the item up by barcode,
otherwise it looks it up by symbol,
an item it cannot find may be created in Subiekt by the connector together with the order - this is a setting on the connector side.

¶ What this route does not synchronize

Items, prices and stock levels are not synchronized by this integration - orders go from the shop to Subiekt, and invoices go the other way.

¶ Version

The integration uses the standard Hummerce REST API, in which orders, views and order properties are available in current platform versions.

¶ Dependencies

Subiekt GT with an active Sfera (an InsERT license) - the connector logs in to Subiekt through Sfera; without it, document export does not work.
The e-mo S2S application installed next to Subiekt, with its own license and implementation on the e-mo side.
REST API enabled in the shop, with a dedicated role and an API user account.
Valid item symbols or EAN codes - a condition for matching order lines in Subiekt.

¶ 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 order and order line properties (including the EAN code) visible in the API,
- configuring the invoice fields for the customer and their display in the customer account,
- end-to-end tests: order, transfer to Subiekt, invoice in the shop.
On the customer and e-mo side: installing and configuring S2S next to Subiekt, connecting it to the shop, and licenses.
We set the implementation time individually after analyzing the scope - it depends on the number of shop views, how well item symbols match Subiekt, and the scope of work on the e-mo side.

¶ Limitations

The scope is orders and invoices - items, prices and stock levels are not synchronized by this integration.
The invoice returns to the shop as a PDF file. Documents other than invoices are not supported by the connector.
An order line reaches Subiekt only when the item can be matched by a valid EAN-13 or by symbol.
The connector is a product of an external vendor - availability, versions and fixes depend on e-mo, and changes on the S2S side require updating the software next to Subiekt.
Subiekt GT must have an active Sfera.
The exchange works on a pull model: an API outage stops the flow of orders to the ERP, so we recommend monitoring API availability.
The order status from which an order goes to the ERP depends on the S2S configuration - with a different configuration the connector may fetch all orders.
We do not verify the task for legal compliance (e.g. accounting, JPK and VAT in the ERP, shop terms and conditions).

¶ Frequently asked questions

Does Hummerce connect to Subiekt GT?
Yes. Hummerce connects to Subiekt GT through the e-mo S2S connector and the REST API - orders go to Subiekt, and the invoice returns to the shop.

Is Sfera required?
Yes. The connector logs in to Subiekt GT through Sfera, so a Sfera license must be active.

Can the customer download the invoice in the shop?
Yes. The sales invoice from Subiekt returns to the order as a PDF and is available in its details in the customer account.

Does the shop synchronize items, prices and stock with Subiekt?
No. This integration handles orders and invoices - it matches items by EAN code or symbol, while their data, prices and stock come from another source.

How are items from an order matched to items in Subiekt?
By EAN code or by symbol. A valid EAN-13 is searched as a barcode, any other symbol as an item symbol.

How long does it take to launch the Subiekt GT integration?
We set the time individually after analyzing the scope. It depends on the number of shop views, how well item symbols match, and the scope of work on S2S.

REST API - integration with external systems - data scope, permissions and API diagnostics.
Integrations - catalog - other ERP, payment, delivery and marketplace integrations.
Sage Symfonia - ERP integration via REST API - 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: Subiekt GT integration, Integrations.

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

¶ Configuration details

¶ Access in the admin panel

API role and user - an account with API permissions, with access to the views the connector is to fetch orders from. The REST API module must be enabled in the shop.
Location of order parameters visible in the API - order and order line properties are assigned to it, including the line EAN code and the invoice fields: file content, number and file name (Parameters and locations).
Customer invoice - the file sent back from the ERP is stored with the order and made available to the customer in the order details.
Diagnostics - the Status -> REST API diagnostics screen shows what the connector sent and what the shop replied.

¶ REST API and MCP

The connector uses the REST API: it reads the list of views and orders, and adds the invoice to the order through a partial update of properties. The shop API address and credentials are set during implementation.

¶ Parameters

Data type	Object	Purpose
EAN code	Order line	Item matching in Subiekt, copied from the item to the order line
Invoice content (PDF)	Order	Invoice file sent back by the connector, stored as a file with the order
Invoice number	Order	Document number from Subiekt
Invoice file name	Order	PDF file name visible to the customer
Customer invoice	Order	File visible in the customer account