↑↓ selectEnter openEsc close

    1. Elbuz

    How to track shop prices on Hotline.ua

    15 min readUpdated

    Elbuz pulls competitor prices from Hotline.ua — shops selling your products — plus specifications, photos, and descriptions, straight into your price list.

    When you need this:

    • What do your products sell for on Hotline — the module finds the pages and fetches prices every run.
    • What each competitor charges — each product gets shops with price, availability, warranty.
    • You benchmark against one or two competitors — the row price counts only shops you've marked.
    • Your catalog lacks specifications and photos — Hotline becomes a content source; the fast module adds the barcode.

    Where to start: choose a module and create a source in the connection wizard.

    What the Hotline parser can do

    Which Hotline module to choose and what a run costs

    Hotline appears twice in the list of ready-made parsers, and that's not a mistake. These are two different ways to get the same data.

    “Hotline”
    regular parsing: the program downloads a page and breaks it down using selectors
    “Hotline (API)”
    fast module: data is fetched in batches from the site's own programming interface

    The difference isn't in the settings but in the unit of work. The regular module gets one downloaded page and parses it. The fast one queries the site in batches: forty products per request (shop offers — twenty, they're heavier), and pages aren't downloaded at all. For the same number of products, a run is many times faster.

    In the wizard's list of ready-made modules, these two rows differ only by name — “Hotline” and “Hotline (API)”, with the same logo and the address hotline.ua. In the “Product content search” window, where the same list of sites is used to fill in product cards, the fast module is also marked with the “⚡ Fast” label.

    The fast module has one limitation: it works only in server mode — you can't run it through the browser extension. If your plan doesn't include server crawling, the regular module is your option. Another advantage of the fast one: it brings the barcode and the full description, which can't be extracted from a regular page.

    From here on, everything not marked separately applies to both modules.

    What a run costs

    You pay not for products in the price list but for the work of our server — and the billing unit differs between the two modules.

    ModuleWhat is billed
    Hotlineeach downloaded page: one request — one cost line. A section page is one request, each product page is another
    Hotline ()products fetched from the source. Forty products arrive in one request, but forty products are billed, not one request

    For the fast module, the bill has three parts: your own products from the watch list, other products from section links, and the same products once more if shop offers were collected for them. The second depth is a separate pass over the site, not a free add-on to the price.

    Both modules are billed at the regular server rate: the premium anti-bot bypass mode isn't needed for Hotline and doesn't turn on. Crawling through the browser extension isn't billed at all: your browser makes the requests, not our server. On a fixed-price plan, the regular module isn't billed; the fast one is billed there too.

    You can see what was spent in the “Balance” window on the “Transaction history” tab (a separate article covers the balance). The charge isn't made at the moment of the run: costs accumulate as lines, a separate background job deducts them from the balance, and they appear in the history as a total per operation type.

    If your balance runs short, the run won't stop because of it and won't show a warning: only the premium anti-bot bypass mode checks the balance in advance, and Hotline doesn't use it. The charge simply makes the balance negative — what happens next is covered in the balance article.

    How to create a source and limit the crawl

    The steps are the same as for any source: the wizard asks who the data comes from (“Who”) and where to get it (“From where”). At the “Who” step, choose an existing contact or type a name — for example, “Hotline, monitoring”. At the “From where” step, choose the site — the “Ready-made parsers” block expands; find the Hotline row you need there.

    Ready-made parsers list in the new source wizard with the Hotline and Hotline (API) rows
    1Hotline
    2Hotline (API)
    1. Hotline — the regular module: it parses the site pages it loads.
    2. Hotline (API) — takes data in batches through the site API, runs many times faster and works only in server mode.

    A ready-made module's settings are shared by all sources built on it. No copy is created for your price list: if you've set up two sources on “Hotline (API)”, changing a checkbox in one changes how the other behaves. When there's more than one source, the window warns you about it with a line above the tabs.

    List of links

    The “List of links” tab is a list of starting addresses. You enter either Hotline section addresses or the addresses of specific product pages. The “This is a link to a product” checkbox in a row means the address goes straight to product page parsing; without it, the address is treated as a section from which product links must be collected first.

    How much to take from a section is set on the “Additional” tab: “Max. number of pages from category” and “Max. number of products from the category”. Zero in both means “no limit” — for a first try, that's almost never what you want.

    A Hotline section page returns exactly 48 products, no matter how many you ask for — tested with requests for 100, 200, and 500. The fast “Hotline (API)” module doesn't read the pages field: it goes through a section page by page while products keep coming, and only “Max. number of products from the category” stops it. Start with one or two hundred products, look at what arrived, and only then lift the limit.

    There's also a ceiling you can't bypass with settings: the fast module takes no more than 200 pages from one section. That's nine thousand products — more than the largest section on the site, so in practice you hit it only when “Max. number of products from the category” is set to zero.

    City: why prices differ from what you see

    Hotline shows prices and the number of offers by region. If no city is set, the site determines it from the request address — and requests go through proxies, so the region can differ every time. The result is unpleasant: the same product returns a different price and a different number of sellers in different runs, and you go looking for an error in the settings.

    The “City ID (code, name)” field on the source settings tab settles this. The fast module defaults to 187 — Kyiv. Enter your city's code, and the numbers become stable and comparable between runs.

    The interface has no hint with city codes — these are Hotline's own internal numbers. It's easier to check by the result: take one product, look up its price on the site with your city selected, and compare it with what arrived in the price list. If they match, the code is right.

    How to collect offers from all shops

    A regular update brings one price from the product page — the minimum for the product. The “Collect shop offers” checkbox turns on the second depth: a list of sellers is fetched for every product.

    Only the fast module can do this. In the regular one, seller list parsing is turned off — the Hotline page became dynamic, and sellers can no longer be extracted from a downloaded page; its settings don't have the checkbox either.

    What comes with an offerWhy
    price and currencythe market snapshot itself
    availabilityto tell a real offer from “made to order”
    warrantyto compare terms, not just numbers
    deliverysame
    shop: name, website, logo, ratingto know exactly who is undercutting
    link to the product in the shopto check the price manually

    The “Offers per product” field limits the list length; the default is 200.

    Where to see offers for a product

    Collected offers appear in the side panel of a base catalog product, in the collapsible “Competitor prices” section: a table where each row is a shop and its offer: “Price”, “Seller”, “Availability”, “Warranty”, “Delivery”, “Name”, SKUs and description, website, rating, the shop's city and phone, a link to reviews, and “Date added”.

    The section takes offers from the price list rows that are matched to this product: until a Hotline row is linked to the product card, the section is empty. The side panel of a parser price list row has the same section — there you see offers even before matching.

    If a product has no shop offers, the section shows matched rows from price lists of contacts in the “Competitor” group: the supplier in the “Seller” column, price, availability, warranty, delivery, name, SKUs, and date; the shop columns (website, rating, city) are empty there. The section is visible to groups with the “Sidebar: competitor prices” access block; without it, “Product price history” also disappears from the panel.

    The checkbox is off by default for a reason: roughly a hundred times more data arrives than with a regular price update. On a long product list, that means both run time and database volume. Turn it on when you really need a breakdown by competitor, not just “to have it”.

    How a run works and how to tell it finished

    You start the source from the price list card with the “Import” button — the “Import data from the site” window opens, with a “Start download” button in it. In the fast module, the “Update prices” button on the “My products” tab in the source settings does the same.

    The fast module fills the price list in two ways, in this order:

    1. the price list is cleared — rows from the previous run are deleted along with their photos, specifications, and shop offers;
    2. addresses from the “List of links” are crawled: sections page by page, individual product pages one at a time;
    3. for products from the “My products” watch list that don't have a Hotline product page yet, a match is searched for by name;
    4. prices are fetched for watched products whose product page is already known;
    5. if the offers checkbox is on, seller lists are fetched in one pass for everything that landed in the price list;
    6. at the end, price list operations (availability, markups, matching) are applied and the summary table is recalculated.

    Until the sixth step is done, the job isn't finished, even though prices are already visible in the price list.

    The top fork checks whether there's anything to work with: if not, the price list stays as it was. The “Site didn't respond” arrows are a break-off, after which price list operations aren't run.
    NoYesYesNoSite didn't respondSite didn't respond“Start download”or “Update prices”Products in “My products”or links in the “List of links”?“The watch list is empty”price list untouchedPrice list is clearedCrawl the “List of links”Search product page by namefor products without onePrices for productswith a known page“Collect shop offers”on?Seller listsfor the whole price listPrice list operationsand “Job completed”Break-off — price list stayswithout price list operations
    • Action or result
    • Decision: the path depends on the answer

    How to tell a run finished

    Look at the run log — the same window the “Import” button opens — and at the “Last run” tile in the price list card: it shows the completion date, and clicking it opens the same log. The log lines state the numbers directly:

    • “⚡ Price monitoring: … products updated, … new matches, … requests to the source” — the fast module's summary: how many rows were written to the price list, how many products got a site product page for the first time, and how many requests went to Hotline.
    • “📂 Section “…”: … products received” — a separate line for each address from the “List of links”.
    • “🏬 Shop offers: … saved” — how many seller offers landed in the price list.
    • “Job completed” — the last line of the run. Until it appears, price list operations haven't been applied yet.

    The same numbers continue in the interface. On the “My products” tab, the “Checked” column shows when the price was last fetched for that product (for a product labeled “not found on the site” — when it was last searched for), and the “Card on the site” column shows how the match was found: the label “by SKU”, “by name”, or “not found on the site”.

    My products tab of the site data import settings window
    1Found by SKU
    2Found by name
    3Checked
    1. Card on the site marked “by SKU”: the card was found by the product SKU.
    2. Card marked “by name”: the card was found by name, so it is worth checking by eye.
    3. Checked column: when the price of the product was last collected.

    If there was nothing to collect, the log says so: “⚠️ The watch list is empty. Select products in the catalog and pick “Add to price monitoring” in the menu.” In that case the price list isn't touched — the previous data stays in place.

    The two link warnings mean different things. “⚠️ No products for … Check the address…” — Hotline answers a wrong path with an empty list, not an error, so reread the address. “⚠️ Selection … has no products…” — the address is correct, but nothing matches all the filters selected on the site at once.

    How to stop runs: disable or delete a source

    Turning off the activity toggle in the source header removes the price list from shared operations: when a batch catalog update runs across all price lists together, rows of an inactive price list aren't included. Collected prices, “My products”, the “List of links”, and seller marks stay.

    Deletion is irreversible: the price list takes its rows, the “List of links”, the seller list, category matching rules, and price history with it. More: How to temporarily disable or delete a source.

    Turning off the activity toggle doesn't stop scheduled runs. The “Parsing products from the site” scheduled task keeps its own list of price lists and its own switch: to stop automatic runs, turn off the task itself or remove this source from it (schedule and queue).

    What to do if a run breaks off

    The price list is cleared at the very start, so a break-off leaves exactly what managed to be written — the old prices are already gone. If the site doesn't respond to the very first request, the log shows “⚠️ The source did not answer, products stay in the queue:” with the error text, and the price list stays empty.

    Restarting is safe and doesn't double anything: it clears the price list again and collects everything from scratch. Whatever was written last time disappears along with everything else, so there are no duplicate products or duplicate shop offers even after several broken attempts in a row.

    A broken run is marked by the missing “Job completed” line. Price list operations (availability, markups, recalculation) run in one pass at the end, and on a broken run they didn't run at all.

    The regular module crawls through a job queue, and it behaves differently. A job that hasn't responded for too long goes back to the queue: when crawling through the browser extension — after 35 seconds, in server mode — after 150 seconds. In the log, such a retry is recorded as “no response for more than 35 sec” — regardless of the mode.

    The “Continue” button in the import window catches up on what's left in the queue without touching what's already collected; the “Cancel” button ends the run gracefully — what's collected stays, and price list operations are applied to it. In the fast module, “Continue” does the same as “Start download”: the price list is cleared and collected from scratch.

    What a repeat run overwrites and what stays

    Price list rows aren't updated in place. Before each run, the fast module deletes all products of this price list — along with their photos, specifications, and shop offers — and writes what it collects anew. So edits made by hand right in the price list product grid (price, name, availability) disappear after the next run: the price list will contain what the site returned.

    In the regular module, it depends on the “Delete products before loading” checkbox on the “Additional” tab:

    • checkbox selected — the price list is cleared just like in the fast module and collected from scratch;
    • checkbox cleared — addresses of products already collected go to an ignore list, and their pages aren't downloaded again. Old rows stay as they were, with your edits — but also with the old prices. Only products not yet in the price list arrive; the hint under the checkbox says so directly: “If this flag is not set, then only new products will be downloaded from the site”.

    What a run doesn't lose:

    • Manual matching of a price list product to a catalog product. It lives in the matched products list, separate from the rows, and is restored on every run. The key is the combination of SKU, name, and product address: if the Hotline product page's name or address changes, you'll have to set the link again.
    • Category matching rules. They're tied to the Hotline section name and applied to freshly loaded products — you don't need to rematch categories after every run.
    • Marks in the “Seller list” — “Blacklist”, “Whitelist”, “Price source”. The seller list isn't cleared along with the price list rows.

    You can lock your own value not in the price list but in the catalog product card: “Do not update” takes the product out of the batch update entirely, and “Fixed Price” keeps your price when a different one arrives from the price list. The price list itself has nothing to lock with — the row will be overwritten anyway.

    A product disappeared from Hotline

    The row simply won't appear in the price list — neither with the old price nor with zero: the price list holds what the source returned on this run and nothing more. In the “My products” list, the product stays in place, but the date in the “Checked” column won't update — that's how such items are filtered out.

    If the product page still exists on the site but is marked as archived, the row arrives, and the availability field will contain archive.

    Shop offers work the same way: they're collected anew every time. A shop that stopped selling the product disappears from the offers but stays in the “Seller list” — with zero in the “Total products” column.

    If you've already collected the wrong data

    The cheapest way is to fix the cause (set your own “City ID (code, name)”, remove an unneeded link) and run again: clearing at the start removes everything collected earlier. No separate cleanup is needed.

    When you need to remove only part of it:

    • Unneeded products. In the price list product grid, filter them — the Hotline section name is in the “Category from the price list” column — select them with checkboxes, and choose “Delete” → “Delete product” in the menu. The “Delete all products” item clears the whole price list. A row's photos, specifications, and shop offers go with it.
    • An unneeded section. On the “List of links” tab, clear the mark in the “Status” column: the row stays, but it's no longer crawled. Deleting the row does the same permanently.
    • A specific shop. On the “Seller list” tab, set it to “Blacklist” — at the end of every run its offers are deleted from the price list, so the ones already collected disappear after the next run. Requests are still spent on them: offers are fetched first and filtered out only afterwards. The opposite option is “Whitelist”: only offers from marked sellers stay in the price list.

    What comes from Hotline and where it goes

    The set is controlled by checkboxes in the source settings: specifications, photos, description, price. What Hotline provides:

    • Name and manufacturer — the way the aggregator keeps them.
    • Site section — useful for category matching.
    • Minimum price for the product.
    • Short specifications — the line shown under the name on the site.
    • Full description — only in the fast module and only with the description checkbox on.
    • Specifications — split into groups, the way they're grouped on the site.
    • Photos.
    • Barcode — only in the fast module. Rare and useful: it's a good key for matching products.

    What you won't get: reviews and videos. These checkboxes change nothing for Hotline.

    Where shops, categories, and manufacturers go

    A run brings more than prices — it adds to three different lists, and each is cleaned up differently.

    What arrivedWhere it goesWhat to do with it
    Shops from offersthe “Seller list” tab in the source settings: name, website, logo, rating, “Total products”a row is created at the end of the run for each new shop name; after that, the “Blacklist”, “Whitelist”, and “Price source” marks control it
    Hotline sectionsthe section name goes into each price list row, and the names make up the price list's category listcategory matching works with it; the list is rebuilt on every run
    Manufacturersthe manufacturer field in the price list rowprice list operations check the name against the catalog's manufacturer list

    You can delete a seller row — all its offers leave the price list with it. But that's not a way to get rid of a shop for good: the next run adds it again, with clean marks. To keep it out of the price list, set “Blacklist” — the mark survives runs, a deleted row doesn't.

    There's no point cleaning the price list's category list by hand: it's rebuilt on every run from the section names that arrived. Matching rules are stored separately and tied to the section name — as long as the name on Hotline doesn't change, your links to catalog categories stay.

    Hotline doesn't create catalog categories: site sections stay inside the price list until you match them to your own.

    Manufacturers, though, the program can add on its own — that's controlled by the general “Add new manufacturers” setting (the “Processing price lists” section). The price list product grid menu item that asks “Add new manufacturers from the price list to the manufacturer list?” does the same manually. The manufacturer list is shared across the whole catalog — names from the aggregator end up there next to yours.

    Hotline as a content source

    The second scenario, besides monitoring, is filling your own catalog. The approach is the same as with any source: collect products, match them to yours, and then transfer the fields you need with a batch update. The aggregator's specifications and photos are often more complete than what a supplier provides in a price list.

    The barcode the fast module brings makes matching more accurate: a barcode match is more reliable than a name match.

    Scenarios

    Track prices for your own products

    Goal: know what products from your catalog sell for on Hotline.

    What to turn on. A source on the “Hotline (API)” module. In the base catalog, filter the products and choose “Add to price monitoring” in the menu, then this price list in the window. Next, the “Update prices” button on the “My products” tab. In the “City ID (code, name)” field — your city's code; an empty field means 187, Kyiv.

    What you get. The Hotline product page is searched for by name once: once found, it's remembered, and later runs take the price from it without searching. The price list row gets the minimum price for the product, the maximum next to it, and the quantity holds the number of offers on Hotline. The row is linked to your catalog product, so there's no need to match it manually.

    What you won't get. A product whose page wasn't found gets the “not found on the site” label and doesn't go into the price list; on the next run it's searched for again. There won't be a seller list either until the checkbox from the next scenario is on.

    See what each competitor charges

    Goal: for each product — not one price, but a list of shops with prices, availability, and warranty.

    What to turn on. The “Collect shop offers” checkbox in the source settings (it exists only in “Hotline (API)”) and the “Offers per product” field — the list length, 200 by default. After the first run, mark shops you're not interested in as “Blacklist” on the “Seller list” tab.

    What you get. Offers are collected for everything that landed in the price list — both “My products” and products from section links. Each new shop appears in the “Seller list” at the end of the run. The price in the price list row is then the lowest among the offers.

    What you won't get. Offers from shops on the “Blacklist” don't stay in the price list: they're deleted at the end of the run, before the row price is calculated. This doesn't reduce requests — offers are fetched in full first and filtered out only afterwards.

    Compare yourself with a specific shop

    Goal: benchmark against one or two competitors rather than the market minimum.

    What to turn on. “Collect shop offers”. After the first such run, the shop you need appears in the “Seller list” — give it the “Price source” mark.

    What you get. From the next run on, the price list row price is the lowest price among offers from the marked shops, and the name of the shop that gave it is written to the row.

    What you won't get. Products the marked shops don't sell keep the Hotline minimum price. “Price source” doesn't remove other sellers from the price list — that's what “Whitelist” is for: when it's set, only offers from shops marked in it stay in the price list.

    Seller list tab with whitelist, blacklist, rating and price source columns
    1Whitelist
    2Blacklist
    3Price source
    1. Whitelist: only offers from the checked shops stay in the price list.
    2. Blacklist: offers from the checked shop are removed from the price list at the end of the run.
    3. Price source: the row price is taken as the lowest among the checked shops.

    Collect the assortment of a Hotline section

    Goal: see what sells and at what price across a whole section, not just your products.

    What to turn on. On the “List of links” tab — the section address, optionally with filters already selected on the site; a single product page — with the “This is a link to a product” checkbox. On the “Additional” tab — “Max. number of products from the category”, so you don't take the whole section. You don't need to fill in “My products” for this.

    What you get. Section products land in the price list with the Hotline section name, and the log has a line “📂 Section “…”: … products received” for each address. They aren't linked to your catalog: matching works the same as with a regular supplier.

    What you won't get. No more than 200 pages of 48 products are taken from one section. If nothing matches the address, the run doesn't stay silent: the log will have a warning with that address.

    What to do when prices or products are wrong

    What you seeWhyWhat to do
    Prices jump between runs No city is set, so the region is determined by the request address Fill in “City ID (code, name)”
    A run takes very long The regular module is selected, or crawl limits aren't set Switch to “Hotline (API)” and limit pages and products from the category
    The fast module doesn't start It works only in server mode Switch the source to server mode or use the regular module
    No sellers, only one price “Collect shop offers” is off, or the regular module is selected, which doesn't collect sellers at all Switch to “Hotline (API)” and turn on the checkbox; keep the data volume in mind
    Prices didn't update, and the log says “⚠️ The source did not answer, products stay in the queue:” The run broke off after the price list had already been cleared Run it again — it clears the price list again and collects everything from scratch, with no duplicates (run break-off)
    Edits made by hand in the price list grid are gone The price list is rebuilt from scratch on every run Lock values in the catalog product card — “Do not update” or “Fixed Price”
    A product was in the price list but is gone now It's no longer on Hotline: the price list holds only what arrived this time Check the date in the “Checked” column on the “My products” tab
    The schedule keeps starting runs although the price list is inactive The source's activity toggle doesn't affect the parsing schedule Turn off the “Parsing products from the site” scheduled task or remove this source from it (how to stop runs)
    No barcodes or descriptions Only the fast module provides them, and the description needs a separate checkbox Switch to “Hotline (API)” and turn on the description checkbox
    Exactly 48 products arrived from a section “Max. number of products from the category” is set to 48 Raise “Max. number of products from the category” or set it to zero — the pages field doesn't affect section crawling in the fast module
    I changed a setting, and it changed in another source A ready-made module's settings are shared Split scenarios across different modules or agree on common settings

    FAQ

    Do I need a Hotline account to turn on the parser?

    No. Public product page and offer data is collected; you don't need to sign in to the site.

    How many sellers are collected for one product?

    As many as set in the “Offers per product” field; 200 by default. The “Collect shop offers” checkbox must be on.

    Can prices be updated automatically?

    Yes, you put the source on a schedule just like a regular supplier price list.

    Will the module find all my products on Hotline?

    No. Search by name on the aggregator doesn't find everything: a product that isn't on Hotline gets the “not found on the site” label, and it's searched for again on the next run.

    Does the module collect reviews and videos?

    No. There's no review or video parsing for Hotline, and the checkboxes for collecting them change nothing.

    Can I sell or order on Hotline through the module?

    No. This is data collection, not a marketplace integration.

    Where to find it and who has access

    Menu
    Directories → Processing price lists → List of price lists
    Create
    connection wizard → “From where” step → “Site parser” → “Ready-made parsers” → Hotline
    Configure
    the source row in the list → the “Setup” button in the right panel header
    Access right
    the “Price lists” window (in the menu — “List of price lists”)
    Prepare
    Hotline section addresses or catalog products to monitor; your city code

    The parsing module for Hotline is already written — you don't need to configure selectors, unlike with an arbitrary supplier website.

    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