Running Subiekt nexo?The shop will come off its database.
We connect to the Subiekt nexo database and take goods, photos, warehouses and tax rates from there. The stock in the ERP stays the source of truth, and shop orders travel on: into documents and into the tools you ship with.
The product file, units, tax rates and photos come straight from the Subiekt database, with no retyping by hand.
The shop sells from the same stock your warehouse sees. Overselling stops being a matter of luck.
A sale in the shop does not end in an inbox: it flows into documents and into the tools you pack and ship with.
What comes down from the Subiekt database to the store
This list comes from the code of an implementation we run in production. Orders go onward from the store, into documents and fulfilment tools; if they should return into Subiekt itself, we will say plainly during the database review what is possible.
| Products from the records | ERP to store |
|---|---|
| Product photos | ERP to store |
| Units and VAT rates | ERP to store |
| Business partners | ERP to store |
| Warehouses and stock | ERP to store |
| Store orders onward to fulfilment | store onward |
You do not upload photos twice
Subiekt nexo keeps product photos in the same database as the catalogue. We take them from there and build the product gallery in the shop.
There is no step where you export photos to a folder and send us the package. They come in the same way as the rest of the catalogue.
- 01photos in the nexo database
- 02no export to a folder
- 03product gallery in the shop
One route, straight from the database
We connect to the Subiekt nexo MSSQL database and read records, photos, warehouses and business partners directly from it. No intermediate files, no manual exports.
From review to launch, together with you
- step 1Database review
We check the nexo version, warehouses and records. After this review you receive the implementation quote.
- step 2Access
We set up a secure connection to the database: VPN or tunnel, plus a read-permission account.
- step 3Mapping
You point to warehouses and the scope of the records: units, rates, photos. We agree where orders go after a sale.
- step 4Test on a few items
A sample product import and a test order travel the full route before the whole thing goes live.
- step 5Launch and schedule
We switch on synchronisation on a schedule matched to the size of your records.
Three things on your side. The rest is on us.
- access to the Subiekt nexo database (VPN or tunnel) and a read-permission account
- a person who knows your Subiekt configuration
- the list of warehouses the store should sell from
You receive the implementation quote after the database review. It depends on four things:
- database access and the number of warehouses
- the scope of records to map: units, rates, photos
- where orders should go after a sale
- the scope of testing before launch
We quote ERP integrations individually, after reviewing the installation, from 999 PLN net. You do not pay the cost up front: we spread it over months and add it to your subscription, and the subscription is at least 10% cheaper for the first year of the contract.
We launch the Subiekt nexo integration together with you and quote it individually, after reviewing your database.
- a review of the database and warehouses
- mapping product files, tax rates and units
- a test on a few items before the whole lot goes live
what changes day to day
Products, photos, units and rates enter the store straight from the database. Nobody copies thousands of items by hand.
The store sells from nexo warehouse stock. The same source your warehouse looks at.
A store sale does not end in a mailbox: it flows into documents and the tools you pack and ship with.