How to import products and verify the result
SC uses one importer foundation for files and supported feeds: it reads and validates first, shows a plan, and writes only after confirmation.
We will show this workflow with your store data.
Prepare identity
A stable SKU or external ID updates the same product instead of creating a copy.
Check mapping
Map columns to canonical fields and inspect ambiguous or skipped rows separately.
Read the result
Run statistics separate created, updated, skipped and failed rows.
Before applying
Keep the source file
It is needed for repeatable verification and result comparison.
Run preview
Check currency, prices, SKU, availability and protected fields.
Repeat without duplicates
The same mapping profile should reproduce the decision without setup from scratch.
Honest boundary
Formats and policies vary by source. SC does not guess missing identity or currency and presents such a row as a problem.
Related resources
How to resolve an integration error
Distinguish access failures, rate limits, provider outages, mapping and row errors in SC CRM, retry safely and verify the result.
Want the same in your store?
Leave a request — we will show SC CRM on your own tasks and agree on connecting your store.