Work in your product lines, never lose the lineage.
Group your products by family, such as milk and cheese or soy and maize. Choose your lines in the header and every list, dashboard and report follows; lineage, recalls and approvals still see everything.
The problem
From one long list to the lines you work in
A company with several product families gets lost in its own lists.
A product line only groups. Lists follow the lines you choose; traceability and approvals never do.
Every family in one list
Lots, stages, processes and certificates of every family in one place, for people who work in one of them.
Feed is not a product line
The maize a dairy farm feeds its cows shows up beside its milk, as if it were something the farm sells.
Filters that cut the trace
Narrow a list too far and a recall misses the milk behind a cheese.
What it does
One scope in the header
With two lines or more, the header shows a third switcher after the company: All product lines, one line, several, or Other products. Products, lots, processing, deliveries, certificates, dashboards and reports follow it, on every device you sign in on. A link someone sends you shows its own lines without changing yours.
Read the full moduleInputs never make a line
Every product has a role: main product, co-product, by-product or input. Feed, seed, fertilizer and veterinary medicines are inputs: they never show as a line, and they belong to the lines of the work that uses them. Cattle fed with maize stay cattle.
Read the full moduleTraceability is never filtered
Lineage, recalls, traces, custody and mass balance always read every lot, whatever the scope. A run that makes cheese from milk shows in both lines, marked as a bridge.
Read the full moduleNothing waits unseen
Approvals, Needs you, findings, the agents' Review and the notification bell keep their whole list. Above what is in your lines they say, for example, +3 in other product lines, with Show.
Read the full moduleAutomations by line
Add Only if the product line is Cheese. The line is read when the automation runs, so a product that joins the line later is covered.
Read the full moduleRequired stages from a line
Pick the products of a product line in the Required stages editor. When a product joins the line later, Needs you asks you to add it; the ledger keeps the products, never the line.
Read the full moduleOwn checks for a line
Scope a check you write to one line or several. The lines are read each time it runs, and its findings carry the line's tag.
Read the full moduleLines on webhooks
Every event about one lot carries productLines, the lines the lot is in when the event is sent; processing events add the lines of their inputs or outputs.
Read the full moduleReports and exports by line
A library report runs in your lines by default, and its schedule keeps the lines chosen when it was scheduled. Report tables in CSV, spreadsheet and JSON add a Product line column after every lot, so does the findings CSV, and the exit kit adds directory/product-lines.json.
Read the full moduleHow it works
From your products to the lines you work in.
Choose the lines
Pick the product lines your group works in during setup, each with what it recommends.
Give each product its role
Main product, co-product, by-product or input; inputs never make a line.
Work in your lines
Choose them in the header; every list, dashboard and report follows.
Act by line
Automations, required stages, own checks and webhooks name the lines; traces and approvals still see everything.
What follows your product lines
A product line is a view and a report dimension, never a boundary: access, lineage and approvals ignore it.
| Area | With your product lines |
|---|---|
| Lists | Products, lots, processing, deliveries, certificates, sites and plots, parties, field work and facts follow the header scope. |
| Never narrowed | Lineage, recalls, traces, custody and mass balance; the audit trail, billing, members and settings. |
| Never hidden | Approvals, Needs you, findings, the agents' Review and the notification bell show what is outside your lines as a count, with Show. |
| Reports and dashboards | Datasets about lots have a product_line field, and the lines and Other products always add up to the company's total. A scheduled report keeps the lines chosen when it was scheduled. |
| Automations, agents, dashboards and reports | Tagged with the lines they belong to; none chosen means every line. |
| Rules and checks | Required stages can be picked from a line, and own checks scoped to lines. The ledger keeps products, never lines. |
| Webhooks | productLines on every event about one lot, as the lot was when the event was sent. |
| Exports | A Product line column after every lot in report tables (CSV, spreadsheet, JSON) and in the findings CSV; the exit kit adds directory/product-lines.json. |
| Not yet | Webhook subscriptions filtered by line. |
Who uses it
Product lines change what each person sees first, never what they may see.
Company owner
Decides the lines and the role of each product.
Organization administrator
Keeps the lines with the organization's product catalog.
Operator
Works in one line or several, with every trace still whole.
Developer
Reads productLines on webhooks and narrows lists by line through the API.
Lots become other lots: a truckload is split between buyers, silos are merged, wheat is milled into flour.
Resources
The guides, the open standard and the details behind every screen.
- GuideProduct lines, to group your products by familyKeep lists of lots, stages and processes short when your company works with several product families, such as milk and cheese or soy and maize.
- GuideHelp centerGuides for every screen of the console
- StandardThe A-REX standardThe open standard, kept by the A-REX Foundation
- DevelopersDevelopersAPI, events, signed webhooks and the MCP server
Bring your product families into view.
Tell us what your company makes, trades and uses. We will set up its product lines in a sandbox.
Explore more