Catalog import

Prepare a file

Use CSV or Excel through Retail > Catalog. Keep barcodes as text in spreadsheets so leading zeroes are not lost before import. The required fields are barcode, SKU/product code, product name, and category. Optional fields include size, color, MRP, collection and a supported image URL field.

Example CSV:

barcode,sku,name,category,size,color,mrp
001234,SHIRT-BLUE-M,Blue cotton shirt,shirt,M,Blue,1499
001235,SHIRT-BLUE-L,Blue cotton shirt,shirt,L,Blue,1499

Preview and map columns

1. Choose your file in Retail > Catalog.
2. Check the automatically recognized columns. Map unfamiliar headings to the correct standard fields; explicitly ignore columns you do not want imported.
3. Run preview and inspect row errors, samples, and ignored columns.
4. Correct invalid rows and preview again, then import the reviewed data.
5. Review the final import report and check the catalog.

Changing the file, organization, or mapping invalidates the preview. Preview is not a reservation or a guarantee that products are ready for generation. Limits are 5,000 data rows and 200 columns, subject to upload size limits. Quoted CSV commas, escaped quotes and multiline cells are supported.

Automatic recognition can use supported alternative headers. An explicitly selected column does not fall back to another column when its value is empty. Treat ignored columns as omitted, not saved.

Updates and duplicates

Within your organization, the barcode identifies the existing record to update. A matching SKU alone is not the duplicate key. Give separate variants distinct barcodes. Omitted optional fields preserve existing values; explicitly supplied blank optional fields clear those values. Re-importing an archived barcode restores its existing record, so do not include archived items unless you intend to restore them.

An import preserves existing image/preparation readiness; it does not approve new images or run preparation. Image URLs are references only and are not automatically downloaded. Finish image setup and check readiness.

Custom columns and vendor exports

A column such as Fabric is not automatically stored as a custom field or injected into a workflow. Add supported typed values through Custom fields after import. Standard column mapping and catalog-to-workflow mapping are separate operations.

A vendor export may be usable after mapping its standard columns, but general CSV/Excel support does not imply a dedicated LOGIC ERP connector, image importer or stock synchronization. Confirm those integrations with Aabhas before relying on them.

Partial or interrupted imports

Review errors before retrying. An interrupted import can leave successfully saved products in place; those writes are not automatically rolled back. If a run remains pending or fails, inspect the catalog and contact support rather than assuming nothing was saved. Older integrations may save valid rows while reporting invalid ones; Studio requires a valid preview for its reviewed import flow.