Once the manufacturer is chosen and the first orders are placed, the harder work begins: running orders, the technical file, the quality criteria and the shipping consistently. The follow-up model is not identical from one project to the next; the existing contract, the risk profile and the scope decide the shape of the follow-up.
Existing contract and technical file
The entry point for TRADIQ coordination is the existing contract between the customer and the manufacturer plus the technical file. The contract sets the scope, the delivery terms and the quality criteria; the technical file sets the product as defined. No new solution is invented — a structured follow-up is built on top of the existing document chain.
Reference specimen and series comparison
Before series production, a reference sample that records the approval of the parties and the identity of the sample becomes the baseline for series comparison. Evaluating production batches against that reference provides a common source if a conformity dispute surfaces later.
Approval authority and responsibility map
Who decides what — product change, packaging revision, shipping release, quality acceptance — is written at the start of the project. Writing down the delegation between the customer representative and the TRADIQ project lead keeps both the pace and the paper trail intact.
Milestones and reporting
The number of milestones and the reporting cadence are project-specific — there is no fixed count of control points for every project. Production time, critical risk moments and customer preferences combine into a schedule. Report formats are kept short and decision-oriented: what was done, what is planned, where a decision is needed.
Change record
Every change that surfaces during production — technical, commercial or operational — is captured in writing and tracked by version number. Recorded changes are submitted for the approval of the authorised parties; those that affect price, duration or scope take effect through the agreed contractual procedure.
Pre-shipment check and non-conformity
The scope of the pre-shipment check is defined per project: visual inspection, functional test, packaging conformity, documentation review. When a non-conformity is found, a CAR (corrective-action-request) style flow records the reason + corrective action + follow-up date, so the same issue does not recur in the same form.
Manufacturer confidentiality
You are not required to share the manufacturer's name at the initial inquiry. The information needed for the project can be collected once the scope and confidentiality terms are clarified. Automatic blanket confidentiality or unauthorised representation claims are not given — what is shared, with whom and at which stage, is agreed in the contract.
Practical notes
- Are the existing contract + technical file + approved reference specimen in hand?
- Are the approval authority and delegation written down?
- Are milestones + reporting cadence defined per project?
- Is the change record tracked by version number?
- Is the pre-shipment check scope written down and project-appropriate?
- Is non-conformity + corrective-action followed through a CAR-style flow?
- At which stage will manufacturer confidentiality apply, and with whom — is it set in the contract?