PrestaShop and Allegro integration
Listing offers, importing orders and syncing stock between the store and Allegro - through the official API, with category parameter mapping.
Integrating PrestaShop with Allegro covers three things: listing and updating offers based on the store catalogue, importing orders into the store and keeping shared stock levels. Allegro provides a REST API with OAuth 2.0 authorisation and a sandbox, so the whole thing can be built without intermediaries.
What the integration covers
- Listing offers from store product pages, including images and parameters.
- Updating prices and stock in both directions, with one agreed source of truth.
- Importing orders and shipping details as PrestaShop orders.
- Sending tracking numbers and statuses back to Allegro.
- Invoice handling in line with the company’s document flow.
The hardest part: category parameters
Allegro requires an offer to have all the mandatory parameters for its category, and these differ for every category and change from time to time. A store catalogue rarely keeps them in the same form. Mapping PrestaShop features to Allegro parameters – including a rule for what to do when a value is missing – is usually a bigger part of the implementation than the API connection itself.
The second typical surprise is rate limits. A bulk update of several thousand offers needs queuing and spreading over time, not a loop over the catalogue.
Where these implementations usually go wrong
- Shared stock. The last item sold in both channels at once is the classic scenario. You need a buffer or a lock.
- Prices. Allegro’s commission and the delivery cost mean the price can rarely be a copy of the store price – you need a conversion rule.
- Returns and complaints. The flow on Allegro’s side differs from the store’s and has to be reflected in the statuses.
- Buyer data. The scope of data Allegro passes on has its own rules – a store account created automatically must take that into account.
- Token expiry. An integration that doesn’t handle refreshing its authorisation stops working at the least convenient moment.
Ready-made module or custom integration
For a typical catalogue and a few hundred offers, a ready-made module or BaseLinker is enough and cheaper. A custom integration is worth writing when offers are built from unusual data, sales run in many price variants or the company has its own document flow that a panel can’t handle. We make this decision before implementation – it’s a typical question at the consulting stage.
Frequently asked questions
Can offers be listed automatically for the whole catalogue?
Technically yes, but in practice it is rarely worth it. Allegro categories and mandatory parameters require decisions for most products. It makes more sense to automate updating offers than listing them for the first time.
Will Allegro orders reach my ERP?
Yes, if the store is already integrated with the system – then an Allegro order comes in the same way as a store order. It is the simplest setup and the one I usually recommend.
I have a module, but offers keep going out of sync. Do you fix that?
Yes. I start by checking which system overwrites which and whether the problem is the order of synchronisation or missing error handling in the module.
Tell me how many offers you run and where their parameters come from – I will tell you whether a ready-made tool is enough in your case.