OpenBOM pricing and alternative
Paying OpenBOM per editor, per record band and per CAD seat? Own the system your engineering changes live in.
Book 30 minutes with Sam. Bring your OpenBOM plan, your editor count, your record count and your CAD add-ins. We look at what you pay now, what it becomes as the product range grows, and how your team reviews and releases a revision. Then we show you your own version with your bills of materials brought across. One setup fee, then a monthly retainer, and the system is yours.
OpenBOM's pricing page lists Professional Team at US$30 per editor a month billed yearly (US$55 monthly) and Company at US$90 billed yearly (US$165 monthly). Product records above 2,000 are charged on top, from US$100 a month for up to 5,000 on yearly billing, and each CAD add-in is US$25 per seat a month billed yearly. One Company editor is US$1,080 a year before records and add-ins.
- check_circle30 minutes with Sam, no obligation
- check_circleYour OpenBOM bills of materials brought across
- check_circleNo editor seat or record band to pay for
The OpenBOM bill
Three meters: editors, product records and CAD seats
OpenBOM's pricing page, read 14 November 2026, prices people, product data and design connections separately. Readers are free; everything that changes a record is counted.
A seat for every editor
Professional Team is US$30 per editor a month billed yearly, or US$55 monthly. Company, for PDM and PLM needs, is US$90 billed yearly, or US$165 monthly.
The year per editor
One Company editor is US$1,080 a year on yearly billing, or US$1,980 on monthly billing. Multiply by everyone who maintains product records.
Product records on a second meter
The first 2,000 records are free. Up to 5,000 is US$100 a month billed yearly, US$1,200 a year, and the price climbs with each band. Part numbers, BOM lines and managed CAD files all count.
CAD add-ins per seat, per CAD system
US$25 per seat a month for each CAD system billed yearly, or US$45 monthly, on top of a Professional Team or Company seat.
ERP connections by quote
Integrations with systems such as QuickBooks, NetSuite and SAP are a flat rate per integration, priced by contacting sales.
A new pricing model from January 2026
Customers who signed up before 2026 are grandfathered. Anyone new, or anyone reviewing a contract, is on the per-editor, per-record model.
What you get instead
Release the right revision with the right evidence
Changes
Start the week with the decisions waiting
See the engineering changes that still need an owner or a review, worst first.
- check Review open changes by their agreed date.
- check Separate overdue changes from upcoming work.
- check Compare unresolved work by author.
- check Find draft revisions untouched for a month.
Components
See where a part change reaches
Trace the dependency before releasing the next assembly.
- check List the parents of a component revision.
- check Follow dependencies through nested assemblies.
- check Find obsolete components still specified in designs.
- check Compare components shared across different assemblies.
Release
Keep approval attached to the revision
The free base checks its release conditions before a design changes to released.
- check Require a reviewer different from the change author.
- check Freeze a revision after approval.
- check Recheck that each direct component is released.
- check Record who released it and the release note in the history.
Handover
Keep the instructions with the design
Prepare the review paperwork from the same records, with no record band to pay for as the range grows.
- check Flag missing intended use and test references.
- check Keep safe-use information on each revision.
- check Produce branded change notices and design handovers.
- check Add your own release questions and evidence fields.
Make it yours
Design your own OpenBOM replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from OpenBOM. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your OpenBOM data across and run it for you.
What it looks like
Ask it like you would ask a colleague
Real answers from the demo data that ships with Engineering Changes for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.
Engineering Changes for Claude Code
Connected to your own database
Which engineering changes are overdue?
40000000-0000-4000-8000-000000000001
- Name
- Washdown guard review
- Number
- PUMP-100
- Code
- B
- Author
- Moana
- Due
- 2026-10-03
- Status
- open
- Days_past_due
- 9
| Id | Name | Number | Code | Author | Due | Status | Reviewer | Days_past_due |
|---|---|---|---|---|---|---|---|---|
| 40000000-0000-4000-8000-000000000001 | Washdown guard review | PUMP-100 | B | Moana | 2026-10-03 | open | 9 |
Ask it anything
Questions to ask your engineering records
Each question has a working answer in the free base. OpenBOM also offers reporting; the difference here is control over your records and review rules, with no seat or record count behind them.
Switching
How to switch from OpenBOM
A move usually involves exporting each bill of materials, testing the import, checking the draft records and running both systems side by side while you verify the handover.
- 1
Export your BOM records
Export each single-level bill of materials from OpenBOM as CSV, including part numbers, descriptions, quantities, unit labels and revision names. These are the records the free importer can bring across as drafts. CAD files, attachments, custom properties and historical approvals need a separate agreed migration. Do not assume they are included with the BOM export.
- 2
Test the import first
Start with a sample BOM and use the import's test run before saving records. If your CSV headings differ, map them to the fields the importer expects. The importer handles one single-level BOM at a time, so plan to repeat the process for additional assemblies and link their revisions after importing.
- 3
Review the import results
Check the test results before importing for real. Confirm that headings, part numbers, descriptions, quantities, unit labels and revisions have been read as intended. Identical lines are skipped, while conflicting descriptions or quantities stop the batch. Lines absent from the input are not silently deleted. Imported records are drafts, not historical approvals.
- 4
Run both systems side by side
For a short agreed period, keep OpenBOM as your live reference while you use the new register for selected work. Compare imported component lists, quantities and revisions with OpenBOM. Have the people who review changes check that the new records and evidence references support their handover. Note any gaps and correct the mapping or agreed migration before moving more work.
- 5
Switch off OpenBOM
Once the checks are complete and your team is working from the new register, agree a final cutover point. Confirm that remaining in-flight records are covered by the migration scope and that the people responsible know how to access and maintain the database. Then stop using OpenBOM in line with your account arrangements.
Where the real effort goes
The real work is usually mapping your own fields and review rules, then deciding which history to bring. The BOM import creates drafts, not historical approvals, and CAD files, attachments and custom properties need a separate agreed migration. If you have Enterprise DNA run the move, they handle this migration work as part of the scoped setup.
Not ready for a call?
Get your OpenBOM switch plan by email
We will send you the step-by-step plan for moving your business off OpenBOM, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your OpenBOM switch plan is on its way.
Rather talk it through? Book a call arrow_forwardThree ways to own it
Do it yourself, have it customised, or have it run for you
Open source
Do it yourself
Free, open source
- 1 Clone Engineering Changes for Claude Code and install its dependencies.
- 2 Run npm run demo and inspect the fictional engineering records.
- 3 Open it in Claude Code, Codex, OpenCode or Cursor.
- 4 Test your OpenBOM CSV import, then arrange your database, access and backups.
Built around your business
We customise it
One setup fee, then a retainer for ongoing work
- check Your fields, evidence requirements and review roles written in.
- check Your OpenBOM bills of materials and revisions brought across.
- check Screens for the people who want to click, if your team needs them.
- check CAD, document storage and production connections agreed before we build.
Omni by Enterprise DNA
We run it for you
One setup fee, then a retainer
- check Installed and run inside Omni by Enterprise DNA, with the rest of your business.
- check Backups and access for each engineer and reviewer set up.
- check The overdue changes and obsolete parts lists ready each Monday.
- check Your review rules kept up as products and responsibilities change, with no seat to add.
Questions
Instead of OpenBOM, answered
How much does OpenBOM cost? expand_more
OpenBOM's pricing page lists Professional Team at US$30 per editor a month billed yearly or US$55 monthly, and Company at US$90 billed yearly or US$165 monthly. Read-only users are free. Product records above 2,000 cost extra, from US$100 a month for up to 5,000 on yearly billing, CAD add-ins are US$25 per seat a month per CAD system, and ERP integrations are quoted. Enterprise DNA charges one setup fee, then a retainer, with no seats or record bands.
Our OpenBOM bill is small. Is a 30-minute bill review worth it? expand_more
For a small team the subscription is rarely the real cost. The review looks at what your bill becomes as the record count and the CAD seats grow, and at the hours spent chasing reviews and checking which assemblies still use an obsolete part. If staying on OpenBOM is the better choice for you, we say so.
Which OpenBOM records can we bring across? expand_more
The free version imports a single-level bill of materials exported as CSV. Part numbers, descriptions, quantities, unit labels and revision names become draft records, and export headings can be mapped. CAD files, attachments, custom properties and historical approvals need a separate agreed migration, which Enterprise DNA does when it builds your version.
Does this replace our CAD tools? expand_more
No. Your engineers keep the design tools they use. Your version holds the revision and approval records, with references to the supporting evidence. We scope CAD connections, file storage and any screens as part of your custom version.
Does a passed check mean a design is safe? expand_more
No. The checks flag missing design information and unreleased components. Your engineers assess the evidence and the design. The included record prompts reference New Zealand upstream duties; other countries and specialist product rules need their own review.
Stop paying per editor and per record to see your own product data
30 minutes with Sam. Bring your OpenBOM plan, your editor and record counts, and one assembly with its next release decision. We look at what you pay now and as the range grows, how your reviewers sign off a revision, and what your own version would look like. If it is a fit, we build it and run it. If not, take the free version.
Engineering Changes for Claude Code is free and open source, published by Enterprise DNA.
Done paying for OpenBOM?
Book a 30-minute bill review