↑↓ selectEnter openEsc close

    1. Elbuz

    How to import a price list and get prices into your catalog

    16 min readUpdated

    Elbuz imports a supplier price list in the background, then moves prices to your catalog and website — by button or automatically after a scheduled import.

    When you need this:

    • The import has started — it runs in the background and reports the product count when done.
    • The supplier sent a new file — the source's products are fully replaced; manual matches are reapplied.
    • Prices must reach the catalog and site — a separate step: “Update my catalog” or the post-schedule chain.
    • A product is in no price list — the catalog update takes it off sale if missing-product deactivation is on.

    Where to start: source card → “Import”.

    What the import does

    How to run an import

    Use the “Import” button in the source header (its tooltip says “Load the file and import products”). Next to it is “Stop import”.

    The window doesn't lock. The import is registered in the operations center, and the app says “Import started — watch in “Operations””. The operation is called “Price import “‹source name›””, and when it finishes you get the notification “Import finished: N products” with the “Open source” action. So after starting it, you can go on working in other windows.

    To run several sources at once, open the left panel menu, item “Import sources”: “Import all sources”, “Price lists only (no parsers)”, “Run all site parsers”.

    “Upload a file first in the “Settings” tab” — the source exists, but there's no file in it yet. The “No file” tile in the readiness bar shows exactly this state.

    “This source is already being imported (started at ‹time›). Wait for it to finish or stop it with the “Stop” button.” One source runs one import at a time; it's busy only while the process lives, so a crashed run never blocks it. Scheduled runs log “Scheduled price list import canceled: another price list is being loaded (data processing conflict).”

    What a single-source import checks before touching the old products: every branch on the right ends with the previous list staying in place, and only the bottom branch replaces it with the new one
    YesNoNoYesNoYesNoYesYesNo“Import” buttonIs this source already beingimported?Rejected — “This source is alreadybeing imported”Are column addresses filled in,including fields with “Consideruniqueness”?not checked for XMLStop — “Column addresses are notfilled in”Was a fresh file received?The previous file is used — the runis marked as an errorWas at least one row read from thefile?The previous product list staysWas a stop rule with the “Block”action triggered?Import canceled, old data keptThe source's old rows are deleted,new ones are written
    • Action or result
    • Decision: the path depends on the answer

    You can follow progress in the run log: reading data from the file and from a specific sheet, “Rows loaded”, saving rows, indexing, attributes, photos, removing duplicates, “Categories Imported”, “Products Imported”, “Updating statistics”. At the end — “Data loading completed!” and “Time spent”.

    What was loaded appears on the source's “Products” tab — the supplier's products exactly as they were sent. The “Matched with catalog” tile in the readiness bar shows “N / M” — how many of them are already linked to your catalog.

    What's left is matching with the catalog: the supplier's categories with your categories, and their items with your products. The source has the “Categories” and “Matching” tabs for this.

    What a repeat import replaces and what stays

    An import doesn't append the new file to the old data; it replaces the source's products entirely. Before writing new rows, the app deletes all previous rows of this particular source: products, their attributes, photos, videos, warehouse stock and the price list's category tree. Other sources aren't touched — the replacement works one source at a time.

    This answers the main question about a repeat run. Items missing from the new file simply disappear from the list. They aren't deactivated, their stock isn't set to zero, and they aren't marked as outdated — the row is gone, and so is any trace of it in the source's products.

    You can see how many items disappeared in the source header: next to the number on the “Products” tile there's a badge with the change since the last run, and its tooltip says “Previous import: N”. Minus forty means the file now has forty fewer products.

    It's easy to read the “Deleted” column in the run log as “how many items the supplier dropped”. It's a different number: it counts the rows removed by the “Remove products that are on the ignore list” operation, that is, your own ignore rules, not the supplier's behavior.

    Edits made by hand in the source's “Products” grid don't survive a repeat import. In this grid you can edit “Name”, “Price”, “Manufacturer”, “Quantity”, “Manufacturer SKU” and more — and all of it lives in the same price list row that the next run deletes and loads from the file again.

    There's no way to lock your own value in a price list row: the row is a copy of the supplier's file, and the app brings it back in line with the file every time.

    In the catalog, however, you can lock your values — enter them there. A catalog product has the checkboxes “Do not update” (the catalog update skips the product entirely), “Do not update attributes”, “Do not update photo” and “Fixed Price”: the last keeps your price while other fields still update.

    What survives a repeat import and is applied again without your involvement:

    • Manual product matches with the catalog. They're stored separately from price list rows, and every import includes the operation “Matching products from the price list with the products of the base catalog”, which starts with the “search for manually matched products” type.
    • Category matches between the price list and the catalog — they're tied to the supplier's category name. If the supplier renames a category, the app sees a new category with no match (Matching price list categories).
    • Ignore lists, text auto-replace rules, regular expressions, markups, field formulas, stop rules and the schedule. These are source settings, not file data, and a run doesn't touch them.

    Next time, a price list row is recognized by the manufacturer SKU plus the name; if columns have the “Consider uniqueness” checkbox, the key is built from those columns. While the supplier keeps the name and SKU, a manual match returns by itself. A changed name means a new product that you match again.

    Old data isn't deleted in one case: when not a single row could be read from the new file. Deletion doesn't run, the log shows “No data received, previous product list will be displayed”, and the “Products” tab keeps the previous list. This is the “nothing happened” situation: the run is marked as an error, the products are old.

    When prices reach the base catalog

    An import ends at the supplier's products. Prices from a price list don't move into the by themselves: that's a separate step.

    To run it manually, use the “Update my catalog” button in the window header (tooltip: “Update my base product catalog based on price lists”). It opens the “Updating base catalog” window with all its settings: what to update — prices, attributes, photos — and what to do with products that dropped out of the price lists.

    This step runs automatically only when the “Update catalog after import” setting is on. Then it starts after a scheduled import — both the schedule for all price lists and the schedule of a single source — and also after a manual “Import all sources” run.

    A manual import of one source with the “Import” button doesn't start this chain — however many times you click “Import”, catalog product cards keep the old price until the catalog update runs.

    Exports come next in the same chain: if “Build exports after update” is on, the app rebuilds the templates after the catalog update — and only then does the new price reach marketplaces and your website. This step happens only in a run over all price lists — on a schedule or with the “Import all sources” button.

    The catalog gets new products only if “Add new products” is on, and only in a scheduled run. Without it, prices of existing products are updated, and new items stay in the price list.

    Two cases when the chain waits:

    • Some sources are site parsers, and their tasks aren't finished yet. Then the catalog update is postponed, and exports don't start at all — otherwise they would go out with the old catalog. The app waits for parsing to end and does both steps by itself.
    • A scheduled price list import is running right now. A manual catalog update at this moment is rejected with the message “Scheduled price list import is in progress — catalog update start was rejected”, and the settings window shows a warning about the same instead of the button. This isn't a fault: the update starts by itself if the corresponding setting is on.
    The chain after importing all price lists: the two top checks decide whether and when the catalog updates, and the bottom one decides whether the new price goes to marketplaces. A single-source import with the “Import” button isn't part of this chain
    NoYesYesNoYesNoImport of all price lists — on aschedule or “Import all sources”Is “Update catalog after import” on?Is “Build exports after update” on?Are site parser tasks still unfinished?The catalog update waits for parsingto endAfter parsing — catalog update,then exports if they are onBase catalog updateEmpty fields translated if “Translatetexts after update” is onExport templates are builtExport templates are not rebuilt
    • Action or result
    • Decision: the path depends on the answer

    What happens to a catalog product that dropped out of the price list

    The fate of such a card is decided by the “Product activity” section in the same “Updating base catalog” window — “What to do with products that disappeared from price lists or reappeared in them”:

    • “Deactivate products in the base catalog if the product is not found in price lists” — the product goes off sale, gets the “out of stock” status and zero quantity, and is marked for re-export to marketplaces. The rule doesn't touch products with the “Do not update” checkbox.
    • “Activate products in the base catalog if the product is found in price lists” — the reverse: the item is back in a price list, and the product is turned on again.
    • “Days a product stays current; after that it is deactivated” and “Days a product stays current; after that it is deleted” — . The app shows an empty field as an infinity sign, which means there's no limit.
    The Product activity card on the Additional tab of the Updating base catalog window
    1Deactivate products not found in price lists
    2Activate products found in price lists
    3Days a product stays current before it is deleted
    1. Deactivate products in the base catalog if the product is not found in price lists.
    2. Activate products in the base catalog if the product is found in price lists.
    3. Days a product stays current; after that it is deleted (0 means never).

    Deletion by relevance days really deletes the product from the catalog rather than taking it off sale, and it can't be undone: the only way back is to add the product from the price list again as a new one. Before entering a number here, test with deactivation — it's reversible.

    Neither days-based mechanism touches products with the “Do not update” and “Fixed Price” checkboxes. In the log, the deletion step is labeled “Removing products from the base catalog that are not in the price lists”. The other update settings are covered in Updating the base catalog from price lists.

    Scenarios

    Products no supplier has should go off sale and come back when they reappear

    What to turn on. The “Updating base catalog” window, “Product activity” section: “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”.

    What you get. On every catalog update, a product that isn't in any active source becomes inactive, gets the out-of-stock status, the quantity from that status and a re-export mark. Once it's back in a price list, it turns on again.

    What won't happen. The rule doesn't touch products with the “Do not update” checkbox or products that are bundles. The price list import itself doesn't turn anything off in the catalog: it all happens only during the catalog update. And nothing is deleted until “Days a product stays current; after that it is deleted” is filled in.

    You need to keep your own price for a product even though the supplier changes it

    What to turn on. In the base catalog product card — the “Fixed Price” checkbox.

    What you get. The catalog update keeps your price and updates the product's other fields from the price list. Editing the price in the source's “Products” grid won't do: the next import overwrites it.

    What to do when an import fails

    What you seeWhyWhat to do
    “Upload a file first in the “Settings” tab” The source exists, but there's no file in it yet Add a file or a link in the card; the “No file” tile in the readiness bar shows the same state (source card)
    “This source is already being imported (started at ‹time›)” Two imports of one source can't run at the same time Wait for it to finish or stop the run with the “Stop” button (running an import)
    “No products found in node “‹tag›” — check the XML product branch setting” The wrong product branch is set; the old products stayed in place because the replacement didn't start Check the branch in the “XML structure” section of the source card (repeat import)
    The source's products show the new price, but the base catalog and website show the old one An import doesn't touch the catalog: moving prices is a separate step Click “Update my catalog” or turn on the update after the scheduled import of all price lists (when prices reach the catalog)
    “Import blocked by a stop-rule” A was triggered: the import was canceled and the old data kept See which rule was triggered in the “Import stop-rules” fold on the “Log” tab (what to do when it's triggered)

    FAQ

    What happens if I run the import twice?

    The second import won't start: the app replies that this source is already being imported. Wait for it to finish or stop the run with the “Stop” button.

    Will my edits to price list products survive the next import?

    No: the import loads the source's rows from the file again. To lock your value, use the catalog product card — the “Do not update” and “Fixed Price” checkboxes. More: repeat import.

    What happens to products the supplier no longer sends?

    They disappear from the price list. The fate of the catalog card is decided by the “Product activity” section of the “Updating base catalog” window. More: a product that dropped out of the price list.

    How do I stop an import that's already running?

    With the “Stop import” button next to “Import” in the source header.

    The supplier renamed a category — why did the products arrive without a catalog category?

    A category match is tied to the category name. A new name means a new category with no match: match it again. More: Matching price list categories.

    Where it is and who has access

    Menu
    Directories → Processing price lists → List of price lists
    One source
    source card → “Import” button in the header
    All sources
    left panel menu → “Import sources”
    Catalog update
    “Update my catalog” button in the window header
    Access right
    “List of price lists” window
    Prepare
    a source with a file and a mapped “Name” column — connecting a source

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free