Manufacturing BOM & inventory AI that shows what you can build.

Sovun BuildList is the manufacturing workflow inside Sovun Assistant. It organizes your bills of material, rolls up costs, checks on-hand inventory against build demand, and flags shortages before production gets blocked — and nothing is purchased, committed, or posted to your books without your approval.

Built for how small manufacturers actually build

Manufacturers and fabricators run on parts, assemblies, revisions, vendors, labor, overhead, and purchase timing — not conversations. A generic chatbot cannot tell you whether tomorrow's build is ready. Sovun BuildList turns that daily operating pressure into a clear view of what is ready, what is short, and what needs a human decision. It is built for machine shops, product builders, and fabricators who want an operations layer around the spreadsheets and systems they already use, without exposing private data or handing control to automation.

One anonymized example: a Maine truck-body manufacturer runs Sovun every day to keep its build data and shortages organized. The setup is customized to that shop's parts, pricing, and approval rules — the same way every BuildList workspace is configured to a single company.

Bills of material, organized and accurate

BuildList maintains your items and bills of material with full structure intact: parent assemblies, sub-assemblies, and child components, each with item type, quantity per, unit of measure, and revision. When a shared component changes, the update rolls through every assembly that uses it, so the build list stays accurate instead of drifting across a dozen spreadsheets.

  • Multi-level BOMs with assemblies, sub-assemblies, and components
  • Item types, quantities per, units of measure, and revision tracking
  • Shared components that update everywhere they are used
  • Import from Excel, CSV, spreadsheet, or accounting-system exports

Requirements lists that compare demand to what's on hand

Tell BuildList what you plan to build and it explodes the BOMs into a requirements list — every component, every quantity — then compares that demand against current inventory. You see build readiness before you commit a single part: what is fully covered, what is partially short, and exactly how many of each item you still need to pull or buy.

  • BOM explosion into a consolidated component requirements list
  • Demand-versus-on-hand comparison for each build
  • Build-readiness view before production inventory is committed

Cost rollups you can trust before you quote

BuildList rolls up cost through the whole assembly — material, labor, overhead, freight, and other charges — so you know what a finished unit actually costs before it goes out the door. Because the rollup follows the same structure as the BOM, a change to a component cost or a revision flows straight up into the assembly total.

  • Rolled-up cost across material, labor, overhead, and freight
  • Assembly totals that update when component costs or revisions change
  • A dependable basis for quoting and margin review

Shortage checks and reorder drafts, not surprises

Before a build is scheduled, BuildList runs a shortage check and surfaces low-stock, out-of-stock, and below-reorder-point items. When something is short, it drafts the reorder — quantity, vendor, and cost — and holds it for review. Nothing is purchased and no inventory is committed automatically; you approve the reorder, and only then does anything move.

  • Low-stock, out-of-stock, and reorder-point flags per item
  • Reorder drafts prepared for approval, never auto-purchased
  • Shortages caught before production is blocked, not after

Inventory visibility and daily production briefings

BuildList keeps on-hand counts, suppliers, and reorder points in one place and starts the day with a briefing: what is ready to build, what is short, and what is sitting in the approval queue. The production side stays separate from accounting — your books remain the financial record while BuildList focuses on what the team needs to build, buy, review, or approve.

  • On-hand inventory, suppliers, and reorder points in one view
  • Daily briefings for builds, shortages, and pending approvals
  • Production data kept separate from your financial records

A four-week rollout that proves itself before it touches production

The right rollout is controlled and measurable. A safe start is read-first: exported item lists, inventory reports, and BOM files are reviewed before any live connector or outside-system write is considered. You begin with one product family or a small BOM library, confirm the requirements list matches the shop's expected output, then run real builds in parallel before changing anything live.

  • Week 1: map your current BOM, inventory, and accounting data sources
  • Week 2: import data and reconcile assemblies, items, costs, and quantities
  • Week 3: run read-only build-readiness and shortage reports against real demand
  • Week 4: test approved build, reorder, and accounting hand-off workflows in parallel

Throughout the rollout, the human-approval promise holds: BuildList drafts and organizes, and you approve every purchase, inventory commitment, and write-back to your books.

Questions

Common questions

How does Sovun BuildList handle multi-level BOMs?

It preserves the full structure — parent assemblies, sub-assemblies, and child components, with item types, quantities per, units of measure, and revisions. Change a shared component once and the requirements roll up through every assembly that uses it, so the build list stays accurate.

Does Sovun BuildList replace my accounting or QuickBooks?

No. BuildList keeps the production side — items, BOMs, inventory, and build readiness — separate from your books. Your accounting software stays the financial record. BuildList reads first and only writes back to accounting after you approve a hand-off.

Will it purchase parts or reorder stock on its own?

Never. When a shortage check finds a low or out-of-stock part, BuildList drafts the reorder — quantity, vendor, and cost — and holds it for you. Nothing is purchased and no inventory is committed until you approve it.

How long does a manufacturing rollout take?

A typical rollout runs about four weeks: map your data sources, import and reconcile BOMs and inventory, run read-only readiness and shortage reports, then test approved build, reorder, and accounting hand-off workflows in parallel before anything goes live.

Book a PilotCall