Elbuz pulls the Yug-Contract B2B price list with the dealer price, RRP, stock and photos, plus full product cards if needed.
When you need this:
- Prices go into the catalog without conversion — the dealer price and RRP are in UAH.
- Products get added with a description and photos — cards come by whole categories and are kept between imports.
- “Expected” and “on request” must differ from out of stock — the state code maps to your statuses.
- Purchase orders need a reservation at Yug-Contract — sent from a document; resending creates no duplicate.
Where to start: generate an API key in your Yug-Contract account and allow the Elbuz IP.
What the Yug-Contract integration does
- Imports the Yug-Contract price list — code, SKU, name in Ukrainian, brand, barcode, dealer price and RRP, warranty, weight, category, stock, photo, short description and product link.
- Fills in full product cards — HTML description, all specifications and all photos.
- Tells stock states apart — in stock, reserved, expected, on request.
- Sends orders to Yug-Contract from a document: Yug-Contract creates the order and reserves the products.
API key and allowed IP address in your Yug-Contract account
- API key and secret. In your Yug-Contract account, open “API settings” and click “Generate” — a new key pair appears. The key goes into “Login”, the secret into “Password (token)”.
- The Elbuz IP address on the allowed list. Yug-Contract lets into the API only from addresses added in the same “API settings” section. Copy the address from the source's access settings window — the line “IP address of the Elbuz Jumper server to give to the supplier for access:” (where exactly).
Without these two steps, Yug-Contract refuses with a 403 error (when the price list didn't arrive).
Which Yug-Contract request parameters to set
In the new source wizard, at the “From where” step, choose the “API” tile and “Yug-Contract”. The app sets the address https://b2b.yugcontract.ua/api/, format and columns itself (what the binding does). “Get reference data” only shows “This integration has no reference data…”: find customer and contract codes in your Yug-Contract account, API section, post-order method.
| Parameter | Default | What it does |
|---|---|---|
| “Full product cards” | 1 | 1 — HTML description, specifications and all photos from Yug-Contract (details); 0 — price list only |
| “Merge specification values” | 1 | 1 — specifications with the same name become one: “Socket: 1156 / 2011 / AM4” instead of three rows; 0 — each value on its own row |
| “Specification value separator” | / | the character between merged values; for a comma or semicolon, a space goes only after the character |
| “Order: payment” | cash | cash — cash payment, bank — bank transfer; Yug-Contract uses it to choose the contract if none is set |
| “Order: warehouse priority” | 0 | 0 — regional warehouse first, then Kyiv; 1 — Kyiv first, then the region; 2 — Kyiv only. Works if this option is enabled in your Yug-Contract account |
| “Order: customer (ID)” | empty | your customer code in Yug-Contract; empty — Yug-Contract determines it itself |
| “Order: contract (ID)” | empty | contract code; empty — Yug-Contract determines it itself by payment type |
1
Full product cards2
Order: payment3
Order: warehouse priority- Full product cards — 1 loads the description, specifications and photos from Yug-Contract; 0 does not import them.
- Order: payment — cash is cash payment, bank is bank transfer.
- Order: warehouse priority — 0 means the regional warehouse first, then Kyiv.
In sources connected earlier, “Full product cards” is off (0). In new sources, cards are on from the start.
What comes from Yug-Contract: columns by number
Yug-Contract returns the price list via API, and the app builds a CSV file from it: each product is a row, each field is a numbered column. Columns the binding maps on its own:
| Column | What's in it | Field in Elbuz |
|---|---|---|
| 1, 2 | Yug-Contract category and subgroup | “Category from price list” (the two columns together) |
| 5 | brand | “Manufacturer” |
| 6 | Yug-Contract product code | “Supplier SKU” and “Product ID (UUID string)” — by this code the product goes into the order, and card specifications and photos are linked |
| 7 | name in Ukrainian | “Name” |
| 8 | dealer price, UAH | “Price” |
| 10 | RRP, UAH | “RRP” |
| 13 | stock | “Stock status (from price list)” (stock) |
| 14 | SKU | “Manufacturer SKU” |
| 15 | barcode | “EAN Barcode” |
| 21 | warranty | “Warranty” |
| 24 | weight | “Weight” |
| 27 | short description | “Short description” |
| 28 | link to the product page in your Yug-Contract account | “Product link (URL)” |
| 29 | photo | “Link to product photo” |
| 30 | full description from the card | “Full description” (filled in when full cards are on) |
Other columns are taken with a free row in the “Columns” section by entering the number in “Column address”:
- 3 and 4 — subgroup and category codes; 12 — stock state code;
- 9 — price per minimum pack; 11 — controlled RRP; 18 — price excluding VAT; 19 and 20 — VAT rate;
- 16 — name in English; 17 — condition (New or ДУ); 22 — country; 23 — UKT ZED customs code;
- 25 — minimum pack weight; 26 — volume.
Price and RRP in UAH
At Yug-Contract, the dealer price (column 8) and RRP (column 10) are in UAH, so the “Price” and “RRP” rows should have UAH; new sources are mapped this way automatically. Yug-Contract doesn't send an exchange rate, and there's nothing to convert.
Column 11 is the controlled RRP: the amount below which Yug-Contract asks you not to sell the product; 0 means no control. The price list comes with products in the “New” and “ДУ” condition; it contains no discounted products.
1
Price2
Stock status (from price list)3
Link to product photo4
Full description- Price — address 8: the dealer price in hryvnia.
- Stock status (from price list) — address 13: stock levels as bands.
- Link to product photo — address 29: the photo from the price list.
- Full description — address 30: the description for the product card.
How to get full Yug-Contract product cards
In the price list, Yug-Contract provides one photo and a short description. It returns full cards separately, and not per product but by whole categories. So the app works like this:
- Requests only the categories it needs — those with a product that has no card or a card older than 30 days. The first time, this is almost the whole catalog and takes a few minutes; after that, usually no categories at all.
- Keeps cards separately from the price list. The “Import” button doesn't erase them.
- Fetches cards only for products in stock and reserved. “Expected” and “on request” products come without cards.
- Remembers when a card is missing. The app doesn't ask again about such products for 30 days and gives them the photo from the price list.
- Refreshes cards every 30 days. Yug-Contract doesn't send a list of changes, so a card corrected yesterday is refreshed once it turns 30 days old.
How to turn it on
- Turn cards on: in the request parameters, enter
1in the “Full product cards” row. No separate sign-in is needed: cards are fetched with the same key. - Optionally, choose how specifications are shown: “Merge specification values” and “Specification value separator”. If you change them, import the price list again — the cards aren't downloaded again.
- Import the price list with the “Import” button. When the app requests missing cards, the log shows “Yug-Contract full cards: request for ‹how many› categories”.
- Check the description, specifications and photos in the price list products.
| Data from the Yug-Contract card | Where it goes in the price list |
|---|---|
| full description (with HTML markup) | “Full description” — column 30 |
| all photos | price list product photos |
| all specifications | price list product specifications |
Photos and specifications are linked by the Yug-Contract code (column 6), so no extra column addresses are needed. A product with a card gets all its photos; the rest get one photo from column 29.
When you add a product from the price list to the base catalog, its card arrives filled in (product specifications, product photos). If Yug-Contract didn't return the cards, the log shows “Yug-Contract full cards were not received (…) — the price list is imported with the cards saved earlier”; new ones are fetched next time.
How to tell “expected” and “on request” apart
The binding takes stock from column 13, the stock level. It has no exact quantities: Yug-Contract gives steps (1, 2 … 10, 50, 100, 500), above zero only for products in stock; “reserved”, “expected” and “on request” have 0. Standard statuses handle this without setup: 1 and above — “In stock”, 0 — “Out of stock”.
To tell the states apart, take the state code from column 12:
| Code | State at Yug-Contract |
|---|---|
| 0 | none |
| 1 | in stock |
| 2 | reserved |
| 3 | expected |
| 4 | on request |
Set address 12 in the “Stock status (from price list)” row and add rules for the statuses you need on the source's “Availability” tab (product stock in a supplier price list). Without your own rules, codes 2, 3 and 4 — like any number from 1 — become “In stock”.
The binding doesn't map the “Quantity” row. If you enter 13 there, the quantity is a step, not an exact number.
How to send an order to Yug-Contract with reservation
A purchase order created in Elbuz for the Yug-Contract contact is sent from the document; Yug-Contract creates a real order and reserves the products. The settings are the “Order: …” rows in the request parameters; the app takes them from the first active API source of the document's contact.
What happens after you click
Open the “Purchase order” document, click “Send to supplier” and confirm. The app:
- checks whether Yug-Contract already has an order from this document;
- sends the lines by Yug-Contract code; identical products are combined into one line;
- passes the internal Elbuz document (Yug-Contract later finds this order by it), the comment “Elbuz ‹document number›”, the payment type and warehouse priority, and the customer and contract only if they're set.
The Yug-Contract order number is saved to the document, the status from the supplier is “Reserved”, and the result appears in the message and the document history.
1
Send to supplier2
Refresh status from supplier- Send to supplier — places the order with a reserve at the supplier.
- Refresh status from supplier — shows how much is in reserve.
When not everything is reserved
The order is created even if Yug-Contract didn't reserve some of the products. The app lists those lines after “Warning:”, and the status from the supplier is “Partly reserved”:
- “‹product› — reserved ‹how many› of ‹how many›” — there wasn't enough stock in the warehouses;
- “‹product› — Yug-Contract did not find the product by code, not added to the order” — match the product with the current price list.
Order the rest or replace missing items in your Yug-Contract account or with a separate document.
When nothing is sent
- a line has no Yug-Contract code — the product isn't matched with the price list; the names of such lines are in the message (product matching);
- the document has no lines with a quantity above zero;
- Yug-Contract didn't let the app in — a wrong key or secret, or the IP address isn't on the allowed list (a message with “403”).
Sending again doesn't create a second order. Yug-Contract knows the order by the Elbuz document ID, so clicking again shows “The order already exists in Yug-Contract — not created again.” and the state of the existing order.
Order status
The status doesn't update on its own — only with “Refresh status from supplier” in the menu next to the send button. It shows “Yug-Contract: order ‹number›, ‹how many› pcs reserved.”, and the status from the supplier is “Reserved”, or “Not reserved” if nothing is left in reserve.
We tested sending orders against a simulated Yug-Contract server, not a real order. Make your first order a small one and check the result in your account.
Scenarios
Add Yug-Contract products to the catalog with a description and photos 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 catalog products get the description, specifications and photos from Yug-Contract. Later imports update prices and stock and fetch cards for new products.
Don't sell below the controlled RRP
What to do. In the “Columns” section, add a free row with address 11. Leave the “RRP” row at address 10: far from every product has a controlled RRP.
What you get. The Yug-Contract controlled RRP appears in the price list; 0 means the product has no price control.
Bank-transfer order on a specific contract
What to do. In the API parameters, set “Order: payment” = bank, and in “Order: contract (ID)” enter the contract code from your Yug-Contract account.
What you get. Orders from Elbuz are created on this contract with bank-transfer payment.
What to do when Yug-Contract returns 403 or the price list is incomplete
| What you see | Why | What to do |
|---|---|---|
| “Supplier API error: Yugcontract auth: 403 Error: Forbidden” | Wrong key or secret, the new key pair isn't entered in the source, or the Elbuz IP address isn't on the allowed list | Check the key and secret, add the IP address from the access settings window to “API settings” in your account (key and IP) |
| The source was connected long ago, and the price list has no photos or descriptions | Columns 27–30 and the product key weren't mapped in older sources | Import the price list again; turn on “Full product cards” if needed |
| “Expected” and “on request” products come in as “Out of stock” | Stock is taken from the stock level, and for them it's 0 | Take the state from column 12 and add your own rules (stock) |
| The “Partly reserved” status | Yug-Contract didn't reserve or didn't find some lines — they're listed after “Warning:” | Order the missing items in your account or with a separate order (when not everything is reserved) |
| “Some lines have no Yug-Contract code…” | The document product isn't matched with the Yug-Contract price list | Match the product with the Yug-Contract price list (product matching) |
When the price list didn't arrive
Yug-Contract takes longer to build its price list than most suppliers — up to a few minutes, and the first import with cards takes even longer. In the log, work with it shows up as “Getting file via API”, “Connecting to the API server” and “File received: ‹size› MB”.
With a wrong key or a missing Elbuz IP address, the log shows “Supplier API error: Yugcontract auth: 403 Error: Forbidden”, followed by “No new file received, using the previous one”. Prices and stock then stay as of yesterday (why).
FAQ
Why does Yug-Contract return 403?
Yug-Contract lets into the API only from IP addresses added in “API settings” in its account, and only with a valid key pair. Add the address from the access settings window and check that the source has the key and secret of the most recently generated pair.
Will photos arrive without full cards?
Yes, one photo per product — from the price list photo column. With full cards, a product that has a card gets all its photos.
Will a duplicate be created if I click “Send to supplier” twice?
No. Yug-Contract knows the order by the Elbuz document ID, so clicking again only shows the state of the existing order.
Can I confirm shipment or delete a Yug-Contract order from Elbuz?
No. Delivery, shipment confirmation and order deletion are handled in your Yug-Contract account.
Can I import discounted Yug-Contract products?
No. The API price list contains only products in the “New” and “ДУ” condition.
Where it is and who has access
- Menu
- Directories → Processing price lists → List of price lists
- New Yug-Contract source
- new source wizard, the “From where” step → the “API” tile → “Yug-Contract”
- Access and request parameters
- source card, the “Source” section → “API settings”
- Sending an order
- “Purchase order” document → “Send to supplier”
- Access right
- the “List of price lists” window plus “Import settings” and “…price list file”; for orders — editing documents
- Prepare
- an key and secret from your Yug-Contract account, and the Elbuz IP address on the allowed list
Related topics
- If you need to understand what the app does with any API source and where to enter credentials — How to connect a supplier via API.
- If the states from column 12 should be mapped to your own statuses — Product stock in a supplier price list.
- If you need an extra Yug-Contract column — Price list column mapping.
- If the purchase order still has to be built from customer orders — Purchase orders.
