Suppliers and orders
The supplier record
Suppliers → Definition & members describes the third party and who has access to it.
| Section | Content |
|---|---|
| Definition | Name, code, type (external or internal to the group), status |
| Identity and billing | Legal name, legal id, VAT number, default payment terms, address |
| CRM record | The link to the supplier's record in your CRM; the icon next to it opens it in a new tab (http or https addresses only) |
| Contacts | The supplier's contacts, entered or workspace members — see the contact directory |
| Members | Three roles: Purchasing lead, Member, Reader |
The New supplier button in the top bar opens this same view in creation mode; its creator automatically becomes purchasing lead.
Filling the record from a contract
The Fill from a contract button, at the top of the Definition card, reads a contract you drop (PDF, Word or text) and proposes what it finds: legal name, legal id, VAT number, payment terms, address, and the contacts named in it. A review shows, field by field, the current value and the proposed value:
- an empty field is checked by default; a field already filled with a different value stays unchecked — the AI completes the record, it does not overwrite an entry unless you ask;
- a contact already in the directory is unchecked;
- the contract can be filed in the supplier's Documents at the same time.
Nothing is saved before Apply. The same button exists on the client record and also works while a record is being created: the selected contacts are then added at creation. It only appears if AI is configured for the company, allowed to the user's group and open to the Clients and suppliers category of the AI authorizations; each analysis is recorded in the AI request history.
Creating the contract at the same time
The review also proposes the contract itself: name, reference, commitment type, period, amount (or recurring amount and frequency for a subscription), cap of a capped time-and-materials contract, installments and daily rates per profile. Leave Create this contract as a draft checked and choose:
- Type: framework agreement, or order (framework contract and order on the client side);
- Attached to: for an order, the party's existing framework agreement. If it has only one, it is preselected; if it has none, FoxPlan creates a minimal framework agreement (name, reference, dates) from the document; if it has several, you choose.
The contract is created with the Draft status, with the document attached: review it, then activate it. Grid rates are matched to the reference profile when its label matches (in any language); otherwise the contract's label is kept, to be linked by hand. If the record is already up to date, only the contract is created. While creating a record, the contract is created right after the Create button.
On the Contracts screen, the Create from a document button does the same for the active party, without touching its record: the new contract opens directly in the panel.
The review also proposes the contract's qualification — folder, purchasing category, duration type, notice, renewal, price revision — and protects the budget of a contract denominated in a foreign currency: see Contract qualification.
There is no workspace "buyer" role. A member — whatever their role — sees the supplier and everything attached to it. Only the purchasing lead and workspace administrators change the member list, and a supplier must always keep at least one.
A supplier that still carries contracts cannot be deleted: delete them first.
Finding a supplier
The banner's dropdown only searches on the name. Past a few dozen suppliers, the funnel icon to its right opens the advanced search — the exact counterpart of the one for projects.
The grid carries the business columns (code, status, type, legal name, VAT number, payment terms) and your custom fields. Each column has its own search box under its header — that is the per-attribute search — and the box at the top sweeps every column at once. Clicking a row makes that supplier active.
The “Apply the filter to the dropdown” checkbox is the point. Ticked, the banner's list narrows to the result and you keep working in it after closing the panel: that is what makes this a search rather than a mere picker. The funnel then turns orange to signal that the list no longer shows everything. Untick it to restore its full extent.
The active partner stays visible in the list even when it falls outside the filter: hiding it would make the list lie about what is actually selected.
The criteria, the searched text and the state of the checkbox are saved on your account: you find your search again at your next sign-in, on any workstation. Each module has its own — filtering your suppliers does not touch your clients.
On sign-in the dropdown is narrowed to the last known result. Reopening the panel replays the criteria against the current list: a partner created since then joins it at that moment.
Clients have the same search, in the same place.
Fields declared on the Supplier object in Custom fields become columns of this grid. A “Sector” or “Criticality” field then helps you find a supplier, not merely describe one.
Framework agreements and orders
Suppliers → Contracts & orders shows a two-level tree: the framework agreements and, under each, its orders.
| Column | Content |
|---|---|
| Reference | Your contract or purchase order number |
| Level | Framework agreement or Order |
| Nature | Price request or Firm order |
| Status | Draft, Active, Closed, Cancelled |
| Commitment type | See the table below |
| Committed | The order amount; on a framework agreement, the sum of its orders |
| Allocated | The share actually assigned to envelopes — a gap with the committed amount shows in red |
| Consumed and Left to consume | See Commitments and installments |
An order must be attached to a framework agreement of the same supplier, and a framework agreement carrying orders cannot be deleted.
A price request commits nothing: it enters neither the budget nor the consolidated totals. Switch it to a firm order the day it is placed.
The Qualification section of the panel describes what the contract covers (folder, purchasing category, company), its notice and tacit renewal, and can warn you before the notice deadline. See Contract qualification.
The five commitment types
The type drives how the order is consumed, and therefore what the panel displays.
| Type | How it is consumed |
|---|---|
| Fixed price | Through installments, backed by the delivery milestones of the plan |
| Time and materials | Through the days of the supplier's consultants, valued by the rate grid |
| Capped call-off contract | Like time and materials, with a cap in days and/or amount |
| Subscription / licence | Through periodic installments, which can be generated automatically |
| One-off purchase | A single expense: a single installment, created automatically at the committed amount, carries its receipt and invoice; no rate grid |
On a capped contract, an overrun is flagged — never trimmed. On the sales side, trimming protects the client; on the purchasing side, it would hide precisely the information the buyer needs to see.
Allocating the commitment
The Allocation to projects section splits the committed amount. Each line carries:
- a project,
- a budget envelope of that project — to spread across several envelopes, add one line per envelope, each with its own share,
- a share, expressed as a percentage of the committed amount or as a firm amount — the firm amount wins when both are entered.
Two markers appear under the table: the allocated total and the left to allocate. The server refuses an allocation that would exceed the committed amount.
An incomplete line — no project, no envelope or no share — is flagged and not saved. It is not silently lost: the message says so.
This is normal and expected: they consume it instead of sharing out its total. There is therefore no 100 % rule per envelope, unlike client contracts.
The amounts of an order are expressed in the workspace currency (Settings → Workspace → Budget). There is no per-contract currency: the commitment flows into the budget envelopes as it stands, so a contract-level currency would silently produce wrong amounts. A purchase genuinely denominated in a foreign currency would need an exchange rate, as envelopes carry.
The Contract currency field of the qualification does not change this rule: it informs, it does not convert.
The schedule
For a fixed-price contract or a subscription, the Schedule section describes the slices: label, linked plan milestone, due date, receipt date, share or amount, invoice number and status.
The generate button of a subscription creates one installment per period between the order's start and end dates. Installments already received, invoiced or paid are kept — they record a fact — only those with the Ordered status are regenerated.
A generated installment does not store its label but its period: "Q3 2026" in English, "T3 2026" in French, including on the purchase order. A label frozen at generation time would stay in the language of whoever created the order.
Custom fields
The supplier record and an order's panel host the fields declared on the Supplier and Supplier contract objects in Settings → Custom fields — exactly like projects, risks or clients.
The record's business fields (name, code, status, legal name…) appear there read-only: they are properties of the entity, edited on the record itself. They are listed in the settings so you can arrange them in your edit groups next to your own fields.
The partner's documents
The conditions of an agreement rarely fit in an input field. They live in a document — terms and conditions, rate card, technical appendix — and the same document often serves several contracts.
Suppliers → Documents (and its counterpart Clients → Documents) is the partner's library. You upload its documents once; contracts reference them.
| Column | Contents |
|---|---|
| Label | Business name — “2026 terms and conditions” — distinct from the file name |
| Description | What this document is for |
| File, Size | The uploaded file |
| Uploaded on | Upload date |
In a contract's panel, the Linked documents section attaches as many as needed. Clicking a document downloads it.
A contract points at a document, it does not keep a copy of it. Replacing the terms and conditions with their updated version in the library benefits every contract at once — no stale version lingers in a corner.
It has not gone away: it earns its keep for a short clause specific to one contract. But for anything that gets drafted, signed or updated, the linked document is the right place.
Deleting a document from the library warns that contracts referencing it will lose that link. Those contracts then show one row fewer, never an empty row: a visible absence beats a pointer to a file that is gone.
Files are stored as private objects: no public address circulates, and every download re-checks that the reader does have access to that partner.
The purchase order
On a saved order, two buttons produce the document as PDF or Excel: supplier identity, contract terms, committed amount, allocation by project and envelope, schedule.
Its title follows the nature of the order — "Purchase order" or "Price request" — and its footer recalls that this is a management document, not an accounting one.
The purchase order number
Each order receives a purchase order number such as BC-2026-0042: one sequence per
workspace, restarting at 1 every year. It is assigned on save when the Purchase order no.
field is empty; a number you type yourself (your ERP's, for instance) is kept as is and never
overwritten. An order created before numbering existed gets its number on its next save, or at the
latest when its purchase order is generated.
The document shows it with the note "to be quoted on your invoice". This is the number that invoice import looks for on the supplier's invoice to find the order. Framework agreements are not numbered: their reference remains your contract number.