BOM Import Preflight

What does BOM Import Preflight do?

Find structural problems in a manufacturing bill of materials before you load it into an ERP system. Paste a CSV containing parent items, components and quantities, optionally supply an item master, and receive a report with exact source record numbers. No ERP login, spreadsheet installation or AI subscription is needed.

This is an independent structural checker for manufacturing BOMs. It is not a software dependency/SBOM scanner. It does not change your data or certify that an import will succeed.

What it checks

• Circular assemblies, including self-references and cycles across multiple levels. The report identifies every edge belonging to a circular group without incorrectly flagging downstream leaf components.
• Parent or component codes absent from an optional supplied item master.
• Missing codes, surrounding whitespace and case-only code differences. Codes are never silently merged or corrected.
• Invalid decimal quantities and nonpositive component consumption.
• Repeated parent/component/UOM combinations, reported as warnings because repeated lines can be intentional.
• Missing or padded UOM values when the optional UOM column is included.

Input

Use these exact CSV headers: parent,component,quantity and optionally uom. Preserve leading zeros in item codes. Quantities must be plain decimals without thousands separators or scientific notation. Supply one effective BOM structure; select the relevant revision, date and site before exporting. Revision, routing and other extra columns are rejected so separate versions are not silently combined.

The limit is 10,000 BOM records and 2 MB of CSV text. The optional itemIds list accepts up to 20,000 exact codes. Omitting it explicitly skips missing-item checks. An empty supplied list means no codes are valid.

First run: sample data and your own file

The example input contains both a sample BOM and sample item-master codes: BIKE, FRAME, WHEEL, HUB and BOLT. When using your own BOM, replace those sample codes with your actual item master. Leaving the sample codes in place checks your file against the sample master and can flag valid items as missing.

To skip item-master checks, use the JSON input editor and omit the entire itemIds property. Do not use an empty list ([]): that means an explicitly empty master, so every supplied code is absent. Check itemMasterChecked and the summary coverage before interpreting a result. Do not build a master list from the BOM itself to make missing-reference errors disappear.

Here is a complete JSON input without an item master. The \n sequences represent CSV line breaks. Replace the full JSON input, including any existing sample itemIds property:

{
  "bomCsv": "parent,component,quantity\n00100,00200,2"
}

For this example, expect one BOM record, zero errors, zero warnings and itemMasterChecked: false. Missing-item-reference checks are explicitly skipped. This result does not certify ERP compatibility.

To see findings with the supplied example unchanged, expect five BOM records, three errors and zero warnings: circular-assembly findings at records 4 and 5, and a nonpositive quantity at record 6. These are intentional sample defects. A completed sample run is still subject to the $1 completed-preflight price.

For CSV preparation, export one effective revision/date/site, preserve item codes as text, and use parent,component,quantity with optional uom. Choose the correct source columns yourself; native ERP import templates have not been validated. BOM CSV accepts CSV text, not an XLSX workbook or a file URL.

Results

The Dataset contains one summary followed by findings. Each finding includes a code, severity, source record number, parent/component codes and an explanation. Record 2 is the first data record after the header, including CSV records containing quoted fields. The complete JSON report is also saved under REPORT in Storage.

no_issues_in_checked_scope means only that these structural checks found nothing. It does not establish ERP compatibility, correct costs or correct business quantities. No UOM conversion, alternate/revision selection, scrap/byproduct modeling or automatic repair is performed.

Pricing and support scope

$1 per completed preflight, up to the stated limits, with platform usage included. A report that finds problems is still a completed preflight. Findings do not add charges. Invalid input fails before a completed report and does not trigger the completed-preflight charge. Set your maximum run budget to at least $1. No subscription or manual cleanup service is included.

All processing uses deterministic Python code. Input is processed within the run; no external website, LLM or ERP receives the submitted data from this Actor. Apify stores input/output under the account's platform retention and access settings. Use only files you are authorized to process.

Example finding

{"kind":"finding","code":"CIRCULAR_ASSEMBLY","severity":"error","row":4,"parent":"WHEEL","component":"HUB","message":"Edge belongs to circular assembly group 1"}

How to use it

1. Export one effective BOM and map its headers to the supported columns.
2. Paste the CSV into BOM CSV in the Input tab. Optionally enter item-master codes.
3. Run the preflight and review summary coverage, errors and warnings in Output.
4. Correct source records in your own process and run again if needed.

The API, scheduling and integrations are available through Apify. The Dataset supports platform exports including JSON, CSV and Excel. Use the Issues tab to report reproducible product defects; custom ERP configuration and data-cleanup services are outside this product.