Store Integration with Subiekt GT, nexo and Comarch Optima
Key facts
- We connect WooCommerce with Subiekt GT (through the Sfera licence), Subiekt nexo and nexo PRO and Comarch ERP Optima (through the API).
- As a rough guide: connecting a store to Subiekt or Comarch ERP Optima is PLN 8,000-20,000 net. The Sfera licence for Subiekt GT is a separate cost on your side. Support after go-live starts at PLN 300 net per month.
- Subiekt GT needs a separate Sfera licence from InsERT and you have to add it to the rollout budget. Subiekt nexo and Comarch Optima do not need it.
- Scope: product records, stock from one or several warehouses, retail and B2B price lists, orders as ZK (sales order), FS (sales invoice) or a receipt, customer records, payment reconciliation and credit notes after a return.
- A typical rollout takes 3-6 weeks, counting from the moment the product records in the trading system are cleaned up.
- For every type of data we set one source of truth. Two-way sync of everything is the simplest way to get conflicts.
Subiekt GT, Subiekt nexo and Comarch ERP Optima hold what matters most in a company: product records, stock, prices and sales documents. As long as the store does not know about it, somebody has to retype orders by hand, and the warehouse and the website show two different truths.
We connect WooCommerce with Subiekt and Optima so that a product is created once, stock goes down automatically, and every order produces the right document – ZK (sales order), FS (sales invoice) or a receipt – with no copying of data.


What has to be settled before integrating with Subiekt or Optima?
The system version. Subiekt GT needs the Sfera licence before anything can be automated. Subiekt nexo and Comarch Optima have their own APIs and work differently. That drives both the licence cost and the way the integration is built.
The direction of the data. Usually the ERP is the source of stock and prices, and the store is the source of orders. But if descriptions and photos live in WooCommerce, the store stays the owner of the content and we sync only what really has to move.
Documents. We settle what is created after a paid order, who issues the invoice, how documents are numbered and what happens on a return. This point usually surfaces only after launch, so we ask about it at the start.
The role of BaseLinker. Sometimes it pays to put it in the middle as a packing and marketplace layer, sometimes it is a needless part. We advise after the analysis, not by default.
How does the rollout work, step by step?
Data audit
We look at product records, units, VAT rates and price lists. Dirty data in the ERP is the most common reason integrations fail, so we clean it up before the start.
Connection and mapping
We set up the exchange through Sfera or the API, map fields, prices and warehouses, and run the sync on test data.
Documents and handover
We check the full path: order, stock reservation, sales document, shipment, return. Only then do we switch production on.
What does the integration cover?
Product records – from the ERP to the store, together with SKU, EAN codes, units and VAT rates.
Stock levels – from one or several warehouses, with reservation rules and a minimum stock level.
Price lists – retail prices, B2B prices for logged-in customers, promotions and discount thresholds.
Orders – from the store to the ERP as ZK (sales order), FS (sales invoice) or a receipt, with customer data and the tax ID.
Customers – creating and updating records from the data in the order.
Payments and returns – reconciling payments and issuing credit notes after goods come back.
Which systems do we work with?
Subiekt GT – exchange through Sfera, also in a setup with BaseLinker as the middle layer.
Subiekt nexo and nexo PRO – integration through the API, with support for several warehouses and individual prices.
Comarch ERP Optima – product records, stock, price lists and trading documents.
WooCommerce and PrestaShop – on the store side, together with B2B and wholesale plugins.
BaseLinker – when marketplaces and bulk packing are in play.
wFirma and other accounting systems – if invoicing sits outside the ERP.
Frequently asked questions
How much does a Subiekt or Optima integration cost?
Roughly PLN 8,000-20,000 net, depending on the number of warehouses, B2B price lists and how your document flow works. The Sfera licence for Subiekt GT has to be added to the budget and is bought separately from InsERT. Support after go-live starts at PLN 300 net per month. The quote follows a free pre-implementation analysis.
Do I need the Sfera licence for Subiekt GT?
Yes, if the integration is to write anything on the Subiekt GT side. Sfera is a separate InsERT licence and you have to add it to the rollout budget. Subiekt nexo and Comarch Optima have their own APIs and do not need it.
Does the data have to flow both ways?
Not always, and usually it is not worth it. The more fields synced two ways, the more conflicts. We set one source of truth for each type of data and stick to that rule.
What about products that are not in the ERP?
We leave them in the store as manually managed items and exclude them from the sync. That is common for services, delivery and marketing items.
How long does such a rollout take?
Most often 3-6 weeks, counting from the moment the product records are cleaned up. We give the date and the price after a pre-implementation analysis, which is free.
Related: BaseLinker integration, KSeF in an online store, Allegro integration, e-commerce solutions.
Write to biuro@web-systems.pl or call: +48 501 231 448. A quote for a specific rollout is free.
What do they say about us?
Jason McNeil
Daniel Korhonen
Joanna Kowalczyk
Małgosia Grobelna
www.inspire.com.pl
Michal Masłowski
Jacek Jurczyński
Michał Gałaj
holdentalesklep.eu
Daniel Tael
xlash.com
Ben Bodude
keyspireprograms.com
Mike Weiss
www.clientengagementacademy.com