Elbuz moves photos from supplier price lists and parsers into product cards during the catalog update and recognizes photos a product already has, so daily price lists create no duplicates.
When you need this:
- A price list arrives daily — append mode adds only new links; existing photos stay.
- You maintain some cards by hand — “Do not update photo” shields them from any photo step.
- The supplier removes images — “Cloud photo storage” downloads photos to your storage.
- Card photos must match the price list — “Delete all photos before updating” replaces the list with the price list's.
Where to start: checklist before your first photo load.
What photo transfer from a price list can do
- Collects photos from all sources into one list — price list, , your website, product duplication and merging.
- Splits the cell with links — up to 31 photos per row, in the same order as in the price list.
- Doesn't duplicate photos on reload — five checkboxes in the “Photos and media” group plus card-level overwrite protection.
- Makes your own copies instead of someone else's links — the “Cloud photo storage” mode.
Where product card photos come from
Only a handful of products get photos by hand. Most photos arrive on their own, and every route leads to the same product photo list:
- Supplier price list — a column with image links, the photo step of the .
- Parser source — the same update, but the data was collected from the supplier's website.
- Site parser — a separate parser run.
- Your own website via a tunnel — photos are pulled from your website along with the other product data.
- Product duplication — the copy receives the photos as files.
- Merging duplicates — photos move to the winning product.
By default, the app stores not the photo itself but a . What that means in practice — see the section on storage.
How the list of links from a price list is split
Suppliers put several addresses in one cell, separated by commas, semicolons, or vertical bars. The app normalizes this and splits it into separate photos:
- Semicolons and vertical bars are replaced with commas.
- Repeated cells with the same list of addresses within one price list row are removed; identical addresses inside one cell are not.
- The list is split at commas. No more than 31 links are taken from one price list row — this is the parsing limit, and extra addresses simply won't reach the catalog.
- Each link gets a key — a checksum of the lowercase address. This key is how the app later recognizes that the product already has this photo.
- Any extension outside jpg, jpeg, png, gif, webp, svg is replaced with
jpg. - Empty rows are removed; the rest get technical file names.
You can see each photo's source in the product grid, in the “Photo source” column: it shows “Прайс: price list name”, “Прайс-парсер: parser name” or “Парсер: parser name”.
The photo order comes from the price list: the first link in the cell becomes the first photo, that is, the main photo. Checkbox settings, schedule, and the cost of the run itself are in Updating the base catalog from price lists; this article covers only what the run does with the photo list.
Updating photos from parser sources costs €0.05 per product: once for each product whose photos came from a parser, not per run. File price lists are free. If your balance is too low, the photo step doesn't run at all.
How to reload photos without duplicates or losses
The most common photo question is: “the price list arrives every day — won't a product end up with a hundred identical images?” Rerunning the same price list won't do that: each link has a key — a checksum of the address — and the app recognizes the ones the product already has.
This protection works within one product and only for identical addresses, so the same photo from two different price lists gives two tiles. The add modes themselves differ, and not in the way their labels suggest.
| “Photos and media” checkbox | What it does with photos |
|---|---|
| “Add photo” | Works only for newly created products and only when “Update photo” is off |
| “Update photo” | Works for products already in the catalog |
| “Check whether the photo exists (by link)” | Adds only a link the product didn't have yet. Append mode |
| “Check for photo existence (flag)” | Adds photos only to products that have none |
| “Delete all photos before updating” | For products that get links from the price list this time, first deletes all existing photos, then uploads the new ones |
One detail isn't visible in the interface. Clearing “Check whether the photo exists (by link)” doesn't mean “upload everything”. In this mode the app skips every product that already has at least one photo and adds photos only to products with none — the same as the “(flag)” checkbox.
Two product checkboxes in the card's “Statuses and flags” section protect photos from being overwritten: “Do not update photo” — targeted, images only, and “Do not update” — for the whole product. Both are in the condition of every photo step query, so the run simply skips a product with either one.
- Action or result
- Decision: the path depends on the answer
“Delete all photos before updating” is the most costly checkbox here. It doesn't act on the whole catalog: only products that this same run brings new price list links for are affected. A product with no links in the price list keeps its photos.
But for affected products, everything is wiped: photos you uploaded by hand, photos from other price lists, parsers, and your website, the order, the label mark, and hidden states. You get back exactly what the price list provided this time. The service keeps no photo backups, there's no trash, and no undo.
With “Cloud photo storage” on, a product can end up with no photos at all: the app deletes old photos with their files first, then downloads new ones — if none download, the product is empty. In link mode, deletion and upload are one transaction: if either query fails, both roll back and the old photos stay.
The nightly scheduled run reads this checkbox too — set it once and forget it, and it fires every night by itself. There's no automatic safeguard: the app never clears this checkbox on its own.
Before you load photos from a price list
How to make price list photos your own copy
In a product's photo list all photos look the same, but they live differently.
| State | What it means |
|---|---|
| Link | The file is on the supplier's server. If they remove it, rename it, or restrict access, the image disappears for you and on your website |
| Copy in Elbuz cloud | The file is yours and sits in the service's storage. The supplier no longer affects it |
| Local file | Own-disk mode: the file is on a disk, not in Elbuz cloud storage |
- Action or result
- Decision: the path depends on the answer
This is controlled not by the card but by an account mode. If is on, photos from price lists and parsers are downloaded to Elbuz storage. If the mode is off, the catalog gets just the links.
To turn it on, go to Account → Balance, the “Cloud photo storage” add-on card labeled “Product photo files stored in cloud storage · +0.33 EUR / day”: the “Activate” button and the “Activate cloud photo storage” confirmation. Demo accounts don't have this add-on card.
How much space your photos take is shown in the same place — the “Disk space usage” block, “Photo” tile.
Photos uploaded by hand from the card always go to the cloud, regardless of the mode: the paid checkbox controls only bulk loading from price lists and parsers.
Here's what that means in practice. While the mode is off, only photos added by hand from the card become your own copy — the whole catalog that came from price lists and parsers relies on other people's servers. Every image a supplier removes disappears at once from the card, the website, and the feeds.
Scenarios
Each scenario is a store task, the checkboxes that solve it, and the result. The “Photos and media” checkboxes are in the “Updating base catalog” window, “Settings” tab.
You manage photos by hand, and the price list should update everything else
What to turn on: in the product card, “Statuses and flags” section — “Do not update photo”.
Result: the photo step skips this product with any combination of “Photos and media” checkboxes, including when “Delete all photos before updating” is on. The run updates prices, availability, and other data as usual. What won't happen: new photos from the price list won't reach the product either, and the “Photo source” column keeps its previous value.
A price list arrives every day, and new photos should be added without duplicates
What to turn on: “Update photo” and “Check whether the photo exists (by link)”; “Delete all photos before updating” — cleared.
Result: each new price list link is added as a separate photo. Existing photos — uploaded by hand, from other price lists, hidden, or marked “Label” — stay in place. What won't happen: a link the supplier dropped from the price list stays on the product, and the same photo at a different address gives a second tile.
Card photos must exactly match the supplier's price list
What to turn on: “Update photo” and “Delete all photos before updating”.
Result: a product that gets links from the price list this time receives exactly the price list's list, in cell order: the first link becomes the main photo.
What won't happen: products with no links in the price list and products with “Do not update photo” keep their photos. But affected products lose everything else — photos added by hand, the “Label” mark, hidden states — on every run, including the nightly scheduled one.
New products from the price list should arrive with photos, and existing ones should stay as they are
What to turn on: “Add photo”; “Update photo” — cleared.
Result: only products created by this same run get photos from the price list. What won't happen: products already in the catalog won't get price list photos, even if they have none. If both checkboxes are on, “Add photo” doesn't work separately — “Update photo” takes over.
Photos must not depend on the supplier's servers
What to turn on: Account → Balance, the “Cloud photo storage” add-on card (“Product photo files stored in cloud storage · +0.33 EUR / day”), the “Activate” button.
Result: the photo step for price lists and parsers downloads photos to Elbuz storage instead of keeping links.
What won't happen: photos already in the catalog as links won't turn into copies by themselves — a run without “Delete all photos before updating” doesn't rewrite rows the product already has. And if “Delete all photos before updating” is on together with the cloud, old photos are deleted before the new ones download.
What to do when photos disappear after a run
| What you see | Why | What to do |
|---|---|---|
| After the nightly run, products have no photos left | “Delete all photos before updating” is on, and the new photos failed to download: with cloud storage on, old photos are deleted before the new ones arrive | Clear the checkbox in the “Photos and media” group and reload photos from the price list. The old photos weren't saved anywhere (reloading) |
| After the run, the product has only price list photos, and yours are gone | The same checkbox: for products that get new links from the price list, it wipes all existing photos, including ones uploaded by hand | Clear the checkbox, and set “Do not update photo” on products you maintain by hand (reloading) |
| The card shows a broken image instead of the photo, and the photo is gone from the website | It was a link to the supplier's server, not your copy | Turn on “Cloud photo storage” in Account → Balance and reload photos from the price list (whose photo it is) |
FAQ
How many photos are taken from one price list row?
No more than 31 links. The app converts separators to commas, removes identical addresses within the row, and splits the list; addresses beyond the thirty-first won't reach the catalog.
Why did a photo disappear from the website when I didn't touch it?
Most likely the catalog held a link to the supplier's server, and the supplier removed the file. To make photos your own copies, turn on “Cloud photo storage” in Account → Balance. A photo link check finds broken links across the whole catalog.
New photos from the price list arrived, but the old one is still the main photo. Why?
When links are loaded on top of existing photos, the earlier photo stays first and the new ones go after it. To make another photo the main one, click the star on it (photo order).
I turned on cloud storage — did my old photos become copies?
No. Photos already in the catalog as links won't turn into copies by themselves: a run without “Delete all photos before updating” doesn't rewrite rows the product already has (scenarios).
One photo came from two price lists as two tiles — is that a bug?
No. The app recognizes a repeat by the link address and only within one product. The same photo at different addresses from two price lists gives two tiles (reloading).
Where to find it and who has access
- Photo checkboxes
- “Updating base catalog” → “Settings” tab → “Photos and media” group
- Card protection
- product card → “Statuses and flags” → “Do not update photo”
- Cloud storage
- Account → Balance → “Cloud photo storage” add-on card
- Prepare
- products are in categories, price list rows are matched to products
Related topics
- If you need the big picture — Product photos: how to add them, set the main one and not lose them.
- If you're setting up the run itself: schedule, prices, other checkboxes — Updating the catalog from price lists.
- If the supplier has already removed some images — Photo link check.
- If photos should also reach product variants — Option products from a price list.
