Elbuz fetches supplier price lists, applies your markup and updates stock in your product catalog and on your website. You set up a chain of steps once.
When you need this:
- You're new and don't know where to begin — steps go in order, marked “required” or “recommended”.
- A supplier changed hundreds of prices — new prices with your markup reach your cards automatically.
- A supplier dropped a product — it gets “Out of stock” and can be hidden from your storefront.
- You edited a card by hand — the name, description and photos stay yours.
Where to start: step 1 — connect a supplier and a price list source.
What the set-up chain gives you
Once the required steps are done, the “supplier price list → your catalog → website” chain runs on its own.
- Price lists arrive on their own — from a link, email, or , with no manual downloads.
- Prices and stock land in your product cards — thanks to matching price list products with your catalog.
- Selling prices calculate themselves — by markup, formula or rules on every update.
- A broken file doesn't reach your website — stop rules and filtering of abnormally low prices catch it.
- Your catalog grows with new products — with photos, descriptions and categories, if you turn on the recommended steps.
- Everything runs on a schedule — the catalog updates overnight, and in the morning you check the log.
Example: a supplier raised prices on two hundred items and took fifty out of stock. After the price list update, the new prices are already calculated with your markup, and the out-of-stock products are hidden from customers — you didn't touch a single product card.
If you don't have a catalog yet
The catalog is your products in the app: price lists arrive and update your own product cards. If your catalog is already loaded, go to step 1. Wherever it came from, the steps after that are the same.
- From supplier price lists — the catalog grows on its own as supplier products are copied into your cards (step 7). This is the default path.
- From your own website — your existing catalog is moved into the app via Elbuz Tunnel or with the site parser.
- From 1C — with an exchange file, via CommerceML import.
- From a file or feed — which import method to choose.
- By hand — you create the category tree and product cards yourself. For a small range, this works perfectly well.
Ten steps from price list to website
Required steps (1–3, 5, 6, 9) make prices and stock update on their own. Recommended ones (4, 7, 8, 10) aren't for everyone: skip them and return when needed. Each step links to a detailed article.
Step 1. Connect a supplier and a price list source required
You tell the app where to get the price list: a link, email, FTP or API. Then Elbuz fetches the file itself. A supplier can have several sources; one source is one price list that keeps being updated.
Details: Connecting a supplier, Supplier directory.
Step 2. Import the price list required
The app reads the supplier's file and shows its products. It maps the columns — name, price, stock — almost by itself; you check and confirm. Multi-sheet Excel, extra rows and odd formats are handled here too.
Details: How to import a price list, Multi-sheet Excel, Order of operations during import.
Step 3. Match price list products with your catalog required
The heart of the setup. To update prices and stock in your cards, the app must know which price list product is which of yours. Match by hand, by SKU or name rules, or with AI — when supplier names differ from yours.
Details: Manual matching, Auto-matching rules, AI matching.
Step 4. Distribute by category recommended
New products go into the right catalog sections on their own, with no manual sorting. Useful when many products arrive in batches.
Details: Where the supplier category comes from, Category distribution rules, AI category matching.
Step 5. Set up prices and markups required
You define how the selling price comes from the supplier price: a percentage markup, a formula, or conditional rules (say, different markups per product group). Prices are then recalculated on every price list update.
Details: Markups, Field formulas, Choosing the supplier price.
Step 6. Stock and stop rules required
You decide what shows as in stock. Stop rules catch a broken supplier file — truncated, with zeroed prices, in another currency — and warn you or cancel the import, keeping the previous data.
During the catalog update, a price several times lower than other suppliers' is filtered out and doesn't reach your website.
Details: Stock statuses, Price by stock level, Stop rules and supplier price control.
Step 7. Add new products to your catalog recommended
The batch update copies new supplier products into your base catalog, so your range grows on its own. Not everyone needs it: some only update prices on what they have.
Details: Updating the base catalog from price lists.
Step 8. Enrich new product cards recommended
New products often have bare cards: just a name and price. Elbuz pulls photos, descriptions and specifications from other websites. Do it after new products are added (step 7) — it's their cards you enrich.
Details: Site parsing, What the parser takes from a product page, Product photos, Attribute directory.
Step 9. Export to your website and marketplaces required
Finally, publish the result where you sell: your website and marketplaces. Without this, the work stays inside Elbuz and customers never see it.
Details: Export templates, Elbuz Tunnel, Price list for customers.
Step 10. Automate recommended
Once the chain works, put it on autopilot: a schedule fetches fresh price lists on a timer, and triggers run actions on events. Set it up once, and the catalog updates without you.
Details: Schedule and queue, Trigger rules.
Don't do everything at once. Run the required steps on one source, check that prices and stock come out right, and only then turn on the schedule and recommended steps.
What happens to your edits on later updates
The update doesn't touch every field of the card. The app turns on five “price list field → catalog field” links by itself: price, RRP, cost price, quantity and stock status. The name, description, photos and specifications stay yours until you turn on a link for them on the “Field links” tab of the “Updating base catalog” window.
If a field's link is on, the price list wins over your edit. An empty price list cell doesn't touch the card while “Update if value is not empty in price lists” is checked (on by default). Details: How not to overwrite your values with an empty cell.
1
Price — link is active2
Update if value is not empty in price lists3
Old price — link is off- The Price row has Active switched on, so the price list overwrites this catalog field.
- This column makes the field update only when the price list value is not empty.
- The Old price row has Active off, so the price list leaves this field untouched.
Two checkboxes in the product card lock your value more reliably:
- “Fixed Price” — the update doesn't touch the product's price, RRP, cost price or old price; with the “Date to remove the “Fixed price” flag” field, the flag clears itself on the set date.
- “Do not update” — the product drops out of the update entirely. The narrower “Do not update photo” and “Do not update attributes” take the price from the price list but leave the gallery or specifications alone.
Details: How to stop a price list from overwriting a price or a product.
Manual matching survives a re-import — if the “Search for manually matched products” matching type is enabled in the source's list of matching types. Without it, pairs are searched again by the automatic types. Details: How manual pairs come back.
A product disappeared from the supplier's price list
The card stays in the catalog with its description and photos. A product with no offer in any price list gets the stock status classified as “Out of stock” (in the standard set, that's “Out of stock”) and a quantity of 0 — if the stock status and quantity links are on.
Stricter options are on the “Additional” tab of the same window and are off by default: deactivate a product that isn't in any price list; deactivate or delete it after a set number of days without a price update.
1
Deactivate products not found in price lists2
Activate products found in price lists3
Days before deletion- Deactivates products in the base catalog when they are not found in price lists.
- Activates products again when they reappear in price lists.
- Days a product stays current before it is deleted — the only setting that deletes.
Deletion by days of relevance removes products permanently, without asking and with no way to restore them. All three settings apply to the whole catalog, not just the source you updated. Details: When products disappear from the storefront or the database.
After all price lists are imported on schedule, the catalog update starts by itself — “Update catalog after import” is on by default. New products are added in such a run only if “Add new products” is on — it's off by default. Both are in “System settings” → “Catalog update” → “Run and general rules”.
- Start or end
- Action or result
- Decision: the path depends on the answer
How to check that a run worked
Check three places.
- The “Log” tab in the source card — the result of each price list import: how many rows were read, how many made it into the price list, and the status “Done”, “Error”, “Blocked”, “Canceled” or “Running”. Details: What changed in the supplier price list.
- The “Operations” panel — the “Update my catalog” summary: “Products updated: N”, “Products added: N”. Zero products updated usually means the products aren't matched (step 3) or the supplier or source is turned off. Details: How to monitor a run.
- The “Date updated (price)” column in the catalog grid — when the product's price last came from a price list. Sort by it to see which products the run touched. For products with “Fixed Price”, this date doesn't change.
1
Loaded2
Status- Loaded is the number of rows read from the file, including rows that did not make it into the price.
- Status shows Done or Error for each run.
When several rules match a product
The chain has many rules, and almost all of them follow one principle: the first rule that fires takes the product, and the rules after it leave it alone. So the order of rules is the priority.
- Product matching (step 3). Matching types are tried top to bottom in the order they appear in the source's list; drag them to change the order. Each next type only looks at rows that don't have a pair yet. That's why “Search for manually matched products” is kept at the top: otherwise an automatic type grabs the row first.
- Category distribution (step 4). Rules apply by the value in the “Rule order” column, and a category is set only on price list rows that don't have one yet. A product that got its category from a rule higher up isn't moved by a rule below.
- Markup (step 5). Markup types run first, one after another; within a type, rules run by the same “Rule order”. A row whose price was already calculated by an earlier rule is skipped by the rest.
- One product from several suppliers. Here it's not a rule that wins but the price: the card gets the minimum (the default), average or maximum — set by the “Price selection type” switch in the “Updating base catalog” window. What's compared isn't the bare price but the price adjusted by the supplier's priority coefficient from the contact card, “Finance” section.
How long a run takes and what costs money
Regular work with file price lists — import, rule-based matching, markup, stock, catalog update, export — costs nothing beyond your subscription. Content from parser sources is paid separately: photos and specifications copied into the catalog at steps 7–8 cost €0.05 per product. The amount shows in the window header before you start. Details: How much an update costs.
There's no cap on the number of price list rows. The limits are about time:
- In a bulk run (“Import all sources”, the nightly schedule), a file source that doesn't respond for two hours is cut off, and the run moves on to the next one. This limit doesn't apply to site parsers.
- A whole bulk run lives for up to eight hours.
- A run with the “Running” status older than 15 minutes is checked as soon as you open the “Log” tab: if the process is dead, the row switches to “Canceled”.
The window isn't locked during an import: the run goes on in “Operations”, and you can keep working. For large price lists, the schedule is more reliable (step 10): the server handles the import and catalog update, with no browser left open.
Scenarios
Update prices and stock every night without expanding the catalog
What to turn on. A schedule to import all price lists (step 10). In the “System settings” window, “Catalog update” section, leave “Update catalog after import” on and “Add new products” off — that's how they're set by default.
What you get. Once all price lists are imported, the catalog updates itself through the field links — price, RRP, cost price, quantity and stock status. Then, if “Build exports after update” is on (it is by default), export templates are built.
What won't happen. Supplier products that aren't in your catalog aren't created. The card's name and description aren't overwritten until you turn on a link for them on the “Field links” tab.
A product is gone from suppliers — hide it from the storefront but don't delete it
What to turn on. In the “Updating base catalog” window, “Additional” tab: “Deactivate products in the base catalog if the product is not found in price lists” and “Activate products in the base catalog if the product is found in price lists”. Leave the “Days a product stays current; after that it is deleted” field empty.
What you get. During the catalog update, a product that isn't in any enabled source becomes inactive and gets the stock status classified as “Out of stock”. All enabled sources are checked, not just the one you've just updated. When the product reappears in an enabled source and is matched, the next update makes it active again.
What won't happen. The card isn't deleted. Deactivation skips products with the “Do not update” checkbox and product bundles. A product whose category is turned off isn't reactivated.
Keep your own price on a product until a certain date
What to turn on. In the product card: the “Fixed Price” checkbox and the “Date to remove the “Fixed price” flag” field.
What you get. The catalog update doesn't change this product's price, RRP, cost price or old price. Stock and quantity update from the price list as usual. Once the date passes, the very next catalog update clears the checkbox, and the price is calculated from the price list again.
What won't happen. This product's “Date updated (price)” doesn't move while the checkbox is set.
Several suppliers carry the same product — take the best price
What to turn on. Match the product with the price list rows of all suppliers (step 3). In the “Updating base catalog” window, leave the “Price selection type” switch on “minimum” — that's the default. If you trust one supplier more, give it a priority coefficient in the contact card, “Finance” section.
What you get. The card gets the price of the supplier with the lowest “price × priority coefficient + priority value”, and the card remembers that supplier as the product's supplier.
What won't happen. The nominally cheapest supplier doesn't win automatically: if its coefficient is higher, another one can win.
What to do when a run breaks off or prices are wrong
A run broke off or was stopped
Data won't get mixed up: a source's old rows are deleted only after the new file has been read and has rows in it. Running it again is safe — it replaces the source's whole set of rows, so there are no duplicates. Details: What a re-import replaces.
- “This source is already being imported” — wait for it to finish or click “Stop”.
- “Batch processing is already running in another process” — the catalog update doesn't start twice; the next run takes over a stuck lock older than 2 hours. Details: What to do when a run lock is stuck.
- “Canceled” status after “Stop” — whatever was already written stays; run the import again.
- “Import canceled, old data kept” — a stop rule fired, and the database holds the data from the previous import. Details: Run blocked.
- Start or end
- Action or result
- Decision: the path depends on the answer
Prices or stock came out wrong
Markup doesn't stack: every recalculation starts from the supplier price. Fix the rule → on the source's “Markup/Discount” tab, click “Apply markup to products” → “Update my catalog”. Stock is fixed the same way, by the next run.
There's no bulk “undo” button. The previous price is visible in the “Old price” column, and “Operation history” in the card restores values one product at a time — if “Value change history” was turned on in advance. Details: How to roll back prices in the catalog.
FAQ
How long does setup take?
The required steps take from half an hour to a few hours, depending on how “clean” the price list is and how closely product names match. It's a one-time job; after that, updates run on their own.
My catalog is already loaded — where do I start?
Go straight to step 1: connect a supplier and specify the price list source.
Prices updated, but no new products appeared in the catalog — why?
The update only touches matched products. New supplier products are added separately — at step 7, and in an automatic run only when “Add new products” is on.
Can I put everything on autopilot right away?
First go through the chain by hand at least once and make sure prices and stock come out right. Otherwise a mistake in the settings becomes automatic too and spreads across your whole catalog.
The supplier only has a website, no price list file — what do I do?
The price list is collected from the supplier's website with the parser: Elbuz pulls names, prices and stock from its pages. Then come the same matching, pricing and stock steps.
Where it is and who has access
- Menu
- Directories → Processing price lists → List of price lists
- Catalog update
- “Price lists” → source → “Update my catalog” button
- Access right
- the “List of price lists” window; “Catalog update from price lists” is a separate row in group rights
- Prepare
- a sample file from the supplier and your product catalog
Related topics
- If you've just signed in and haven't got to grips with the desktop yet — First sign-in: where to start.
- If you're ready to connect your first supplier — How to import a supplier price list.
- If the price list is already imported and you need to move prices into the catalog — How to update the catalog from price lists.
- If you're worried a supplier will send a broken file — How to keep price list errors off your website.
- If you're deciding whether to hand price lists over to the app — what it gives your store.
