Modules and features
The modules and features Redbrix designs inside B2B and manufacturing software. Each entry describes what the capability covers, who uses it, what makes it hard to design and the common mistakes.
23 Entries
01
Traceability design
Traceability design is the interface work that lets a person reconstruct the full history of a material, from receipt to consumption.
02
Lot genealogy map
A graph view of lot splits and merges answers recall and root-cause questions that a flat trace report makes too long to read.
03
How should audit trails and activity history work?
Audit history should answer who changed what and when from the record itself, without an export. Buyers and auditors ask about it early.
04
How should permissions and role-based access work?
Administrators configure access, so the screens that manage permissions need as much design attention as the rules themselves.
05
Work order and job structure
Scheduling, terminals, costing and traceability all read from the work order structure, so it shapes most screens built after it.
06
Role-based production interfaces
Operators, planners, supervisors and auditors differ in time horizon, data density, input method and cost of a mistake, so the layout should reflect the task differences.
07
Scan-first input with manual fallback
Scan-first input records shop floor transactions by barcode scan or scale reading, with a keyboard form for every scan action.
08
Production scheduling and simulation views
A scheduling view places work orders on resources and time.
09
Costing interfaces
Cost figures depend on postings made on the shop floor, so the design of costing screens starts with the screens that capture those postings.
10
Inventory and master item models
The master item model defines an item's identity, units of measure, variants and tracking rules.
11
Receiving and stock item flows
Receiving turns external material into inventory.
12
Pick-and-ship fulfilment flows
Lot selection at pick time decides which lots leave the building, so pick-and-ship design affects traceability as much as logistics.
13
Label and document output design
Labels, packing slips and certificates fail after the data leaves the application: at the printer, at the customer or with the regulator.
14
Warehouse map builder
A warehouse map is configured once and read every day by people who did not build it, and every stock address depends on it.
15
Regulatory and government reporting
Regulatory reporting interfaces produce the statements an authority requires, such as excise returns and batch records, from data the system already holds.
16
Configurable dashboards
Configurable dashboards let users choose which metrics and lists appear first.
17
Design systems at ERP scale
At ERP scale the hard parts of a design system are the dense components: tables, line-item editors, forms and filters.
18
Legacy-to-modern transition direction
Long-term users work fast in the legacy system and judge every new screen against that speed while the business keeps running.
19
AI-assisted workflow surfaces
AI-assisted workflow surfaces are the points where a model's output enters a business process, such as a suggested reorder or a drafted document.
20
Where do AI features fit in an ERP product?
For an ERP vendor, AI features fit best where users already make repeated judgments, such as reorder suggestions and schedule changes.
21
How should human approval work in AI-assisted workflows?
The approval step should match the consequence: one click for a low-risk suggestion, a review with evidence for a posting or a regulatory record.
22
How do you make AI output verifiable in regulated software?
The interface shows which records, documents or code an AI output relied on and how confident the model was, so a reviewer can check it.
23
Automation or decision support?
With automation the system acts and a person reviews afterwards.