In forceDecided on 19 September 2026 · Ref. RF-001
A missing value is never a zero
- What the tool does
- An unknown price, volume, date or dimension stays empty, with the reason why. An impact without a volume stays empty and is sorted to the bottom; an average only counts what is known and states what it could not measure.
- Why
- Counting zero in place of an unknown value distorts every total and every average, silently.
In forceDecided on 19 September 2026 · Ref. RF-002
The tool does not guess, it asks
- What the tool does
- When the reading of a file is not established (how a number is written, currency, unit, price basis, date, reference), a closed question is raised in “Interpretation questions”, showing for each possible answer the figures it gives on a real example from the file. Nothing is calculated on an assumption.
- Why
- A wrong reading (1,000 read as 1, 04/01 read as 1 April) produces wrong gaps that nobody notices.
- Where to see it
- All screens
- Interpretation questions
In forceDecided on 19 September 2026 · Ref. RF-003
The ERP is read, never written
- What the tool does
- ERP systems are accessed read-only. What the tool prepares for the ERP is a file, loaded by someone on your team; it never writes directly into the ERP.
- Why
- The ERP remains the company's system of record; an error in the tool must never spread into it on its own.
- Where to see it
- All screens
- Entities, ERP & rates
In forceDecided on 11 October 2026 · Ref. RF-055
A decision never silently overrides someone else's
- What the tool does
- When someone decides on an item (a link, a discount, a special price, a supplier record, a target, a task…), the screen sends the version it displayed. If someone changed the item in the meantime, nothing is saved: a message says who changed it and when, and the screen is reloaded before deciding again. On a set (an import, a portfolio), a change made in the meantime rejects the whole set. The same action already taken by someone else is not a conflict: the screen says “already handled by…”.
- Why
- Without this check, the last decision won and the author of the first one never knew.
In forceDecided on 13 October 2026 · Ref. RF-085
Acting on a colleague's supplier: allowed, but flagged
- What the tool does
- A buyer can enter data or decide on a supplier handled by another buyer: nothing blocks it. Before confirming, the screen says “This supplier is handled by X. Your decision will be logged and X will be notified.” The action is logged as “outside portfolio” and a task notifies the supplier's buyer. Two decisions remain reserved to that buyer: strong-increase thresholds and decisions on intercompany opportunities. No flag for the purchasing manager or the administrator, nor for entries that are part of the supply planner's role (transport, entered purchase price, export check).
- Why
- The team must be able to help each other (absence, emergency) without reassigning the supplier, but the supplier's buyer must never find out afterwards that a decision was made on their supplier.
In forceDecided on 16 October 2026 · Ref. RF-115
Trois profils d'appui aux achats — supply chain (hiérarchique sur l'approvisionneur), commercial (engagements de volumes et visites), responsable de site (décisions et KPI de son site)
- What the tool does
- Three support functions, each bounded to what it requires. The supply chain manager has hierarchical authority over the supply planner: they see their work across every entity in their scope (price alerts, volume advice, anticipatory purchases, transport, delivery acknowledgements) and check that they make no mistakes; they have no commercial data. The commercial manager's objectives cover only holding volume commitments at special prices and their common visits, both counted; they have commercial data and no right to act on tariffs. The site manager has an overview of their site — spend, savings, ERP application delays, tasks — filtered server-side to their entity, and they validate within their scope.
- Why
- Un profil d'appui qui verrait tout le périmètre comme un acheteur créerait un contour flou des responsabilités ; chaque profil ne reçoit que ce que sa fonction exige : le contrôle hiérarchique pour le supply chain, la mesure de ses propres engagements pour le commercial, la décision et les KPI de son site pour le responsable de site.
In forceDecided on 16 October 2026 · Ref. RF-120
An optional date left empty stays empty
- What the tool does
- An optional date — the end of a special price, its issue date, a task's due date, the period of a conversion rule — opens empty when it has no value, and stays empty when saved. Empty means "open-ended" or "no due date": the tool never fills it with today's date.
- Why
- A field prefilled with today's date gave an end to a commitment that had none: edited without touching that field, it expired the next day, without anyone deciding it.
In forceDecided on 18 October 2026 · Ref. RF-131
The commercial manager follows the commitments of their end customers and their joint visits, without seeing a purchase price
- What the tool does
- The purchasing manager attaches end customers to each commercial manager's account. That manager then sees only the volume commitments of those customers: held when the volume realised over twelve months reaches the committed volume, not held below it, undetermined when a volume is missing. They enter their own joint supplier visits with the buyer, after the visit, and these are counted per quarter. The purchasing manager sets each quarter's objectives: expected visits and rate of commitments held. Everything is versioned and cancellable, and the screen shows neither a purchase price, nor a gap, nor a margin.
- Why
- Decisions of 18 October 2026: the commercial manager has objectives on keeping the volumes of special prices and on their joint visits, nothing else. They measure what depends on them, on their own customers only, without access to the prices negotiated by purchasing.
In forceDecided on 20 October 2026 · Ref. RF-154
A portfolio passes from one buyer to another without losing anything: the successor is checked, the handover is previewed and the past stays with whoever held it
- What the tool does
- When a buyer leaves, the manager hands their portfolio to another account in a single step. The tool first checks the accounts: the successor must exist, be active and be a buyer, otherwise the handover is refused with its reason and nothing is written. A preview, which writes nothing, shows beforehand which suppliers will change hands, from whom to whom and from which date. A reason is mandatory. The past does not move: a saving made in March stays attributed to whoever held the supplier in March. The handover can be cancelled as one block. The leaving buyer's entered tasks that are still open are offered to the successor, who receives them through an explicit command that can also be cancelled; the leaving buyer's objective is never transferred on its own, it is flagged to the manager, who sets a new one. A brand-new account that holds nothing yet is offered as a successor.
- Why
- Teams change: a tool that accepts a handover to an account that does not exist, or that loses the history, becomes a brake. Here the tool reads the accounts before acting, keeps no name hard-coded, keeps the trace of who held what and lets you go back.
In forceDecided on 20 October 2026 · Ref. RF-155
A portfolio can be split supplier by supplier, a supplier can have no holder, and the manager is alerted
- What the tool does
- A reorganisation is almost never "everything to one person": the manager chooses, supplier by supplier or by family, who takes what, and can even leave a supplier without a holder. The preview shows each line before anything is done, what would be refused and why; every successor is checked (they exist, they are active, they are a buyer); if a single line is refused, nothing is written; the whole thing is one operation that can be cancelled as a block, and the past stays with whoever held it. A supplier without a holder is in no buyer's portfolio; it is counted, shown in a "Without assignment" section, and the purchasing manager receives a "N suppliers without a holder" alert with the list for as long as it lasts. A buyer account that holds no supplier yet is a normal account. Deactivating an account that still holds suppliers warns (how many, and where to hand them over) and never blocks.
- Why
- A departure does not wait for everything to be prepared, and a team rarely reorganises in a single block. The tool warns instead of preventing, keeps the trace of who held what and lets you go back.
Decided, to be deliveredDecided on 26 October 2026 · Ref. RF-181
The language model never receives a price nor an identifying key: it recognises references behind anonymous keys
- What the tool does
- When a language model helps recognise a reference, it only receives the text of the items: the reference, the description, the unit and the family. It never receives a price, a discount, a net price, a volume or an amount, nor the supplier's name, the entity or the ERP item number. Each item is shown to it under an anonymous key drawn at random, new at every call; the table linking these keys to the real items stays in the tool and is never sent. The model answers with a key, the tool translates it back on its side, and a person validates the proposal. Figures in comments are written by the tool, without a model. This rule is decided and will apply as soon as a model is connected; none is today.
- Why
- Recognising references must carry no risk of leaking price lists, discounts or net prices. Without prices and behind keys renewed at every call, what goes out can be linked neither to a supplier price list nor to an ERP item.
