# Shopify Supplier Data: Standardise Inconsistent Import Files
> Multiple suppliers, multiple file formats, multiple column naming conventions. How to stop reformatting supplier files before every Shopify import.
- Published: 2026-09-09
- Author: Importier Team
- Category: Import Guides / File Imports
- Canonical: https://www.importier.app/blog/shopify-supplier-data-standardisation
---
A fashion wholesale merchant sources products from five suppliers. Every two weeks, each one sends a product file. Supplier A uses "Product Title" as the column name, prices in AUD, and weights in kilograms. Supplier B uses "Item Description" for the title, "Unit Cost" for price, and weights in pounds. Supplier C sends an Excel workbook with a company header spanning rows 1-4, column names on row 5, and a merged cell covering three description columns. Supplier D separates size and colour into two rows per product. Supplier E sends a PDF price list.
Shopify supplier data standardisation is the process of getting all five of those files into a consistent format that an import tool can process. For this merchant, that process takes 90-120 minutes per supplier file before a single product reaches Shopify. They are spending seven or more hours a month reformatting files before any import can happen. None of that time adds a product to their store.
The root cause is that every supplier maintains their own product database in whatever structure makes sense for their business. They are not trying to produce Shopify-compatible files. They are producing files that work for their own ERP, accounting system, or warehouse management tool. The merchant inherits that structure every time a new product list arrives.
## Why supplier file inconsistency is harder than it looks
Most merchants expect supplier data normalisation to be a one-time problem. Map the columns once, done. In practice, supplier files have four overlapping inconsistency layers, each of which requires a different fix.
**Column names**: "Price", "Unit Cost", "RRP", "Retail", "Wholesale Price", and "List Price" are all used by different suppliers to mean the same thing: the price the merchant sells the product at. [Shopify's CSV column specification](https://help.shopify.com/en/manual/products/import-export/import-products#product-csv) requires "Variant Price" as the exact column name. Every supplier column name that differs from the Shopify standard is a mapping challenge that must be resolved before import.
**Column meanings**: The harder case is when two suppliers use the same column name to mean different things. "Description" from Supplier B means the product title (20-30 words). "Description" from Supplier C means the long-form product body (200-400 words). If you treat them the same way, you either import short descriptions as the product body or product titles as very long text. Neither produces usable products.
**File structure**: A CSV with headers on row 1 is a clean starting point. An Excel file with branding rows, merged cells, hidden discontinued rows, and a sheet for each product category requires a separate handling decision at each step before any column mapping begins.
**Unit and format differences**: Supplier A prices in AUD. Supplier B prices in USD. Supplier C gives weights in pounds. Supplier D uses a comma as a decimal separator ("1,250" meaning $1.25 in some European locales). Each of these produces either silent errors or import failures unless normalised before import.
Most of these inconsistencies do not cause import failures. They cause silent wrong data. A price column named "Unit Cost" that holds wholesale prices is imported at wholesale instead of retail. Shopify creates the product without any error. The merchant discovers it 48 hours later when customers start ordering at cost price. Supplier data inconsistency is the leading source of products imported at wrong prices, wrong weights, and wrong descriptions in Shopify catalogues.
## The four normalisation steps before every import
Regardless of supplier or file type, every import goes through the same four normalisation decisions. The work is not different from supplier to supplier; only the answers are different.
**Step 1: File format detection.** Is this a CSV, Excel, TSV, or PDF? [Excel files with formula cells and merged headers](/blog/shopify-excel-import) need different handling from a flat CSV. A PDF needs AI parsing to extract product data before any column work can begin. The file format determines which tool to open the file with and what structural problems to expect.
**Step 2: Header row identification.** Where do the actual column names start? Row 1 for a clean CSV. Row 5 or 6 for a supplier workbook with a company letterhead. The [header row selection guide](/blog/shopify-csv-header-row-selection) covers this step in full, but the key point is that an import tool that assumes headers are always on row 1 will misread any supplier file that uses the top rows for branding.
**Step 3: Column mapping.** Which supplier column maps to which Shopify field? This is the step that takes the most time when done manually, and the step where column-name collisions between suppliers create the most errors. "Description" from Supplier B maps to Title. "Description" from Supplier C maps to Body (HTML). These are opposite mappings for the same column name, and both are correct for their respective suppliers.
**Step 4: Unit and format conversion.** Does the price need a currency conversion? Does the weight need a unit conversion from pounds to grams? Are there prices formatted with commas as decimal separators? These conversions must happen before the data reaches Shopify, not after.
## How import profiles eliminate the per-file setup work
The first time a merchant imports from a new supplier, the four normalisation steps take time. The second time from the same supplier, they should take zero time. That is the purpose of [import profiles](/blog/shopify-import-profiles): the column mapping, header row selection, unit settings, and price conversion configuration are saved once and reused on every subsequent import from that supplier.
An import profile stores:
- Which row contains the column headers
- The column-to-Shopify-field mapping for every column in the file
- Price markup percentage (if the supplier provides cost rather than retail prices)
- Currency (if the supplier prices in a foreign currency)
- Weight unit (if the supplier uses a unit other than grams)
When the same supplier sends next month's price update, the merchant selects the profile, uploads the file, and lands directly in the Review step. The four normalisation decisions are already made.
The "Description" collision problem is solved by profiles because the mapping is tied to the supplier identity, not to the column name. Profile B maps "Description" to Title. Profile C maps "Description" to Body (HTML). Both profiles coexist. The merchant never remaps.
For a merchant with five suppliers, five profiles handle the normalisation permanently. Adding a sixth supplier means creating one new profile. Every subsequent import from that supplier uses the saved profile.
## What to do when supplier files change structure
Supplier files change. A supplier upgrades their ERP system and the export format shifts. A new product category adds columns that did not exist in previous files. A supplier switches from CSV to Excel without warning.
When a file structure change invalidates a saved profile, the fix is to update the profile rather than start from scratch. Most changes affect one or two columns, not the whole structure. Updating a profile for a renamed column takes minutes rather than the 90-120 minutes of manual normalisation the first import required.
For structural changes that go beyond column renaming (a supplier switching from a single-sheet CSV to a multi-sheet Excel workbook), the profile needs a reset on the structural settings (header row, sheet selection) before the column mapping step can be validated. The saved column mappings usually survive this reset if the column names themselves have not changed.
## Handling suppliers who send the same product with different SKUs
Multi-supplier operations often carry overlapping product ranges. Supplier A and Supplier B both supply the same brand's products, but Supplier A uses the brand's SKU codes and Supplier B uses their own warehouse codes. An import from both suppliers without de-duplication creates the same product in Shopify twice under different SKUs, with competing inventory levels and potentially different prices.
The practical approach is to use Shopify's SKU as the unique product identifier and standardise incoming SKU formats before import. In the column mapping step, a "Supplier Code" column from one supplier and a "Model Number" column from another can both be mapped to Shopify Variant SKU — giving the merchant a consistent field to work from regardless of what the supplier calls it.
For title and keyword standardisation across suppliers, the [bulk title editing tool](/blog/shopify-bulk-edit-product-titles) applies formatting rules to titles after import: removing supplier-specific prefixes, standardising case, and front-loading relevant keywords. A merchant who wants consistent title formats across products from five suppliers can run a single Title Optimizer pass after each import batch rather than editing titles individually.
Seven hours a month reformatting supplier files is a hidden cost that most merchants accept as normal. It is not normal. The normalisation work only needs to happen once per supplier, not once per import.
## Building a standardisation workflow across five suppliers
For a merchant managing five suppliers with fortnightly import cycles, a repeatable standardisation workflow reduces the per-import time from 90-120 minutes to under 10 minutes per supplier.
The setup investment happens once when each profile is created. From that point, the fortnightly import cycle is: select the profile, upload the file, review 10-20 products in the Review step for structural surprises, confirm the import. The Review step is the quality gate that catches any file structure changes the profile has not yet been updated for. Per [Shopify's import documentation](https://help.shopify.com/en/manual/products/import-export/import-products), product imports cannot be partially undone at the Shopify level. The Review step in Importier is the last point where an incorrect mapping is visible before products go live.
For an operation that processes five supplier files every two weeks, that is ten imports per month. At 90 minutes of manual normalisation each, that is 15 hours per month of reformatting work that produces no products. At 10 minutes per import with profiles, it is under two hours per month. The 13+ hours freed up can go toward reviewing the products the imports produce, writing channel-specific descriptions, or setting category metafields on the newly imported catalogue.
## Key takeaways
- **Supplier file inconsistency is not a one-time problem.** Every supplier has their own file structure, column names, unit conventions, and format. These differences persist across every import from that supplier unless normalisation is automated.
- **The "Description" collision is the most dangerous inconsistency.** When two suppliers use the same column name to mean different things, a shared mapping produces wrong data silently for at least one of them.
- **Import profiles solve the reuse problem.** The normalisation work for each supplier happens once when the profile is created. Every subsequent import from that supplier uses the saved mapping, header row, unit settings, and currency configuration.
- **Review every import before confirming, even with a saved profile.** Supplier files change when they upgrade systems. The Review step in Importier shows every product with its mapped values before anything reaches Shopify, giving the merchant one final check for structural changes the profile has not yet absorbed.
- **The time savings compound quickly.** For a merchant running two imports per supplier per month across five suppliers, switching from manual normalisation to profile-based import saves ten or more hours per month.
Stop reformatting supplier files before every import at [importier.app](https://importier.app).