WEBSITE PLANNING

Prepare a Spreadsheet for a Reliable Website Import

Prepare a small sample import with identifiers, validation rules and a rejection report before moving a spreadsheet into your website.

Separate file format from business rules

A CSV file can open successfully while still containing unusable records. First document the expected columns and their meanings. Decide which identifier remains stable when a name changes, which fields are required and whether blank means unknown, empty or unchanged. Keep a copy of the original export so corrections can be explained and an import can be compared against its source.

Use a fictional three-row sample

Consider columns item_id, name and price. Row A is SKU-001, Sample Mug, 12.00. Row B repeats SKU-001 with a different price. Row C has a name but no identifier. A useful dry run accepts A only if it meets the agreed rules, flags B as a duplicate requiring a decision, and rejects C with a specific missing-identifier message. It should not silently invent identifiers or pick whichever duplicate happened to appear last.

Check punctuation and representation

A name containing a comma needs correct CSV quoting; quoted fields also require careful handling of embedded quotes. RFC 4180 documents the common format. Separately define dates, currency, leading-zero identifiers and text encoding for your importer. A postal code should not lose its leading zero just because a spreadsheet treated it as a number. Formatting consistency is a requirement you agree, not something to guess from the first row.

Approve the preview before the import

The review should show records to create, records to update and rows to reject, with line numbers and reasons. Compare the counts with the original sheet and decide whether one bad row stops the batch. Use a nonproduction sample first; do not experiment on the only copy of customer data. North Front Digital can discuss import requirements through custom application planning.