Automating supplier price lists means building a repeatable pipeline: receive the file, map the columns, clean the data, apply your margin and stock rules, flag exceptions, then publish only approved rows to Shopify, Amazon, eBay, your ERP or wholesale system. The review step matters. It is what stops one bad supplier spreadsheet becoming hundreds of bad live listings.
If someone on your team spends every week reformatting supplier sheets, copying prices into Shopify, checking stock files or preparing Amazon updates, that is not just admin. It is a business process that has not been properly designed yet.
I care about this because I have lived it. Before Olivers Consulting, I ran a multi-channel ecommerce operation with around 200,000 SKUs across Shopify, Amazon and eBay. One supplier-file process that used to take about eight hours was reduced to roughly two minutes, with human review and bad rows flagged before anything went live.
Start with the file, not the software
The mistake is to begin with the destination: Shopify, Amazon, eBay, Sage, Xero or the ERP. The better starting point is the supplier file itself.
Ask what actually arrives. Is it CSV, Excel, PDF, email attachment or portal export? Do the column names change? Are SKUs reliable? Are pack sizes mixed with units? Does the file include discontinued products, promotional prices or stock that is already out of date?
That assessment decides the automation. A clean weekly CSV needs a different build from a supplier who sends a new spreadsheet layout every month.
The pipeline should have gates
A sensible supplier-price-list workflow usually has six stages:
- Import: collect the supplier file from email, upload, folder or portal export.
- Map: match supplier columns to your fields: SKU, barcode, cost, stock, case size, product title and category.
- Clean: remove blank rows, fix formats, normalise currencies and catch obvious errors.
- Apply rules: add margin, VAT logic, price rounding, minimum margin checks and channel-specific rules.
- Flag exceptions: hold back rows with missing SKUs, strange costs, negative stock or margin problems.
- Publish: send approved data to Shopify, Amazon, eBay, wholesale sheets or your internal system.
The exception stage is the difference between useful automation and dangerous automation. Your team should review the five rows that need judgement, not manually rebuild the whole file.
Do not automate bad rules
If your current process relies on someone “just knowing” which products need a different margin, the automation will expose that. That is a good thing. It forces the business to write down the rules.
For example, one category might need a minimum 35% gross margin. Another might be priced to match a marketplace. Some products may never go to Amazon because the fees ruin the margin. Some wholesale lines may be sold in case quantities only.
Those decisions should not sit in one person’s head. They should be visible in the process.
The useful question: if your product administrator left tomorrow, would someone else know exactly how supplier data becomes live channel data? If not, the process is too dependent on memory.
When automation pays back
The simplest calculation is time saved. If a supplier file takes five hours a week and the loaded staff cost is £25 an hour, that one process costs about £6,500 a year before errors are included.
But the better payback is often control. You know what changed, which rows failed, which margins dropped and which products are safe to publish. That reduces firefighting later.
Automation is not worth it for a one-off task or a supplier you use twice a year. It is worth investigating when the work is recurring, rule-based and painful enough that your team already dreads it.
What to prepare before building
Before asking anyone to build the automation, collect three recent supplier files, your current output file, and the rules your team applies by hand. Mark the awkward cases: missing SKUs, price jumps, pack-size confusion, discontinued products and anything that needs approval.
That gives a builder the real shape of the process. It also stops the project becoming vague. The goal is not “make supplier files easier”. The goal is “turn this supplier format into this approved output, with these rows flagged for review”.
FAQs
Can every supplier price list be automated?
Most recurring supplier files can be automated, but not all should be published without review. The process needs rules for missing data, strange formats, discontinued SKUs and price changes.
Should supplier data update Shopify and Amazon automatically?
Only after checks. A good workflow prepares and validates the data first. Rows that fail the rules should be held back for review rather than pushed live.
Is this better than hiring a product data administrator?
If the work is repetitive and rule-based, automation is worth checking before you hire. If the work needs merchandising judgement or supplier negotiation, a person may still be the right answer.
Free process review
Bring one supplier file you hate dealing with.
In a 30-minute review, I’ll map the workflow, estimate the time cost and tell you whether it is worth automating. If the ROI is not obvious, I’ll say so.