Elbuz fetches the MTI Distri price list itself — dealer price and RRP in hryvnias, stock quantity, barcode, warranty, brand and MTI category — no files, no currency conversion.
When you need this:
- Customers need to see the stock — quantity arrives automatically: exact up to 9 units, then 10 or 50.
- You need to pass purchase orders to MTI — one button in the document sends it, the MTI number is saved back.
- Orders must go to another warehouse or payer — the warehouse, accounting type, payer and address are set in the source parameters.
Where to start: ask MTI for your company ID and API key.
What the MTI integration does
- Imports the MTI price list — MTI code, part number, model, name in Ukrainian, brand, barcode, dealer price and RRP, warranty, category.
- Takes the stock quantity — exact up to 9 units, then “10 or more” and “50 or more”.
- Sends orders to MTI from a document; the MTI order number is saved in the document.
Company ID and API key from MTI
The MTI API needs two things, and MTI issues both: a company ID and a key the app uses to sign every request. Ask your MTI manager for them or write to MTI API support at support_dd@mti.ua.
The ID goes into “Login”, the key into “Password (token)”. If they're wrong, MTI refuses, and the reason shows in the log (when the price list didn't arrive).
How to connect MTI and set the order parameters
In the new source wizard, at the “From where” step, choose the “API” tile and “MTI”. The app sets the address https://api.mti.ua/, the format and the columns itself (what the binding does). For MTI, “Get reference data” only shows “This integration has no reference data…”: get the payer and delivery address codes from your MTI manager.
The parameters in the “Request parameters” card apply only to sending orders; they don't affect the price list. Sources connected earlier have the default values.
| Parameter | Default | What it does |
|---|---|---|
| “Order: MTI accounting type” | NS | NS, BS or US — the order type at MTI; change it only if agreed with your MTI manager |
| “Order: MTI warehouse” | W600 | the warehouse MTI picks the order from: W600 or W300 |
| “Order: MTI payer (code)” | empty | the payer code at MTI; empty — your default payer at MTI |
| “Order: MTI delivery address (code)” | empty | the delivery address code at MTI; empty — your default address at MTI |
1
Order: MTI accounting type2
Order: MTI warehouse3
Order: MTI payer (code)- Order: MTI accounting type — NS by default.
- Order: MTI warehouse — W600 or W300.
- Order: MTI payer (code) — empty means the default payer.
What comes from MTI: XML tags and prices in hryvnias
MTI returns the price list as a single XML file, and the columns of an MTI source are tag names, not numbers. Columns the binding maps itself:
| Column | What's in it | Field in Elbuz |
|---|---|---|
| productgroup_id | MTI category | “Price category” — by code; the app takes the category name from the category list in the same file |
| mticode | MTI product code | “Supplier SKU” — the product goes into the order by it |
| partnum | part number | “Manufacturer SKU” |
| model | model | “Model” |
| prodname | name in Ukrainian | “Name” |
| brand | brand | “Manufacturer” |
| price_uah_order | dealer price, UAH | “Price” |
| rrp | RRP, UAH | “RRP” |
| store | warehouse stock | “Stock status (from price list)” (availability) |
| barcode | barcode | “EAN barcode” |
| guarantee | warranty, months | “Warranty” |
1
Price2
Stock status (from price list)3
Supplier SKU- Price — price_uah_order: the dealer price in hryvnias.
- Stock status (from price list) — store: the stock quantity.
- Supplier SKU — mticode: the MTI code used for ordering.
Other tags are taken with a free row in the “Columns” section by entering the tag name in “Column address”:
prodname_invoice— name for the invoice;country— country of manufacture;tnved— UKT ZED customs code;nds— VAT rate;weight— weight;length,width,heightandvolume— dimensions;reserved— how many are already in your unshipped orders;similar_products— codes of similar MTI products;rrp_control— RRP control (Y or N);purchase— purchase terms (FOB, DDP).
MTI doesn't provide photos, descriptions or specifications via API.
Price and RRP
MTI's dealer price and RRP are in hryvnias, so the “Price” and “RRP” rows must be set to UAH; new sources are mapped this way automatically. The dollar price in the MTI price list is empty, so no currency conversion is needed. If you sell at RRP, take rrp_control with a free row and watch products marked Y.
Availability and quantity: exact up to 9 units
The binding takes availability from the store tag. MTI shows the exact quantity from 1 to 9 units, and more as text: “10 и более” (from 10 to 49) and “50 и более” (from 50). Products with no stock aren't in the price list.
Standard statuses recognize this without any setup: any number from 1 is “In stock”. The app takes the quantity from the same tag: 1–9 as is, “10 и более” as 10, “50 и более” as 50. You don't need a separate “Quantity” row.
The warehouse doesn't affect the price list: MTI returns the same price list for W600 and W300. The warehouse matters only for orders.
How to send an order to MTI
A purchase order created in Elbuz for the MTI contact is sent from the document, and MTI creates a real order. 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 this document has already been sent to MTI;
- sends the lines by MTI code; identical products are merged into one line;
- passes the accounting type and warehouse, the comment “Elbuz ‹document number›” on each line, and the payer and address only if they're set.
The MTI order number is saved in the document, the status from the supplier is “Created”, and the result appears in a message and in the document history.
1
Send to supplier2
Refresh status from supplier- Send to supplier — places the order with the supplier (MTI).
- Refresh status from supplier — pulls the supplier's order number and current status.
When MTI didn't add everything
In its response, MTI lists the products that made it into the order. If one is missing, the app shows “Warning: MTI did not add to the order: ‹products›”, and the status from the supplier becomes “Partially created”. Check those lines in your MTI account and order them with a separate document.
When nothing is sent
- a line has no MTI code — the product isn't matched with the price list; the message lists such lines by name (product matching);
- the document has no lines with a quantity above zero;
- MTI refused — its text follows “MTI:”, no number is saved in the document, so after fixing it you can send the document again.
Sending again doesn't create a second order. If the document already has an MTI order number, clicking again shows “The order has already been sent to MTI (number ‹number›) — not created again.” Each document is a separate MTI order.
Order status
MTI doesn't report order status via API, so “Refresh status from supplier” only reminds you of the MTI order number. Status, reservation, shipment, changes and deleting the order — in your MTI account.
We tested sending orders against a simulated MTI server, not a real order. Make your first order a small one and check the result in your MTI account.
Scenarios
Show customers the exact stock
What to do. Nothing: the quantity comes from the store tag by itself.
What you get. Products with 1–9 units have the exact quantity, the rest show 10 or 50. If your site shows “only N left”, for these products it's the lower bound.
Orders to another warehouse or payer
What to do. In the API parameters, set “Order: MTI warehouse” = W300, and in “Order: MTI payer (code)” enter the payer code from your MTI manager.
What you get. Orders from Elbuz are created at MTI for that warehouse and that payer.
Add weight and country of manufacture to the catalog
What to do. In the “Columns” section, enter the weight tag in the “Weight” row, and country in a free row.
What you get. Weight and country arrive with the price list and can go into the product card when products are added to the catalog.
What to do when MTI refuses or didn't add everything
| What you see | Why | What to do |
|---|---|---|
| “Supplier API error: MTI: Компания с указаным идентификатором не найдена” (company with this ID not found) | The source's “Login” has the wrong company ID | Enter the ID issued by MTI (ID and key) |
| Products have a quantity of 101, 110 or 150 instead of 1, 10, 50 | That's how older versions counted: the standard statuses' “Default quantity” was added to the number | Import the price list again — the quantity will be recalculated |
| Status “Partially created” | MTI didn't add some lines to the order — they're listed after “Warning:” | Check those products in your MTI account and order them with a separate document |
| “No MTI code on the lines…” | The document's product isn't matched with the MTI price list | Match the product with the MTI price list (product matching) |
| “The order has already been sent to MTI…”, but you need a new one | The document already has an MTI order number | Create a new “Purchase order” document |
When the price list didn't arrive
In the import log, work with MTI shows as the lines “Getting file via API” and “File received: ‹size› MB”. If MTI responded with an error, the log shows “Supplier API error: MTI: ‹text from MTI›”:
- “MTI: Компания с указаным идентификатором не найдена” — the “Login” has the wrong company ID;
- a signature rejection — the key is wrong.
The price list isn't overwritten then: prices and availability stay from the previous import (why). If the error is on MTI's side, you can send the request and response text to MTI API support.
FAQ
Can I import product photos and descriptions from MTI?
No. The MTI API returns a price list with prices, availability, barcode, warranty, weight and dimensions, but no photos, descriptions or specifications.
Why do MTI products have a quantity of 10 or 50?
MTI shows the exact quantity only up to 9 units, then “10 or more” and “50 or more”. The app takes the lower bound: 10 or 50.
Will a duplicate be created if I click “Send to supplier” twice?
No. If the document already has an MTI order number, the app doesn't send it again and shows that number.
Can I see in Elbuz that an MTI order has shipped?
No. MTI doesn't report order status via API, so check the status in your MTI account.
Will discounted products come from MTI?
No. The MTI price list via API contains only regular products, without discounted items or products in damaged packaging.
Where to find it and who has access
- Menu
- Directories → Processing price lists → List of price lists
- New MTI source
- new source wizard, the “From where” step → the “API” tile → “MTI”
- Access and order 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
- your company ID and key from MTI
Related topics
- If you need to understand what the app does with any API source and where to enter access details — How to connect a supplier via API.
- If MTI quantities or statuses need to be calculated differently — Product availability in a supplier price list.
- If you need to take an extra MTI tag into a column — Price list column mapping.
- If the purchase order still needs to be built from customer orders — Purchase orders.
