Check repeated order references
Locate references imported more than once across several exports, then confirm in the source system whether those repetitions represent legitimate transactions or an accidental second import.
Find duplicate lines, count occurrences and export a clean summary. Processing stays local in your browser.
Before deleting repeated entries, establish which values recur and how often they appear. The duplicate analyser creates that inventory from one item per line: order references, participant identifiers, copied addresses or log messages. It displays only repeated lines, each with its total occurrence count. Your original list remains in the input field. The output is a frequency report, rather than a deduplicated replacement list or a uniqueness check across selected table columns. It helps you decide what deserves investigation before changing the source records.
Windows CRLF endings and standalone CR characters are converted to LF before the text is split. Each physical line then becomes a separate value for comparison. Completely empty lines are ignored, but a line consisting only of spaces remains a real value and may therefore appear as an invisible duplicate. There is no special header record: a repeated heading counts in exactly the same way as another input line.
Comparison is exact. Capitals, accents, tabs and spaces at either end remain significant. York, york and York followed by a space form three different groups. The analyser performs no Unicode normalisation, address correction or numerical conversion. An identifier written as 0012 is therefore separate from 12. This behaviour suits a check for identical strings; it does not find similar names, spelling mistakes or records that might represent the same person despite having different text.
Each occurrence increases a counter, after which only values appearing at least twice are retained. Results are sorted by decreasing frequency, with first appearance used to preserve order when counts tie. Every output line begins with its total, followed by × and the original value. A count of three means three occurrences in the input, leaving two excess occurrences if your aim is to retain one. When no value repeats, the output is empty; that does not mean reading failed.
Paste a single spreadsheet column or import a plain-text list. When checking identifiers, do not append a customer name or comment to the same line unless it belongs in the comparison.
If surrounding spaces or capitals should not distinguish entries, deliberately clean those differences before running the analysis. There is no switch for ignoring them during this operation.
Run the analysis, inspect a few reported values, and copy or export the text report. Return to the original list to decide what to remove, since unique values are absent from the report.
Locate references imported more than once across several exports, then confirm in the source system whether those repetitions represent legitimate transactions or an accidental second import.
Count repeated participant identifiers before removing entries manually. Identical registrations provide a reason to check the record rather than proof that a person should be deleted.
Bring the most frequent identical log lines to the top. Different timestamps prevent a match, so remove them beforehand only when that is appropriate for your investigation.
ORDER-205 occurs three times and is listed first. ORDER-104 occurs twice. Keeping one instance of each reference would require deleting two occurrences of the first and one of the second: three source lines altogether.
Input
ORDER-104
ORDER-205
ORDER-205
ORDER-104
ORDER-205Result
3 × ORDER-205
2 × ORDER-104The two York lines are identical. The lowercase york is a separate, unique value, as is Bristol, so neither appears in the output. Lowercasing the input beforehand would deliberately change what qualifies as a duplicate.
Input
York
york
York
BristolResult
2 × YorkIt counts every occurrence, including the first. For a result starting 4 ×, retaining one instance means removing three occurrences. The analyser does not delete any input entries automatically.
Different capitals, trailing spaces, tabs or Unicode representations are sufficient to distinguish them. The analyser compares the characters it receives; it does not test address deliverability or establish that two addresses belong to the same person.
No. This analyser does not interpret CSV columns or quoted records. CSV deduplication lets you select the columns that define a repetition; the analyser here counts complete text lines.
No non-empty line occurs at least twice with exactly the same spelling. It does not establish business-level uniqueness: differently written names may refer to the same entity while remaining different strings.
Related tools
Tools similar or complementary to this one.
Remove duplicate CSV rows using the columns you choose as matching criteria.
Remove extra spaces, repeated tabs and empty lines from copied text.
Remove duplicate lines from a list while keeping one occurrence of each value.
Put cleaning, validation, filtering, merging, comparison and conversion in a sensible order, and learn when a reusable pipeline is better than isolated tools.
Learn how tabular data is structured, how CSV, Excel, JSON and TSV differ, and how to choose the right format before cleaning, converting or automating a workflow.
Learn a practical order for removing empty rows, trimming values, standardizing headers, checking identifiers and validating a CSV or Excel dataset.
Learn when to pivot, transpose or convert a table to HTML, Markdown or SQL according to its structure and final use.