Elbuz pulls the price list from TDB B2B (Техніка для бізнесу) with your dealer login and password: UAH prices, stock, and optionally descriptions, photos, and specifications from the TDB catalog.
When you need this:
- TDB gave you a price list link — it holds the login, password, and price list number.
- You want catalog products with photos and descriptions — full cards update daily.
- You keep prices in UAH — no exchange rate needed: TDB has converted the price.
- You sell only from the Lviv or Kyiv warehouse — stock comes from that warehouse.
Where to start: take the login, password, and price list number from the TDB link.
What the TDB integration does
- TDB price list with no manual mapping — product code, manufacturer SKU, Ukrainian name, brand, dealer price and RRP, warranty, barcode, category, and stock.
- Prices in UAH at the TDB rate — or in USD at your own rate, if that's how you keep prices.
- Full product cards — description, all photos, weight, dimensions, and specifications; products are added to the base catalog already filled in.
- Total stock or stock per warehouse — Lviv or Kyiv.
The general mechanics of ready-made integrations — the wizard, the access settings window, column mapping — are covered in How to connect a supplier via API. This article covers only what is specific to TDB.
Where to get the login, password, and price list number
All three values are in the price list link that TDB gives its dealers in TDB . It looks like this: https://api.tdb.ua/hs/get_price/get_xml?username=…&pass=…&priceid=….
- after
username=— the login; - after
pass=— the password; - after
priceid=— the price list number.
If you don't have the link, ask your TDB manager for it.
Which TDB request parameters to fill in
- In the new source wizard, at the “From where” step, choose the “API” tile and “TDB” in the list. Elbuz fills in the address, the format, and the columns itself (what exactly it does).
- In the “API access settings” window, enter your TDB login in “Login” and your password in “Password (token)”.
- In the “Request parameters” card, enter the number from
priceid=in the “TDB price list number” row.
The “Get reference data” button shows nothing for TDB — you'll see the message “This integration has no reference data…”.
| Parameter | Default | What it does |
|---|---|---|
| “TDB price list number” | empty | the number after priceid= in the TDB link; without it the price list won't import |
| “Full product cards” | 1 | 1 — description, photos, dimensions, and specifications from the TDB catalog (details); 0 — price list only |
| “Merge specification values” | 1 | 1 — specifications with the same name become one, with values joined by the separator; 0 — each value on its own row |
| “Specification value separator” | / | the character between merged values |
1
TDB price list number2
Full product cards- TDB price list number — the number after priceid= in the link TDB gives you.
- Full product cards — 1 loads descriptions, specifications and all photos from the supplier; 0 turns it off.
Once the source is connected, it works like any other price list: import and import schedule.
How to switch from a link to the integration
A source that imports the TDB price list via a get_xml link keeps working as before, but it has no full product cards. Elbuz doesn't convert such a source on its own. To get the cards:
- create a new source through the “TDB” integration for the same supplier;
- enter the login, password, and price list number from the link;
- import the new source — and disable the old one.
You no longer need a separate source for the content.xml catalog: the integration fetches the cards itself.
Which fields come from TDB
TDB sends the price list as a single XML file. The columns of a TDB source are XML tag names. Columns the binding maps automatically:
| Column | What it contains | Field in Elbuz |
|---|---|---|
| id | TDB product code | “Supplier SKU”; the card is linked to the product by it |
| manufacturerCode | manufacturer SKU | “Manufacturer SKU” |
| name | name in Ukrainian | “Name” |
| manufacturer | brand | “Manufacturer” |
| Category | TDB category — name only, no nesting | “Price category” |
| price_r_uah | dealer price, UAH | “Price” |
| price | retail price, UAH | “RRP” |
| stock_all | total stock | “Stock status (from price list)” (stock) |
| barcode (not every product has one) | “EAN barcode” | |
| warranty | warranty, months | “Warranty” |
| content_description, content_weight, content_width, content_height, content_depth | description, weight, and dimensions from the full card | “Full description”, “Weight”, “Width”, “Height”, “Length” (filled in when full product cards are on) |
The file has other tags too, and you can take any of them with a free row in the “Columns” section:
price_r— dealer price in USD;price_gurt— wholesale price in USD;stock_lvivandstock_kyiv— stock at the Lviv and Kyiv warehouses;UKT ZED— the UKT ZED (Ukrainian customs) code.
1
Supplier SKU = id2
Price = price_r_uah3
RRP = price- Supplier SKU is taken from the id field of the feed.
- Price is taken from price_r_uah, in UAH.
- RRP is taken from price, in UAH.
Which price to use: UAH or USD
The binding takes the dealer price in UAH — price_r_uah, so you don't need to maintain an exchange rate in Elbuz. TDB calculates prices in USD and converts them to UAH at its own rate. The currency is set by the UAH code, not by the currency's sequence number in the directory.
RRP is the price tag: the TDB retail price in UAH. If you keep prices in USD, put the price_r tag in the “Price” row and set the currency to USD — the rate from your currency directory will then apply.
How to get descriptions, photos, and specifications
Set “Full product cards” = 1 (new sources already have it). The TDB price list has no photos or descriptions: TDB publishes them in a separate content.xml catalog — description, all photos, packed weight and dimensions, specifications. Elbuz handles it like this:
- Downloads the catalog once a day. It's small, and TDB updates it constantly.
- Stores cards separately from the price list. The “Import” button doesn't erase them, and each import of the price list gets the saved cards.
- Decodes specifications into ready values. For example, «Тип: Підставка для ноутбука», «Охолодження: Активне» (Type: Laptop stand, Cooling: Active).
Almost every product has photos and specifications, but TDB doesn't write descriptions for all of them. When you add a product from the price list to the base catalog, the card arrives filled in, and the specifications are matched to your attributes (product specifications, product photos).
During import, the log shows the line “TDB full product cards: ‹how many› saved”.
How TDB stock is read
The binding takes stock from the stock_all tag — total stock. TDB shows the exact number up to 5 units, then thresholds: “>5”, “>30”, “>80”. The standard statuses recognize this with no setup: any number means “In stock”, and the quantity is the threshold itself: “>30” becomes 30 units, “>80” becomes 80.
Need stock from a specific warehouse? Put the stock_lviv or stock_kyiv tag in the “Stock status (from price list)” row. Warehouses can also show “Call” — the product is available on request; so it isn't treated as out of stock, add a rule for this word on the source's “Availability” tab (product stock in a supplier price list).
Scenarios
Add TDB products to the catalog with photos and descriptions right away
What to do. Set “Full product cards” = 1, import the source, then add products from the price list to the base catalog as usual.
What you get. New products in the catalog get the description, photos, weight, dimensions, and specifications from TDB. Later imports update prices and stock, and the cards are updated once a day.
Sell only what's in stock in Lviv
What to do. In the “Columns” section, in the “Stock status (from price list)” row, replace stock_all with stock_lviv.
What you get. Products not at the Lviv warehouse (stock 0) are treated as out of stock.
Keep TDB prices in USD
What to do. In the “Price” row, replace price_r_uah with price_r and set the currency to USD.
What you get. The dealer price is converted at the rate from your currency directory, not at the TDB rate.
What to do when the TDB price list doesn't arrive
Why the price list didn't update
If TDB responds with an error, Elbuz doesn't overwrite the price list: prices and stock stay from the previous import. If TDB doesn't return the card catalog, the price list still imports with the saved cards, and the cards update next time. The general mechanics are in the article on ways to get a price list.
| What you see | Why | What to do |
|---|---|---|
| “Supplier API error: TDB get_xml…” with the text «Користувач не зареєстрований» (User not registered) | Wrong login or password | Check them against the TDB link: after username= and pass= (where to get them) |
| “TDB: enter your TDB B2B account login and password…” | Login, password, or “TDB price list number” is empty | Enter the three values from the TDB link (parameters) |
| “TDB full product cards were not received (…) — the price list is imported with the cards already saved” | TDB didn't return the card catalog | Nothing: the price list imported, and the cards will update during the next import |
| Quantity 105, 130, or 180 instead of 5, 30, 80 | Older versions counted it this way: “Default quantity” was added to the number | Import the price list again — the quantity will be recalculated |
| Products have no photos or descriptions | The source is connected via a link, or “Full product cards” = 0 | Switch to the “TDB” integration (how to switch) and set it to 1 |
FAQ
Why do TDB products have a quantity of 30 or 80?
TDB shows exact stock only up to 5 units, then thresholds: “>5”, “>30”, “>80”. Elbuz takes the lower bound: 5, 30, or 80.
How often are TDB photos and descriptions updated?
Elbuz downloads the card catalog once a day; prices and stock update with every price list import.
Can I send an order to TDB from Elbuz?
No. The TDB service provides only the price list and the catalog; orders are placed in your TDB account.
Where do I get the dealer price in USD or the wholesale price?
They're also in the TDB file: price_r is the dealer price in USD, price_gurt is the wholesale price in USD. Put the tag you need in the “Price” row or in a free row of “Columns” (prices).
Does the integration build the TDB category tree?
No. The category in the TDB price list is just a name, with no nesting. You match it to your categories as usual (category matching).
Where to find it and who has access
- Menu
- Directories → Processing price lists → List of price lists
- New source
- new source wizard, the “From where” step → the “API” tile → “TDB”
- Access and parameters
- source card, the “Source” section → “API settings”
- Access right
- the “List of price lists” window plus “Import settings” and “…price list file”
- Prepare
- the price list link TDB gave you
Related topics
- If you need the overall picture of ready-made integrations and the parameters window — How to connect a supplier via API.
- If the price list has imported and you need to set up the schedule and import — price list import.
- If on-request products or stock thresholds aren't handled the way you expect — product stock in a supplier price list.
- If TDB specifications don't map onto your attributes — product specifications.
