WAPRO Mag and a storewithout middleware.How it works.
The warehouse stays the source of truth, the store reads it straight from the database, and orders come back as ZO documents. No agent installed at your site and no third system to pay for and babysit.
The most common setup in Polish e-commerce with an ERP looks like this: the store has its own database, WAPRO Mag has its own, and between them sits a separately paid integrator that moves data every so often. Every link means delays and room for error. In Torveo the WAPRO Mag integration is part of the platform: the store connects to the warehouse database directly, and writes on the ERP side go through the vendor's official procedures.
A direct connection to the database
Torveo connects to the Microsoft SQL Server database that WAPRO Mag runs on. You enter the server credentials in the store panel and they are stored encrypted. Orders are written through Asseco's official stored procedures, the same ones the program itself uses. The integration never writes to the tables by shortcut.
The only technical requirement: the SQL server must be reachable over the network for the platform, in practice usually through a VPN. You install no agent or connector on your side and pay no middleman between the store and the warehouse.
What flows, and in which direction
From the warehouse to the store: catalogue indexes (the catalogue number becomes the SKU), EAN codes, descriptions, photos, per-warehouse stock counted as quantity minus reservations, and prices. There are two price levels: a retail level for the store and a separate wholesale level that feeds the B2B price list. Promotions set in the ERP start and end with their dates.
From the store to the warehouse: an order lands in WAPRO as a ZO document, which does not touch stock until the warehouse staff fulfil it. Business partners are created in the ERP at the first order, not at every account registration. Invoices can be issued in WAPRO straight from the store order, or pulled into the store after being issued in the ERP. Always one of the two, so the same order never ends up with two invoices under different numbers.
The default scope is narrow on purpose: prices and stock sync, and nothing new appears in the catalogue without your decision. Categories are not carried over from WAPRO. Warehouse product groups rarely make a good store menu, so you assign categories in the panel before products go on sale.
Rhythm and the safety net
WAPRO Mag sends no change notifications, so the sync works by polling: you set the frequency per integration, from a few minutes for stock alone to rarer full catalogue runs. Every run leaves a report: what arrived, what sold out, where a price jumped, where wholesale came out above retail.
An order that could not be written to the ERP goes into quarantine with the reason and a retry button, while the rest of the batch keeps moving. Invoice issuing in WAPRO starts in a dry-run mode that writes nothing to the ERP until you review the results and switch it off yourself.
If your warehouse lives in WAPRO Mag, the store does not have to be a second place where you maintain the same data by hand. Stock and prices flow from the warehouse, orders come back as ZO documents, and you watch one report instead of three systems.