Distributors email a CSV and get an answer.

Registered distributor senders email a CSV to Dexor. Unknown or spoofed senders are dropped, and every file is checked line by line before import.

Dexor - file NOT processed: 2 error(s) found (oct_week3_sales.csv)
From Dexor, to accounts@primemedical.example

Your file was checked and NOT imported. Please fix the rows below and re-send the corrected file to this same address.

File: oct_week3_sales.csv
Rows checked: 1,284   Would import: 1,282   Errors: 2

Line 214'31/09/2026' in 'Invoice Date' is not a valid date, expected DD/MM/YYYY (field: invoiceDate)
Line 877'12 ctn' in column 'Qty' is not a number (field: qty)

Nothing from this file was imported. Line numbers count the rows of your file (including the header row); blank lines are not counted.

All or nothing
A file with a bad row is never half-imported
Allow-list
Only registered sender addresses
Line by line
Errors named in the reply

Only registered senders get in.

Each distributor sender address is registered against your account, a distributor and a mapping. Mail must pass sender authentication before Dexor even looks the sender up, so a forged From address is dropped without a reply.

The account always comes from the registered sender, never from anything in the email. An unknown or revoked sender is dropped silently, which also stops anyone probing for valid addresses. Only the hash of each address is stored.

All or nothing, with a clear reply.

Each email carries one CSV, and its rows are checked with the distributor's mapping. If any row fails, nothing is imported and the reply lists each problem by line number and field, so the distributor can fix the file and send it again.

A clean file is handed to the same pipeline as every other upload, and the reply confirms how many rows were accepted with a batch reference.

Polite to inboxes.

Auto-replies and bounces are ignored, so Dexor never gets into a mail loop. No message is ever answered twice, and a reply that fails for a temporary reason is retried.

Questions people ask.

What if a distributor changes their export format?
The reply says the column headers did not match, lists the expected and found headers, and suggests likely matches. Your Dexor administrator can update the mapping.
Can someone else send data pretending to be our distributor?
A message must pass sender authentication and come from a registered address. A forged or unregistered sender is dropped with no import and no reply.
What does the distributor hear back when a file is accepted?
A reply confirming the file was received and queued, how many rows were accepted, and a batch reference they can quote if they have a question later.
Who registers sender addresses?
Dexor registers them for you, against a distributor and mapping that already exist in your account.

Distributor data ingest

Distributors send sell-out and stock by API push, the upload API or email. Every file is checked, stamped with where it came from, and kept as received.

Read more

Data quality workbench

Match rate, rejected rows by reason and duplicate outlets for each distributor, on one screen, linked straight to the match queue.

Read more

See 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.