Build something from a recipe, at what the build actually cost
Not everything you sell arrives in the box it leaves in. A gift basket, a kit, a repair with parts and labour, a bundle the wholesaler calls one SKU — SeroBooks models each of them properly: an assembly consumes its components at cost and posts a journal, a group sells several products as one line, and a variation is a real product with its own SKU, cost and price.
What you get
Why a bundle is not a discount
The lazy way to sell a kit is to discount the components on an invoice. The stock is right and the revenue is right, but the product you actually sell — the kit — never exists in your reports, so you cannot see its margin, its velocity or whether it is worth the shelf. A group makes the kit a product; an assembly makes it a product with a cost of its own, built from parts that are relieved when it is built rather than when it is sold.
The product form, finally in the app
Products can be added from the Products page in the desktop and tablet apps — previously that meant leaving for the legacy web admin, on a form that never asked for a cost. The new form asks for cost, alert and reorder quantities and lead time, creates variations as their own rows, and offers Single, With variations, Group and Assembly as the four things a product can be.
Frequently asked questions
Can I see what I could build right now?
Yes — Inventory ▸ Assemblies answers 'what can be built from what is on hand', scales a recipe, and records the build.
Are these Pro features?
Assemblies and product groups are SeroBooks Pro; variations and case packs are in every plan.