PrestaShop and Subiekt GT integration
Products, stock levels, prices, customers and sales documents between the store and Subiekt GT. Through Sfera, not by writing straight to the database.
Integrating PrestaShop with Subiekt GT means that products, stock levels, prices and customers flow from the inventory system to the store, and orders flow the other way – as sales documents. Subiekt GT runs locally on Windows, so the exchange happens through a connector running on the company’s side, in cycles rather than in real time.
What the synchronisation covers
- Product records: names, descriptions, EAN codes, units, VAT rates, categories.
- Stock levels – split by warehouse if the company runs several.
- Price lists, including individual prices for customer groups in B2B sales.
- Store orders saved as an order, an invoice or a receipt.
- Customers with their tax ID and invoicing details.
- Fulfilment statuses and tracking numbers returned to the store.
How the connection works
Subiekt GT has no REST interface of its own. The official route for programmatic access is Sfera for Subiekt GT – a separately licensed add-on that works as COM automation on a computer with Subiekt installed. The connector therefore runs as a Windows service at the company’s premises or on a terminal server, connects to the store via the PrestaShop API and moves data at set intervals.
Writing data directly to Subiekt’s MS SQL database, bypassing Sfera, is technically possible and regularly ends with inconsistent documents: numbering, settlements and links between documents are created in the program’s logic, not in the tables themselves. For reading stock levels this can be acceptable; for writing, it is not.
If the company works on the InsERT nexo line (Subiekt nexo), there is a .NET-based Sfera nexo, so the connector looks different, but the division of roles between the systems stays the same.
The key decision: what is the source of truth
Before writing any code we agree which system settles a dispute over a given value. Usually Subiekt is responsible for stock, purchase prices and documents, and the store for descriptions, images, SEO and marketing content. Without that split, synchronisation starts overwriting manual corrections – most often product descriptions written for search engines.
Where these implementations usually go wrong
- Product variants. In Subiekt each size is often a separate product; in the store it is one product page with combinations. Mapping this relationship is the hardest part of the implementation.
- Reservations. Stock sent to the store without taking reservations into account leads to selling goods that are no longer there.
- Bundles and kits. A bundle’s stock follows from the stock of its components and has to be calculated, not fetched.
- Lost connection. The computer running Subiekt is often switched off overnight. The connector has to queue changes and complete them when the connection returns instead of losing orders.
- Performance. A full sync of tens of thousands of records on every cycle puts load on both Subiekt and the store. A sensible integration sends only the changes.
What you get
- A data flow map: what goes where, how often and which side wins in a conflict.
- A connector that logs every operation – when there is a complaint, you can see what was sent and when.
- Error handling: retries, a queue and a notification when something didn’t go through.
- Documentation and repository access, so someone else can take over maintenance.
Frequently asked questions
Do I need a Sfera licence?
For two-way exchange – yes. Sfera is a separately licensed InsERT add-on and it provides the supported way of writing documents. Reading stock alone can be arranged differently, but then the integration stays one-way.
How often is stock synchronised?
Typically every few to a dozen or so minutes. More often only makes sense for fast-moving goods, because each cycle loads the computer running Subiekt, which is usually also used for everyday work.
I already have an integration module, it just works badly. Do you fix those?
Yes. In that case I start by finding where the data diverges and whether the cause is the connector itself or the assumptions made when configuring it. You get the result of this diagnosis whether or not you decide to continue working with me.
Can this be done without changing how we work in Subiekt?
Rarely one hundred percent. Usually the records need tidying up: filling in EAN codes, standardising units and attribute names. That is work on the company’s side, but without it the integration moves the mess instead of the data.
Describe how you work with Subiekt today and what you expect from the store – I will get back to you and we will work out whether an integration is the cheapest answer in your case.