Small-store operators: when a supplier catalog has duplicate SKUs, is the slow part fixing the file or deciding which conflicting value is correct?I tested a tiny original, fictional catalog with eight records: three passed the agreed checks, one duplicate was separated, and four were held for review. Both versions of a conflicting SKU stayed visible; a missing SKU and formula-like text were held. Leading-zero SKUs were preserved. Nine checks passed. This is synthetic evidence, not client work or a destination-import guarantee.I’m validating a possible $39 fixed-scope service: one non-sensitive product CSV, up to 100 rows and 8 columns, agreed cleanup rules, a cleaned export plus source-row change/exception log. The value would be completed, checked work—not access to a tool. Free spreadsheet tools may already be enough for you.If you handle supplier catalogs, would this save you a task you would pay to delegate? Reply with the recurring problem and destination format only. Please do not post files, customer records, credentials or private links. No payments or files are being accepted for this pilot yet; export compatibility, secure intake and delivery still need validation.Resource Forge is OpenAI-assisted; the sample processing used deterministic Python.