Supplier Price List Import for OpenCart 2.3, 3 and 4

Supplier Price List Import updates prices and stock in OpenCart from a file sent by the supplier — Excel, CSV or XML/YML, from your computer or by URL. There are three builds: for OpenCart 4.0.2 – 4.1.x, 3.0.2 – 3.0.5.0 and 2.3.0.x; the functionality is identical, only the package differs. The code is open, ionCube isn’t required, and no core files are changed.

Any supplier file

The module reads XLSX (ordinary Excel, no need to re-save as CSV), CSV in UTF-8 or windows-1251 with any delimiter, and also XML and YML — the format Rozetka, Prom and most Ukrainian distributors use for price feeds. The delimiter, encoding and format are detected automatically; the Excel sheet, the number of header rows, and the product tag in XML can be set manually if needed.

A price list can be uploaded as a file or given as a URL — the module then fetches it from the supplier’s site itself on every run.

Columns are detected on their own

The module reads the file’s header and finds the SKU, price and stock columns itself: it recognises “Артикул”, “Код товара”, “Цена закупочная”, “Наличие”, “vendorCode”, “stock_quantity” and dozens of other spellings. Any mapping can be overridden manually — the first rows of the file are shown alongside so you can see exactly what will land in the shop.

A product is matched by SKU (or MPN or model), separately by model, or by barcode (EAN, UPC, JAN, ISBN) — whichever field is actually filled in in your catalogue.

Plan first, then write

The module never writes to the catalogue immediately. First it reads the file, matches it against products, and shows a full plan: how many rows were read, how many were found in the catalogue, which prices and stock levels will change — a “before → after” table for each product. Rows with unknown codes, suspicious changes, errors, and rows with no change are shown separately.

Only after your confirmation is the plan applied — in batches, so 40,000 rows don’t depend on whether a single request survives the server timeout.

Log and rollback

Every run is stored: when, from which file, how many rows were read and how many products were updated. All changes are recorded field by field — old and new price, old and new stock — so any run can be rolled back with one click to the values it had before. This isn’t “restore a database backup” — it’s an exact rollback of precisely the products the import touched.

Automatic updates on a schedule

A supplier profile with a price-list URL can be put on a schedule — hourly, every 6 hours, daily or weekly. The module fetches the file itself, calculates prices by your rules and updates the catalogue; the result of each run stays in history with the same rollback available. The run happens at a cron URL with a secret token, so no one else can trigger the import.

Why a shop needs this

A supplier’s price list is almost always someone else’s Excel file with arbitrary columns, arriving once a week and slightly different each time. Reconciling such a file with the catalogue by hand takes hours and ends up with pricing mistakes.

The module takes over this work: it recognises the columns itself, calculates prices by your rules, and shows a plan of changes before anything is written.

How to install

1. Upload the archive via “Extensions → Installer” and install the module.

2. Upload one price list and check that the columns were detected correctly.

3. Set the price rules and behaviour for products outside the price list.

4. Look over the plan of changes, and only then trigger the write.