Prepare XLS Source Data Files
Prepare Product data for the XLS Source Platform using the required products.xls workbook, product worksheet, 43-column schema, and record structure.
Prepare XLS Source Data Files
Section titled “Prepare XLS Source Data Files”When XLS is selected as the Source Platform, Next-Cart reads standard Product data from products.xls 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.
Keep the workbook structure, worksheet identity, field names, and field order defined below. Change the Product values without rebuilding the workbook into a different layout.
File scope
Section titled “File scope”This is the standard Product template for the XLS 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 sample workbook
Section titled “Download the sample workbook”Download the XLSX Product reference workbook to inspect the required product worksheet and all 43 columns. To prepare the native products.xls upload, open this workbook in Excel or a compatible spreadsheet editor and use Save As → Excel 97–2003 Workbook (.xls). Verify the resulting file is genuinely in XLS format and still contains the product worksheet and all 43 fields. Changing the filename extension alone does not convert XLSX to XLS.
- Replace both illustrative example records with your own Product data and preserve the worksheet, headers, and column order.
- The XLS Source setup expects
products.xls. Save the actual XLS file in that format, not an.xlsxfile renamed to.xls. - Use the XLSX copy as the reference and save a separate verified XLS copy for upload. If you cannot create a genuine XLS workbook or need help confirming the format, contact Support Tickets before uploading.
Required XLS structure
Section titled “Required XLS structure”| Requirement | Required format |
|---|---|
| Source Platform | XLS |
| Migration Service | Standard Migration or Managed Migration for this exact standard Product structure; Custom Migration when custom file processing is required |
| Standard supported file scope | Products |
| Connection method | File Upload |
| Filename | products.xls |
| Workbook format | XLS (.xls) |
| Product worksheet | product |
| Record layout | One header row followed by one Product or Product-variant record per row |
| Columns | 43, in the required order |
The header row must contain these fields 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_atDo not rename the product worksheet, rename fields, remove fields, insert additional columns, or reorder the Product columns. Do not add title or note rows above the header.
Supported Product fields
Section titled “Supported Product fields”| Field group | Fields |
|---|---|
| Product identity, pricing, status, dimensions, stock, and content | product_id, sku, price, status, weight, length, width, height, manage_stock, qty, name, description, short_description, barcode, manufacturer, categories, images |
| Product options | option_name_1, option_value_1, option_name_2, option_value_2, option_name_3, option_value_3 |
| Product attributes | attribute_name_1 through attribute_name_9, paired with attribute_value_1 through attribute_value_9 |
| Timestamps | created_at, updated_at |
Format Product records
Section titled “Format Product records”- Use one worksheet row for each Product or Product-variant record.
- Variants of the same Product can use the same
product_idwith differentskuand option values. - Keep option and attribute name/value pairs aligned by their numeric suffix.
- Leave unused cells blank. Do not remove the corresponding columns.
- Keep multiple category entries in one
categoriescell, separated by commas, and use>for hierarchy where needed. - Keep multiple image URLs in one
imagescell, separated by commas. - Use numeric 0 or 1 values for
statusandmanage_stockrather than text labels. - Use
YYYY-MM-DD HH:MM:SSforcreated_atandupdated_atwhen timestamps are provided.
Prepare the workbook
Section titled “Prepare the workbook”- Open
products.xlsand keep the Product table on theproductworksheet. - Keep the required 43-field header row unchanged and in the exact order shown above.
- Replace the Product values with the data that should be migrated.
- Keep one Product or Product-variant record per row and leave unused fields blank.
- Do not add merged headings, introductory rows, alternate field names, or extra columns to the Product table.
- Save the workbook in XLS format with the filename
products.xls. - Reopen the workbook and confirm that the worksheet, header, and records remain aligned.
Verify before upload
Section titled “Verify before upload”| Check | Pass condition |
|---|---|
| Filename | products.xls |
| Workbook format | The file remains a valid .xls workbook. |
| Worksheet | The Product table remains on product. |
| Header | All 43 fields are present in the required order. |
| Record rows | Every Product or variant occupies one row under the header. |
| Empty values | Empty data remains in blank cells without removing columns. |
| Options and attributes | Each numbered name/value pair remains aligned. |
| Timestamps | Supplied timestamps use YYYY-MM-DD HH:MM:SS. |
Store identity for file-based migrations
Section titled “Store identity for file-based migrations”XLS 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.xls 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.
If Product progress is 0/0
Section titled “If Product progress is 0/0”For a standard-template import, a 0/0 Product result means Next-Cart did not recognize Product records from the uploaded workbook 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, XLS format, product worksheet, header names, column order, and row alignment. Correct the workbook 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 XLS provides a file-based Source for a migration. It does not create a recurring synchronization feed between the workbook and the Target Store. The standard XLS workflow recognizes Products from products.xls 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.
Next Steps
Section titled “Next Steps”Continue with Upload Source Data Files to prepare and validate the file for the Source connection.