Elbuz fetches the Brain B2B price list itself: dealer price, RRP and stock at your pickup point, plus full cards if needed.
When you need this:
- You sell what can be picked up at your Brain point — the price list has only products in stock there.
- Products must enter the catalog with description and photos — Brain cards fill in within minutes, then are only topped up.
- You also sell made-to-order goods — the whole Brain catalog arrives.
- Purchase orders must go to Brain — Elbuz fills the Brain cart, places the order and reserves the goods.
Where to start: get the company manager's login for the Brain portal.
What the Brain integration does
- Imports the Brain price list — names, Brain code, SKU, brand, dealer price, RRP, short description, warranty, category and product link.
- Takes the stock of your pickup point or the whole Brain catalog, including made-to-order products.
- Converts dollar prices at the Brain rate and keeps RRP in hryvnias.
- Fills in full product cards — description, all specifications and photos, barcode, weight and dimensions.
- Sends orders to Brain from a document, reserves the goods and pulls in the status.
The Brain category code and name come with every product; you match them to your categories as with any price list (category matching).
What you need from Brain: manager sign-in and pickup point
- Login and password for the Brain wholesale portal. There's no separate key, but Brain only lets an account with company manager (administrator) rights into the API. If your rights are lower, ask your company's administrator on the portal or your Brain manager.
- The number of your pickup point. It decides which stock comes in. You don't need to look it up on the portal — after connecting, the “Get reference data” button shows it.
- You don't have to provide an IP address. If your Brain manager asks for the address requests will come from, it's in the access parameters window (where exactly).
Which Brain request parameters to set
In the new source wizard, at the “From where” step, choose the “API” tile and BRAIN in the list. Elbuz sets the address https://api.brain.com.ua/, the format and the columns itself (what the binding does). Enter your Brain portal details in “Login” and “Password (token)”.
Then click “Get reference data”: Brain shows pickup points and delivery services with their , warehouses, and currencies with rates. Enter your point's ID in “Pickup point (ID)”. This button creates nothing in Brain.
| Parameter | Default | What it does |
|---|---|---|
| “Language” | ua | language of names, descriptions and specifications: ua or ru |
| “Pickup point (ID)” | 29 | the point Brain builds the price list and stock for; replace it with yours |
| “Price list scope” | 0 | 0 — the stock of your point, 1 — the whole Brain catalog; don't use 2 (details) |
| “Import discounted products” | 0 | 1 — only Brain's marked-down products are imported instead of the regular price list |
| “Full product cards” | 1 | 1 — description, specifications and all photos from Brain; 0 — price list only (details) |
| “Merge specification values” | 1 | 1 — specifications with the same name become one: “Socket: 1156 / 2011 / AM4” instead of three “Socket” rows; 0 — each value in its own row, as in Brain |
| “Specification value separator” | / | the character between merged values; for a comma or semicolon the space goes only after the character: “INTEL, AMD” |
| “Order: pickup point / delivery (ID)” | empty | where Brain prepares the order; empty — the same point as for the price list |
| “Order: currency” | USD | order currency in Brain: USD or UAH |
1
Pickup point (ID)2
Price list scope3
Full product cards4
Order: currency- Pickup point (ID) — the ID of your own pickup point, taken from “Get reference data”.
- Price list scope — 0 is the stock of your pickup point, 1 is the whole catalog.
- Full product cards — 1 loads the description, specifications and photos from Brain.
- Order: currency — the currency in which the order is placed in Brain.
In sources connected earlier, “Language” may be ru and “Full product cards” 0: cards aren't turned on for older sources automatically, because the first fill takes a few minutes.
How much of the catalog to take: “Price list scope” and stock
“Price list scope” isn't an “in stock only” filter — it chooses how much of the catalog Brain sends. We tested all three values on the same pickup point:
| Value | What comes in | Size (measured 03.10.2026) |
|---|---|---|
| 0 | only products in stock at your pickup point; all of them in stock | about 25.7 thousand items, 24 MB |
| 1 | the whole Brain catalog: products at your point plus those you can order from other warehouses and those currently unavailable | about 210 thousand items, 190 MB; about 184 thousand of them out of stock |
| 2 | a short price list: code, prices and stock without names and brands | the same 210 thousand |
- 0 — for a shop that sells what can be picked up at its own point.
- 1 — when you also sell made-to-order products: they come in with the “Out of stock” status, and the import takes longer.
- 2 doesn't work as the main source: without names, a product can't be shown or matched with the catalog.
Stock
Brain sends stock in the Available attribute: 0 — the product isn't available, 1, 2 or 3 — it is. It's a grade, not a unit count: the Brain price list has no exact quantity. Standard statuses recognize these values without setup: 1 and up — “In stock”, 0 — “Out of stock”.
The quantity of such products is nominal: the “In stock” status adds its “Default quantity” to 1–3, giving, for example, 101–103. If you need the same quantity for all, turn off quantity detection by number in the status (details).
Stock is tied to the pickup point. If the price list shows stock for the wrong city, check “Pickup point (ID)”.
What comes in the Brain price list
The Brain price list is an XML file where all product values sit in the attributes of the <product> tag. Elbuz asks Brain for a link to the file and downloads it; if the Brain server sends no data for 10 minutes, the download breaks off (when the price list didn't arrive).
Columns the binding maps on its own:
| Brain attribute | Field in Elbuz | Note |
|---|---|---|
Code | “Supplier SKU” | Brain code (like U0000707); the product goes into orders by it |
ProductID | product identifier in the price list, and also “JAN (Japanese Article Number)” | numeric Brain ID; full cards are matched by it |
Article | “Manufacturer SKU” | |
Name | “Name” | |
Vendor | “Manufacturer” | |
PriceUSD | “Price” | dealer price, always in dollars |
RetailPrice | “RRP” | retail price, always in hryvnias |
Available | “Stock status (from price list)” | 0 — not available, 1–3 — available (stock) |
Description | “Short description” | a short list of specifications in one line |
Warranty | “Warranty” | in months |
CategoryID | category ID from the price list | for category matching |
URL | “Product link (URL)” | product page on the wholesale portal |
Other attributes — Model, CategoryName, Country, UKTVED, RecommendedPrice, DayDelivery (in how many days the product will be at your point), Bonus — can be taken by any free column row: enter the attribute name in “Column address”. You can write the address as a plain name (Name) or in square brackets ([Name]).
The Brain price list has no photos or full description at any “Price list scope” value — they only come with full cards.
1
Name address2
Price in USD3
RRP in UAH4
Full description address- Name address — it can be written with or without square brackets.
- Price in USD — the Brain dealer price is always in dollars.
- RRP in UAH — the Brain recommended retail price is always in hryvnias.
- Full description address — the full description from the Brain product card.
Price in dollars, RRP in hryvnias and the Brain rate
The Brain dealer price PriceUSD is always in dollars, and the RRP RetailPrice is always in hryvnias. In the “Columns” section, the “Price” row must have USD and the “RRP” row UAH. No multi-currency needed. The Brain price list has a DDP attribute, but it doesn't mark the currency: with DDP 0 and 1 the price is in dollars all the same. Don't confuse it with ERC, where the ddp tag does tell the price currency.
The “RRP” row has USD. Then the hryvnia RRP is multiplied by the rate, and the retail price comes out dozens of times higher. Set UAH. New Brain sources are mapped correctly on their own; the mistake shows up in sources connected earlier.
Brain rate. If “Take currency rates from the file (currencies tag)” is on in the source card, “XML structure” block, before each import Elbuz takes Brain's non-cash hryvnia rate and applies it to the dollar “Price” and “RRP” rows. The log shows “Supplier USD rate: ‹number›”.
If you turn the checkbox off, the columns keep the last Brain rate; change it manually or in the currency directory.
How to get full Brain product cards
Brain sends descriptions, specifications and photos through a separate method, not in the price list. Elbuz fetches them so the import doesn't drag on for hours:
- In batches of a thousand products per request: the first fill of 25 thousand cards takes about 4–5 minutes (measured 03.10.2026).
- Separately from the price list. The “Import” button doesn't erase cards, so the next import doesn't start from scratch.
- Only the difference: products not yet among the saved cards and those Brain has marked as changed. That's usually a minute; the run itself with cards takes about a minute and a half longer per 25 thousand products.
- Only for products in stock. A made-to-order product gets its card as soon as it appears in stock.
How to turn them on
- Turn on cards: in the request parameters, enter
1in the “Full product cards” row. No separate key is needed: cards are fetched with the same login and password. - Optionally, choose how specifications are shown: the “Merge specification values” and “Specification value separator” rows. After a change, just import the price list again — cards aren't downloaded anew.
- Import the price list with the “Import” button. The log rows “Brain full cards: ‹N› of ‹N›” show the progress.
- Check descriptions, specifications and photos in the price list products.
| Data from the Brain card | Where it goes in the price list | Column address |
|---|---|---|
| full description (with HTML markup) | “Full description” | content_description |
| barcode | barcode | content_ean |
| weight, width, height, depth | “Weight”, “Width”, “Height”, “Length” | content_weight, content_width, content_height, content_depth |
| all photos | price list product photos | the picture tag, no separate address needed |
| all specifications | price list product specifications | the param tag, no separate address needed |
Card addresses are mapped in all Brain sources, older ones too; Elbuz keeps your own addresses in these rows. The “Load attributes” and “Load photos” toggles (“Products” section, “What data to load” block) turn on automatically with cards. The file in the log (“File received: …”) is several times bigger with cards — that's expected.
A product added from the price list to the base catalog arrives with a filled card, and specifications are matched to your attributes (product attributes, product photos). About 7 in 10 Brain products have a description, in our measurement. Elbuz discards Brain placeholder photos (“no photo”). After a “Language” change, cards are filled in anew in that language.
How to send an order to Brain and reserve the goods
A purchase order created in Elbuz for the Brain contact is sent to Brain from the document. Settings are the “Order: pickup point / delivery (ID)” and “Order: currency” rows in the request parameters; Elbuz 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: Brain receives a real order. Then Elbuz, in one go:
- checks that the Brain cart is empty;
- puts the document lines in it by Brain code; identical products are combined into one row;
- places the order for the specified point and in the specified currency, with the comment “Elbuz ‹document number›”;
- reserves the goods. Brain sets the reservation period — usually until the next day; the date comes in the message.
The Brain order number is saved in the document, the status from the supplier is “Reserved”, and the result appears in the message and the document history. Shipping, delivery to the customer and dropshipping are arranged on the Brain portal.
1
Send to supplier2
Refresh status from supplier- Send to supplier — cart, checkout and reservation in Brain.
- Refresh status from supplier — the order type and state in Brain.
Why Elbuz stops when the cart isn't empty
Brain has one cart per account, shared with the portal. Products already in it would end up in your order, so Elbuz adds nothing and shows “The Brain cart already has items — place or clear them on the Brain portal and send again”. It doesn't touch the cart.
If Brain refuses at the cart or checkout stage, Elbuz clears the cart. What was just added disappears — along with any product someone added on the portal in those seconds.
When nothing is sent
- a line has no Brain code — the product isn't matched with the Brain price list; the names of such lines are in the message (product matching);
- the document has no lines with a quantity above zero;
- Brain rejected the login or password from the source settings;
- the Brain cart isn't empty.
- A repeat doesn't create a duplicate. If the document already has a Brain order number, clicking again asks for the state of the existing order: “The order has already been sent to Brain — not created again” or “No Brain order with this number was found”.
- Reservation failed, but the order exists. The message is “Could not reserve (…) — reserve the order on the Brain portal”, and the status from the supplier is “Created”.
Status from Brain
The status doesn't update on its own — only with “Refresh status from supplier” in the menu next to the send button. Brain replies with type and state separated by a slash, in its own words, for example «Бронь / Обробка» (reservation / processing) or «Відвантаження / Обробка» (shipment / processing).
Scenarios
Add Brain products to the catalog with description and photos right away
What to do. “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 descriptions, specifications and photos from Brain. Later imports update prices and stock and fetch cards only for new and changed products.
Also sell made-to-order products
What to do. “Price list scope” = 1. To see in how many days a product will be at your point, enter DayDelivery in a free column row.
What you get. The price list has the whole Brain catalog: products available at your point are “In stock”, the rest are “Out of stock”. The file is several times bigger and the import takes longer.
Switch to another pickup point
What to do. “Get reference data” → ID of the new point → “Pickup point (ID)”. Orders go there too — leave “Order: pickup point / delivery (ID)” empty or enter the same ID. Run the import.
What you get. The price list and stock follow the new point. Saved cards aren't lost: they don't depend on the point.
What to do when the Brain price list didn't arrive or came in empty
| What you see | Why | What to do |
|---|---|---|
| The import runs, but the price list has zero products | In the previous version, column addresses without brackets didn't read Brain attributes | Run the import again; if there are still no products, check “Price list scope” (not 2) and the log (what comes in) |
| RRP in the price list is dozens of times too high | The “RRP” row has USD, but Brain RRP is in hryvnias | Set UAH (price, RRP and rate) |
| Products without names or brands | “Price list scope” = 2 — the short price list | Set 0 or 1 (price list scope) |
| No photos or specifications | “Full product cards” = 0, or the product isn't in stock | Set 1 and run the import (full cards) |
| “Brain full cards were not received (…) — the price list is imported with the cards saved earlier” | Brain refused the card request, for example because of a request limit | Nothing: the price list was imported, new cards will be fetched next time |
| “Supplier API error: sid empty Incorrect login or password” | Wrong login or password, or the account has no company manager rights | Check your Brain portal details (what you need from Brain) |
| “The Brain cart already has items…” when sending an order | The shared Brain cart has someone else's lines | Place or clear the cart on the Brain portal and send again |
| “Some lines have no Brain code…” | The document product isn't matched with the Brain price list | Match the product with the Brain price list (product matching) |
When the price list didn't arrive: what the log says
If Brain refused or the file didn't download, the import log shows “Supplier API error: …” with the reason:
- “sid empty Incorrect login or password” — wrong login or password;
- “Brain price download failed: …” — the file didn't download;
- “targetID empty” — “Pickup point (ID)” isn't filled in.
In all these cases the run uses the previous file: price list products are updated with yesterday's data (why).
FAQ
Does the “Import” button erase saved Brain cards?
No. Descriptions, specifications and photos are stored separately from the price list, and a new import doesn't delete them — it only adds products that are new or changed in Brain.
Why is the Brain product quantity 101 or 103?
Brain sends a grade of 1–3, not units, and the “In stock” status adds “Default quantity” to it. How to make the quantity the same — see stock.
Why is the RRP from Brain so high?
Brain RRP is always in hryvnias. If the “RRP” row in the “Columns” section has USD, the hryvnia amount is multiplied by the rate. Set UAH.
Can I import only certain brands or categories from Brain?
Not on Brain's side. You cut out what you don't need in Elbuz with ignore rules.
Can I ship a Brain order or arrange dropshipping from Elbuz?
No. Elbuz takes the order as far as reservation; shipping and delivery to the customer are arranged on the Brain portal.
Where it is and who has access
- Menu
- Directories → Processing price lists → List of price lists
- New Brain source
- new source wizard, the “From where” step → the “API” tile → BRAIN
- 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
- the Brain portal login and password with company manager rights
Related topics
- To understand what Elbuz does with any API source and where to enter access details — How to connect a supplier via API.
- If Brain stock statuses aren't recognized correctly — Stock in a supplier price list.
- If cards arrived but specifications don't fit your attributes — Product attributes.
- If the purchase order still has to be built from customer orders — Purchase orders.
