↑↓ selectEnter openEsc close

    1. Elbuz

    How to update products on a Horoshop site from Elbuz

    18 min readUpdated

    Elbuz sends prices, stock, and product texts to your Horoshop site through the Horoshop API — no files or links: it updates existing cards and creates new ones.

    When you need this:

    • You manage prices and stock in Elbuz — a run moves them to the site; descriptions stay untouched.
    • Your catalog came from this site — products land in their sections by section ID.
    • You use your own stock status names — the site gets your text for each.
    • Your products have variants — the site groups them under the main product.

    Where to start: create a “CMS Horoshop API” template and enter the API credentials.

    What the Horoshop export can do

    How to connect the site

    The connection relies on the site address and a login/password pair. The site must be reachable during the run: Elbuz contacts it directly.

    Template fieldWhat to enter
    API URLyour site’s API address — the store domain with /api/ at the end
    Loginthe login of the API user created in the Horoshop admin panel
    Passwordthat user’s password

    The API user is created on the site side: Horoshop admin panel → «Налаштування» → «Адміни» (Settings → Admins). If you’ve already set up catalog import from this site, use the same credentials.

    Horoshop issues a temporary access key for about ten minutes. Elbuz gets a new one itself before each batch of products. So an authorization error in the log almost always means a wrong address, login, or password, not “an expired key”.

    Which products go to the site

    This template does one thing: products. It doesn’t create or rename sections on the site — the “Categories” checkbox has no effect here. The section must already exist on the site.

    Of the card’s other checkboxes, only “Attributes” affects the exchange — specifications. The Horoshop driver ignores the “Photo”, “Options”, “Stores”, “Warehouses”, and “Orders” checkboxes: photos, for example, go as a separate field in the list.

    The run includes products that pass the template’s filter: the export flag in the product card, an active category with export allowed, the store in the “Store” field, and the “Export limit (filter)” tab. A product without such a category isn’t sent at all. Details: Where product filtering is set.

    The “Only export new data” checkbox selects products without the “Exported” flag. The Horoshop template sets this flag on every product in each batch it sends, so with the checkbox on, the next run sends only what hasn’t gone to the site yet. The flag is shared by all export templates.

    Field list: what exactly goes to the site

    You build the set of fields yourself. The “Export fields” button in the template card opens a list where each field has an “Update” checkbox. In a new template, three fields are on: “Price”, “Stock status”, and “Category”.

    • The SKU is always sent. It’s the key the site uses to find the product, so Elbuz turns this field on itself.
    • A language field pulls in the main one. Turn on the Ukrainian description, and the description field itself is turned on too. The same goes for the name, SEO fields, and the variant name.
    • An empty row does no harm. A row with neither a field nor a formula is skipped.

    Product name, description, and SEO fields come in pairs — one for Russian («Наименование RU», «Описание полное RU» — name and full description) and one for Ukrainian. Turn on only the languages your catalog actually has: an empty Ukrainian version goes to the site empty.

    Variants aren’t created separately: Elbuz puts the main product’s SKU into the “Main product ID” field. In a new template this field is off — without it, variants go as ordinary products.

    The Export fields window with the Field name, Update, Formula and API field columns
    1Update checkbox
    2API field: article
    3Formula for the SKU source
    1. The Update checkbox shows which fields are sent to the site.
    2. The API field article is the key the site uses to find a product.
    3. The formula takes the SKU from the product's internal SKU field.

    Product condition

    The «Состояние товара» (product condition) field sends the condition from the product card to the site: “New” → New, “Discounted” and “Used” → Used, “Refurbished” → Refurbished. It’s off in the template: check “Update” for it if you sell discounted or used items on the site. Where the condition comes from: Product condition.

    Check the SKU source

    The row the site calls article is the key: the site uses it to find the product and decide whether to update the card or create a second one.

    • In a new template the row is “Product ID (UUID string)”. It holds the site’s SKU when the catalog was imported from this site — nothing needs changing.
    • In an older template the row may take “Manufacturer SKU”, which is often empty in cards that came from the site. Enter {Product: Product ID (UUID string)} in this row’s “Formula” column.

    {Product: SKU (internal)} is a common choice — it matches the site’s SKU until a separate “display SKU” field is filled in on the site; for such products the values diverge, and they go as new. A test run shows what went into article: an empty or wrong value creates a duplicate.

    The “Formula” column

    Instead of a ready field you can put an expression: a product field by column name, {Product: Field name} macros, and functions such as REPLACE or CONCAT_WS. Formulas are used most often for the category.

    The formula is inserted into the catalog query. If it’s invalid, the log shows “Error getting products!” — and no product goes out until you fix it.

    Specifications

    The “Attributes” checkbox adds specifications to the request: attribute code → value, separately for each language. Attributes in the attribute directory need codes; Elbuz fills an empty code itself by transliterating the name. Check the codes before the first run: a code changed later is treated by the site as a new specification.

    How a product lands in the right section

    When the catalog came from the site through import, service sections arrived in Elbuz along with the product sections — “Home”, “Product catalog”, “Contacts”, “About us”. Because of this, a product’s category path may look like this:

    Home / Product catalog / Home appliances / Washing machines

    But the site expects a path from the catalog root:

    Home appliances / Washing machines

    In the first case the site looks for a “Home” section and doesn’t find it: the product isn’t created or lands in the wrong place. The site’s warnings about individual products appear in the log (run), and the easiest way to check the path is a test run.

    What Elbuz does on its own

    Elbuz doesn’t send the field at all when the path exactly matches a service section: Главная / Каталог товаров, Каталог товаров, Главная, or Каталог. Elbuz doesn’t strip a service level at the start of a longer path — a formula in the “Category” row does that:

    TRIM(REPLACE({Product: Category}, "My site / Product catalog /", ""))

    Substitute your own level names — exactly as they appear in the path, separator included.

    Export fields window scrolled to the category row with its formula and API field
    1API field: parent
    2Formula that trims extra category levels
    1. The API field parent carries the path to the website section.
    2. The formula cuts off the extra top levels of the category path.

    The more reliable way: send the section ID

    The Horoshop API accepts a section ID instead of a path, and Horoshop’s documentation recommends it as the main method. In the field list it’s called «Категория ID UUID» (category ID); for sections that came from the site, it holds the section’s ID on the site.

    All the sections you need came from the site — turn on the ID field and turn off “Category”. Some sections were created in Elbuz manually — keep the path with a formula.

    A section created in Elbuz by hand has no ID on the site. For a new product in it, create the section on the site, or keep “Category” with the path and turn off the ID field: the ID wins over the path, and with an unknown ID the site looks for a section it doesn’t have.

    Stock goes as a word

    The “Stock status” field sends the site a word, not a number. Elbuz replaces a standard status name with a short word the site understands. The standard names are:

    • Russian: В наличии, Нет в наличии, Ожидание 2-3 дня, Предзаказ, Под заказ (in stock, out of stock, 2–3 days wait, pre-order, made to order);
    • Ukrainian: В наявності, Немає в наявності, Немає на складі, Під замовлення, Під замовлення 2-3 дні, Очікування 2-3 дні (in stock, not available, out of stock, made to order, made to order in 2–3 days, 2–3 days wait).

    For your own names, set the text in the “Stock-based update setup” window — it goes to the site instead of the standard word. The settings work per template and are read only from rows with “Active” on; the “Quantity” and “Product status on site” columns don’t affect this export.

    No text set and the name isn’t standard — the site gets the Elbuz status name as is. This field doesn’t send the stock quantity.

    Text entered in the setup window wins over the standard word; the Elbuz name goes to the site only when neither applies
    yesnoyesnoStock status name in the productcard“Title on site (in file)” entered for thestatus and “Active” on?The site gets the entered textIs the status name standard?The site gets its standard wordThe site gets the Elbuz status nameas is
    • Start or end
    • Decision: the path depends on the answer

    Stock on Horoshop isn’t updating: what to check

    Stock goes one way — from Elbuz to the site — and only through a template run. Check in order:

    1. Is there an export template? “Data export” must have a template of type “CMS Horoshop API”. A Horoshop import template doesn’t send stock to the site.
    2. Was there a run? The site doesn’t pull anything itself: check the date of the last run and how it ended.
    3. Is the field on? The “Stock status” row of the field list must have “Update” checked.
    4. Did the status change in Elbuz? The site gets the status, not the quantity: zero quantity with the “In stock” status shows “in stock”.
    5. Did the product pass the filter? Products that don’t pass the filter drop out silently.
    6. Did “Only export new data” filter it out? Clear the checkbox and run again.
    7. Did the site recognize the product? A different SKU in Elbuz and on the site — another card gets updated (SKU source).
    8. Did the site reject the value? The line “Horoshop accepted the batch with warnings” — for example, a custom status name the site doesn’t know: set text for it.

    How to check and run the export

    The flask button in the template header opens the “Export template check” window. It runs one product and shows the catalog data and the request to the service that would go to Horoshop. Nothing is sent: the check stops before the site. You can enter a product ; without one, the first product that passes the filter is used.

    Look at three things: whether the section path is built correctly, whether fields that should be filled are empty, and whether it’s the right product.

    Export template check window showing the request that would be sent to Horoshop
    1Request address
    2Values sent to the product
    1. Request address — exactly where the data would be sent.
    2. Values — article, price and availability that would go into the product.

    Manual and scheduled runs work as for all templates: Running manually and on a schedule.

    Run: batches, log, errors

    Products go to the site in batches of a thousand; after each, the log shows “Rows exported 1000 of …”. A product with an empty SKU isn’t sent — at the end, the log says how many were skipped.

    A product with an empty SKU is dropped before batching; among batches, the first site error stops the run, and batches accepted before it stay on the site
    noyesnoyesnoyesyesnoyesno“Export” button“Products” checkbox on?No products go to the siteFiltering products and rows checked“Update”Catalog query built?“Error getting products!” in the logProduct SKU filled in?Product skipped — their count is inthe log at the endBatch of up to a thousand products— new access key and request tothe siteSite returned an error?Site response to the log — runstoppedSite has warnings about someproducts?Orange line in the log with SKUsand the site’s textBatch accepted — the next one isassembled
    • Start or end
    • Action or result
    • Decision: the path depends on the answer
    • The site returned an error — the export stops at this batch and writes the site’s response to the log.
    • The site accepted the batch with warnings — the run continues; the log shows an orange line “Horoshop accepted the batch with warnings, products: N.” and up to twenty SKUs with the site’s text.

    Batches sent before the error are already applied on the site. Elbuz doesn’t remember what was on the site before the run. So check the field list and do a test run before the first live run. Damage is fixed in reverse: correct the values in Elbuz, leave only the damaged fields in the list, and export again.

    Repeat export

    Each run looks up the product on the site by SKU. Found — the card is updated with the checked fields; not found — the site creates a new one, which requires the name and section in the field set. So rerunning after a break-off is safe: you get updates instead of duplicates.

    Change the SKU, and for the site it’s a different product: it creates a new card, and the old one keeps the old prices. Keep SKUs unique and unchanged — both in Elbuz and on the site.

    A product that no longer passes the filter stays on the site as it was: this exchange has no “delete product” command.

    Scenarios

    Update only prices and stock on the site

    Task: names, descriptions, and sections on the site are managed by hand, and only price and stock should come from Elbuz.

    What to turn on: in the template card, the “Products” checkbox; in the “Export fields” window, the “Update” checkbox only in the “Price” and “Stock status” rows. The “Category” row is on in a new template — clear its checkbox too.

    Result: the site gets the SKU, price, and stock word; Elbuz adds the SKU itself. This won’t create new cards: they need a name and a section. Without the “Products” checkbox, the run sends nothing.

    Your own stock status names

    Task: stock statuses in Elbuz have their own names, and the site should show its own words.

    What to turn on: the “Update” checkbox in the “Stock status” row; in the “Stock-based update setup” window, for each status, text in the “Title on site (in file)” column and the “Active” checkbox.

    Result: the site gets the entered text, even if the status name is standard. A status with no text and a non-standard name goes as the Elbuz name as is.

    Variants should be grouped into one card

    Task: product variants should become options of the main product on the site, not separate cards.

    What to turn on: the “Update” checkbox in the “Main product ID” row. The main product must pass the template filter too.

    Result: the variant gets the main product’s SKU in this field. If the main product doesn’t get into the export, the field isn’t sent, and the variant goes as an ordinary product. The main product itself doesn’t get this field.

    Catalog came from the site — sections by ID

    Task: the catalog was imported from this same site, and products should land in their sections without fixing the path with a formula.

    What to turn on: the “Update” checkbox in the «Категория ID UUID» row, and clear it in the “Category” row.

    Result: the site gets the section ID that arrived with the section. Service levels like “Home / Product catalog” have no effect. A section created in Elbuz manually has no such ID on the site.

    What to do when the site isn’t updated

    What you see, why, and what to do
    What you seeWhyWhat to do
    Authorization error in the log Wrong API address (missing /api/ at the end), wrong login, or API access is turned off on the site side Check in this order: address → login and password → access settings in Horoshop (connection)
    Products aren’t created or land in the wrong section The category path still has the site’s service levels — “Home / Product catalog / …” Check the path with a test run; remove extra levels with a formula or send the section ID (section)
    “Horoshop: products skipped without an SKU (article): N” These products have an empty column that the SKU is taken from — without it, the site can’t find the product Set another source in the SKU row with a formula, or fill in the SKU in the cards (SKU source)
    “Horoshop accepted the batch with warnings, products: N.” The site accepted the batch but has warnings about the listed SKUs — the text is next to each SKU Fix what the site points to in these products and run the export again (run)
    Products weren’t updated, no errors in the log The product didn’t pass the filter: export flag, category, template filter Check the flags in the product card and the template filter (which products go)
    A second product with the same name appeared on the site The site didn’t recognize the product: a wrong value went into article, or the SKU was changed in Elbuz Use a test run to check what goes into article and change the field’s source; remove the extra card on the site by hand
    “Error getting products!” A formula in the field list is invalid — the catalog query failed Fix the formula and run again; the site received nothing (“Formula” column)
    Specifications didn’t appear on the site The “Attributes” checkbox is off, or attributes have empty codes Turn on the checkbox and check the codes in the attribute directory (specifications)
    A variant isn’t linked to the main product The “Main product ID” field is off — in a new template it’s unchecked Check “Update” for it and export again (variants)

    FAQ

    Do I need to give Horoshop anything — a file or a link?

    No. The exchange goes directly through the site’s API: Elbuz contacts it during the run.

    Will Elbuz create sections on the site?

    No. The template only creates and updates products, and the section must already exist on the site. The site won’t accept a product whose section it doesn’t have.

    Can I roll back a wrong export?

    No. Elbuz doesn’t store what was on the site before the run. Fix the values on your side, leave the damaged fields in the field list, and export again.

    Will Elbuz create a product that isn’t on the site?

    Yes, the site creates the card by SKU. For that, the name and section must be turned on in the field list.

    Where does Elbuz get the SKU the site uses to find the product?

    From the column in the article field row. In a new template it’s “Product ID (UUID string)”; in an older one, the source is changed with a formula (SKU source).

    Are product specifications sent to the site?

    Yes, if the “Attributes” checkbox is on. Values are sent by attribute code, separately for each language.

    The category path shows “Home / Product catalog”. What do I do?

    These are site sections that arrived with the catalog import. The extra level is removed by a formula in the “Category” field or by replacing the path with the section ID (section).

    What if a run broke off on an error?

    Check the site’s response in the log. Batches sent before the break-off are already applied — fix the cause and run again: a repeat run updates the same products instead of creating duplicates.

    Where it is and who has access

    Menu
    Directories → Operations → Data export
    Create
    add a template → type Horoshop
    Configure
    the template card: “Connection”, checkboxes, and the “Export fields” button
    Access right
    the “Data export” window; for the card — “Export Template Setup”
    Have ready
    an API user in the Horoshop admin panel

    An export template and an import template are two separate records with different API addresses, even for the same site. Creating a template, the schedule, run history, and the log are shared by all types — see Export templates.

    Horoshop export template form: header with status pill and the Connection card
    1API URL
    2API login
    3Status pill
    1. API URL — the address of the Horoshop site API the data is sent to.
    2. Login — the API user the export connects as.
    3. Status pill — shows the template is Active.

    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