Category mapping, resuming Allegro offers, and XML feeds
Three screens for one-time setup when connecting a channel. That is why they are here rather than in the everyday integrations menu.
Category mapping
This maps a category in our catalog to a marketplace category. Choose a marketplace and catalog; the table lists categories and whether they are mapped. Missing matches are marked No mapping. Filter by mapping status and search category names on both sides.
Click Add mapping and choose the marketplace, catalog category, and marketplace category. Marketplace category search starts after three characters.
Use this when connecting a new sales channel or when an offer cannot be listed because the product has no matching marketplace category (Mapping categories to a marketplace).
Resuming Allegro offers
The Resume ended Allegro offers screen lists offer numbers that are not resumed automatically and lets you resume an individual offer manually.
The screen has two parts:
- Offers excluded from automatic resuming — numbers that will never be resumed automatically. Enter an offer number and optional note. Use this for offers ended deliberately and incorrect listings that have since been relisted correctly.
- Ended offers — ended offers for the selected account, with number, EAN, name, and current stock. Choose Do not resume or Resume now without looking up numbers on Allegro. A Only with available stock filter is available.
Manual resuming lists the offer immediately and cannot be undone. The system asks you to confirm and warns if the offer is on the exceptions list or has no available stock.
Typical messages say the offer is no longer on Allegro and was marked inactive; stock synchronization is disabled for this account, so the offer will never receive stock updates; or Allegro’s request limit has temporarily been reached.
XML channels
XML product feeds from suppliers, fetched from a URL or uploaded as a file. The list shows each feed’s source, product count, last and next run, and whether automatic import is enabled and at what interval.
Configure in this order: load the feed so the system can read its structure → choose the record level (the path to one product) → map fields. Map fields yourself or request an AI suggestion. Suggestions work if the company has any AI integration. Choosing an integration and model in the feed settings is optional; otherwise the system uses its defaults. Separately assign the supplier’s warehouse to ours and select a price group.
Products are matched by EAN. When a feed stores attributes as repeated named fields (for example Ceneo’s <a name="EAN">), paths appear by name, such as attrs.a[@name=EAN], instead of only by an index that varies between products.
The images field adds photos. Map one image address (for example imgs.main.@url) and the system takes every address in that branch (main and additional), in feed order. A list of addresses in one field, separated by commas, semicolons, or |, also works. Images do not require a warehouse, price, or stock.
In the feed settings under Product data from feed, each of name, SKU, and images has one of three behaviors:
- Do not change: the feed never edits the field. This is the default for name and SKU because a supplier code is not your SKU and order lines are matched by SKU.
- Fill when empty: import the value only if the product has none. This is the default for images; the supplier gallery is added only to products with no photos.
- Update when different: overwrite the value whenever the supplier has a different one. For images, the gallery follows the supplier: new photos are added, removed supplier photos disappear, and the feed determines order.
Safeguards always apply. An empty feed value never clears anything, and a product retains its gallery if the supplier has no photos. The feed never deletes or reorders photos added manually or by other feeds; its photos come after them. Preview and run history show how many names, SKUs, and photos will change or changed. If photos were imported before this setting existed, the feed takes them over during the first update if the supplier still provides them. Photos the supplier no longer provides remain as if added manually. An unmapped field is labeled to say the feed will not change it.
Preview shows what will happen without saving. Run the feed now or enqueue a background job. Run history is available from the feed.
Use this when connecting a new supplier, or when an import stops running or imports incorrect data. A paused feed is marked in the list and has a banner on its detail page.
Access: category mapping and Allegro require the Integrations module; XML feeds require Documents. Each also requires Advanced.
Want to see this with your orders? We’ll show you NOXTI with your sales channels and warehouse.
Book a demo