Agree what one exported row represents
Before a supplier creates the file, specify whether each row represents a physical container, a plate position or a project line. Name the fields for the buyer ID, supplier ID and container identity. RFC 4180 documents a common CSV format, including how quoted fields handle commas. Ask both parties to exchange a short mock file because different spreadsheet programs can still interpret dates, numbers and text identifiers differently.


Open the mock file as an import
Ask receiving to import identifier columns as text and to state its preferred encoding. Compare the imported rows with the original file while checking leading zeros, punctuation and repeated location values on different plates. Where a human-readable PDF is supplied too, compare its total number of records with the electronic file. Keep the source version unchanged while investigating any differences introduced by the spreadsheet.
Try a supplier name that contains punctuation
Create a mock line with a site name such as “Receiving, West” and a buyer ID such as PL-0031. Ask the supplier to export the line using its normal system. Import it at the receiving end and confirm the site stays in one field. A shifted column can make the following location appear under the wrong heading even though the overall row count remains correct. Resolve this using dummy records before the first delivery.
Worked example
A regional spreadsheet setting may display a date such as 03/04 differently from the sender’s system. Ask both parties to agree an unambiguous date representation and test it on the sample export. Preserve the source file so the original record can be checked.
Prepare your inquiry
Verify both the number of rows and the content of individual identifiers after import.