↑↓ selectEnter openEsc close

    1. Elbuz

    How to connect the Comportal price list: dealer.xml with all photos and specifications

    3 min readUpdated

    Elbuz fetches the comportal dealer price list itself — the dealer.xml file from comportal.kz: price in tenge, stock, brand, model, warranty, category, all photos and product specifications.

    When you need this:

    • You need all product photos, not just one — every photo in the price list comes in.
    • Brand, model and warranty sit among the parameters — the binding maps them to fields itself.
    • Your manager gave you a personal price list link — the app will download from it.
    • Prices must update often — the file is small and arrives in seconds.

    Where to start: new source wizard → the “From where” step → the “API” tile → “Comportal”.

    What the Comportal integration does

    Prices and stock update on a schedule, like any price list source. How ready-made integrations work in general is covered in How to connect a supplier via API.

    Where the app gets the Comportal price list

    The app takes the price list from https://www.comportal.kz/auth/documents/prices/dealer.xml — the Comportal dealer price list in format. The source needs no login or password. If your Comportal manager gave you a different, personal price list link, enter it in “API Server URL” — the app will download from it.

    Don't confuse it with “ComPortal ESD” in the same integration list: that's a separate integration for esd.comportal.kz electronic keys and licenses, with its own login and password.

    How to connect Comportal

    1. In the new source wizard, at the “From where” step, choose the “API” tile and “Comportal” in the list.
    2. Click “Import” — the first price list arrives in a few seconds: the file is small, about a thousand products.

    The app fills in the price list address, sets the format, the product node offer and the category node category, maps the columns, turns on photo and specification import and sets the KZT currency (what the binding does). Comportal has no request parameters: whatever is in dealer.xml is what comes in.

    What comes from Comportal

    The columns of an XML price list are tag names. Brand, model and warranty have no tags of their own in the Comportal price list — they sit among the product parameters, so the binding takes them with an expression like param[@name="Бренд"].

    ColumnWhat's in itField in Elbuz
    [id]Comportal product code (offer attribute)“Supplier SKU”
    articulmanufacturer part number“Manufacturer SKU”
    namename“Name”
    fullnamefull name with brief specifications“Short description”
    param[@name="Бренд"]brand“Manufacturer”
    param[@name="Модель"]model“Model”
    param[@name="Гарантия"]warranty“Warranty”
    stockwarehouse stock“Stock status (from price list)” and “Quantity”
    categoryIdComportal category codeprice list category
    priceprice, tenge“Price”

    The file has other tags too, and you can take any of them with a free row in the “Columns” section:

    • articul_quality — product condition (new or not);
    • inReserve — reserved stock;
    • TnVedCode — TN VED (HS) commodity code;
    • any parameter: param[@name="Цвет"] gives the color.
    Products tab of the Comportal source filtered by brand DELL, with the Product preview gallery on the right
    1Brand filter
    2Product photo and stock in the row
    3Product preview gallery
    1. Brand filter — here limited to DELL, 197 rows in this cabinet.
    2. Each row shows the supplier's photo, brand and stock status.
    3. Product preview — the selected row's photo gallery, model and description.

    How Comportal stock is read

    The binding takes availability and quantity from the stock tag — the number of units in the Comportal warehouse. Standard statuses read a number from 1 up as “In stock” with that quantity, and 0 as out of stock (stock status in a supplier price list).

    Which specifications to take into the catalog

    Each param tag becomes a specification: processor, memory, panel type, color, ports, etc. Service parameters come too: “Процент скидки” (discount %), “Дата начала акции” (promo start), “Товары в пути” (in transit), “Специальная цена” (special price), etc. They aren't filtered out but the catalog doesn't need them: leave them unmatched to your attributes, and they stay off product cards (product specifications).

    Scenarios

    Download the price list from a personal link

    What to do. Get the link to your price list from your Comportal manager and enter it in “API Server URL” in the source's API settings window.

    What you get. The app downloads exactly your price list; if the link stops working, the reason shows up in the log and the old prices stay.

    Show the product color on your site as a separate field

    What to do. In the “Columns” section, add a row for the field you need with the address param[@name="Цвет"].

    What you get. The color goes into that field, not only into specifications. Any other Comportal parameter is taken the same way.

    Update prices every hour

    What to do. In the Comportal source schedule, set an hourly import (import and schedule).

    What you get. The price list is small and comes as a single file, so frequent updates take seconds and don't load the app.

    What to do when the Comportal price list didn't arrive

    Why the price list didn't update

    If Comportal didn't return the price list (link closed or changed, or site down), the source log shows “Supplier API error: Comportal dealer.xml: …” with the server response code, e.g. “HTTP 403”, and the start of the page Comportal returned. The price list isn't overwritten: prices and stock stay from the last import (how it works in general).

    Common problems
    What you seeWhyWhat to do
    “Supplier API error: Comportal dealer.xml: HTTP 403 …” Comportal closed the link or changed the price list address Get the current link from your Comportal manager and enter it in “API Server URL” (where the price list comes from)
    The price list shows “HP”, but Comportal has “HP Europe” The manufacturer directory merges brand name variants into one Nothing: this way products from different suppliers end up under one manufacturer
    The price list has only keys and licenses The source was set up with “ComPortal ESD”, not “Comportal” Create a new source with the “Comportal” integration

    FAQ

    Do I need a Comportal login and password?

    No. The app takes the dealer.xml dealer price list from a link (where the price list comes from).

    What currency are Comportal prices in?

    Tenge. The binding sets the KZT currency by code.

    How is “Comportal” different from “ComPortal ESD”?

    “Comportal” downloads the dealer.xml product price list. “ComPortal ESD” is a separate integration for electronic keys and licenses with its own login and password.

    Why are discount percent or goods in transit among the specifications?

    These are Comportal service parameters, such as “Процент скидки” and “Товары в пути”. Don't match them to your attributes, and they won't reach product cards.

    Can I send an order to Comportal from Elbuz?

    No. The Comportal price list is just a file; orders are placed on the Comportal website.

    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 → “Comportal”
    Price list address
    source card, the “Source” section → “API settings” → “API Server URL”
    Access right
    the “List of price lists” window plus “Import settings” and “…price list file”
    Prepare
    Comportal dealer access; if needed, a personal link to dealer.xml

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free