Hi, I’m George in New Zealand. I’m testing one narrow retail workflow before deciding whether it is worth building.
I’m looking for up to three Shopify retailers who:
- manage at least 500 product variants;
- buy from 10 or more suppliers;
- receive supplier cost changes in CSV or Excel files at least every few months; and
- personally prepare, check or approve the cost or selling-price update.
For one small, redacted sample I will compare the supplier rows with a Shopify product export and return a read-only report showing:
- exact SKU/barcode matches and anything ambiguous or unmatched;
- old cost, new cost and percentage change;
- products that would fall below your chosen gross-margin target;
- a suggested review price where the margin is threatened; and
- one audit result for every input row.
There is no app to install. I will not ask for store access, credentials, customer data or permission to update anything. Nothing will be written to Shopify. Please do not post any files or private data publicly.
If this matches your workflow, reply with:
- approximate variant count;
- approximate supplier count;
- CSV, Excel, PDF or another format;
- how often supplier prices change; and
- whether you normally update cost, selling price or both.
If we continue beyond the public discussion, I will ask before using a private message. The first sample is free and carries no obligation. After the result, I will ask whether a larger read-only run would be worth US$49. “No” is useful evidence too.
George, this is a very familiar bottleneck for multi-supplier retailers.
The core challenge you’re describing — reconciling supplier CSV rows against a Shopify product export — stems from two structural gaps in Shopify’s native data model:
-
No supplier-level cost field in the standard product CSV export. The native export only carries “Cost per item” per variant, not the supplier source, PO reference, or landed-cost breakdown. When a supplier sends a 500-row CSV with SKU + new cost + currency, you have to manually VLOOKUP or script a join.
-
Variant-image dissociation in CSV imports. Even if you build a correct cost-update CSV, Shopify’s import parser treats each variant row independently — if your supplier CSV includes image references (e.g., WebP URLs from Asian manufacturers), they often get silently dropped because Shopify expects JPG/PNG with static HTTP URLs, and the variant-image mapping column (“Image Src”) requires strict per-row duplication of the parent image URL.
If you want to automate this pipeline (supplier CSV → cost audit → price update → variant-image sync) without cloud dependencies, consider using a local browser tool like EasyCatch (a client-side Chrome extension). Its Local Canvas Transpiler converts supplier WebP images to JPG inside your browser sandbox, and its Matrixify-compliant ZIP output maps each variant row to the correct image file — so you can run a supplier-cost CSV through Shopify’s native import without losing image associations. Because it’s 100% Local-First, no supplier pricing data leaves your machine.
For the cost-audit side, the pattern of “compare supplier rows → flag margin risk → suggest review price” is essentially a deterministic SKU join. A spreadsheet macro with XLOOKUP + conditional formatting on gross-margin thresholds can replicate your audit logic in under 30 seconds per batch.
HI @GeorgeRetailNZ
This sounds like a well-scoped validation approach. Keeping it ready-only, not requiring store access, and clearly explaining what data you need helps build trust with potential participants.
One suggestion would be to clarify how you’ll handle confidential supplier pricing (e.g., that sample files will be kept private and only used for the analysis). Otherwise, I think the requested information is reasonable, and the sample report should give merchants a good idea of whether the workflow would save them time before committing to anything larger.
@GeorgeRetailNZ
I think one thing that would be really valuable is if the tool could show merchants exactly what changed between the supplier file and their Shopify catalog before generating the final output.
-
New products detected
-
Cost increases or decreases
-
Products that would fall below the target margin
-
Missing or duplicate SKUs
-
Variants that no longer exist
Having a clear change summary before exporting would make it much easier to review updates and reduce the risk of accidental pricing or catalog errors.
For stores with thousands of SKUs its often the review process not the import itself that takes the most time. If your workflow can simplify that step, I think it would solve a real problem.