Choose a section
Section P / For identified goods
Issued form · pages 12–13Product origin and traceability
Confirm what is being bought, where it comes from and the evidence supporting the agreed sourcing requirements.
When this applies
Use Part P when RCDEN requests assurance for identified goods, including internal-use equipment. RCDEN completes P.2 before supplier acceptance; the supplier completes P.3–P.5 and RCDEN records the decision in P.6. Services-only registration does not require a product schedule.
Help with this section
Open a question for help. The numbers match the printed questions and agreement clauses.
P.1(a)Master agreement and Part P reference / revision
What to enter
Copy the master agreement reference and assign a Part P identifier and revision for these goods. Use a referenced continuation for a product list.
P.1(b)Supplier legal name and affected orders / item lines
What to enter
Identify the supplying legal entity and the affected order or proposed order item lines. Part P may cover scanners or other equipment bought for RCDEN’s own operations.
P.2(a)Finished-product scope and prohibited PRC connections
What to enter
RCDEN states the goods, countries and links excluded: actual origin, manufacture/final assembly, ownership or control, and any other expressly specified connection. Include RCDEN internal-use products where required. This is an RCDEN purchasing requirement, not a blanket MOD rule. Do not treat brand headquarters or shipping location as origin evidence.
PRC means the People’s Republic of China. RCDEN must state the relevant territorial and ownership/control tests expressly; suppliers must not assume that “non-Chinese” has a settled technical definition. Here “excluded links” means prohibited sourcing connections.
P.2(b)Components / assemblies: required depth, BOM references and excluded links
What to enter
RCDEN defines component and assembly depth, relevant BOM references, excluded PRC links and evidence criteria before supplier acceptance. Do not silently limit checks to critical components or assume omitted components are excluded. Unresolved depth or unavailable evidence remains unapproved.
P.2(c)Software / firmware, cloud / support and provider ownership or control
What to enter
Record embedded software and firmware, associated cloud and remote support, provider locations and ownership/control within the purchasing restriction. RCDEN expressly identifies any agreed exclusions and the authority permitting them; the supplier cannot self-waive them.
P.2(d)RCDEN source requirements, applicability review and scope authoriser / date
What to enter
Identify source document, clause, edition/date, applicable scope and evidence criteria; record RCDEN issue authoriser/date. Reference controlled records using an authorised route; do not attach private client terms to a public guide. Unresolved applicability prevents affected order acceptance or activity until resolved.
P.3(a)OEM, model / part and hardware / firmware versions
What to enter
Identify the actual OEM legal entity, product model, part number, hardware revision and software/firmware version as applicable. Identify the relevant order item for each entry; use a referenced continuation for multiple products.
P.3(b)Actual country of origin and final assembly country
What to enter
State actual origin separately from final assembly. Specify the basis, applicable origin rules where relevant, evidence and any uncertainty. Branding, distributor address and shipment country alone do not establish origin.
If a country code is required, give the country name as well. State the basis for the origin claim and separate any assembly location. An origin determination for the finished item does not establish every component’s origin.
P.1(c)Repeated master and Part P references
What to enter
Repeat the master and Part P references on page 13. Keep both pages and all referenced evidence together.
P.4(a)Manufacturer-backed origin evidence and relevant conformity evidence
What to enter
Identify issuer, document/date, product scope and verification route. Use manufacturer-backed declarations or equivalent product-specific evidence; state exactly what each document proves. Conformity certificates are required only where applicable law or the agreed product scope requires them. No certificate proves every origin or sourcing condition.
Where to find it / what to do next
- Ask the OEM or authorised distributor for evidence covering the exact part or model and relevant production period.
- Check issuer, date, product identifiers and any qualifications. Confirm doubtful documents through the manufacturer’s established contact route.
- For applicable radio equipment, check the declaration of conformity covers the supplied configuration and intended market. This is separate from origin and non-PRC evidence.
Useful external help
Opens in a new tab so you can keep this question open.
- Country of origin and the applicable rules (opens in a new tab)HMRC
Origin may differ from the country of purchase or shipment; use the applicable rules for the claim being made.
- Radio Equipment Regulations: Great Britain (opens in a new tab)Office for Product Safety and Standards
Manufacturer, importer and distributor duties for radio equipment placed on the Great Britain market.
Record which evidence is missing in P.5(a). The manufacturer may be able to give a scoped declaration without disclosing a proprietary bill of materials; RCDEN must decide whether that meets the recorded criteria.
P.4(b)Supply-chain and serial / batch / lot / invoice traceability
What to enter
Connect supplied items to the OEM or authorised channel and applicable evidence. Record serial, batch or lot identifiers where used; where none exists, use appropriate delivery or invoice references. These identify the supply but do not establish country of origin or complete component provenance. Retain specified product conformity, provenance and traceability records for six years after supply, or longer where law or the expressly agreed order requires, minimising personal data. Identify evidence limits.
P.4(c)Component, software and service evidence against P.2
What to enter
Map evidence to the agreed component depth and all covered firmware/software, cloud/support, location and ownership/control conditions. Reference a BOM or evidence matrix where useful. Do not disclose sensitive detailed architecture through an unapproved route.
For connected equipment, include relevant update and vulnerability-support arrangements, support lifetime and remote-service dependencies within the requested scope. Do not demand internal architecture or a full software bill of materials unless the requirement calls for it.
P.5(a)Known PRC links, unknowns, evidence gaps and proposed exceptions
What to enter
List each known covered PRC connection, unverified source, unavailable evidence, unresolved requirement and proposed exception. State affected item, impact and proposed resolution. Unknown or unavailable information is not an approval. Only express RCDEN approval with any necessary customer authority can accept an exception; law cannot be waived.
P.5(b)Supplier confirmation and authorised signature
What to enter
Confirm reasonable enquiry and accurate, non-misleading evidence with limitations declared. Sign to agree the recorded requirements subject only to expressly accepted departures. This declaration is not RCDEN acceptance and does not authorise supply.
P.6(a)RCDEN product assurance decision
What to enter
RCDEN records approval only for an identified, evidenced scope, with necessary authorities established. Keep affected ordering or supply on hold while scope, unknown provenance or evidence gaps remain unresolved. A recorded exception needs express written RCDEN approval and any necessary customer authority.
P.6(b)Evidence review, authorised exception references and release conditions
What to enter
Identify evidence reviewed, outstanding conditions and approval or exception references, including customer authority where necessary. Conditions must not be used to authorise an unresolved prohibited activity. Separate registration, contract acceptance and controlled-activity approvals remain necessary.
P.6(c)RCDEN authorised reviewer and decision date
What to enter
Identify reviewer, role and date. Approval is confined to the recorded product configuration and scope. Through agreed change control, obtain required written approval for substitutions or material changes affecting agreed specification, sourcing or security restrictions, or approved supply arrangements. Ordinary compliant maintenance or security updates are not automatically prohibited.
If more detail is needed
For the relevant work only. These are not extra questions in the initial registration.
For a barcode or RFID scanner, what is normally useful?
Start with the precise model and manufacturer, product-specific origin evidence, authorised supply route and serial or batch information. For radio equipment, ask for the applicable declaration of conformity and confirm the regional radio configuration. Ask about supported firmware, update delivery, end of support and any cloud or remote-support dependency where relevant to the intended use.
An ordinary reseller need not create an aerospace quality system simply to quote for scanners. It must still disclose evidence gaps and meet the actual sourcing, product and contractual requirements before the affected supply is approved.
How to use the addendum →What does RCDEN need to retain after approval?
Record the purchase order and line, supplier, OEM/model/part, delivered serial/batch/lot identifiers and references to the approved evidence. Check the delivered configuration against the approval and hold unexpected substitutions for review.
If an item is incorporated into another product, link the received item or batch to RCDEN’s bill of materials, build record and outgoing serial or delivery record. An onboarding questionnaire cannot create that downstream traceability by itself.
How to use the addendum →Are country codes, commodity codes and certificates the same?
No. Record the country name and a country code if the order or system requires one. A customs commodity code classifies the goods; it does not identify origin. A certificate of origin, conformity declaration and manufacturer declaration each have different purposes and scope. Check what the actual document establishes.
How to use the addendum →This guide explains form v2.2. It does not amend the issued requirements or approve work, exceptions or information release. Use the external help to find records and understand the rules. For questions about RCDEN's requirements or the proposed work, use the contact in Section 1.2 and quote the question number.