Name the product configurations a tender offers and the markets they are offered into, check that they may be bid, see which qualifications lapse during the contract, and review answers proposed from what the configuration actually holds.
When a tender offers a product, the bid is for a specific configuration of that product, offered into a specific market. Recording that on the tender's Products tab does three things: it checks that the configuration may lawfully be offered there, it shows which qualifications will lapse during the contract, and it proposes answers to the tender's requirements from the test results, claims and authorisations the configuration holds.
The products themselves are managed in the Product Library. This tab reads from it and never changes a product, its claims or its test results.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open the tender in Tenders and choose the Products tab.
Task | Who |
|---|---|
See what the tender bids, the qualification risks and the proposed answers | Team members with View Tenders ( |
Bid and remove configurations, choose the lead product, set the contract period, propose, decide and insert answers | Team members with Create & Work on Tenders ( |
Finding a product also needs the Products module and View Products. You see only products, configurations and evidence that your product clearance allows; see clearances. Administrators can work on every tender; everyone else works only on tenders whose team they belong to. Buttons you cannot use are not shown.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open the tender in Tenders and choose the Products tab.
Open the tender and choose the Products tab. Under What this tender bids, choose Bid a product.
In Find a product, enter part of the product's name or number and choose Search, or press Enter.
Choose the product in Product. Each option shows the product number and name.
Choose the Configuration being offered. Configurations that cannot be sold are marked not marketable.
Choose the Market being bid into: a region group or a single country. This is also the destination for the export check.
Wait for the eligibility check, described below.
Optionally, record Why this configuration, up to 4,000 characters, for example "Only 3.1 has the extended temperature range the RFP asks for".
Tick This is the lead product on the bid if it is the main product of the offer.
Choose Bid this configuration. Configuration added to the bid. confirms it.
No products matched. The Product Library is where products are created. means the search found nothing you can see. Choose Cancel to close the form without bidding.
A tender can bid several configurations, and the same configuration into several markets. Bidding the same configuration into the same market twice is refused.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open the tender in Tenders and choose the Products tab.
As soon as a configuration and a market are chosen, ComplyTrain checks whether it may be bid, showing Checking whether this may be bid… meanwhile. The check records nothing; it runs again, and is recorded, when you choose Bid this configuration.
Result | Meaning | Can you bid? |
|---|---|---|
This configuration may be bid into that market. Nothing stands in the way. | The configuration is marketable and export control permits the market | Yes |
Export control blocks this bid | Export control does not permit this configuration to go to this market | No |
This configuration cannot be offered | The configuration's lifecycle state is not marketable, for example still in development or withdrawn | No |
Export control warning | Export control permits the bid but flags something to check, such as a missing or overdue export determination, or a licence that is nearly used up | Yes, after reading the warning |
Each finding explains the reason under its title. A blocking finding keeps Bid this configuration unavailable. To bid, fix the cause in the Product Library: move the version to a marketable state (see lifecycle and history), or resolve the export determination or licence (see export control).
If the check cannot run, Whether this may be bid could not be checked, so it cannot be bid from here. Try again. appears, with the reason. Nothing is bid until a check succeeds.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open the tender in Tenders and choose the Products tab.
Each bid configuration shows:
The product number and name, with Lead on the lead product.
The configuration, the market, the lifecycle state and the classification.
Sold in this market as followed by the marketed name, or No marketed name recorded for this market — the response will use the register name. Use the marketed name in your response.
The reason recorded in Why this configuration.
The lead product is listed first. One configuration at a time can be the lead; choose Make lead on another to move the badge. The lead is for display and does not change any check.
If a bid configuration later leaves a marketable lifecycle state, it shows not marketable, and A configuration on this bid is no longer marketable appears at the top of the tab. Replace it with a marketable configuration or withdraw the bid.
To stop bidding a configuration, choose Remove, then confirm Remove this configuration from the bid? with Remove. Answers already accepted or edited are kept, and the confirmation says so. Its other proposals are removed.
Nothing is bid yet means no configuration has been added. Until one is, there is nothing to check for export restrictions, qualification gaps or answers.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open the tender in Tenders and choose the Products tab.
A qualification that expires halfway through the contract is worth knowing about before you submit. Under Qualifications lapsing inside the contract:
Choose Set contract period.
Enter Contract starts, if known, and Contract ends. The end date turns the check on and cannot be before the start date.
Choose Save.
ComplyTrain then checks every bid configuration against the qualification profile for its market and lists each problem:
Column | What it shows |
|---|---|
Configuration | The product and configuration |
Qualification | The required test method, with its regime |
Market | The market bid into |
Lapses | The date the result expires, or a dash when there is none |
Risk | Lapses mid-contract: valid today but expires before the contract ends. Already lapsed: expired. Never held: no valid result for this market |
No qualification lapses before the end date means every required qualification lasts the whole contract. Without an end date, the tab says that nothing is being checked. For how results, markets and waivers count, see qualification.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open the tender in Tenders and choose the Products tab.
Under Proposed answers, choose Propose answers. ComplyTrain compares each of the tender's requirements with what each bid configuration holds for its market:
Evidence | Offered when | Example proposal |
|---|---|---|
Test result | Passed and still valid, for this market or all markets | "Northstar TM-200 3.1 is qualified to IEC 60068-2-6 by Nordic Test Lab. Valid until 2027-12-31." |
Approved claim | Assertable: approved, backed by valid evidence and within its dates; see claims | The claim's own wording |
Marketed name | A market placement with a marketed name | "In DK this configuration is marketed as ThermoGuard 200." |
Regulatory authorisation | Active for this market | The authorisation type, reference, issuing body and expiry |
Matching compares the words of the requirement with the evidence; it is not AI and cannot invent a qualification. A message reports how many new proposals were created. Choosing Propose answers again after new evidence is recorded adds only the new proposals and leaves your decisions untouched.
Each proposal shows the requirement, the proposed wording, where it came from (for example "Approved claim, approved by" and a name), the product and configuration, a match percentage and any classification. Proposals are grouped by requirement, strongest match first. The counts line shows how many are awaiting review and how many are decided. Proposals drawn from classified evidence are shown only to people cleared for it.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open the tender in Tenders and choose the Products tab.
Every proposal waits for a person. For each one marked Awaiting review:
Accept takes the proposed wording as it stands. The status becomes Accepted.
Edit opens the wording for changes; choose Save answer to record your version. The status becomes Edited.
Reject discards it. The status becomes Rejected.
Each decision records Decided by with the person's name, and is final. If the evidence behind a proposal lapses before you decide, it says The evidence behind this proposal has lapsed, so it cannot be accepted. Reject it and propose again. and Accept is unavailable.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open the tender in Tenders and choose the Products tab.
An accepted or edited answer is the reviewed wording for its requirement, and it goes into the response in two ways:
Into the section. Use the insert action on the answer to add it to the response section linked to its requirement. When the requirement is linked to several sections, choose the section. When it is linked to none, you are asked to link it first; see linking requirements. The section then shows Drafting, and the requirement counts as covered.
Into the compliance matrix. The Compliance matrix tab lists the accepted answer as a product answer under Addressed by for its requirement, and the PDF and Word exports include it, so reviewers see what the bid states about the product. See compliance and coverage.
Review the inserted text in the section like any other content; see writing and reviewing sections.
Deleting a requirement on the Requirements tab asks you what should happen to the answers accepted for it.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open the tender in Tenders and choose the Products tab.
Product Library: the product's connected records list this tender under Tenders, with the configuration and market bid, the submission deadline and a warning when the configuration is no longer marketable. See connected records.
Export control: each bid records the export decision that permitted it.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open the tender in Tenders and choose the Products tab.
A hospital group in Denmark tenders for cold-chain monitoring. The contract runs from 1 April 2027 to 31 March 2030.
The bid manager chooses Bid a product, finds the Northstar temperature monitor, and chooses configuration 3.1 and the market Denmark. The check shows This configuration may be bid into that market. Nothing stands in the way. They tick This is the lead product on the bid and choose Bid this configuration.
The entry shows Sold in this market as "ThermoGuard 200", so the response uses that name.
They choose Set contract period and enter both dates. The vibration test is listed as Lapses mid-contract on 31 December 2027, so they ask the quality team to book a retest and mention it in the response.
Propose answers creates six proposals. The claim "The enclosure is rated IP67 to IEC 60529." is proposed for "State the ingress protection rating", and they choose Accept. They edit the vibration-test proposal to add the planned retest date and choose Save answer, and reject a weak match about packaging.
They insert the accepted and edited answers into the sections linked to those requirements. The Compliance matrix tab now shows the IP67 answer against the ingress-protection requirement.
