Kerno

Recorded as live: beta access is open and free, the app holds real accounts, and shops are using it. Where our label runs ahead of the vendor's own wording ("Join Kerno Beta", "as we prepare for launch"), the cautions say so. Verified here means an editor checked the claims against first-party evidence; it is not a statement that the software is proven in production.

2026-08-14. A review of the six Full MRP rules moved the record from 0 of 6 to 2 of 6: the formula-to-batch flow carries rules 1 and 4, and rules 2, 3 and 5 had real evidence recorded as partial. Most evidence then was the vendor's interactive prototype, and the resource articles were cited only against partial values, never to support a yes. Campaign reporting was corrected twice that day: the creator profile's "0 backed" counts projects the creator has backed, not backers of this one, and a logged-out crowdfunding page is not a reliable read of campaign state. Promoted to Verified the same day, as a side effect of the rules review rather than a separate push.

2026-08-27, morning. All 178 articles on the vendor's resources site, its five feature videos, the Kickstarter page in a browser, the Discord invite and the company page were read. The articles are advice with a closing paragraph about Kerno, almost all in the future tense; the two that describe the software most directly, on costing and on finished goods, are quoted in the notes. No field moved on them. The campaign is recorded as ended on the site owner's account, with the $1 reservation refunded and the reservation page gone, while the public project page still renders as pre-launch and the vendor's free-beta page still offers the reservation; the campaign's figures are not recorded because no page showed them.

2026-08-27, afternoon. The record was checked against a running beta account, the site owner's own, with every menu opened and nothing changed beyond one draft batch created to see what a product pulls in. Eight fields moved to yes on that evidence: bill of materials, netting against stock on hand, work orders, routings, shop-floor tracking, quality, lot traceability and costing. Four moved to no, because a complete walk of a live account with nothing of the kind in it is evidence of absence in a way a marketing page never is: incoming orders, serial numbers, CSV export and full data export. Recipes and formulas went from yes to partial, because a different batch size did not scale the quantities. The six rules stay at 2 of 6, and rules 2, 3, 5 and 6 now fail on what the account shows rather than on missing evidence. API, webhooks, MCP, accounting and e-commerce stay unknown because an integration can live outside the interface; nothing in Account Settings points to one. Scan Simple, the vendor's separate label printer, is never cited for this product.

2026-09-15. Kerno replied on the four fields that went to no. Tracking incoming purchase orders is part of the v2 being built now, which adds purchasing. Serial numbers are not on the current roadmap, though the request has been noted. CSV export does not exist yet and is going on the roadmap. Whether a full account export exists is being checked internally, with an answer to follow. No release dates were given. We take the vendor at its word on what it plans, but a plan is not a shipped feature, so all four stay at no, purchasing stays at partial, and the rules stay at 2 of 6. Each field's note now carries the vendor's answer.

2026-09-15, second pass. Rather than put to the vendor what the account could answer, the account was walked again, on the site owner's login, with two products and four batches in it now. Three fields moved. Multi-level bills of materials went from unknown to no: the Add Ingredient picker on a batch lists raw ingredients only, so a premix that is itself made in a batch cannot feed the next one. Accounting and e-commerce went from unknown to no: every settings surface, the business Account Settings page and all five owner-level pages, holds no integration of any kind. Formula scaling was retested and still does not scale, so recipes and formulas stays partial on firmer ground. The absence of a sales order and of a lead time field was confirmed field by field on the vendor, ingredient and stock-receipt forms. API, webhooks and MCP stay unknown on purpose: the interface has no key management anywhere, but an interface is not where an API would show itself. Nothing was saved to the account beyond opening forms and closing them.

2026-09-23. Third account walk, on the site owner's login, this time setting up a new test business, Directory Test Batch Co, from nothing: a vendor, a raw ingredient with its form and category created inline, a stock receipt, a product type, a product formula and a draft batch T-1 with one ingredient line. Nothing moved. The vendor and stock-receipt forms still have no lead time; the stock receipt asks for SKU, vendor, lot, purchase date, expiry date, cost, unit and stock. Scaling was retested and still does not scale. The sidebar is unchanged apart from Categories being renamed Raw Material Categories, so v2 purchasing has not shipped. The Subscription page still reads only "active trial". No page offers API keys or integrations, and /api/ while signed in lands on the owner dashboard, so API, webhooks and MCP stay unknown with that written into each note. Public pages: the pricing tiers match the record, the pricing section says "No hidden fees" and lists no setup charge, which is noted on each plan but left unknown because it never says outright that there is none, and Solo and Teams limits were filled from the tier cards. The free beta page now redirects to the homepage and the $1 reservation checkout is commented out of the early-access page, so the pricing note and caution were brought up to date. The batch T-1 was left in draft, because adding a production step needs a labour operation set up first; the test business was left in the account for later walks.

2026-09-28. An outside audit of the six Full MRP rules, read against this record, the methodology and the vendor's public site, found wording that ran ahead of the evidence. No rule moved, and the count is 1 of 6. The entries above that say 2 of 6 were wrong from 2026-08-27, when formula scaling failed: rule 4 never had an assertion of its own, so the site has shown it as unknown. It now has one, at partial, because copying a product's lines into a batch gives one level of components but does not calculate them from demand. The BOM note that called that copying "one level of explosion" now says what it is. The stock-on-hand half of rule 3 cites the pricing page's "Inventory reservation and reconciliation", and the incoming-orders note says that purchase-order tracking in v2 would still have to count in the plan to pass. The finished-goods guide's line that Kerno "does not guarantee completion dates" is no longer used as evidence for rule 5: it is a disclaimer, not a feature limit. The public forecasting article is not counted for rule 2, since it still ends in the sample-article footer. The homepage quote on reusable formulas was re-fetched on 2026-09-28. The audit could not sign in to the app or see Kerno's roadmap, so it added no account evidence.