Syncing your PrestaShop catalogue with Amazon, Cdiscount or eBay
Every marketplace requires its own connector module and its own seller account: there’s no single solution that talks to Amazon, Cdiscount and eBay at once. The trickiest part isn’t the initial catalogue upload, it’s two-way stock synchronisation, without which a sale on the marketplace may never flow back to PrestaShop.
What each marketplace requires
Amazon, Cdiscount and eBay each run on their own PrestaShop module, their own API credentials, and a seller account opened directly with the marketplace. Setting one up gets you nowhere with the others: each integration is prepared and tested separately.
Most of these marketplaces require a valid EAN or GTIN code per product, entered in the dedicated field on the product record, before they’ll accept a listing. A catalogue that has only ever sold direct often has no EAN codes at all, which blocks the upload until those codes are filled in.
Beyond the EAN, each marketplace also imposes its own product categorisation, its own mandatory fields and sometimes specific image rules, different from PrestaShop’s own catalogue. Mapping the internal catalogue to each marketplace’s requirements is part of the initial setup, before continuous synchronisation even comes into play.
Why stock synchronisation is delicate
- A sale on the marketplace needs to reduce PrestaShop’s stock quickly, otherwise the same product can be sold twice across two different channels.
- Sync frequency depends on the module and its configuration: a sync that runs too infrequently raises the risk of overselling a low-stock product.
- A poorly installed marketplace module, or one conflicting with another module, can go as far as locking access to the back office entirely: testing before going live isn’t an unnecessary precaution.
Related pages
-
Exporting the catalogue or orders to CSV
The foundation of a clean catalogue to export or connect, before any marketplace sync.
-
Custom PrestaShop module development
For an EAN integration or a particular sync flow the marketplace module doesn’t cover.
-
PrestaShop back office inaccessible
When a poorly installed third-party module locks the back office rather than just the sync.
Describe your need in one minute
A few targeted questions so I can reply with an estimate rather than another questionnaire.