Elbuz turns any stock notation in a supplier price list — “+”, “***”, “true”, “>3 pcs”, an empty cell — into your short status list for the catalog. Teach it each supplier’s notation once; later imports apply it automatically.
When you need this:
- The supplier writes “In stock” in Ukrainian — one status keyword covers every price list.
- Pluses or asterisks instead of quantity — a price list rule sets status and nominal quantity.
- Only in-stock products wanted — the rest are removed on import.
- A file without stock — a stop rule warns or blocks the import.
Where to start: the checklist for a new supplier.
What stock statuses can do
- A shared list of statuses — “In stock”, “Preorder”, “Out of stock” and your own, each with a color and a name in every language.
- Status keywords — recognize stock notation in any price list.
- Rules for one price list — tailored to a specific supplier’s format: a list of notations, numbers, a different column.
- One decision order — price list rules first, then keywords, then everything left over.
- Transfer to the catalog — during the base catalog update, with priority by status.
- Protection against mass stock loss — a stop rule compares the new file with the previous one.
Where the app gets stock from
Keywords have nothing to work on until the app knows which file column holds stock. You specify it in the price list card, in the “Columns” section: among the system fields there is “Stock status (from price list)”, and that is where you enter the address of the column with the stock notation.
Next to it is a separate “Quantity” field, and it serves a different purpose: it holds the number of units, not the stock notation.
For files, the app assumes the stock field is always present and does not check the column address.
If no column is specified, no rule has a source field, and the stock values are empty, the app gives the entire price list a status of type “In stock”. That is worse than an error: the storefront shows products that may be missing. An empty stock column means: stop and check “Columns” before importing.
The second field, “Quantity”, works as a switch for all the arithmetic: when the quantity column is specified, the app takes the quantity from the file as is.
Settings that calculate quantity from the stock text (“Detect by number”, “Default quantity”, “Add quantity” in a rule) apply only when there is no quantity column. There is one exception — a rule with the “Set this status for all products” checkbox: it overwrites the quantity for the entire price list regardless of the column.
Before writing rules, look at the notations the supplier sent: the hint on the “Availability” tab.
The order in which the decision is made
When a price list is imported, detecting stock is a separate step inside the import. It always runs in the same order — and this order is exactly what shows why you got something other than what you expected.
- Is there a “Set this status for all products” rule? If one is found among the price list’s active rules, the whole price list gets its status and its “Add quantity”. The other rules, keywords and ranges are then skipped — only the last step, formatting and options, remains.
- Is there anywhere to get stock from? The app checks: the “Stock status (from price list)” column address is specified, or some rule has “Source field” filled, or the stock values in the rows are already non-empty (for example, a formula filled them in). For XML, the answer is always yes. If there is nowhere to get stock from, the entire price list gets a status of type “In stock”, and nothing else is calculated.
- This price list’s rules — one by one, in rule order. The first one that matches closes the row.
- First cleanup. If at least one row got a status and an active rule has the “Only import products with this status” checkbox, rows with other statuses are removed from the price list — including those not yet recognized. This happens right here, before the global keywords.
- Global status keywords pick up whatever is still unrecognized: first by quantity range, then by words, in a fixed order of types “In stock” → “On order” → “Out of stock” → “Other”.
- Leftovers. If no row was recognized, all of them get the “In stock” status. If at least one was, all remaining rows get a status of type “Out of stock”.
- Second cleanup. The same “this status only” check runs once more, after the keyword pass.
- Formatting and options. The price list rows receive the status name, color and image in your language. The main product’s quantity becomes the sum of its options’ quantities, and if the options are linked to the main product by , any one of them being in stock makes it in stock too.
- Action or result
- Decision: the path depends on the answer
The order of steps four and five matters. When the price list has “Only import products with this status”, unrecognized rows never reach the global keywords and do not become “Out of stock” — they are removed earlier.
After such a cleanup there is nothing left to pick up: every remaining row has a status. There is one exception — when no price list rule matched: then the cleanup does not run and the global keywords work as usual.
The last step explains one more thing people often ask about: a main product with options has no stock of its own. It is assembled from the options — from their quantities and statuses.
How stock reaches the catalog and the website
Stock in the price list is not yet stock in the catalog. The price list is what the supplier sent; the catalog is your products that customers see. Data is carried between them by the base catalog update, which runs separately from the import.
Which statuses take part in choosing an offer, and in what order, is set by the “Select price based on stock status” grid in the update settings: a cheaper offer from a supplier who doesn’t have the product won’t beat a more expensive one from a supplier who does. Learn more: stock status priority.
A row missing from the new file simply disappears from the price list. The product stays in the catalog and, after the update, gets “Out of stock” if it received no offer from any price list. Learn more: stock reset.
The catalog grid has a “Stock status date” column. It moves only when the status has actually changed — it is the date of the stock change, not the date of the last price list import. A product where it stays put for weeks is not “forgotten”: its stock is simply stable.
On the website, customers see the status name, color and image in the storefront’s language, so fill in your own status name in every language. Marketplaces add one more layer: in each export template you can set a custom status text that this particular marketplace requires.
How not to miss a file where stock has disappeared
A supplier may send a file where stock has disappeared for every product: an export failure on their side, a truncated file, a changed column format. Without a check, such a file will quietly empty your storefront. That is why the import checks include the “Mass stock loss” rule.
Before the import, the app takes a baseline: how many rows the price list had and how many were in stock. An item counts as in stock if its quantity is above zero or its status has type “In stock”: flag-style price lists give no exact quantity, and without this condition the rule wouldn’t work for them at all.
What gets compared next is not the share of in-stock items itself but its drop relative to the baseline. The difference matters: for a supplier with 92% of items “out of stock” month after month, an absolute share would raise an alarm every time, while the drop shows exactly the change — eight percent in stock before, zero now.
By default, the threshold is 90% and the action is “Warn”: the import goes through, and you get “Price list imported, but anomalies detected”. With “Block”, the import is canceled and the price list keeps the previous data. Both are set with the other stop rules, for all sources or one. Learn more: what happens when a rule triggers.
When the protection stays silent
- The source’s first import — there is nothing to compare with, and “Block” acts as “Warn”.
- A with no items in stock. If stock already dropped to zero last time, the next import gives zero again, and there is nothing left to drop. The rule stays silent exactly when things are at their worst — so check the price list after every trigger instead of putting it off.
- The new file is empty. This case is caught by a neighboring rule — “Almost empty feed”.
And the fourth, most important point: with the “Warn” action, the data has already been overwritten by the time you see the warning. A warning is a prompt to check the price list and fix the rules, not a cancellation of the import.
- Action or result
- Decision: the path depends on the answer
Scenarios
Set up stock for a new supplier
Set up stock for a new supplier
How to write rules for specific notations — pluses, asterisks, a different column: price list rule scenarios.
Don’t miss a file where stock suddenly disappeared
Setup. The “Log” tab of the price list card → “Import stop-rules” → the “Mass stock loss” row, in the “Action” column select “Block”, then “Save rules”.
Result. When the share of in-stock items drops by more than the threshold, the import is canceled, the price list keeps the previous data, the run is marked as blocked, and you get “Import blocked by a stop-rule”.
What won’t happen. Blocking won’t trigger on the source’s first import, and if the previous data had no items in stock, the rule stays silent altogether.
What to do when stock behaves oddly
| What you see | Why | What to do |
|---|---|---|
| “Price list imported, but anomalies detected”, followed by “Check the source data. Warnings: Mass stock loss (‹number›%)” | A triggered: the share of in-stock items dropped by more than the threshold | Open the “Availability” tab and compare “Availability values from the price list” — most often the supplier has changed the format (about the protection) |
| “Import blocked by a stop-rule”, “Import canceled, old data kept” | The rule’s action is set to “Block” | The database holds the previous data, nothing is lost. Sort out the file and import it again |
| “previous data shown” under the run status in the log | That run was blocked, and the price list kept the previous version | Fix the source and repeat the import |
| The entire price list became “In stock” | The app has nowhere to get stock from: no column is specified and no rule is filled in | Specify the “Stock status (from price list)” column address in the “Columns” section of the price list card (where stock comes from) |
| Stock disappeared for all products in the catalog | The products received no offer from any price list: the source is disabled, the file didn’t arrive, or the rules cut out the rows | Check the last run in the log and the statuses in the price list itself, not in the catalog (how stock reaches the catalog) |
| “Stock status not detected” | The product didn’t get any status | Check the stock column address and the “Activity” column in the rules |
FAQ
The supplier colors cells: green means in stock, red means out. Does that work?
No. Cell color is ignored when detecting stock: the app reads only text. Ask the supplier for a separate column with a notation — even just “+” and “-”.
The stock cells contain formulas. Does the app evaluate them?
No. The app takes the result shown in the cell; the formula itself is not evaluated.
What happens if I don’t specify the stock column?
The entire price list gets a status of type “In stock”, and the storefront shows products as available even though they may not be. Check the column address before the first import (where stock comes from).
Why didn’t stock in the catalog change after the price list import?
The import updates the supplier’s products, not the catalog. Data is carried over by the base catalog update. Also check whether the status is enabled in the “Select price based on stock status” grid.
How do I set “Out of stock” for all of a supplier’s products at once?
In the price list rules, add an “Out of stock” rule with the “Set this status for all products” checkbox; the update will carry the status to the catalog (about the checkbox). A manual edit in the catalog with “Set value in bulk” will be overwritten by the next update.
Where it is and who has access
- Menu
- Directories → Availability statuses (the shared list of statuses)
- Price list rules
- price list card → “Availability” tab
- Stock column
- price list card → “Columns” section → “Stock status (from price list)”
- Access right
- the “Availability statuses” window; rules — the “Availability” tab of the price lists window
- Prepare
- an imported price list and the file column where the supplier writes stock
The status list is shared across the whole app. The rules that turn notations from the file into statuses are set separately for each supplier.
1
Availability statuses- Availability statuses — opens the window where stock statuses are managed.
Related topics
- If you need to understand at which import step stock is detected — Order of operations during price list import.
- If the catalog gets the price of a supplier who doesn’t have the product — Choosing the supplier price.
- If a product has disappeared from price lists and you need to know what happens to it in the catalog — Delisting products missing from price lists.
- If a stop rule triggered and you need to decide what to do — Price list stop rules.
- If you are deciding whether to manage inventory in Elbuz — what it gives your store.
