Primavera · Stock · Orders · Catalogue
Integration between your online store and Primavera
Primavera is the management system of many companies in Portugal, holding the catalogue, stock and invoicing. We connect Primavera to the store and catalogue through the integration API available for Primavera, and design each connection around the company's process, so everything works from that data instead of duplicating it.

The problem this solves
When the store and Primavera do not talk, the team spends the day bridging the two by hand, and every manual step is a chance to get it wrong.
- Online orders entered by hand into Primavera
- Stock differences between what the store shows and what exists
- Price changes that only reach the store days later
- Invoicing piling up to be handled in batches

What data starts flowing
Primavera stays the central system; the store becomes another channel fed by it, within what the integration API allows. It works with PrestaShop, Magento, WooCommerce or custom-built stores.
- From Primavera to the store: items, prices, stock and commercial terms
- From the store to Primavera: complete orders, with customer and shipping
- Customers created and maintained without duplicates
- Documents issued in Primavera from online sales

How we handle the connection
What flows in each project is set during the assessment, based on what the system lets us read and write. When the connection goes through another company's API, that is written into the proposal.
- Assessment of what the API exposes in your case
- A log of every operation
- Alerts when the connection stops responding
- Integration maintenance after go-live

How often it syncs
It depends on each company's infrastructure and is configured per project. For example: stock every 5 minutes, master data every 15 minutes and other data hourly or a few times a day.
- Frequency set per type of data, not the same for everything
- Adjusted to the capacity of the company's ERP and server
- Reviewed whenever the operation needs it
If the connection fails
An integration that stops without anyone noticing is the worst case. That is why every connection is designed to fail safely.
- A record of every operation, to know what went through and what did not
- Automatic reprocessing, without duplicating orders or documents
- Alerts to the team when the connection stops responding
- Fixes and evolution of the integration by the same team that built it
Related case studies
Want to connect your ERP to the rest of the business?
Tell us which management system you use and what needs connecting (store, warehouse, marketplaces) and we will explain how we would do it.