Skip to content
EN RU UA
Connect a supplier

When something goes wrong

The import created nothing, the run stopped, prices did not update, products are postponed with an error.

Start with the log: it almost always states the reason in plain words. Below are the cases that come up most often.

The import ran but there are no products

The usual cause is categories. A product is imported only from a category that is enabled and has a store category assigned. In the log this reads as “the supplier category is not mapped”. Check Setup → Categories: enabled rows without a store category are highlighted.

The second cause is products skipped for having no description or no images. That is in the log too.

The run stopped

You closed the tab, the connection dropped, the session expired. Nothing is lost: the queue survives. The import screen will say how many products are left from the previous run. “Continue” processes the remainder without polling the feeds again; “Start import” clears the queue and builds it from scratch.

Products postponed with an error

The program tries to write a product three times. After three failures it is postponed and no longer picked up, and a block appears with the reason and the attempt count. Deal with the reason and press “Retry” — the products go round again.

Prices are not updating

Check in order: is the supplier enabled, is it ticked for price updates, is the period from the settings preventing an early start, does the feed answer. All of that is visible in the price update log.

A separate case is an update skipped because “products are not loaded”: the price update works on products that already exist, and it is the import that creates them.

“Work not started: store settings do not add up”

The program could not reach the store database or did not recognise its structure. Open Settings → Diagnostics, the “Store” group, and press “Detect again”.

Not enough memory or time

Lower the batch size in Settings → General — “Products per pass”. The program is built for modest limits; it will simply do less per pass. The current hosting limits are shown under Diagnostics.

If none of that helped

Write to us and attach the part of the log covering the run: it shows almost everything.