Shopify import compatibility
Reviewed September 25, 2026 · Development-store verification: September 11, 2026
PriceListPilot prepares separate cost and selling-price CSV files from your fresh Shopify export. You review and import them manually. Analytical change and issue reports are different files and must not be used as product imports.
What was verified
The documented check used six synthetic products and nine variants in a USD Shopify development store. It included two product images, an image-only CSV row, single barcodes, draft and archived products, and standard variants with up to three option positions.
- Three selected product costs and four selected selling prices were updated through separate imports.
- Unselected sibling cost/price values and all six product IDs and nine variant IDs were preserved.
- Leading-zero identifiers, variant options, product status, images, inventory and other captured fields were preserved.
- A product group with a missing original sibling cost was excluded from the cost file; an independent price update remained valid.
- A metafield-linked option product was identified and excluded from update files.
Comparing fresh exports and the captured fixture state after each import found zero unexpected differences. This establishes those tested cases, not every Shopify configuration, future CSV revision or multiple-barcode arrangement. No production store was used for the verification.
Supported inputs and matching
Use a Shopify product CSV and a supplier CSV or XLSX. Current and documented legacy header aliases are supported by the reader. Match exact string SKUs or barcodes within one vendor; duplicated, missing or ambiguous keys need review instead of a guessed match. The initial import verification covered single barcodes.
Why an update can be excluded
- Metafield-linked options
- These products remain report-only. The app does not offer a supported update file for them.
- Missing original sibling values
- A file may need to carry unchanged sibling values to preserve the product group. If a necessary original value is missing, the corresponding update is excluded rather than filled in or cleared.
- Ambiguous identifiers or invalid prices
- Duplicate matches, malformed costs or unsupported mapped values cannot be safely selected as ordinary update candidates. Check the issue report and source data.
- A stale Shopify export
- The app cannot see live-store edits made after your export. Use a fresh catalog and compare again if the store changes while you work.
What this tool does not do
It does not install a Shopify app, automatically synchronize inventory, create new products from unmatched supplier rows, or write directly to your live store. It does not provide native Shopify undo/history or retain uploaded product files after the browser session ends. Mapping preferences can be saved separately.
Preview and export access
Customer-file previews and issue reports are free. Both paid export options cover at most 5,000 store variants per comparison, with repeat exports during active access. The fictional demo can be used to try the reviewed export workflow. See the service and billing terms for the pass and subscription details.
The production site is a launch preview: the fictional demo, customer-file comparisons and issue reports are free. New purchases for customer-file export access are not open yet.
Further reading
- Update Shopify prices from a supplier spreadsheet
- Shopify’s product CSV reference
- Shopify’s product import guide
Not sure whether your case is covered? Ask a question.