Clear unmatched outlets in a few keystrokes.
A two-pane review queue for outlet names that did not match on ingest. Approve a candidate, override the territory, or reject, from the keyboard.
Choose the correct territory, override with a known one, or reject (leave unmatched).
Choose the correct territory, override with a known one, or reject (leave unmatched).
Choose the correct territory, override with a known one, or reject (leave unmatched).
Choose the correct territory, override with a known one, or reject (leave unmatched).
Pick the right outlet, then move on.
Pick a distributor and the queue lists every distinct unmatched name with its best score and how often it appeared in the latest batch. Select one to see its ranked candidates, each with a score and the territory it would assign.
Approve takes the chosen candidate. Override assigns a territory you know is right when no candidate is. Reject leaves the name unmatched on purpose. j and k move through the list; a, o and r act.
One decision fixes every future file.
Approving or overriding creates an outlet record for that name, so every later file with the same name resolves on its own. Past months stay as reported until you choose to restate them.
If the decision would create a duplicate of another outlet, the queue refuses it and asks you to try again, rather than saving a collision.
Your team decides, within its own patch.
The match queue belongs to your organisation. Managers and admins work it, and a manager can only assign a territory inside their own part of the team. Every decision is written to the audit trail.
Questions people ask.
Who resolves our matches?
Does approving a match fix last month's numbers?
What if none of the candidates is right?
Works well with.
Outlet and SKU matching
Distributor outlet names and SKU codes are matched to your masters. Clean matches land in a territory; uncertain ones wait for a person.
Read moreRestatement
After a match is approved, restate a past month so its unmatched lines land in the right territory. The original source data is never rewritten.
Read moreSee it on your own team.
Tell us your fleet and we will size a proposal. Complete roll-out may take up to 4 months, counted from signed requirements and first payment.