Why Supplier Price Imports Should Not Overwrite Everything

Imagine an electrical wholesaler handling this situation. A new supplier file arrives and the office imports it over the price workbook.

Locally agreed exceptions disappear with no warning. This is an illustrative situation, but the difficulty is familiar: the team can see individual pieces of work without a dependable explanation of what should happen next. It deserves a closer look before another tool is added. The aim is to make the next action clear without adding unnecessary administration.

The import does not distinguish supplier-owned values from adjustments maintained by the business. Whole-row replacement hides those different responsibilities.

Supplier data and local commercial judgement should occupy different fields. This makes a routine refresh possible without overwriting decisions the supplier file cannot know about.

A changed supplier cost can be reviewed alongside its effective date and unit. Local adjustments remain separate inputs to the business's own decision. This gives staff a clearer basis for checking the final result than a workbook where the new file silently replaces every previous value. The record may look complete while still leaving a business question unanswered. That encourages workarounds: a private note, another spreadsheet or a message to a trusted colleague. Each workaround helps locally but can make the overall process harder to follow.

Separate supplier prices from local adjustments and preview changes before applying them. Match on stable product references and send unknown items for review.

If an automated step changes existing information, preview the proposed changes and retain a correction route. Check whether built-in import settings or a clearer workbook structure solve the problem before commissioning code. An identifier, a measured quantity and a displayed value may look similar while requiring different treatment. The output should be checked in the receiving application, not only in the spreadsheet used to prepare it. Define what each relevant column means before deciding how it should be read or written. Keep the original file unchanged while testing the import or calculation on a controlled copy. Unexpected values should produce a usable review item rather than a plausible-looking guess.

A supplier list may omit freight, units or other pricing conditions, so a raw value is not automatically the final selling cost.

For background relevant to supplier price ownership, see The Spreadsheet Nobody Dares to Touch. The issue here is the narrower workflow described in this example.

Import a changed price, a new product and a product with an agreed local override. Choose examples that reflect actual working conditions rather than only the easiest records. Have staff review what was retained, changed and left unresolved. The test is useful when it reveals a decision to improve, not only when the software reports completion.

For supplier price ownership, review the proposed outcome with the staff responsible. Compare the original values, stored values and receiving-system output for the chosen sample. Counts alone will not reveal every interpretation error. Keep rejected rows visible with an explanation so the administrator can correct the cause rather than guessing at a replacement. Before expanding the change, check whether staff can identify and correct an unsuitable result. A small reliable adjustment is more useful than a wider process that nobody can safely maintain.

At Software Logic, we help businesses examine practical improvements to spreadsheet processes, starting with the work their existing tools need to support. Which local decisions would your next supplier import accidentally erase?