Browse categories
Explore
Fiverr Pro
English
$
USD
I will standardize your order CSV files and report duplicates and conflicts
About this Gig
I will standardize up to 2 UTF-8 comma-separated CSV files (max 1 MiB each; 100 data rows total) into 4 agreed fields: order identifier, SKU, quantity, recipient.
Before work starts, send anonymized samples and confirm the order identifier + SKU line-item key and how repeats, variants, split shipments, corrections, returns, and cancellations should be handled.
Deliverables:
- clean.csv
- duplicates.csv for conflict-free exact duplicates
- issues.csv for invalid/conflicting rows
- short field/rule guide
Every output row keeps its source filename and row reference. Nothing is silently dropped. Header, parse, or mapping failures become batch issues; invalid data rows remain in issues. If rows sharing the confirmed key disagree on quantity or recipient, the entire key group is quarantined.
Includes 1 consolidated revision using the original files and agreed rules.
Excludes login, scraping, OCR, Excel, non-UTF-8, APIs, integrations, complex calculations, and unsupported reconstruction. The gallery uses synthetic data and was developed with AI assistance, code review, and browser checks; it is not client work or a compatibility claim.
FAQ
What does the Basic package include?
US$30, 3-day delivery: up to 2 UTF-8 comma-separated CSVs, max 1 MiB each and 100 rows total. Four agreed fields: order identifier, SKU, quantity, recipient. Deliverables: clean.csv, duplicates.csv, issues.csv and a field/rule guide.
How do you identify duplicates and conflicts?
We first confirm the order identifier + SKU key. Identical repeats go to duplicates.csv only in conflict-free groups. Any quantity or recipient disagreement sends every row in that key group to issues.csv for review.
Will any input rows be silently deleted?
Every parseable row in a successfully parsed and mapped batch appears once in clean, duplicates or issues, with source filename and row reference. A malformed file or header/mapping failure becomes a batch issue; row reconstruction is excluded.
What does the included revision cover?
One consolidated revision using the original files and agreed rules. New files, a different key, added fields or changed business rules need a separate scope review.
Do you accept Excel or guarantee marketplace compatibility?
Input is UTF-8 comma-separated CSV only. Excel, non-UTF-8 files, login, scraping, OCR, APIs, integrations and unsupported reconstruction are excluded. Compatibility with a named marketplace requires a separate review of its supplied export.
What quantity and export rules apply?
Quantity must be a positive integer. Formula-like text values get a leading apostrophe in exported CSV; confirm your importer accepts this protection.
