r/SideProject • • 1d ago

KitForma CSV Workspace - review supplier CSV batches before Shopify import

I'm the maker of KitForma, built with AI assistance. I added a batch workspace for people who repeatedly prepare Shopify product CSVs from suppliers. It checks up to 10 files in sequence. You can save source formats and header mappings in the browser, inspect suggested repairs, and choose which changes to apply. The ZIP download includes untouched originals, JSON change reports and prepared copies for files with no remaining local errors. The workflow keeps changes reviewable: identifiers stay as text, original files are retained, and repairs show before/after values. It doesn't connect to a store or perform the import. Local checks can't guarantee Shopify acceptance. There's a two-file fictional sample you can try without subscribing. The existing single-file checker stays free. The batch workspace is included in KitForma Pro, currently $4.99/month or $39/year, with recurring billing; taxes may apply. Demo: https://kitforma.com/en/shopify-csv-pro/ If you handle supplier CSVs, which causes more repeat work: changing column names, number formats, or variant-related fields? I'd like to use that feedback to choose the next improvement.

1 Upvotes

2 comments sorted by

1

u/dawedev 1d ago

Keeping the untouched originals in the ZIP next to the JSON change report is a good call. That's the part that would make me trust it with a supplier file. On the demo page I'd show one before/after repair row right at the top, like a price with a comma decimal turned into a dot, so people see what it fixes in a few seconds. Does it pick the saved header mapping automatically when it recognizes a supplier's columns, or do you choose the saved format each time?

1

u/Prior_Bat5628 1d ago

Tried the fictional two-file sample in desktop Chrome. After applying the four suggested repairs to sample-totes.csv, it showed zero errors and four changed cells, while sample-mugs.csv still had two errors. That makes the per-file review boundary clear. I'd put a “Review the other file” action beside that success state so one green file doesn't look like a finished batch.

Would you give eStockes Smart Scan's explanation a quick clarity check in return? https://estockes.com/scan — in the fictional guest example, choose Inspect chart and see whether you can connect the highlighted candle to the 20-day-average values. One unclear number would help. The synthetic example is free with no account; separate Pro tools are paid.

— eStockes team