Skip to content

Product Matcher

Run a match

Start a match run for your group, see what it costs before it starts, and stop it if you need to. You start the run yourself. Before the run starts, the most it can cost is held in your wallet. If your wallet holds too little, the run does not start and nothing is charged.

  1. Open your group in My Data, pick the Matching tab, then Match the data.
  2. Check your lines between Your list and each Compared shop (see Set up a match). If you see Unsaved changes, press Save config first.
  3. Open the 3-dots menu next to Run match and pick Run configuration. Match settings shows the Run summary (your list, the lines and the shops) and the Schedule.
  4. Read the cost next to the button. It says “Up to” an amount “reserved” and what a run typically costs; the rest comes back after the run. Open How is this charged? to see each cost line.
  5. Press Run match. The button shows “Queuing…” and then Running. The amount is now held in your wallet.
  6. To end the run early, press Stop next to the button, then Stop run.
  7. When the run ends, open Results. Rows are split into Matched, No match and Review. The previous result is kept until the new run ends.
The 3-dots menu next to Run match, open, with Run configuration in it.
The 3-dots menu next to Run match opens Run configuration.

Note

The cost of the run is held in your wallet when it starts. When the run ends, you pay what it used and the rest comes back to your balance.

Costs

A run costs server time, rows and pictures. The estimate shows the cost before you start. In the portal, open How is this charged? next to Run match:

Search server M (cpx52, EUR [PRICE]/h): up to EUR [AMOUNT]

Rows: 50,000 × EUR 0.00015 = EUR 7.50

Pictures: 1,240 × EUR 1.50 per 1,000 = EUR 1.86

Search server, per started hour (minimum 1 hour)shown in the estimate
Rows, per row the run processesEUR 0.00015
Pictures, per 1,000 picturesEUR 1.50

Pictures are counted only when photos are compared, see Photo check. The server price depends on the size of your group.

  • Held, then settled. When the run starts, the most it can cost is held (“Up to … reserved”). When it ends you pay what it used; the rest comes back.
  • Our fault, no charge. If the server fails to start, or the run stops because of a fault on our side, you pay nothing.
  • You stop it. If you stop a run after its server is ready, the started hours are charged.
  • History. After the run, the Cost column in History shows what you paid, for example “Server EUR 0.40 + rows EUR 0.10 + 1,200 pictures EUR 1.80”.

Errors you may see

Save your changes first
You have Unsaved changes. Press Save config, then Run match.
Not enough balance for this run
Your wallet holds less than the run needs. The dialog shows three figures: needed (up to), available and missing. “Top up at least” the missing amount “and press Run match again.” Nothing was started and nothing was charged. See Wallet and billing.
402 FLOW_RUN_SERVER_WALLET_LOW
The same stop over API and MCP. The answer has reserveMicros (needed), availableMicros and missingMicros, and the text “Matching did not start: … Top up … and run again. The previous result is kept.”
409 on a second start
This version is already running, for example from a second tab. Wait for it to end.
409 OWN_MATCH_RUNNING or SCRAPER_RUN_IN_PROGRESS
A match run or a scrape of this group is still going. Wait, then send the same request with the same idempotency key.
409 VERSION_CHANGED
The setup changed since your read. Read it again and send the new version.
403 with a Read key
A Read key cannot start a run. Use a Full key.
A red reason next to Run match
Something in the setup blocks the run, for example a column that no shop has. The text says what to fix.
json
{
  "code": "FLOW_RUN_SERVER_WALLET_LOW",
  "message": "Matching did not start: this run needs up to €1.93 and your available balance is €0.50. Top up €1.43 and run again. The previous result is kept.",
  "reserveMicros": 1932750, "availableMicros": 500000, "missingMicros": 1432750,
  "errors": [ { "code": "FLOW_RUN_SERVER_WALLET_LOW", "message": "...", "reserveMicros": 1932750, "availableMicros": 500000, "missingMicros": 1432750 } ]
}

The other money stop, 402 WALLET_INSUFFICIENT_BALANCE, is for scrapes and requests, not for match runs. See Wallet and billing.

Questions

Is my old result lost when I start a new run?

No. The previous result is kept until the new run ends. A run that fails or is stopped leaves the old result in place.

Can I stop a run?

Yes. While a run is going, Stop sits next to Run match and on the run’s row in History. If you stop after the server is ready, the started hours are charged.

What happens to a scheduled run when my wallet is low?

It is skipped. History shows it with “Not started: balance too low”. Top up and run again. See Schedule and history.

How do I remove the setup?

In Match settings, press Delete matching configuration. It removes only the setup; matched results and history stay. You cannot delete while a run is going.

What do Floor and Max do?

Rows of a step under Floor are no match, at or above Max a match, in between go to review. See Steps, Floor and Max.

Everything on this screen

Run, stop and wallet:

  • Run this match again? or Run a new match?: the question before a run. Run or Create job & run starts it.
  • Stop this matching run?: Stop run ends it, Keep running closes the question.
  • Not enough balance for this run: nothing was started and nothing was charged. Top up balance opens the top-up, Not now closes the window.
  • Your balance is empty: shown when the wallet has nothing left.
  • Delete the current matching configuration? and Delete configuration: removes the setup after you confirm.
  • Delete all matching data…: removes every match result of the group. Delete ALL matching data for this group? asks you to type the group name in Type the group name to confirm, then press Delete everything.

Last updated 4 November 2026