Skip to main content

How to Review and Fix BOM Import Validation Errors

Use this guide when a multi-product BOM import pauses during pre-processing because validation errors or warnings were found.

Before products are created, every BOM file is automatically checked for formatting and data quality issues. This helps you identify and fix problems before the import creates products or BOM items in the platform.

What happens during pre-processing

When you upload a BOM file, the platform validates the file before creating any products.

There are three possible outcomes:

  1. No errors or warnings are found
    The import continues as expected. You will see the product and BOM item counts before confirming the import.

  2. Warnings are found
    The import can still continue. Warnings are shown for review, but they do not block the import.

  3. Blocking errors are found
    The import pauses. No products are created until the errors are corrected and the file is re-uploaded.

Blocking errors vs. warnings

  • Blocking errors

    Blocking errors must be fixed before importing. They usually indicate that required data is missing, incorrectly formatted, or not recognized by the system.

    If blocking errors are found, an error card appears during pre-processing. The card shows how many rows contain issues and includes a link to download the error report.

  • Warnings

    Warnings are flagged for review but do not stop the import.

    For example, generic item names such as “Misc”, “Other”, “TBD”, “N/A”, “Unknown”, or “Various” may be flagged because they can prevent accurate emission factor mapping.

You can choose to proceed with warnings or fix them before continuing.

Download the error report

When validation finds blocking errors, you can download an annotated XLSX copy of your uploaded file.

The error report helps you identify exactly which rows and cells need to be corrected.

The report includes:

  • A Valid entry? column marking each row as valid or invalid

  • An Error description column with a plain-language explanation of the issue

  • Invalid cells highlighted in red for quick scanning

  • A Data Format Guideline sheet explaining the expected format for each column

  • Country of origin dropdowns pre-populated with valid ISO country codes, so you can correct values directly in the file

How to use the error report

  1. In the validation error card, click the link to download the error report.

  2. Open the downloaded XLSX file.

  3. Review the Valid entry? column to identify invalid rows.

  4. Read the Error description column to understand what needs to be fixed.

  5. Check the red-highlighted cells to locate the specific values causing the error.

  6. Use the Data Format Guideline sheet to confirm the expected format for each column.

  7. Correct the flagged rows directly in the downloaded file.

  8. Save the corrected file.

  9. Re-upload the corrected file in the product import flow.
    ​

If the file passes validation after re-upload, the import continues and you can review the product and BOM item counts before confirming.

Validation checks

The following checks are performed during BOM file pre-processing.

  • HS code

    The HS code must be a valid 6-digit numeric code from the HS code reference list.

    For multi-product uploads, HS code is required for top-level product rows. It is optional for other rows, but if the field is populated, it will always be validated.

    This means an invalid HS code will trigger an error even when the field is optional for that row.
    ​

  • Amount

    Amount must be a positive number and cannot be empty.

    If an item is missing an amount, estimate the weight or quantity before re-uploading the file.
    ​

  • Unit

    Unit must be recognized by the system.

    Supported units include:

    • Weight-based units, such as g, kg, t, tn, LT, and lb

    • pcs

    If your source data uses unsupported units, convert them to a supported unit before re-uploading.
    ​

  • Product unit

    Product unit is required for top-level product rows in multi-product uploads.

    It must be a valid unit, such as:

    • kg

    • t

    • l

    • m²

    • m³

    • pcs
      ​

  • Country of origin

    Country of origin is optional. However, if provided, it must be a valid ISO 3166-1 country code.

    The downloadable error report includes country of origin dropdowns pre-populated with valid ISO country codes, so you can correct country values directly in the file.

Warning checks

Warnings do not block the import, but reviewing them can improve emission factor mapping and PCF accuracy.
​

Generic item names

Generic or placeholder item names are flagged as warnings.

Examples include:

  • “Misc”

  • “Other”

  • “TBD”

  • “N/A”

  • “Unknown”

  • “Various”

Replace generic names with more specific material, component, or product names where possible.

For example, instead of “Misc packaging”, use “Corrugated cardboard packaging” if that better describes the item.

Recommended pre-processing steps before upload

Before uploading a BOM file, review and prepare your data to reduce validation errors.

1. Confirm the file format

Make sure your file follows one of the supported BOM template formats:

  • hierarchical-bom

  • multiproduct-bom

Use the instructions in the first tab of the downloaded template to confirm which fields are required for your file type.

2. Check top-level product rows

For Level 0 or top-level product rows, confirm that the following fields are completed:

  • Product name

  • Product unit

  • HS code

These fields are required to create products and support benchmarking and proxy data.

3. Check BOM item amounts and units

Each BOM row must include an amount and a recognized unit.

If values are missing or not weight-based, add estimates before uploading. For example:

  • Estimate missing weights for components or materials

  • Convert unsupported units into supported units

  • Use pcs only when the item is counted by piece

4. Add weight estimations where needed

If BOM items are missing amount and/or unit, or if the values are not weight-based, add weight estimations before upload.

This helps the platform calculate emissions more accurately and reduces validation errors.

5. Add energy estimations where needed

If energy consumption data is missing, add energy estimations before upload.

Use the best available source data, such as internal production records, supplier information, or reasonable engineering estimates.

6. Review HS codes

Confirm that HS codes are valid 6-digit numeric codes.

For top-level products, HS codes are required. For other rows, HS codes are optional, but any populated HS code must still be valid.

7. Review country of origin values

Country of origin is optional, but any populated value must follow ISO 3166-1 country code formatting.

If validation flags a country value, use the dropdowns in the downloadable error report to select a valid country code.

8. Replace generic item names

Review item names and replace placeholders such as “Misc”, “Other”, “TBD”, “N/A”, “Unknown”, or “Various” with more specific descriptions.

Specific item names improve emission factor mapping and reduce the need for manual review.

9. Check file size

Multi-product BOM uploads are limited to 500,000 rows.

Files exceeding this limit are rejected during validation with a clear message. If your file exceeds the limit, split it into smaller upload batches.

Re-upload the corrected file

After correcting the file:

  1. Save the updated XLSX file.

  2. Return to the product import flow.

  3. Upload the corrected file.

  4. Review the validation results.

  5. If there are no blocking errors, continue to the import summary.

  6. Confirm the product and BOM item counts.

  7. Click Confirm to complete the import.

Did this answer your question?