Kit and BOM Package Import

Kit and BOM Package Import

Version support: Inventorinator v0.1.0-alpha and newer supports kit-package import on Linux and Windows desktop. Inventorinator v0.0.9-alpha does not include this feature. Android does not import kit packages in v0.1.0-alpha.

Inventorinator imports documented .inventorinator-kit.json files. The file can be written by hand, generated by a script, exported by another application, or optionally created with help from ChatGPT, Codex, Claude, or another research tool.

AI is not required or built into Inventorinator. The app does not need an AI account, API key, or usage fee, and it does not send package contents to an AI provider.

Import a package

1. Create or obtain a valid .inventorinator-kit.json file.
2. Open Catalog in Inventorinator desktop.
3. Select Import kit.
4. Review the validation results and complete import preview.
5. Confirm the import.

Inventorinator imports:

• Kit name, description, sections, and BOM quantities
• Catalog products
• Optional brands and materials
• Optional associated machines
• Source URLs
• Inventory entries for newly introduced parts

Every newly introduced inventory part starts at quantity 0. Importing a BOM never falsely claims that parts are owned. Existing products are reused by stable package ID or normalized name and type. Importing the same package again updates the kit instead of duplicating it.

If Remote Sync is configured, the confirmed local changes propagate normally.

Package requirements

The root object requires:

• format: exactly inventorinator-kit
• schemaVersion: 1
• id: a stable package ID containing letters, numbers, periods, underscores, or hyphens
• name
• sections: one or more section objects
• parts: one or more BOM part objects

Optional root fields are description, sources, and machines.

Each section requires id and name. Each part requires:

• id
• name
• type
• section: the ID of a declared section
• quantity: a number greater than zero

Supported part types in schema version 1 are:

other, fastener, filament, printedPart, resin, nozzle, heatBreak, heatBlock, and sock.

Optional part fields include material, brand, unitCost, compatibility, and sources. Source URLs must use HTTP or HTTPS. Package files larger than 10 MB are rejected.

A complete example ships in the repository as examples/example.inventorinator-kit.json.

Optional AI-assisted workflow

An AI research tool can produce the same standard JSON file, but the result must still pass Inventorinator's validation and the user's review.

Suggested prompt:

Research the complete official BOM for [KIT NAME AND VARIANT]. Use primary manufacturer documentation whenever possible. Create one valid .inventorinator-kit.json package using Inventorinator schema version 1. Include stable IDs, sections, every BOM part and quantity, item type, material and brand when known, associated machines, and HTTP(S) source records. Do not guess missing values. Use other when no supported item type fits. Return only the JSON file content.

Always verify cited sources and inspect the import preview. AI-generated BOMs can be incomplete or wrong.

Safety and privacy

• Import happens only after local validation and explicit confirmation.
• The preview shows every section, part, quantity, machine, and source count.
• New inventory entries begin at zero stock.
• Inventorinator does not execute instructions contained in a package.
• Import does not contact an AI provider.
• Remote Sync runs only when already configured by the user.

Related filament, attachment, and storage improvements are tracked on the Roadmap.