Import an external catalog
Load products and variants from a source system using the external JSON import.
Before you start
You need product import permission and a catalog export prepared for the external bootstrap format. Record which system owns the data. Use the external JSON object format described below, not a flat product array. CSV is not an upload format on this screen.
Import a small sample
- Open Products → Import at External import.
- Prepare a JSON object with a
productsarray. Each product needs anexternal_id,name, and at least one variant. Each variant needs asku. Include the remaining fields required by your source contract. - Upload the JSON file or paste its contents. Start with one product and its variants.
- Run import and inspect the success/failure report. Correct reported records before loading the rest.
- Find the imported product in Products. Verify its external source, variant SKU, currency, price, and quantity.
- Configure ongoing updates through your integration; an initial import alone does not establish continuous sync.
Expected result
Your source catalog is visible in AI Node. Externally managed fields are corrected in the source system, not in the native product form.
Troubleshooting
Invalid JSON must be corrected before import. An empty or missing products array, missing external ID/name, or missing variant SKU is rejected by the screen. Keep stable external IDs and SKUs across updates. For partial results, inspect each failure rather than treating the whole catalog as imported.
Next step
Follow sync monitoring and the developer reference when implementing source-system updates.
Monitor and recover product synchronization
Check source ownership, last sync, integration health, and failed updates.
Import your first catalog and keep it synchronized
Run a small import, verify ownership, and test one ongoing source update.
Developer reference and contract boundaries
Inspect supported integration metadata and distinguish dashboard operations from external APIs.