CSV, JSON and Excel: The Data Formats Every Online Seller Eventually Meets

Run an online business long enough and the file formats find you: the marketplace exports your orders as CSV, the courier API wants JSON, the accountant wants Excel, and some report arrives as XML nobody asked for. Most sellers treat these encounters as emergencies. They're not — CSV and JSON are two of the simplest formats in computing, and fifteen minutes of understanding plus a browser-based converter turns every future encounter into a thirty-second task.

CSV: a spreadsheet wearing a text file

CSV — comma-separated values — is just rows of text where commas split the columns:

order_id,product,qty,amount
ORD-1001,Blue Kurti M,2,598
ORD-1002,Combo Pack,1,499

That's the entire format. Every spreadsheet app opens it, every system exports it, and it will outlive us all. Its simplicity is also its trap: CSV carries no formatting, no formulas, no data types — just text. Which leads directly to the classic disasters:

Excel eats your leading zeros. Open a CSV with phone numbers or pincodes starting in 0 and Excel "helpfully" converts them to numbers: 09812... becomes 9812.... Fix: import via Data → From Text/CSV and mark those columns as Text — or keep such files in CSV and edit carefully.

Long numbers become 8.9E+12. Order IDs and AWB numbers past 15 digits get mangled into scientific notation and lose precision if you save. Same fix: import as Text. If a column of AWBs ever shows E+, do not save — reimport.

Commas inside values break columns. "Kurti, Blue, M" as a product name splits into three columns unless the export properly quoted it. Good exports quote; if yours didn't, the converter's CSV→JSON round trip makes the breakage visible immediately.

Encoding gibberish. Hindi characters showing as à¤... means the file is UTF-8 but was opened as something else. Use the import dialog and pick UTF-8.

JSON: data with structure

JSON looks scarier and is actually more honest than CSV — it labels every value and supports nesting:

[{"order_id":"ORD-1001","product":"Blue Kurti M","qty":2,"amount":598}]

APIs speak JSON almost universally: courier tracking, payment gateways, marketplace developer APIs. As a seller you mostly need two skills — reading it (each "name": value pair is a labeled cell; square brackets mean a list) and converting it to something a spreadsheet understands.

The Data Converter does both directions instantly: paste JSON → get CSV for Excel; paste CSV → get a clean JSON array (first row becomes the keys) for any API or developer you're working with. There's also JSON beautify — paste a single-line JSON blob from some API response and get it indented and readable — plus validation that points at the exact error when a file is malformed. XML→JSON handles the occasional legacy report. Everything runs locally, which matters given these files contain your order and customer data.

The conversions sellers actually perform

Marketplace CSV → clean Excel for analysis. Export orders, import to Excel with the Text-column trick, then pivot by SKU and date. For settlement PDFs (not CSVs), PDF to Excel is the right tool instead.

Excel → CSV for bulk uploads. Listing tools and bulk-update templates usually demand CSV. Save As → CSV UTF-8, and check the file in a text editor once — thirty seconds that catches quoting problems before the marketplace's importer does.

JSON from an API → spreadsheet. Courier tracking dumps, payment reports: paste → JSON to CSV → done. Nested fields get flattened into their cells rather than lost.

CSV → JSON for a developer. Hiring someone to build your website or integration? Handing them your product list as JSON instead of "an Excel" marks you as a client who'll be easy to work with.

Config files in YAML. If you ever touch deployment or automation configs, the converter's JSON↔YAML pair covers it.

Habits that prevent data accidents

• Keep a raw copy. Before opening any export in Excel, duplicate it. Excel's helpfulness is irreversible after save.
• Dates are ambushes. 03/04 means March 4 or April 3 depending on locale settings; prefer exports with ISO dates (2026-04-03) and sort problems vanish.
• One header row, no merged cells in anything you intend to convert or re-import. Pretty formatting belongs in the report copy, not the data copy.
• Validate JSON before sending it anywhere — the converter's validator with its exact-position error message beats an API's cryptic 400 response every time.

A fifteen-minute self-test

Want the skills to actually stick? Run this drill once: export ten orders as CSV from your marketplace panel, open the raw file in a plain text editor and identify the header row and a quoted field; convert it to JSON in the Data Converter and find one record's amount; beautify a piece of ugly JSON from anywhere; then round-trip back to CSV and import into Excel with pincodes as Text columns. Fifteen minutes, and you'll have personally performed every conversion this article describes — which means the next time a courier integration, accountant or developer sends you a strange file, it's a chore, not a crisis.

Frequently asked questions

Why does my CSV open as one giant column? The file uses semicolons or tabs as separators (common with European locales). Use Excel's import dialog and choose the delimiter — or run it through the converter, which detects the structure.

Is it safe to paste order data into an online converter? Into upload-based ones, you're trusting their server with customer data. This one runs in your browser — paste, convert, and nothing transmits, verifiable offline.

JSON to Excel directly? JSON → CSV in the converter, then open the CSV in Excel. Two clicks total.

What about Excel formulas surviving conversion? They don't — CSV/JSON carry values only. Convert the data, keep formulas in your analysis workbook that references it.

Related tools

• Data Converter — CSV ↔ JSON, YAML, XML, beautify, validate
• PDF to Excel — when the report arrived as PDF
• Developer & Text Tools — JSON formatter, dedupe, diff and more