Import your first catalog and keep it synchronized
Run a small import, verify ownership, and test one ongoing source update.
Prerequisites
Choose the source system and prepare stable product external IDs and variant SKUs. You need product write access and an integration implementer for ongoing external updates.
End-to-end exercise
- Export one product with two variants from your source into the external import format.
- Import through Products → Import. Inspect every failure in the report.
- Open the product and compare names, source, variant identifiers, currency, price, and stock with the source export.
- Configure the source integration's update path and credentials. Do not treat bootstrap as a scheduled synchronization.
- Change one test variant's stock or price at the source. Deliver the update and inspect its result.
- Reopen the variant in AI Node and verify the changed value. Ask a product question and compare the answer.
- Load the remaining catalog only after the small test succeeds. Monitor sync errors during the first full update.
Expected result and recovery
Imported records retain their external ownership and ongoing updates reach the correct variant. For failures check source IDs, SKU, contract, credentials, and sync logs; do not create a native duplicate to hide a failed update.
Import an external catalog
Load products and variants from a source system using the external JSON import.
Monitor and recover product synchronization
Check source ownership, last sync, integration health, and failed updates.
Products: choose your source of truth
Manage your catalog in AI Node or import products owned by an external system.