Product
Data quality
With our proprietary K.Refine algorithm, we audit, clean and reconcile data before it reaches your dashboards. That is what we call a data refinery: raw sources go in, clean and traceable data comes out.
Data and knowledgeData tablesfournisseurs_2026 en Claire MorelCM
Improve quality Analyse Rules Columns (3)N°SupplierCategoryCity
1Acier DurandMetalsSaint-Étienne
2Boulonnerie MartinFastenersLyon
3Emballages RousseauPackagingNantes
4Acier DurandMetalsSt-Étienne
5Transports PetitLogisticsLille
6Emballages RousseauPackagingnantes
7Plastiques MoreauPlasticsOyonnax
8Acier DurandMetalsSaint-Étienne
9Boulonnerie MartinFastenersLyon
10Emballages RousseauPackagingnantes
11Fonderie GirardMetalsSaint-Étienne
12Transports PetitLOGISTICSLille
13Plastiques MoreauPlasticsOyonnax
14Acier DurandMetalsSaint-Étienne
15Transports PetitLogisticsLille
16Fonderie GirardMetalsSaint-Étienne
Clean your data withKRefine
Cleanliness of the analysed columns
94% today, 99% once applied. 23 cell(s) would be rewritten.
On 1,240 row(s) and 3 column(s): fournisseur, ville, categorie
Capitals2 proposal(s), 23 cell(s)Untick all
nantesNantes
City9 cell(s)
LOGISTICSLogistics
Category14 cell(s)
Variants1 proposal(s), 6 cell(s)Tick all
St-ÉtienneSaint-Étienne
City6 cell(s)To review
Reliable data, whatever the source
K.Refine
Data cleaning
K.Refine suggests the corrections, and you review them before applying them.
- Spaces, capitals, variants and unusual numbers
- Every correction you keep becomes a rule for new rows
- No language model, no AI credit
Clean your data withKRefine
Cleanliness of the analysed columns
86% today, 97% once applied. 214 cell(s) would be rewritten.
Capitals1 proposal(s), 214 cell(s)Untick all
lateLate
Status214 cell(s)
Unusual numbers1 row(s) to check
1250expected: 12.5
Row 418prix_unitairereference: VIS-M8
Unique value
Deduplication
A unique-value column drops duplicates as soon as you import.
- Case, accents and spaces ignored
- Two spellings of the same value caught: “Lyon Est” and “LYON-EST”
livraisons_2026
N°Delivery noteSiteQuantity
1BL-26-0412Lyon Est24
2BL-26-0413Nord12
3BL-26-0414LYON-EST40
4BL-26-0415Sud8
5BL-26-0416Lyon Est16
6BL-26-0417Est30
7BL-26-0418LYON-EST22
8BL-26-0419Nord18
Variants1 proposal(s), 31 cell(s)
LYON-ESTLyon Est
Site31 cell(s)
Linked tables
Data matching
Link two tables like a VLOOKUP, on one to five shared columns.
- Lenient matching: case, accents and spaces ignored
- A trial run shows how many rows match before you link
commandes_2026
N°SupplierCityAmount
1Acier DurandSaint-Étienne4 820
2Boulonnerie MartinLyon1 260
3Emballages RousseauNantes2 105
4ACIER DURANDSaint-Étienne3 940
5Transports PetitLille880
fournisseurs_2026
SupplierCity
Acier DurandSaint-Étienne
Boulonnerie MartinLyon
1,180 row(s) out of 1,240 find their match
Rules
Data quality rules that apply themselves
Write a rule once: it corrects every new row, whether typed in, imported or written by a workflow.
- Tested on every row before it runs
- Every run can be undone from the history
New rule
On rows where Status equals “late” and Amount is greater than 1000, write “Chase up” in Priority.
1Which rows
Keep the row ifall criteria
Statusequalslate
Amountis greater than1000
Apply automatically
On every row added or modified, whether typed in, imported or written by a workflow. Rows already there only change if you run the rule.
How K.IOP cleans your data, in 5 steps
-
Import
Excel, CSV or a workflow
-
Analyse
K.Refine spots what is off
-
Review
Keep or drop each proposal
-
Apply
Each correction becomes a rule
-
Use
Dashboards, alerts and AI read the clean table
K.Refine compared with other data cleaning tools
We ran the same files through every tool, with their clean version cell by cell. K.Refine fixes almost half of the errors, damages almost nothing, in under a second.
| Criterion | K.RefineK.IOP | OpenRefineOpen source | Raha + BaranAcademic research | rapidfuzzPython library |
|---|---|---|---|---|
| Errors fixed | 48%6,269 of 13,036 | 6%773 | 59%7,734 | 3%371 |
| Correct cells damaged | 58out of 96,496 | Noneevery group reviewed by hand | 1,059 | 2,254 |
| Time per file | Under 1 s | 1 to 17 splus the review | 40 s to 2 min | About 1 s |
| What you have to give it | Linked columnsoptional, declared in K.IOP | A reviewof every group of values | 20 rows corrected by hand | The columns to processand a similarity threshold |
| No code | Yes | Yes | NoPython script | NoPython script |
| Fixes new rows | On every rownothing to rerun | By handby replaying the history | By rerunningon the whole file | By rerunningthe script |
K.IOP benchmark of 28 and 29 October 2026: 8 files and 13,036 errors, including four public research datasets (hospital, flights, beers, rayyan). K.Refine with the column links declared in K.IOP; some of these files were used to tune it. Brands mentioned belong to their owners.
Deterministic by design, with no language model, and your data never leaves our servers.
Every rule run is recorded and can be undone. Your figures rest on rules, not on guesswork.
- Language model
- Nonezero AI credit used
- Per analysis
- 200,000rows and 30 columns
- Reversible
- 50,000rows per rule run
Common use cases
-
ERP vs files reconciliation
Reconcile ERP data and field files to eliminate discrepancies and duplicates.
-
Supplier data cleansing
Standardize and verify multi-format supplier references before any decision.
-
Ready for an operations desk
Feed an operations desk with data that is already cleaned and reconciled.
Frequently asked questions about data quality
What guarantees that a displayed number is right?
Every rule run is recorded and counted, from the source file to the figure on screen. The rules are written down, and the test shows them before anything is applied.
How are duplicates detected?
Mark a column as a unique value: on import the first row is kept and those repeating its value are dropped. Case, accents and surrounding spaces are ignored. Without a unique column, every row is imported.
Can a transformation be tried without applying it?
Yes. “Test” shows the rule on 50 rows, before and after, with the rows it touches. Nothing is written until you run it.
What is a cleaning rule?
A rule selects rows by criteria, then writes a value or the result of a formula into one or more columns. Nothing changes until it runs. In automatic mode it applies to every row added or modified, and every run can still be undone from the history.
Does data cleaning use AI?
No. K.Refine is an algorithm with no language model, and it uses no AI credit. AI only steps in when you ask it to: writing a formula, proposing a rule, analysing a table.
Can I link two tables as with a VLOOKUP?
Yes. A linked column brings in a value from another table on one to five criteria, ignoring case, accents and spaces, and stays up to date on every write. After an import, K.IOP suggests the link when a shared key emerges.
How much data can K.Refine analyse?
Up to 200,000 rows and 30 columns per analysis. The number of tables and rows per table depends on your plan.
See pricingBefore and after fixing
-
Connect
Integrations
Sources arrive as they are: ERP, APIs, files, legacy systems, with no migration.
See every connector -
Make reliable
Data quality
K.Refine cleans, deduplicates and reconciles the data in between.
-
Operate
Dashboards
Reliable data feeds the indicators, the alerts and the AI assistant.
Explore dashboards
Traceability and reversibility. Every rule run stays in the table’s history and can be undone up to 50,000 rows.
See data quality on your own files
Book a live demo: we start from your real data.
- Dry run
- Runs you can undo
- No language model