PrestaShop and WAPRO Mag integration
Connecting the store with WAPRO Mag: product records, stock, prices, orders and sales documents, with support for multiple warehouses and price lists.
Integrating PrestaShop with WAPRO Mag moves product records, stock levels and price lists to the store, and orders back as trade documents. WAPRO Mag runs on an MS SQL database, usually inside the company network, so the connector runs on the client’s side and communicates with the store through the PrestaShop API.
What the synchronisation covers
- Item records: names, SKUs, barcodes, units, VAT, product groups.
- Stock split by warehouse, plus reservations resulting from unfulfilled documents.
- Price lists and discounts, including prices assigned to customers in B2B sales.
- Store orders saved as a customer order, an invoice or a receipt.
- Customer records with invoicing details.
- Fulfilment statuses and tracking numbers returned to the store.
How the connection works
The scope of programmatic access to WAPRO Mag depends on the version and the modules purchased – in newer releases Asseco provides an API alongside file exchange and B2B mechanisms. The first step of the implementation is therefore to establish what your installation actually offers, rather than assuming up front which way the data will flow.
Whichever route is chosen, the connector sends only changes, queues operations when the connection is down and keeps a log that lets you reconstruct what happened to a specific order.
Where these implementations usually go wrong
- Messy product records. Missing EAN codes and inconsistent units of measure block automatic product mapping.
- Variants. Sizes kept as separate items need a rule for merging them into one store product page.
- Several warehouses. You need to decide whether the store sells from all of them or from one, and what happens when an order spans both.
- Returns and corrections. Without an agreed correction flow, the inventory drifts after the first larger return.
What you get
- A data flow map and an agreed source of truth for every field.
- A connector with a queue, retries and a readable log.
- Notifications when synchronisation stops.
- Documentation and a repository – someone else can take over maintenance.
Frequently asked questions
We have an older version of WAPRO. Is integration possible?
Usually yes, but by a different route than in current versions and with less that can be written automatically. It is one of the first things I check when quoting.
Will stock be updated in real time?
With a locally run system – not literally. A realistic goal is a delay of a few to a dozen or so minutes, plus a mechanism that blocks sales of items below a safety stock level.
Will you also move images and descriptions?
It can be done, but I usually advise against it. Descriptions and images are better managed in the store, because that is where they are edited for search engines, and syncing from the inventory system can overwrite them with a technical name.
Tell me which version of WAPRO you use – I will check the available data exchange routes before I quote anything.