Firstly, a fact – the basic function of supplier spreadsheets containing data is to move product information from one business to another. So far so obvious. However, in practice, for digital merchants they very often create delays, rework, and heightened commercial risk. Your people receive a file which at first glance, appears usable. Then, various team members spend days on grunt work like:
- Renaming columns
- Splitting fields
- Converting units
- Filling gaps
Hardly the most profitable use of their time. Moreover, all this is before anything can enter your PIM or eCommerce platform.Our article explains exactly why this keeps happening, what it’s likely to be costing you operationally and commercially, and what the best alternative actually looks like: A workable intake process which doesn’t cause delays to market or the risk of non-compliance.
A structural, not accidental, problem
Most teams tend to treat bad supplier files as a minor but common irritant. They really aren’t. The root cause is the predictable outcome when two different data models collide.
A typical supplier spreadsheet is created on the foundation of the supplier’s internal logic. It reflects how they manufacture, source, warehouse, or price products. In contrast, your PIM and eCommerce platforms are built around a different set of needs and assumptions, the most important of which are:
- Search
- Filtering
- Comparison
- Channel publishing
- Enrichment
- Regulatory and statutory compliance
That’s why the file never fits cleanly when it arrives.The supplier has one view of the product. You have another. It’s not that either is necessarily wrong. The problem is that the structures, attribute definitions, and validation rules are misaligned from the get-go.
Supplier formats are designed for their schema, not yours
The core issue is that supplier data is hardly ever created to match your product structure.
A couple of instances:
a) A supplier might send you a field labelled “Description.” It contains colour, size, pack count, and marketing copy, all in one cell. In fact, your platform needs those details separated into discrete attributes.
b) A supplier may classify an item under a broad internal category such as “Seasonal Accessories,” but the business may need it mapped across several customer-facing categories with distinct mandatory fields for each.
These mismatches generally appear in the same places:
- field names that look similar but mean different things
- free-text values where your system expects controlled value lists
- style-level data where you need SKU-level variants
- dimensions and weights in inconsistent units
- missing mandatory attributes for channels or marketplaces
- category structures that won’t map to your taxonomy
Hence the need for endless remapping – it becomes routine operational practice (but certainly no less of an irritant). Your team isn’t only loading data but needing to translate one schema into another.
Why standard templates rarely solve it
The logical response of many businesses is to send their suppliers a template and request that they complete it. This can help sometimes but doesn’t alter the underlying issue.
Suppliers work with a multitude of retailers, distributors and marketplaces and each asks for varying formats and different fields. Your template simply becomes one of many. Even if the supplier agrees to use it, they’ll frequently complete it inconsistently, simply skip fields they don’t understand, or populate columns with values which fail your validation rules.
So, although the template ostensibly matches your columns, its columns still aren’t necessarily guaranteed to be populated by data you stipulate as ‘usable.’
That’s why teams end up checking everything manually anyway.
The operational consequence: Never-ending rework
Once you onboard supplier spreadsheets, the burden shifts to your side templates or not. Inevitably, someone has to bridge the gap between what the supplier has sent and your actual product model.
That usually involves some or all of the following:
- renaming and reordering columns
- splitting combined values into separate attributes
- converting units and normalising formats
- mapping categories and variants
- chasing down someone at the supplier for missing data (which they may or may not actually possess)
- correcting values so the upload will pass validation
It’s a repetitive and costly endeavour, often left to skilled people at your end who should be focused on performing what they’re really paid for – higher-value activity such as range expansion, enrichment workflows, or channel optimisation.
The immediate impact is slower onboarding. Products take longer to go live. Seasonal launches slip. New supplier introductions become harder than they should be. Teams spend their week fixing files instead of improving catalogue performance.
The commercial impact is broader than delay
Poor supplier data doesn’t stay in the spreadsheet stage. As it moves through the business, tight launch deadlines often cause the manual mapping to be rushed or inconsistent. The consequences show up downstream:
- weak search and faceted navigation because attributes are not structured properly
- suppressed marketplace listings because required values are missing or malformed
- inaccurate product detail pages that reduce customer confidence
- higher returns caused by wrong dimensions, materials, or compatibility data
- duplicated effort across merchandising, eCommerce and customer service teams
Eventually, what started off as an onboarding issue becomes a trading headache. The catalogue is slower, less reliable and much harder to scale.
Why the cycle keeps repeating
Put simply, it’s because most organisations fix each file, not the intake process.
A new spreadsheet arrivesèThe team cleans it upèThe products go liveèthe next file arrives in a different format, and the work starts again.
No retained and shared mapping logic. No approval gate to prevent poor-quality input being published. All because you’re not enforcing a consistent supplier onboarding procedure.
This also builds product data ‘debt.’ Because every supplier introduces a slightly different version of the truth, the product information management system (such as a PIM platform) fills up, but the quality persists as uneven and ultimately unreliable.
What a workable process looks like
What’s the big fix? First, don’t expect suppliers to think like your PIM. It’s in your hands to build an intake process which is able to absorb variability without creating a need for constant manual intervention. Carry out three key steps:
1. Stabilise the intake rules. Define the attributes, accepted values, mandatory fields, and variant logic required for each product type and channel.
2. Standardise supplier onboarding. Implement clear templates, guidance notes, validation rules, and approval gates so suppliers know what is required before files enter your core workflow.
3. Enforce mapping and validation. Be sure to retain reusable mapping logic by supplier or category and validate incoming files against your schema before they reach the enrichment or publishing stage.
It’s no walk in the park. Nevertheless, once it’s done with diligence, your teams can stop spending their time on basic restructuring and start focusing on initiatives which drive commercial excellence, safe in the knowledge that they no longer need to intervene manually.
Effective onboarding reduces friction everywhere
Supplier spreadsheets aren’t built to naturally match your systems, and never will be Therefore, those businesses that adapt to this fact adroitly don’t need to rely on luck or spreadsheet heroics by teams. They simply put structure around intake, mapping, and validation so that supplier variation doesn’t risk disrupting the rest of your catalogue.
What more can you ask for? Higher-quality data, faster onboarding and, last but certainly not least, a much more reliable foundation for strategic growth.
Next steps
If supplier spreadsheets are creating constant remapping and manual cleanup issues for you, Contact us today at Start with Data. We’ll organise not only a sample output showing how your supplier data can be structured, mapped, and prepared for PIM or eCommerce use without the usual rework, but a demo of the tool which can best help you do this: SKULaunch.