Examples by sector
Six journeys, with the real clients named in the packs: which pack a consultant applies, which rules it activates and why, what the user sees when a rule bites, and the proof screen.
Each journey follows the same thread: which pack a consultant applies for that trade, what rules it contains and why those particular parameters, what a user sees the day a rule bites (the translated message, as shown), and the screen that serves as proof — captured on the portal, demo data left unmasked.
Textile — Cheynet, Pito, Bacovet
Three contract textile makers: receiving tolerance on fabric and supplies, material purchases approved by tier, customer orders that commit to a contractual delivery date. The Oeko-Tex/BSCI normative pack layers on top as soon as a client requires it.
The applied pack textile
| Type | Parameters | Why |
|---|---|---|
sur_reception | pct_max: 5, illimitee: false | Usual over-yardage tolerance on fabric receipts. |
approbation_montant | table: purchase_orders, paliers: ["10000:2", "100000:3"], mode: avertir | Material purchases approved by tier; warn mode to observe before hardening. |
champ_requis_statut | table: sales_orders, champs: ["delivery_date"] | Contractual delivery date required before firming the customer order. |
certificat_expire | normes: ["OEKO-TEX", "BSCI", "GOTS"], mode: avertir | Oeko-Tex/BSCI/GOTS normative pack: material certificates kept current. |
The refusal, as displayed
Supplier FRS-0012's OEKO-TEX certificate expired on 06/12/2026: attach a current certificate before validating the receipt.
certificat_expireProof screen

The supplier record's Certificates tab: standard, number, expiry date — the proof the Oeko-Tex/BSCI pack reads.
Precision mechanics — AMM
Precision machining subcontractor: tight receiving tolerance (little slack on machined dimensions), material/tooling purchases approved at lower thresholds (expensive components in small batches), no manufacturing order planned without an end date, and lot/serial traceability followed through to the delivered part.
The applied pack mecanique_precision
| Type | Parameters | Why |
|---|---|---|
sur_reception | pct_max: 2, illimitee: false | Tight tolerance: little slack on machined dimensions. |
approbation_montant | table: purchase_orders, paliers: ["5000:2", "50000:3"], mode: avertir | Lower thresholds: expensive components in small batches. |
champ_requis_statut | table: manufacturing_orders, champs: ["planned_end"] | Planned end date needed for shop-floor scheduling. |
tracabilite_requise | moments: ["reception", "fabrication"], mode: bloquer | Every received lot and every completed OF stay linked to a searchable serial number. |
The refusal, as displayed
Cannot close OF OF-2026-0032: no serial number was entered for item ART-0016 (traceability required at manufacturing).
document_introuvableProof screen

The serial record: item, lot, originating OF, originating receipt, history — what traceability requires to be filled in.
Cabling / metal — PSZ Cable, SZ Metal
Automotive cabling and metalwork: receiving tolerance on coils/sheet metal, customer credit exposure monitored (deferred payment is common in the industry), supplier lead time required once firm. The IATF 16949 normative pack adds blocking lot traceability, FMEA before OF launch, calibrated instruments and per-workstation operator qualification.
The applied pack cablage_metal
| Type | Parameters | Why |
|---|---|---|
sur_reception | pct_max: 3, illimitee: false | Receiving tolerance on coils/sheet metal. |
limite_credit_client | tolerance_pct: 10, inclure_commandes: true, mode: avertir | Customer exposure monitored: deferred payment is common in the industry. |
tracabilite_requise | moments: ["reception"], tous_articles: true, mode: bloquer | IATF 16949 § 8.5.2: lot traceability from receiving, on every item. |
habilitation_requise | niveau_min_defaut: 2, exiger_formation_valide: true | ISO 9001 § 7.2, IATF § 7.2.1: operator qualified at the level required for the workstation. |
The refusal, as displayed
Operator Amine T. is not qualified at the required level (level 2) for workstation Crimping 3: assign a qualified operator or get their training approved.
droit_insuffisantProof screen

The flow links workstation, operator and supplier; the simulation surfaces probable problems — here three critical signals.
Transport & logistics — 3C, Alonso Forwarding
Forwarder and carrier: carrier and tracking number required before any firm delivery note, customer credit exposure monitored, accounting period locked. No sur_reception: a forwarder rarely receives purchase orders in the reception_items sense — its delays instead feed the carrier risk signal directly.
The applied pack transport_logistique
| Type | Parameters | Why |
|---|---|---|
champ_requis_statut | table: delivery_notes, champs: ["carrier", "tracking_number"] | Contractual traceability of the shipment. |
limite_credit_client | tolerance_pct: 5, inclure_commandes: false, mode: avertir | Frequent billing, thin forwarder margins. |
periode_close | {} | Locks entries in an already closed accounting period. |
seuil_risque | indicateur: carrier.retard, attention: 20, critique: 40 | Share of late deliveries per carrier, with its own alert. |
The refusal, as displayed
Cannot firm delivery note BL-2026-0871: carrier and tracking number are required before firming.
champ_requis_statutProof screen

The risk banner: on-time delivery rate, average delay in days — the same indicator tracks a carrier.
Management control — Tout secteur
Finance and management control: the AFFAIR dimension is required on every invoice before firming (warn mode to observe before hardening), and incompatible dimension combinations on the same document are blocked once configured under Settings → Dimensions. The affair report then aggregates quoted, committed, actual and margin per affair.
The applied pack controle_de_gestion
| Type | Parameters | Why |
|---|---|---|
dimension_requise | table: invoices, dimensions: ["AFFAIRE"], mode: avertir | Affair required on invoices before firming, to tie every line back to a costed estimate. |
combinaison_interdite | {} | Prevents two incompatible dimension values on the same document (forbidden dimension combinations). |
The refusal, as displayed
The AFFAIR dimension is required on this document: set an active affair before firming invoice FAC-2026-00214.
dimension_requiseProof screen

Settings → Dimensions: AFFAIR values sync from the Affairs module; forbidden combinations are added here.
A default value can also be set directly on a client, supplier or article record — the Dimensions tab — so every new document created from that record pre-fills the AFFAIRE (or other) dimension without the user typing it.

The client record's Dimensions tab: one default row per dimension, mirrored from the affair when applicable.
Internal control — Any sector
Segregation of duties (four-eyes control): the person who performed an action cannot alone perform the following action on the same document. The pack sets a single rule with three cautious conflicts, in warn mode — the log is observed before hardening to a block.
The applied pack controle_interne
| Type | Parameters | Why |
|---|---|---|
separation_taches | conflits: ["creer_fournisseur:valider_paiement", "creer_da:approuver", "modifier_rib:valider_paiement"], mode: avertir | Three cautious conflicts: create a supplier then validate its payment, create a purchase request then approve it, change a bank account then validate a payment. |
The refusal, as displayed
Segregation of duties: the person who performed “creer_fournisseur” cannot perform “valider_paiement” on this document — four-eyes control, ask another user.
separation_tachesProof screen

The Internal-control pack sets a separation_taches rule in warn mode: the log fills in before any block.
← Back to Business Rules and Control
See also : Type catalog · Packs by trade · Deployment · Pilotage and risk signals · Copilot · Status profiles






