Product data & imports
Product data cleaned, matched and imported.
I turn awkward supplier information into catalogue data you can actually use.
When the catalogue is the real problem
If supplier files, exports and your live catalogue disagree, I can clean the data, match the records and move the usable parts into WooCommerce without quietly guessing the rest.
Where I focus
The difficult part of a product import is rarely pressing the import button. It is working out which records match, which prices mean what, how variations belong together and what to do with the rows that do not fit. That is where I spend the attention.
Start with the source, not the upload
A supplier spreadsheet, a website export and your store can all describe the same item differently. I look for reliable identifiers and separate definite matches from records that need checking.
The work may involve cleaning columns, restructuring data, matching reliable product identifiers or bringing information from more than one source together.
What I've worked on
Examples include matching supplier prices by reliable product identifier, catalogue expansion with exception reporting and staged imports involving product variations.
Those examples are deliberately specific. A successful catalogue import is not automatically proof of a complete live stock integration.
Keep the awkward rows visible
A file that imports without errors can still contain wrong matches or missing items. I want to know what matched, what did not and what was deliberately left unchanged.
For a price update, that means treating an unmatched product as an exception, not guessing which price belongs to it. For a new catalogue, it means checking the product relationships as well as the row count.
Show me the data you are trying to untangle
Send me the site or a safe sample of the data and explain what is taking too long or not working. I will focus on the smallest useful job first.
Make the next update less painful
Where the data will come back regularly, the structure should support another run. Stable IDs, clear field ownership and a defined exception process are more useful than a one-off file nobody understands later.
Repeatable identifiers and the difference between imports and ongoing sync are good places to start.
Scope the result properly
The deliverable might be a cleaned dataset, a tested import or a repeatable update workflow. It doesn't have to include every product rewrite, image repair and supplier integration at once.
A small source sample and an example of the required output will tell me more than the phrase 'just upload the products'.
Questions
Can you work from more than one source file?
Yes. Matching the records and agreeing which source owns each field are part of the work. Conflicting or unmatched rows need review, not a guessed merge.
Will the next import overwrite my manual edits?
That depends on the update rules. We need to agree field ownership and configure the importer accordingly, then test a repeat run before relying on it.
Explore this area
- Matching supplier prices to WooCommerce products
- Expanding a catalogue and finding supplier exceptions
- Testing a large variable-product import
- Reconciling shop stock and online products
- Bulk promotional price updates
- Investigating stale price data
- Finding alternatives for unavailable products
- From technical datasheets to product pages
- Matching products, variations and brochures
- Does the product data need fixing, or the whole website?
- What makes a product import safe to repeat?
- A product, a variation and a kit are not the same record
- What I check before a bulk price update
HAVE SOMETHING AWKWARD?
Show me the data you are trying to untangle
Send me the URL, what is happening, what you have already tried and what a useful result would look like. A small anonymised sample is enough to start - do not send passwords, credentials or sensitive customer data.