Skip to content

Kentro OS · Manufacturing and kitting

Bill of materials software for brands that assemble, kit or bottle their own products

Save the bill of materials once as a build template. Each build order takes the components out of stock and adds the finished goods, in the same system that sells and ships them. Built for light manufacturing and kitting, not for running a factory floor.

  • Build templates and build orders
  • Materials kept apart from sellable SKUs
  • Kits and bundles
  • Included in every Kentro OS plan
A finished product and the components it is built from

What is bill of materials software?

Bill of materials software stores the list of components and quantities needed to make a product, and uses it to turn stock of parts into stock of finished goods. In Kentro OS, an ecommerce ERP, a build template is the bill of materials and a build order runs it: components are consumed and finished goods are added to stock.

What it does

Parts in, finished goods out, one stock count

Save the bill of materials as a build template

A build template names the product you make and lists each input with its quantity. Add a note with instructions, the vendor if someone else assembles it, and the location the finished goods go to. Start a build from the template and the materials fill in.

  • One template per finished product
  • Inputs and quantities saved once
  • A vendor and a produce-to location on the template
A build template listing components and quantities

Keep materials apart from the products you sell

Materials are stock you consume, not stock you sell: bottles, labels, inserts, raw ingredients. They live in their own list with a SKU and a barcode. A material uses the same record as a product, so it has stock by location like everything else you hold.

  • A separate materials list
  • Search by SKU, barcode or name
  • Stock by location, like any product
A materials list with stock for each component

Run a build order: components out, finished goods in

A build order says what to make, how many and where the finished goods go. When the build is produced, Kentro takes the components out of stock and adds the finished units, and both movements land in the inventory log. Give the finished units a lot number and an expiry date when the product needs them.

  • Product, quantity and produce-to location
  • Lot number and expiry date on what you produce
  • Start from a purchase order when a vendor builds for you
Purchasing and purchase orders
A build order that consumes components and adds finished goods

Sell kits and bundles made of SKUs you stock

A bundle or kit is one product made of other SKUs. Define it once and sell it on any connected channel like a single item. When you want finished kits on the shelf before the orders arrive, assemble them ahead with a build order.

  • Bundles and kits defined once
  • Sold on every connected channel
  • Assembled ahead with a build order
Glossary: kitting
A kit and the SKUs it contains

One job, three ways

Check that you have the parts for a build, three ways

Check that you have the parts for a build

  1. In the app

    Open the build template, compare its inputs with stock on hand, and create the build order for the quantity you can make.

    A build template beside the stock of its components
  2. With Kentro AI

    Ask "How many units of each starter kit component are available?" Kentro AI reads stock for those SKUs and answers with a table. It reads. You create the build order.

    Kentro AIIn Kentro
    1. you ›How many units of each starter kit component are available?
    2. getInventorySummaryRead available stock for the component SKUs
    3. Here is available stock for each component, by warehouse. The mailer box has the fewest units, so it limits how many kits you can build.

  3. With your agent

    Your agent reads component stock over MCP with getInventorySummary. A person creates and produces build orders in the app: no MCP tool runs a build, and the Channel API has no build order resource.

    Your agentConnected to Kentro over MCP
    1. you ›Warn me when a kit component drops below two weeks of stock.
    2. getInventorySummaryRead available stock for the component SKUs over MCP
    3. runKiqReportRead recent sales of the finished kits
    4. Two components are below two weeks of stock at the current sales rate. They are listed with units on hand.

Questions about manufacturing and kitting in Kentro OS

What is the difference between a build template and a build order?

A build template is the recipe: the finished product and the list of inputs with their quantities. A build order is one production run: this product, this many units, into this location. You can start a build order from a template so the inputs fill in, and reuse the template for every run. The template never changes stock; the build order does.

Does Kentro OS calculate cost of goods for a build?

Not as a costing system. Kentro OS tracks what a build consumes and what it produces. It does not offer inventory costing, valuation or cost accounting, so cost of goods stays in your accounting system or a costing tool. Use Kentro for the bill of materials, the build and the stock, and keep the cost roll-up where your accountant already works.

Is Kentro OS an MRP or production scheduling system?

No. Kentro OS handles light manufacturing: bills of materials, build orders and the stock they move. It does not plan material requirements across many levels, schedule production on machines or work centers, or track labor and routings. Brands that assemble kits, bottle or label products, or use a contract manufacturer fit well. A factory that needs finite scheduling should pair Kentro with a manufacturing system.

Can I record a lot number and expiry date for what I produce?

Yes. A build order can assign a lot number and an expiry date to the finished units, and Kentro keeps that lot apart in every location from then on. That gives you lot-level tracking from production to shipment. Kentro OS does not offer full unit-level serial number traceability.

What if a contract manufacturer builds the product for me?

Set the vendor on the build template, or start the build order from the purchase order you send them. The build order still records which materials are consumed and how many finished units come back, and the finished goods go into the location you choose. You see the materials, the purchase order and the finished stock in one system instead of a spreadsheet per production run.

Keep parts and finished goods in one count

Save a build template, run a build order and watch both sides of the stock move.

Choose what this site may use. Necessary storage is always on.

  • Necessary

    Remembers this choice for 12 months and keeps forms safe from spam. No tracking.

    Always on

Cookie policyPrivacy policy