IdoSell + Subiekt nexo
Sync stock levels, the catalogue and orders between Subiekt nexo and IdoSell. One stock level across every channel, with no file exports and no coding.
What you get
Warehouse and order sync for the IdoSell + Subiekt nexo pairing
Two-way exchange with IdoSell
We pull orders from IdoSell through the API and send warehouse stock the other way, with no spreadsheets in between.
Stock straight from nexo
The agent reads stock, the catalogue, contacts and orders straight from the nexo database and refreshes them every 15 minutes by default. You also see the sales invoices issued in nexo, but we create no documents ourselves. You export no files and retype nothing.
One stock level across every channel
The warehouse in your ERP is the source of truth, and NavyFlame pushes that same stock level out to every connected sales channel, with no spreadsheets and no manual corrections.
Orders in one place
Orders from every channel land in one list in NavyFlame, so you fulfil them in a single panel no matter where they came from.
Your data stays with you
The agent runs on your own server and connects outbound. You never expose the ERP database to the internet and you open no ports.
How do I connect IdoSell to Subiekt nexo?
Install the agent next to nexo
Generate a token in the panel, unpack the agent on a machine with access to the nexo database and install it as a Windows service. A read-only SQL account is enough.
Connect your IdoSell store
Generate API access in the IdoSell panel and link the account to NavyFlame.
Match the catalogue to the channel
Link products from Subiekt nexo to listings on IdoSell and choose which stock levels get pushed out.
Switch the sync on
From now on a stock level changed in Subiekt nexo updates on IdoSell automatically, and orders land in one list in NavyFlame.
Why this integration?
IdoSell (formerly IAI-Shop) is a capable Polish e-commerce platform, and NavyFlame exchanges orders and warehouse stock with it through its API. Subiekt nexo keeps the warehouse and the catalogue on site, and the NavyFlame agent reads the nexo database read-only and connects outbound, so the database never has to be visible from the internet. NavyFlame joins the two sides: it pulls stock levels and the catalogue from Subiekt nexo, pushes them out to IdoSell and gathers orders into one list. Writing paid orders back to nexo as a ZK sales order is something we set up with you separately, because it needs Sfera from the nexo PRO edition. This integration does not issue invoices, that is what a separate integration with an accounting system is for.
Frequently asked questions
In NavyFlame you install an agent next to Subiekt nexo, connect your IdoSell account, link products to listings and switch the sync on. From that moment stock and the catalogue flow from Subiekt nexo to IdoSell, and orders come back into one shared list.
The Subiekt nexo integration does not create them. It reads stock, the catalogue, contacts, orders and the sales invoices issued in nexo, but writes nothing to the books, neither invoices nor receipts. Issuing is handled by a separate integration with an accounting system (wFirma, inFakt, Fakturownia, iFirma), which you can switch on alongside.
Not for syncing data from nexo into NavyFlame. The agent reads the nexo database with a read-only SQL account. Sfera nexo, available in Subiekt nexo PRO, is needed only once you switch on writing orders from NavyFlame back into nexo.
The integration runs one way, from nexo into NavyFlame. Writing paid orders back into nexo as a ZK, a customer order, is switched on separately at your request, because it needs Sfera from the nexo PRO edition. Nothing goes into the books either way.
Both agents can run side by side during the move, because the token is separate for each system. Write-back works for one system at a time, though: switching it on for nexo moves it away from GT and covers orders paid from that moment on.
NavyFlame pauses the automatic stock updates on your sales channels and sends a notification, so it never pushes out stock levels that a fresh read from nexo has not confirmed. Manual sync stays available, and the automation resumes on its own after the first successful read.