Identifier integrity
Keep SKUs and leading zeros intact after PDF conversion
Protect product identifiers from number formatting, scientific notation, and accidental date conversion.
Treat an identifier as a label
A SKU can contain only digits and still be a label rather than a number. A product code such as 00127 has a different purpose from a quantity of 127. Before importing an extraction, identify the columns whose exact characters matter: SKU, invoice number, supplier account, barcode, and other reference fields.
Keep these fields separate from quantities and prices. Decide the intended data type before loading the table. This is especially important when a batch combines suppliers with different identifier lengths. Padding every code to the same length can invent characters that were never present in the source.
Know where Excel can change the value
Microsoft documents that Excel can remove leading zeros and change long numbers when it treats them as numeric data. Its guidance describes importing identifier columns as text; current editions also provide controls for certain automatic conversions. Check the functions available in your installed version before relying on a particular setting.
Preserve the converter's raw output and inspect it before opening or resaving it in another application. If the original output contains 00127 but the workbook contains 127, the problem may be the import step. If the zero is already missing in the raw extraction, return to the source and investigate recognition instead.
Use a deliberate import procedure
For a CSV, import through a preview workflow where the column type can be set before loading. Assign text to identifier fields and a suitable numeric type to quantities and amounts. Keep an original-text field when you are testing unfamiliar data. This creates a clear reference for spotting unexpected transformations.
Include sample identifiers with leading zeros, letters, long digit sequences, hyphens, and values resembling dates. Verify the complete string after import. Do not rely solely on the visual width of a cell, because display formatting and the stored value can differ. The test should compare characters, not appearances.
Do not reconstruct missing information blindly
Adding a custom number format can make a known-length code look correct, but it does not establish what the original identifier was. If information has already been lost, recover it from the source document or a trusted product master. Do not guess the number of zeros from neighboring rows alone.
The same caution applies to long identifiers or scientific-looking values. A display change is not a repair when underlying digits have changed. Keep uncertain rows out of a final import until they can be reconciled. For a purchasing workflow, an unresolved product identity deserves more attention than a minor description-formatting difference.
Check the whole route, not just the workbook
Export a small approved sample to the format required by the next system, then import it using the real workflow. Verify that each identifier remains intact. Spreadsheet cells, CSV files, and inventory imports can apply different assumptions, so one successful viewing step is not an end-to-end test.
Document the import settings and keep a small identifier test set alongside the process. Run it again after changing a converter, spreadsheet version, or downstream import template. This simple check helps prevent a formatting adjustment from silently changing which product an otherwise correct price belongs to.
Sources
Evidence status: methodology. No unverified accuracy, savings or traffic claim is made.