XML and CSV import for PrestaShop: preparing catalogue automation

A reliable importer is more than a one-off file upload. It must recognise the same product on later runs, update only selected fields and leave a clear report. This lets the catalogue grow without manually copying a supplier's offer every day.

When this matters

  • the supplier regularly changes prices and availability
  • the file contains its own identifiers, categories and variants
  • some shop content must remain under editorial control

How to approach the implementation

  1. Choose a stable identifier such as SKU, EAN or supplier code.
  2. Map categories, taxes, manufacturers and attributes.
  3. Define separate rules for creating and updating products.
  4. Run a small test file and review the error report.
  5. Set a recurring schedule only after acceptance.

How to assess the result

The test should cover the standard case and at least one exception. The team then knows both that the feature works and how it behaves with incomplete data or an interrupted process.

Checks before going live

  • back up the settings or files that will change
  • test both a customer account and a guest session
  • check the cart, order flow and email messages
  • clear the relevant cache after the change

Apply the change in a test shop first, then run the complete scenario on desktop and mobile. Record the settings and the test result so that later updates can be compared with the same baseline.

Next guide

WebP images in PrestaShop: smaller files without losing quality control

Comments (0)

No comments yet.
Product added to wishlist