Written by DROPS.ST.
Check the saved CSV before application: receiving requirements, exported values and representative rows. A tidy spreadsheet view does not establish import readiness.
DROPS gives the file one catalogue destination for products, prices, units, images and stock, shared with connected Telegram. Agree the actual mapping and transfer method.
Get the receiving requirements first
Ask for the current supported template or documented mapping process. Confirm whether headers are required, which fields are mandatory and which delimiter and character encoding are accepted.
Also establish how the importer distinguishes a new product from an update. Do not assume that a name or SKU is the matching key. Ask what duplicate references and empty cells do.
For images, confirm whether the process accepts uploaded files, file names, public image URLs or another reference method. A link visible in a spreadsheet does not establish that the importer can retrieve it.
Keep the agreed receiving requirements with the file; no universal DROPS specification is assumed.
Inspect the export settings and saved text
A delimiter separates fields. The character encoding determines how text characters are represented. The export's text delimiter handles field contents that would otherwise be confused with separators.
For common comma-separated CSV, RFC 4180 describes double-quoting fields containing commas, line breaks or quotes, with an embedded quote represented by two quotes. It is an informational format reference, not a platform-specific import contract. RFC 4180.
Inspect examples that contain punctuation or paragraph breaks rather than checking only simple names. Count parsed fields, not physical lines: a quoted description may contain a line break inside one record.
LibreOffice exposes the character set, field delimiter and text delimiter in its export options. Its documentation also warns that saving displayed number formatting can produce values that an importer no longer interprets as numbers. LibreOffice CSV export options.
Reopen the exact exported file using the agreed settings. Confirm that special characters, price values and references survived as intended.
Use a sample-check worksheet
Choose ordinary and difficult rows. Record expected meaning before inspecting the saved values.
| Check | Intended meaning | Inspect |
|---|---|---|
| Identifier | Complete reference | Characters/zeros retained |
| Punctuation | One description field | Correct separators/quotes |
| Characters | Approved spelling | Reopened text |
| Price | Amount for defined unit | Numeric representation |
| Quantity | Stock versus pack meaning | Units agree |
| Image | Correct item image | Agreed reference method |
| Empty cell | Deliberate omission | Confirmed receiving behavior |
Resolve identifier and unit ambiguities
Check duplicates, spaces and case differences. Confirm their meaning and receiving rules before normalization.
Treat the product's unit, pack size and stock quantity as separate concepts. A row saying “12” needs context: twelve items, twelve packs or a package containing twelve items are different meanings.
Check quantity limits against the unit. Confirm wholesale package/tier mapping separately rather than guessing a similar field.
Use the approved product record guide to resolve the underlying facts before exporting them. File formatting cannot correct an unclear product definition.
Keep image references checkable
Match each sampled reference to its intended image and assign missing files to an owner.
Check images through the agreed transfer workflow; unrelated replacements do not resolve missing assets.
Keep credentials and secret tokens out of image references. Agree another transfer route when needed.
Hypothetical example: a clean sheet, a faulty export
An owner prepares four fictional catalogue rows. One description contains a comma, one identifier begins with zeros and one row names a missing image file.
The spreadsheet view looks orderly. On reopening the export, the reviewer finds that the description is split into two fields and the identifier is altered. The image issue remains unresolved.
They correct the export settings, preserve the intended reference and identify the missing asset before releasing the file. No live import is needed to discover these problems.
Release one identified file for the next step
Identify the checked version and preparation date. Keep its worksheet and recheck values affected by corrections.
Separate file approval from application authority, confirming row scope and create/update behavior.
For a platform move, use the migration rehearsal checklist for the wider reconciliation and cutover decision. This preflight addresses the file before that process begins.
Prepare for one catalogue your team can maintain
DROPS is a strong fit when the goal is a coherent shop catalogue instead of several channel-specific product files. Good preparation lets the setup discussion focus on actual items, units, prices and images.
See DROPS and explore the demos. Bring the sample worksheet and agree how checked information will become shop records.