Shopify product import is not successful merely because a CSV upload completes. A cross-border store must preserve the relationship between SKU, variants, images, inventory, price, market, and SEO fields. Define master data, mapping, encoding, units, currency, and rollback before choosing CSV, an app, or an API.
Write an import contract
Define stable keys for product, variant, SKU, barcode, supplier ID, image, collection, price, and inventory. Record required fields, null rules, enumerations, units, language, market, and update priority. Do not use a mutable title as the key or let one source overwrite price and stock without conflict rules.
Import in batches and sample outcomes
Start with real products and check variants, images, stock, price, URLs, descriptions, collections, tax, and delivery. Import by market or product group, retaining source file, batch ID, error rows, timestamps, and operator. Validate product pages, orders, and inventory after import instead of counting rows only.
FAQ
What matters before an import?
Stable keys, field mapping, encoding, units, currency, system of record, and rollback backup.
Can product titles be used for matching?
Avoid it. Titles change; use stable SKU, ID, or barcode.
What should happen after an import error?
Keep error rows and batch, fix the cause, and retry a small group instead of overwriting everything.
How should multi-market prices be imported?
Validate by market, currency, and validity so a default price cannot overwrite every region.