Keep product codes intact when moving data between tools

An identifier is a label, even when it contains only digits

Imagine a supplier uses 00472 for one component and 472 for another. A spreadsheet that turns both into the same number has lost the distinction your ordering system needs. This hypothetical example explains why a product-code workflow needs more than a visually tidy sheet. Preserve the original identifier all the way from the supplier file to the destination record. Use numbers for quantities and calculations; decide explicitly how codes should be stored and compared.

Set the type before the conversion happens

Microsoft documents that Excel can remove initial zeros when it interprets a value as a number. It also limits numeric precision to 15 significant digits. For identifiers, its guidance includes setting imported columns to text through Power Query. Automatic conversion controls depend on the Excel version. Formatting a damaged value afterwards cannot recover information already lost, so inspect the original source when repairing an affected file.

Explains numeric conversion, precision and text imports. Product-code agreement and test examples are proposed implementation practices. Microsoft: Keeping leading zeros and large numbers

Write a short identifier agreement

For each supplier, record the identifier column, whether letter case matters, whether spaces are meaningful and which system defines the authoritative value. Do not silently remove punctuation or add zeros to reach an assumed length. A code with an unexpected shape belongs on an exception list until someone familiar with the catalogue confirms it. Keep the source value alongside any approved normalized version so a reviewer can see exactly what changed.

Check the complete round trip

Create a disposable sample with an ordinary code, one starting with zero, a long digit-only identifier and a code containing letters. Send it through the same export, spreadsheet edit and import steps your team plans to use. Compare exact values at the destination with the original file, rather than checking only how cells appear on screen. Confirm that two distinct codes still select two distinct records. Include a saved-and-reopened file because that is often part of the real working routine.

Keep AI away from guessing the missing characters

An assistant can explain which rows failed the agreed checks and prepare a question for the supplier. It should not reconstruct a missing prefix because similar products use one. If a code has already changed, retrieve a clean source export and reconcile affected rows before another update. Your purchasing or catalogue owner approves the repaired mapping. Stop downstream product updates when identifier checks fail, instead of letting a plausible description stand in for a verified match.

Decide whether a direct connection would be simpler

Measure how often files pass through manual spreadsheet edits and how much checking each transfer requires. A native export setting or controlled import may solve the problem without another agent. Include setup, exception review and maintenance costs when comparing alternatives. Exovara can help test the actual route between your tools and document the field rules. The useful result is a reliable match that your team can trace, not a larger number of automated updates.

Discuss an implementation

This guide applies across Canada. We provide remote AI consulting for businesses in Calgary; it does not describe a local client or a staffed office.

AI consulting in Calgary · Explore the service · Compare setup options