The price list opens correctly, but the packaging notes and delivery assumptions are missing. Before asking a supplier to send the same file again, check whether the original quotation was a multi-sheet workbook and the delivered file was a CSV export.

Google's Workspace export-format reference, updated September 3, specifies that Google Sheets exports to CSV and TSV through this route contain the first sheet only. A successful download can therefore be complete as an export while incomplete for the recipient's intended task.

For buyers and international sales teams, the first question is not which format is most familiar. It is what the recipient needs to do with the information.

A data import and a quotation review need different things

A purchasing system may require one table with defined columns. A person reviewing an offer may need several alternatives, packaging conditions and explanatory notes. Sending the same CSV to both recipients can leave one satisfied and the other without essential context.

Supporting sheets can change the meaning of values in the main table. A price may depend on a packaging unit defined elsewhere. A product list may need a separate explanation of which version or market it covers. When those notes disappear, the remaining numbers still look plausible. That makes an incomplete handoff harder to notice than a file that will not open at all.

If the objective is to preserve a workbook's organization, choose an appropriate workbook format and inspect the result in the receiving environment. If the destination accepts only CSV, agree on the specific table and fields it requires. Decide separately how any explanatory material will travel with it.

This is not an argument against CSV. It is a reason to use it for a clearly defined single-table purpose rather than treating it as a smaller equivalent of every spreadsheet file.

Sheet order is a fragile way to express delivery scope

Moving the desired sheet to the first position may solve a one-off export. It is a weak long-term arrangement for an automated job. A colleague can later add a cover sheet, leaving the export process operational but changing its output.

State the intended data range explicitly and use an export or retrieval method that supports it. The technical method can vary; the commercial agreement should not. A recipient should know which products, fields and version the file represents without having to understand the sender's tab order.

Combining all sheets into one long table is not necessarily a solution either. Different headers, units and explanatory rows can make the resulting file difficult for software to interpret. Where the source has genuinely different structures, separate files or a workbook may communicate the material more accurately.

If several files are necessary, give them a clear relationship. A data file and its conditions should not become unrelated attachments whose names differ only by “final” and “latest.” Use a meaningful shared version or reference so that a buyer can tell which explanation belongs with which data.

Review the delivered artifact, not the source workbook

The last check should open the actual file being sent. Returning to the online workbook and pointing out that all tabs are present does not answer the recipient's problem. The question is what survived the chosen export.

Check the intended first and last items, expected row count, field names and required supporting material. If the recipient will import the file into another application, ask what the columns are expected to mean. A visually readable file can still be interpreted differently by software.

Product identifiers deserve particular care. Our article on preserving model names during translation explains why an identifier is not ordinary prose. It is not necessarily a numeric quantity either. The recipient's interpretation matters even when the export itself has preserved the characters.

For recurring quotation exchanges, an agreed sample can make the process simpler. Record the expected files or sheets, required columns and accompanying notes. Review each new delivery against that scope rather than relying on a broad instruction to “export the quotation.”

A buyer can help by describing the intended use before requesting a format. “We need to import these columns” is more actionable than “send CSV.” “We need to review the complete offer” may call for a different package altogether. The format decision becomes easier once both sides mean the same thing by the file they are exchanging.

Sources

Google for Developers, Export MIME types for Google Workspace documents, documentation updated September 3, 2026.