ERP and databases
InsERT
Subiekt, Rewizor, Gratyfikant
We provide service and support for InsERT software. We help with problems, deployments, migrations and day-to-day use of Subiekt, including where the manual is not enough: the MS SQL database, Sfera extensions, non-standard reports and outages.
What we do with InsERT systems
We work with Subiekt GT and Subiekt nexo, as well as Rewizor and Gratyfikant. Requests usually fall into four types: deployments in a new company, migrations between versions, extensions with features beyond the standard, and repairs when something has stopped working.
Outages are the most urgent and can often be fixed quickly if someone has access to the database and knows where to look. Common causes are a full disk, an index damaged after a sudden server shutdown and an update that did not finish.
- Deployment and configuration from scratch, with import of opening data
- Migrations from Subiekt GT to nexo and between versions
- Configuration of documents, warehouses, permissions and price lists
- Reports and summaries the system does not offer as standard
- Integrations with online shops and sales platforms
- Care of the MS SQL database the system runs on
- Emergency support outside working hours
Extensions in Sfera
Sfera is a programming layer that lets you extend Subiekt with features written for a specific company. With it, the system can be adapted to the way the company works, instead of working around its limitations.
Most often we use it for repetitive tasks: issuing documents automatically according to rules, importing orders from external sources, exports in the format a specific trade partner requires, and checking data before it is saved.
We write extensions without modifying the system's tables directly, because code that changes them may stop working after the next program update.
We check whether the feature you need already exists in the system under another name. Much of what Subiekt can do is hidden in its configuration, and setting up an existing option costs less than writing an extension.
Subiekt and your online shop
A common situation: someone retypes shop orders into Subiekt by hand, and stock levels drift apart after the first busy day of sales.
The integration works both ways. Orders and customer data go into Subiekt, while stock levels, prices, photos and descriptions go to the shop. We agree the scope individually, because not every company wants to synchronise everything.
The most work goes into setting the rules for exceptions: what to do when a product runs out while an order is being placed, how to handle partly fulfilled orders and what should happen with a return. These rules decide whether the integration will work without manual fixes.
We write more about the connections themselves under ERP and online shop integrations.
The MS SQL database behind Subiekt
Subiekt runs on MS SQL, and that is usually where slowdowns after years of use come from. The database grows with every document, and archiving and maintenance are often not set up, because the program works, after all.
After a few years the typical symptoms appear: the document list opens with a delay, annual reports take tens of minutes and a stocktake stops work for hours. That is when someone in the company suggests buying a new computer, even though the cause lies in the database.
With requests like these we archive old documents to a separate database, rebuild indexes and set up a backup plan. We describe the details under slimming down databases.
A Subiekt outage that stops sales
An outage of the sales system stops sales immediately: you cannot issue a document, release goods or check stock. We handle such requests as a priority, also outside standard hours.
The first step is to secure the current state before anyone starts repairing. Repair attempts on the original, without a copy, can turn a minor failure into data loss.
They always find a solution. Professional approach and fast help, I highly recommend them!
Who we work for
A typical client is a trading or manufacturing company with anywhere from a few to several dozen workstations, which has used Subiekt for years and is starting to feel its limits.
We also advise companies that are still choosing a system and comparing InsERT with other software. We tell you plainly when Subiekt is a good choice and when another system will work better. The first consultation is free and there is no obligation.
Migration from Subiekt GT to nexo
This is a common decision in companies that have used GT for a long time. Nexo is a newer line with a different architecture and different options for extension. Migration means moving data between two different systems, so it works differently from an ordinary update.
Item records, customers, warehouses and settlements are transferred. What does not transfer automatically is everything the company has built around GT: custom reports, Sfera extensions and shop integrations. Each of these has to be quoted separately, and they usually decide the cost of the project.
That is why we take stock before the migration: what runs around the system, who uses it and what needs to be rebuilt in nexo. Without this, the migration can succeed technically, and then on Monday it turns out you cannot issue a document the way the company always has.
KSeF and e-invoices in Subiekt
An invoice sent to KSeF (Poland's national e-invoicing system) cannot be corrected the way it can in the program: it has been assigned a number, so you have to issue a correcting invoice. That is why we check data that never bothered anyone before: customers' tax IDs (NIP), units of measure, VAT rates on item records and the way discounts are described.
On the program side we configure access to KSeF with permissions for the people who issue documents, and we run a full test in the test environment. We switch on live invoicing only after the test, because in the test environment a configuration error does not cost anything yet.
We also check invoices issued outside Subiekt, in the online shop and on Allegro, if the shop is integrated. They have to go to KSeF too, and that is exactly where gaps in numbering easily appear.
If you are on a version from a few years ago, we check whether it supports KSeF. If it does not, you need an update or a migration, which we plan so that invoicing is not interrupted.
Working together
How we work together, step by step
Diagnosis
We check the system version, the state of the database and what gets in the way of daily work.
Plan and priorities
We decide what to fix straight away and what to schedule. Securing the data comes first.
Implementation
Work in maintenance windows, with a backup and a rollback plan.
Care
Ongoing support with a defined response time, also outside working hours.
Questions
Frequently asked questions
No, we provide service and support for InsERT software. We help with problems, deployments, migrations and day-to-day support. Licences are bought from an authorised InsERT partner, and we help you arrange the purchase.
Not always. GT still works and serves many companies well. Migration makes sense when the company needs features only available in nexo or plans growth that GT will start to hold back.
Yes, in whatever we deploy. For larger deployments training is part of the project, because without it the team starts working around even a well-configured system.
Mainly remotely. We come on site when the matter requires it, for example when setting up new workstations, in the Lublin region (Lubelskie Province) and in Warsaw. Travel outside Lublin is charged and agreed individually.
Related services
What else may be useful
Your city
InsERT (Subiekt, Rewizor, Gratyfikant) in your city
For each of these cities we have a separate page describing the local market and how we work with companies there.
Tell us what is happening with your Subiekt
Give us the system version and describe the problem. In an emergency, call us: 24/7 emergency support is available.