Skip to content
Back to Site

Prepare CSV Source Data Files

Prepare Product data for the CSV Source Platform using the required products.csv filename, 43-column schema, and record structure.

When CSV is selected as the Source Platform, Next-Cart reads standard Product data from products.csv through File Upload. If the file matches the Next-Cart structure documented here and the requested handling is within supported scope, choose Standard Migration or Managed Migration. A non-standard file that Next-Cart must process directly requires Custom Migration and the relevant Data Import Custom Job.

Use the field names, field order, and row structure defined below. Change the Product values without changing the structure that Next-Cart uses to recognize records.

This is the standard Product template for the CSV Source Platform. It does not establish standard support for separate Customer, Order, or other entity files. Non-standard import structures and additional entity requirements are assessed individually through Custom Migration and the applicable Custom Jobs.

If the file structure or requested outcome is outside this standard Product template, do not assume that renaming the file makes it compatible. Prepare Custom Migration Requirements for the additional work before execution.

Download the CSV Product sample as the starting structure. This downloadable example contains two illustrative Product variants. Replace all sample records with your own Product data, keep the 43-column structure, and save the upload as products.csv.

RequirementRequired format
Source PlatformCSV
Migration ServiceStandard Migration or Managed Migration for this exact standard Product structure; Custom Migration when custom file processing is required
Standard supported file scopeProducts
Connection methodFile Upload
Filenameproducts.csv
EncodingUTF-8
Record layoutOne header row followed by one Product or Product-variant record per row
Columns43, in the required order

The first row must contain these headers in this order:

product_id,sku,price,status,weight,length,width,height,manage_stock,qty,name,description,short_description,barcode,manufacturer,categories,images,option_name_1,option_value_1,option_name_2,option_value_2,option_name_3,option_value_3,attribute_name_1,attribute_value_1,attribute_name_2,attribute_value_2,attribute_name_3,attribute_value_3,attribute_name_4,attribute_value_4,attribute_name_5,attribute_value_5,attribute_name_6,attribute_value_6,attribute_name_7,attribute_value_7,attribute_name_8,attribute_value_8,attribute_name_9,attribute_value_9,created_at,updated_at

Do not rename, remove, add, or reorder columns. When a field has no value for a record, leave the field empty and keep the column in place.

Field groupFields
Product identity, pricing, status, dimensions, stock, and contentproduct_id, sku, price, status, weight, length, width, height, manage_stock, qty, name, description, short_description, barcode, manufacturer, categories, images
Product optionsoption_name_1, option_value_1, option_name_2, option_value_2, option_name_3, option_value_3
Product attributesattribute_name_1 through attribute_name_9, paired with attribute_value_1 through attribute_value_9
Timestampscreated_at, updated_at
  • Use one row for each Product or Product-variant record.
  • Variants of the same Product can use the same product_id with different sku and option values.
  • Keep every option name/value pair aligned by suffix, such as option_name_1 with option_value_1.
  • Keep every attribute name/value pair aligned in the same way. Leave unused pairs empty instead of deleting their columns.
  • In categories, separate multiple category entries with commas and use > for a hierarchy, such as Mobile > Phones.
  • In images, separate multiple image URLs with commas.
  • Because CSV uses commas as delimiters, enclose any value containing commas in double quotes so the value remains in one field.
  • Use numeric 0 or 1 values for status and manage_stock rather than text labels.
  • Use YYYY-MM-DD HH:MM:SS for created_at and updated_at when timestamps are provided.
  1. Create or open products.csv.
  2. Place the required 43-field header on the first row in the exact order shown above.
  3. Enter one Product or Product-variant record per row.
  4. Keep unused fields empty without removing columns.
  5. Check comma-containing values, including category lists, image lists, and descriptions, and quote them where required by CSV syntax.
  6. Save the file as UTF-8 comma-delimited CSV with the filename products.csv.
  7. Reopen the file and confirm that every record still contains 43 fields aligned to the header.
CheckPass condition
Filenameproducts.csv
HeaderAll 43 field names are present in the required order.
Record structureEvery Product or variant occupies one row under the same header.
Empty valuesEmpty data does not remove or shift a column.
CSV quotingValues containing commas remain a single field.
Options and attributesEach numbered name/value pair remains aligned.
TimestampsSupplied timestamps use YYYY-MM-DD HH:MM:SS.

CSV does not require a Source Store URL. When the Target setup provides Store URL, that Target Store URL becomes locked after the required Source and Target setup is successfully connected and the customer proceeds with Continue to Configuration. Later migration activity can use another valid products.csv file, including one prepared from a different originating store, but it must keep the locked Target Store.

See Store URL Locking and Store Identity for the complete rule.

For a standard-template import, a 0/0 Product result means Next-Cart did not recognize Product records from the uploaded CSV structure. If the project instead uses an approved custom import structure, compare the upload with that job’s agreed input requirements rather than forcing it into this standard template.

For the standard template, check the filename, header names, column order, delimiter, quoting, and row alignment. Correct the file and upload it again. If the standard-template checks pass but Product progress remains 0/0, use Troubleshoot Connection Setup and provide the filename, a privacy-safe example row, and the migration result.

File Upload is migration input, not recurring synchronization

Section titled “File Upload is migration input, not recurring synchronization”

Selecting CSV provides a file-based Source for a migration. It does not create a recurring synchronization feed between the file and the Target Store. The standard CSV workflow recognizes Products from products.csv when the required Next-Cart structure is used.

For a non-standard Source file that must be processed without conversion to this template, or for additional entities, repeated-feed handling or unsupported business logic, prepare a Custom Migration request and identify the relevant Data Import Custom Job.

Continue with Upload Source Data Files to prepare and validate the exported files for the Source connection.