Bulk, bottle, jar, tube, pump, cap, and the label (yours or a client's) planned as real components with their own lead times.
The grid of product against size that a buyer emails becomes order lines, with each client's own packaging version resolved as it lands.
Minimum and incremental quantities per article and per site drive the purchase suggestion, so the cap minimum isn't a discovery you make after promising the units.
Subcontracted filling as a step in your own order: components leave, finished units come back, and the batch stays traceable across the gap.
Genealogy from the ingredient lot through the bulk batch to the filled units and the customers who received them, built in real time (not after the fact).
Lots stay in quarantine, out of available stock, until the control plan on that article passes.
Core modules
Integration engine
A full ERP. Most cosmetic manufacturing software handles the formula and stops, and most personal care manufacturing software runs a line without having the context of the order behind it. Bonx covers orders, components, purchasing, planning, filling, quality, and shipping in one system.
For the recipe itself, no. In Bonx, a formula is a bill of materials, so your percentages are the quantities (a 3% active is 0.03 per unit of bulk). It scales with the batch, and a client's version inherits the base and overrides only what differs. Every change is logged and each batch keeps the lots it actually consumed.
For the regulatory layer (INCI, restricted-substance checks, safety files) keep your lab tool. Bonx connects to it and takes the approved formula through to production.
Yes, as a step inside your own order. Components leave with a date, finished units come back against the same batch, so the gap between what you sent and what you got back is visible on the order rather than discovered at stocktake.
Yes, per article and per site. Minimum and incremental quantities drive the purchase suggestion, which matters more in cosmetics than almost anywhere else: a pump or a cap minimum can be several times the run you're actually making, and finding that out after you've quoted the units is how a launch date moves.
A lot on hold sits out of available stock until the control plan on that article passes, so nobody can promise it, plan it, or pick it, including someone who has no idea it's there. Someone has to release it, and the record shows who and when.
Yes, in both directions. From one raw material or component lot, Bonx returns every batch it entered and every customer who received one. That's the record behind a recall, and under MoCRA it's also the record behind an adverse event you have to investigate.
Bonx holds the records that the standard asks for. Control plans sit on the article, checks are recorded at each step in real time, batch records assemble as production runs rather than afterward, and quarantine keeps unreleased lots out of available stock. The certification is yours; what Bonx does is make the evidence a by-product of the work instead of a project before the audit.
Bonx is a manufacturing ERP that holds most of what MoCRA asks you to be able to produce: which batch went to which customer, what went into it, who made it and when, and the control records behind release. Facility registration, product listing, and adverse event reporting are yours to file. We hold the operational record those filings rest on.
Bonx invoices natively, including legal gap-free numbering, line-level VAT, the PDF, and e-invoicing where it's legally required.
That said, Bonx is not a finance ERP. We think manufacturing ERP and finance ERP should stay separate, and Bonx is built that way on purpose. There is no general ledger, no accounts payable or receivable, no bank reconciliation, and no financial close. The coded invoice goes to your accounting tool, which posts it and keeps the books.
