Bulk import / export
What it does
CSV/XLSX catalogue import + exports
A ten-thousand-piece catalogue should take an afternoon to bring online, not a season. Bulk import ingests your existing CSV/XLSX export, maps your columns to the platform's jewellery-native fields, and reports every rejected row with the reason.
After import, AI enrichment drafts the fields no spreadsheet contains: search keywords, vernacular names, facets, descriptions. You approve anything customer-visible — and there is one hard rule: money, weight, purity and HUID are NEVER AI-filled. Those come only from your data.
How it works in your store
- Upload CSV/XLSX; map your columns to catalogue fields once — the mapping is remembered
- Validation report: every rejected row with the exact reason, fix and re-run
- Images attach by URL or bulk upload, matched by SKU
- AI enrichment drafts keywords, facets and descriptions for your approval
- Money, weight, purity and HUID are never AI-generated — hard rule
- Re-imports upsert by SKU, so price/stock refreshes are routine
On your surfaces
Questions jewellers ask
What file formats work?
CSV and XLSX. On the concierge plan you can also hand over photos and voice notes and our pipeline drafts the listings for your approval.
What if my spreadsheet has errors?
The validation report lists every rejected row and why — nothing half-imports silently. Fix and re-run; re-imports upsert by SKU.
Will AI invent prices or purities?
Never. Money, weight, purity and HUID come only from your data; AI drafts only descriptive and search fields, and you approve those before they go live.