Elbuz pulls categories, products (prices, stock, descriptions in both languages) and customer orders from your Horoshop site via the Horoshop API, no files needed. The site stays your storefront; price lists, markups, stock and marketplaces live in Elbuz.
When you need this:
- Your catalog lives on the site — Elbuz keeps a copy with categories, SEO fields and photos.
- Site orders are handled with the rest — they arrive as documents with customer and items.
- Prices are set in Elbuz — a field formula recalculates the site prices.
Where to start: create an API user in Horoshop's admin panel and add it to an “API - CMS Horoshop” template.
What the Horoshop connection does
- Categories — the site's category tree with names in two languages.
- Products — prices, stock, descriptions, SEO fields, photos, variants linked by the parent SKU.
- Updates — a repeat run finds each product by SKU and updates it without duplicates.
- Orders — with the customer, delivery, payment and line items.
The opposite direction — updating products on the site from Elbuz — is handled by a separate export template: exporting the catalog to Horoshop.
What you need from Horoshop
| Template field | What to enter |
|---|---|
| Link () | Your site's API address: the store domain with /api/ at the end |
| Login | The login of the API user created in the Horoshop admin panel |
| Password | That user's password |
You create the login and password in the Horoshop admin panel under “Settings” → “Admins” («Налаштування» → «Адміни»). Set up a separate user for the integration rather than using your own admin account: that access is easier to revoke and reissue.
Horoshop returns names and descriptions in the languages enabled on the site. For the Ukrainian version to come through, Ukrainian must be in the “Languages” list of your Elbuz account. Check this before the first import.
Horoshop issues a temporary access key for about ten minutes, and Elbuz gets a new one on its own before every operation. So an authorization error almost always means a wrong address, login or password, not an “expired token”.
Integration details on the platform side: Horoshop API — how to enable access and which functions your plan supports.
How to connect, step by step
- Create a template of the “API - CMS Horoshop” type and enter the API address, login and password.
- Save it and run the import manually.
- Check that the category tree matches the site, and compare a few products: price, stock, descriptions in both languages.
In the “What to import” card only one checkbox works: “Orders”. The connection always imports categories, products and photos. “Import photo”, “Import attributes”, “Fill the manufacturer list” and “Delete entries in the base catalog that are not in the imported file” don't affect the run: it adds manufacturers on its own, doesn't import attributes and deletes nothing.
What goes into the product card
Categories first, then products
First Elbuz pulls the site's categories with their nesting and names in Russian and Ukrainian and builds the category tree from them. Existing categories are updated, new ones are added, and the site's hierarchy is kept. Only then are products imported, in pages of 500 until there are none left.
Product fields
| Horoshop data | Product field in Elbuz |
|---|---|
| SKU | SKU — the main key for matching |
| parent product SKU | Links variants into a family |
| catalog section | Category |
| name, variant name | Name (in Russian and Ukrainian) |
| name for Rozetka | A separate name field for the marketplace |
| brand | Manufacturer |
| manufacturer part number (), | MPN and barcode |
| price and old price, currency | Price, old price |
| availability, quantity | Stock status and quantity |
| short description and description | Short description, description (in two languages) |
| SEO title, keywords, description, | SEO fields (in two languages) |
| friendly URL and product link | Product address on the site |
| photos | Photos (as links to the site's images) |
The SKU is how a product is recognized on repeat imports, and how variants are linked to the main product. SKUs on the site must be unique and must not change: to Elbuz, a changed SKU is a new product, and the old card stays.
Specifications from Horoshop are not imported: the API returns the values but not human-readable specification names, so there's no way to build an attribute table from them. If you need specifications, fill them in Elbuz or pull them from a supplier price list or a manufacturer feed.
What a repeat import does to your edits
The next run looks for each product by SKU: if found, it's updated; if not, it's created. Whatever came from the site is overwritten; everything else stays yours.
- Action or result
- Decision: the path depends on the answer
| Card field in Elbuz | What the next run does with it |
|---|---|
| Price, old price | Overwrites with the site value; leaves cards with the “Fixed Price” flag alone |
| Quantity | Overwrites with the quantity from the site |
| Stock status | Overwrites: Elbuz looks up the site's availability name in its stock status list and keyword lists; if nothing matches, it sets the status marked as “In stock” in that list |
| Card active status | Mirrors whether the product is shown on the site: hide a product on the site and its card in Elbuz becomes inactive |
| Name, in both languages | Overwrites with the name from the site, or the variant name for a variant |
| Short description and description | Overwrites |
| SEO title, keywords, SEO description, H1 | Leaves alone. These fields are filled only when the card is created — after that they're yours |
| Product category | Overwrites with the site category; the product's category list is cleared and rebuilt before writing. If the site category isn't in the tree, the category and category list stay as they were |
| Manufacturer, MPN, barcode, site address | Overwrites if the field is filled on the site; an empty value from the site doesn't erase yours |
| Photos | Adds links the card didn't have yet; doesn't delete existing images. Adds no new links to a card with the “Do not update photo” flag |
- “Do not update” on a card — the run doesn't change it at all: not the price, quantity, texts, category or photos.
- “Fixed Price” — the price and old price stay yours; everything else is updated.
- A field formula with the “Apply when importing the catalog from external sources” flag in the “Field formulas” window is calculated at the end of every import, at the “Updating values based on formulas” step, on top of the imported values.
Whose value wins when two sources write to one field
There's no source priority: the Horoshop import, catalog updates from price lists and manual edits write to one field, and whoever ran last wins (what a repeat run overwrites). If prices come from a price list but the catalog arrives nightly from the site, the card shows the site price until an export sends yours or the card is protected.
The export sends to the site only the fields marked “Update” (exporting to Horoshop). The rest stays with the site, and the next import brings it back.
Your own category tree and deleting categories
Every import restores category names and tree positions from the site. Rename or move a category in Elbuz and the run puts it back. Same with products: a card moved into your category returns to the site category. For a product to stay in your category, that category must also exist on the site.
Deleting a category also deletes all products for which it's the main category, with descriptions, photos, attributes and friendly URLs. Empty the category first, then delete it. Lines of imported orders keep their own name, SKU, price and quantity — only the link to the card disappears.
How to import orders from the site
Turn on the “Orders” checkbox in the “What to import” card. The catalog is imported as before, and orders are added as a separate step at the end.
1
Orders checkbox- Orders — turns on loading of orders from the site.
| Horoshop data | Document field in Elbuz |
|---|---|
| order number | Document number (used to recognize the order again) |
| order date | Order date |
| recipient name | First and last name (the string is split in two) |
| email and phone | Email, phone |
| customer ID on the site | Links the contact to the source |
| delivery city and address | Delivery address |
| delivery method, delivery cost | Delivery type, delivery price |
| payment method | Payment type |
| paid flag | Payment status “Paid” |
| order status | Document status (through mapping) |
| customer comment | Order description |
| total and currency | Document total, currency |
| line items: SKU, name, price, quantity, total | Document lines |
- Statuses, payment types and delivery services come from Horoshop as its own codes. Map them with the buttons in the “Related settings” card — there are separate tables for order statuses, delivery, payment and payment types. An unmapped status arrives as “New”, the payment status as “Pending”; a paid order gets “Paid” right away.
- The customer is looked up by email, phone and site ID; if not found, a new contact is created. An order with no email and no phone goes to the “End consumer”.
- Line items find cards by SKU and by the stored link between the card and the site — not by searching names.
- An order that's already imported isn't overwritten: there's no duplicate, but changes from the site don't reach it either.
- The selection window — the Horoshop API has no date filter, so the first run pulls the entire history and later runs start from the previous import with a twelve-hour margin.
- Action or result
- Decision: the path depends on the answer
What an imported order does to stock
Nothing. The order arrives as an unposted “Customer order” document: quantity doesn't change, no reservation is made and nothing is written off until a manager posts the document.
- Reservations count only posted orders, and only with inventory tracking turned on.
- A reservation is released by a final status — “Done”, “Completed”, “Issued”, “Canceled”, “Rejected”, “Returned” and the like.
- Goods are physically written off by a sales invoice.
- The only thing the import changes in a card is “Number of sales” — it's recalculated across all customer orders.
Scheduled updates
Once a template is checked, put it on a schedule — how scheduling works for API sources. A large catalog takes noticeably longer than a marketplace: every page of 500 products carries descriptions and SEO fields.
Run size
- Products and orders are pulled in pages of 500 for as long as the site returns a non-empty page. There's no upper limit.
- Elbuz waits up to five minutes for the site to respond and up to a minute to connect. If it doesn't get a response, fetching breaks off with an error, and the run continues with whatever has arrived.
- Export to the site goes in batches of 1,000 products.
- You can close the window: the run and its log live in the Operations Center, which also has the “Stop” button.
- Only one scheduled import runs at a time; if cron is busy, the run is canceled with the line “Scheduled import canceled due to another template being imported (data processing conflict).”
What happens if you disable the template
The “Active” / “Disabled” switch in the template header only decides whether the schedule and the “Import all templates” button pick up the template. The address, login, mappings, export settings and imported data stay. The “Import” button in the form works on a disabled template too.
1
Active badge2
Run history button- Active badge — turns the template on and off for the schedule.
- Run history button — opens the history of runs.
Deleting a template doesn't erase data either: only the template and its schedule disappear, while products, categories, contacts and orders stay, marked with their source.
How to check that the run worked
The log is kept in the Operations Center. Its lines name the current step:
- “Requesting a list of categories” → “Adding product categories” → “Updating product categories” → “Updating category keys”;
- “Requesting a list of products” → “Requesting products, items: 1 - 500” → “Determining manufacturers for products” → “Determining product availability”;
- “Adding products” → “Updating products” → “Importing product photos”;
- “Updating values based on formulas” → “Data integrity check” → “Product indexing”;
- “Data import completed!” and “Time spent”.
The log gives no “created, updated, skipped” counts for the catalog: “Total imported: 500” is just the page limit. Counts exist only for orders: “Orders received: N” and “Total orders imported: M” — how many documents were created.
Check the catalog result in the data:
- the “Last import” column in the template list — when the run happened and how long it took;
- the “Run history” button in the template header — earlier runs with their statuses;
- the “Source: name” and “Date updated” columns in the product grid — which cards the run touched.
Scenarios
The catalog is managed on the site and you need a copy in Elbuz
What to turn on. An “API - CMS Horoshop” template with the API address, login and password, without the “Orders” checkbox, plus a schedule.
What you get. Every run updates the category tree, then products: new cards get SEO fields and photos, existing ones get price, quantity, availability, name and descriptions from the site, except cards with “Do not update”. Specifications won't arrive, products removed from the site stay in Elbuz, and a product whose category isn't in the tree gets no card.
Import site orders into Elbuz
What to turn on. The “Orders” checkbox and mapping of order statuses and payment types in the “Related settings” card.
What you get. After the catalog, the run pulls orders: the first run takes the entire history, later ones use a twelve-hour margin. A new order becomes a “Customer order” document for an existing or new contact. An order already imported won't be updated; an unmapped status arrives as “New”.
Prices are calculated in Elbuz, but the catalog arrives from the site every night
What to turn on. In the “Field formulas” window — a price formula with the “Apply when importing the catalog from external sources” flag.
What you get. The run writes the site price, and at the “Updating values based on formulas” step the formula recalculates it. To keep a specific card's price unchanged, use the “Fixed Price” flag.
You started an import at the wrong time and want to stop it
What to click. “Stop” in the Operations Center.
What you get. Until the page fetching ends, products stay unchanged; categories that have already arrived won't be rolled back (interrupted run).
What to do when an import goes wrong
| What you see | Why | What to do |
|---|---|---|
| “API authorization error. Check the site address, login and password.” | The address doesn't end with /api/, the login is wrong, or API access is turned off on the site |
Check them in exactly this order (what you need). The “Data import completed!” line at the end of the log doesn't mean success |
| New products didn't appear | Categories didn't arrive: a product with no category in the tree is skipped silently | Run it again; if it happens again, look in the log for the site's response to the category request |
| Duplicate cards | SKUs were changed on the site | Remove the old cards manually (the SKU is the key) |
| “Error getting product catalog” | The connection to the site dropped | Run it again (interrupted run) |
If a run breaks off midway
Categories come first — they're written right away. Then products: pages are collected in a temporary file and loaded into the catalog in one step after the last page. Orders come last. General rules are in the overview.
- Action or result
- Decision: the path depends on the answer
- “Stop” while pages are being fetched — products won't change: the stop is checked before every page and before writing. The log shows “Operation aborted by user!”, the operation turns yellow, formulas, the integrity check and indexing don't run, and “Last import” isn't updated. Categories stay updated.
- Connection to the site drops — the pages already received still go into the catalog; the log shows “Error getting product catalog” and the site's response.
- The run died on its own (time limit exceeded, server restart) — nothing from the products is written.
Repeating is safe: the temporary file starts from scratch, products are matched by SKU, and orders aren't created twice.
If the wrong data was imported
An import doesn't take “before” snapshots (general rollback procedure).
- Find what was affected — filter the product grid by “Source: name” and “Date updated”.
- Bulk rollback works only for your own bulk edits: bulk field changes and find-and-replace give an “Undo” button for the last five operations no older than a day. It doesn't apply to imports.
FAQ
What do I enter in the link field?
The site's API address: the store domain with /api/ at the end. The login and password belong to the user from “Settings” → “Admins” in the Horoshop admin panel.
Why weren't product specifications imported?
The Horoshop API returns specification values without human-readable names, so there's no way to build an attribute table. All other fields come through in full.
What happens if I change a product's SKU on the site?
The product arrives as new, and the old card is left without a match: the SKU is the main key for matching and for linking variants.
A product disappeared from the site — will it be deleted in Elbuz too?
No, the Horoshop import deletes nothing. Products hidden on the site become inactive in Elbuz, and products removed completely stay as they were.
Can I skip importing photos?
No, the “Import photo” checkbox has no effect on Horoshop. To stop new photos being added to a specific card, use the “Do not update photo” flag on it.
Where to find it and who has access
- Menu
- Operations → Data import → template of the “API - CMS Horoshop” type
- Access right
- the “Import” window in “Group permissions”
- Have ready
- the site's address and the API user's login and password
1
API URL field2
Login field3
Password field- API URL — the address of the store's Horoshop API.
- Login — the API user's login.
- Password — the API user's password.
Related topics
- If prices and stock from Elbuz need to go back to the site — exporting the catalog to Horoshop.
- If a repeat run overwrites your edits — data import overview.
- If an order got attached to the wrong customer — importing orders via API.
