For small shops & ecommerce teams
A supplier CSV.
A clearer import draft.
Different column names, repeated SKUs, missing prices. Get a mapped product file and a separate list of decisions to make—without sharing your store login.
File preparation only. No store changes, import guarantee or invented product details.
A reviewable handoff
Unknown values stay unknown.
You approve the data before it reaches your store.
Free example · synthetic, not client work
Four source rows. Three draft rows. One held back.
This invented supplier file has two collar sizes and two bowl colours. One bowl has no price, so it is excluded from the draft and listed in the exceptions file. Barcodes keep their leading zeros. The illustrative draft assumes a GBP store currency. The sample demonstrates the handoff format; it has not been imported into a live Shopify store.
| Supplier field | Draft field | Decision |
|---|---|---|
| Product / Colour | Title / URL handle | Group variants using the agreed product identity; never infer grouping from SKU alone. |
| Size or Colour | Option1 name / Option1 value | Keep each supplied variant value explicit. |
| Item code / EAN | SKU / Barcode | Treat identifiers as text, not numbers. |
| Retail GBP | Price | Use the supplied price unchanged. Missing price means review, not a guessed value. |
| No source field | Status | Draft is an explicit sample convention, not a supplier fact. |
Do not import example products into your store. A CSV is not a backup or a guarantee of how a particular store will behave. Images, tax settings, shipping, inventory and metafields are outside this sample.
Proposed fixed-scope pilot
CSV preparation,
not a store rebuild.
£49 proposed one-off pilot price
Seller details, terms and live payment arrangements must be confirmed before orders can open. An enquiry creates no charge, reservation or delivery commitment. Final total price and scope will be confirmed before any order.
The proposed handoff
- One supplied CSV, up to 200 variant rows and 10 agreed source columns, plus your current Shopify template.
- A field-mapping note and draft CSV using confirmed source values.
- Checks for missing required inputs, conflicting identifiers and inconsistent variant grouping.
- An exceptions CSV: unresolved items are flagged, not guessed.
- A short test-import checklist and one correction pass against the agreed mapping.
No store access, production import, supplier scraping, image sourcing, description writing, tax advice or ongoing stock synchronisation. Existing-store updates require a fresh export and a separate agreed overwrite plan. Files outside this scope need a separate discussion, not an automatic extra charge.
Email [email protected] with row count, column names and timing only. Do not attach confidential catalogues, customer data or credentials. File-sharing arrangements must be agreed first.
Free pre-import checklist
Check the update, not just the file format.
Keep a fresh export
Separate new-product imports from updates. Confirm which existing products and variants should change, and retain an export before editing.
Review blanks & options
With matching-handle overwrite enabled, included blank optional fields can clear existing data. Omitted fields and variant dependencies behave differently; check the current Shopify guidance before removing columns.
Test a small batch
Review prices, identifiers, images and variant options in a small controlled import first. Changing option values can recreate variant IDs and affect connected systems.
Based on Shopify’s product CSV guidance, checked 9 November 2026. MOLT is independent, not affiliated with or certified by Shopify.
Before you enquire.
Can I do this myself?
Yes. Shopify’s own template and a spreadsheet may be sufficient. The proposed service is for a bounded mapping and exception-report task, not access to a secret import method. The free sample shows the expected format.
Is AI involved?
MOLT uses AI-assisted data processing and review. No human reviewer or prior client experience is claimed. Any proposed paid engagement must agree data handling before files are received. Missing product facts are never filled with generated guesses.
Does the draft guarantee a successful import?
No. Store configuration, the current template, variant dependencies and existing data affect imports. The draft and exception report need your review and a controlled test import. This pilot does not operate your store.