Editorial method
How Shop Floor Index evaluates software evidence
A software feature is useful only in the context of a workflow, a plan, and a task. This page explains how we label evidence in our guides and product field notes.
The current edition
This edition includes a documentation-based comparison of three food-business tools, evaluation guides, fictional exercises, a scorecard, a calculator, and two limited Zoho Inventory field notes: a stock-flow test and a basic assembly test. It does not publish a product ranking or comprehensive reviews. An exercise appearing in a guide is a task to try, not proof that a vendor supports it.
How the three-tool comparison works
We selected candidates for three related situations: stock and order handling, small-batch recipes, and manufacturing planning. The comparison names the official sources and consultation date, separates monthly payments from annual billing, and keeps unpublished prices and conflicting plan claims visible. A documented candidate is not an automatically verified match. Neither a commission nor a low advertised price establishes suitability.
Only the two linked Zoho field notes supply the limited trial observations used in this comparison. They do not validate food traceability, recipes or U.S. operations. Stocksmith has not been tested by us; historical Katana notes do not certify its current offer. The visitor must test the required outcome in the actual plan and region.
Three evidence labels
| Label | Meaning | Boundary |
|---|---|---|
| Tested | A specific task was performed and its observed result was recorded. | Applies only to the recorded product, plan, configuration, date, and task. |
| Documented | A vendor's identified documentation describes the capability or condition. | Does not mean the publisher independently reproduced it. |
| Unknown | Available evidence does not resolve the question. | Is neither a confirmed capability nor proof that the capability is absent. |
What a test record needs
A usable record identifies the product and plan, required add-ons, date, fictional inputs, steps, expected result, observed result, limitations, and supporting evidence. Vendor assistance and workarounds must be stated. Screenshots require an appropriate right to publish and must not expose private information.
Repeatable tasks, explicit limits
The food and beverage exercise separates ingredient consumption, yield, packaging, and order status. The brewery exercise separates transfer loss, packaging outputs, packaging loss, and tank scheduling. Reusing the same quantities makes differences easier to inspect, but it does not replace a full implementation assessment.
Costs and commercial relationships
Cost calculations use stated inputs and identify unknown required charges. A future product price or commission claim must have a source, scope, and review date. Commercial relationships must be disclosed where relevant; they are not evidence that a product fits a workflow. Read the disclosure.
Corrections and updates
If you find an error, send the page URL, the statement in question, and supporting information through the contact page. Corrections will distinguish a changed product from a mistake in the publication. The update log records substantive changes without inventing review dates.
Editorial responsibility
This publication is edited by DP Informatica SCP. Read about the publisher.