Before approving a commercial display deposit, reconcile the order identity and the evidence needed for that order stage. Use seven document packs rather than counting seven PDF files: several records may belong in one pack, and some evidence can only be produced after an agreed sample or production test. This is a procurement control framework, not legal advice, a fixed payment schedule or a guarantee against loss.
1. Seven document packs and their release checks
| Document pack | Fields to reconcile | Release question |
|---|---|---|
| Entity and order | Seller's legal name, buyer, quotation/PO/PI reference, responsible production operation and authorised project contact. | Do the documents identify the same transaction and explain any different entity roles? |
| Configuration baseline | Model/revision, critical component or performance specification, firmware, software licences, options, exclusions and drawing references. | Can both parties identify exactly what is being ordered and how changes are approved? |
| Sample and validation | Sample identifier, configuration, test conditions, results, unresolved deviations and the agreed link to the production build. | Is approval complete, conditional or still pending for this stage? |
| Applicable conformity evidence | Target market, model scope, manufacturer/holder, applicable declarations/reports, revision and gaps for custom variants. | Does the responsible compliance reviewer accept the scope or an explicit test plan? |
| Inspection and release | Checks, conditions, sampling method where relevant, acceptance limits, records, defect handling and release authority. | Who records the result and what happens if the agreed checks fail? |
| Warranty and service | Quoted coverage, exclusions, claim evidence, spare parts, freight/repair responsibilities and support route. | Are responsibilities written for the destination and installation rather than inferred from a website badge? |
| Commercial and payment instruction | Amount/currency, agreed milestones, delivery term and named place, beneficiary details and independently verified changes. | Has the authorised buyer checked the instruction through an established channel? |
2. Reconcile the contracting and payment identities
A quotation, purchase order and proforma invoice should be reconcilable through agreed transaction references. Record which entity sells, which operation produces, who invoices and who receives payment. These roles need not always be identical, but unexplained differences should remain an open issue. A registered address is not a verified production address, and a salesperson's signature alone does not settle the entity relationship.
If manufacturing responsibility is uncertain, start with the display factory audit checklist. Keep identity evidence in the restricted procurement file rather than publishing bank details, personal identification or confidential records. Approval of a supplier name is different from approval of a payment instruction for a particular order.
3. Freeze the meaningful configuration fields
A model name and diagonal size do not define a complete OEM build. Reconcile the specification revision, critical parts or agreed performance baseline, software image, accessories, packaging and exclusions. If component brands cannot be disclosed, agree an alternative controlled specification and a change-approval route. Do not accept an open 'equivalent component' clause without understanding its effect on performance, compatibility and applicable evidence.
For outdoor LCD signage, include enclosure/connector identity, sustained brightness conditions, thermal operation, input power and supply compatibility. A panel's limit or a catalogue IP claim does not define the complete installation; the quoted configuration and project conditions must be linked to the relevant records.
For an interactive flat panel, specify the touch method, application/host test, Android image, optional Windows compute and required licences. Google services, USB-C video/touch/power and conferencing features need their own confirmation; the connector name or operating-system version does not prove them.
For a LCD video wall, distinguish each panel from the total canvas, controller, mounts, calibration and replacement-unit requirements. State which party supplies and accepts each interface. A per-panel quotation and a complete installed-wall quotation are not comparable until their scope is aligned.
4. Link the sample to the production order
The sample record should identify the build that was examined, the tests actually performed and any deviations that remain open. Record content, operating modes, accessories and environmental conditions where they affect the result. Keep photographs and results tied to the same identifier. A sample can establish a reference configuration; it cannot establish that every later unit has passed the same checks.
For a development order, it may be appropriate to approve a defined sample stage before the final production documents exist. Record what is being funded, what acceptance follows and what happens if the agreed stage is not accepted. For a repeat order, compare the previously approved revision with the proposed build and resolve substitutions before the affected release gate. Do not substitute a generic golden-sample label for a configuration and acceptance record.
5. Request applicable documents, not a universal certificate pack
Build a document index for the destination and intended use. Check the model/configuration scope, named manufacturer or holder, issuing party, dates and applicable declarations or reports. Identify whether a changed enclosure, power supply, radio module or software image affects the evidence. An unrelated report or logo does not become applicable because it appears in the same catalogue.
CE marking is not blanket approval of every product or confirmation that an EU authority tested it. Have the responsible compliance party determine the applicable requirements and review supporting documentation. Keep management-system certificates separate from product evidence. If testing is still required, record the plan, responsible party and release condition instead of marking the document as already obtained. This checklist does not determine legal market access.
6. Define inspection, failure handling and after-sales ownership
The inspection plan should state which checks happen at sample, production and pre-shipment stages, who performs them and which records trigger review. Agree limits and methods for the actual application, rather than a generic 'QC passed' stamp. When sampling is used, document its basis and limitations; a sampled release is not a claim that every unit was tested. Address failed results, rework, retest and the person authorised to approve release.
Warranty needs a project-specific scope: covered components, exclusions, claim evidence, spare-parts handling and freight or repair responsibility at the destination. Use the warranty and spare-parts guide for the discussion, then record the terms actually quoted. No warranty duration, lead time, MOQ or service response is established merely by this article.
7. Verify the instruction before acting on a change
Payment instructions can be impersonated even inside a familiar-looking email conversation. Verify a requested account or procedure change through an established contact channel independently of the change message; a new phone number in that same message is not an independent check. The FBI's business email compromise guidance recommends verifying payment requests and account/procedure changes. Do not publish beneficiary details in the public RFQ or treat a logo-stamped PDF as authentication.
The amount, currency, milestone, delivery term and named place should be reconciled with the agreed order. Do not choose a universal deposit percentage or assume that a particular payment method eliminates risk. Have the authorised finance team and, where needed, the bank or legal adviser evaluate the proposed arrangement. If the instruction or entity relationship remains unexplained, pause the payment approval rather than inventing an explanation.
8. Record missing evidence honestly
Use a stage-specific release record. A document request is not evidence that a supplier already has it, and a planned test is not a passed test. The buyer should name who can accept an exception and what evidence closes it. Keep the scope clear: completing this checklist supports a procurement decision, not a certification or a promise of successful delivery.
- Missing but required now: keep approval open and identify the document owner and evidence needed.
- Available only after a later stage: agree the activity, due point and release condition in writing; do not label it verified now.
- Unexplained identity, configuration or payment change: stop the affected approval until independently checked and documented.
9. Copy-ready RFQ fields
Provide product family and model, quantity, target market, installation/operating conditions, required apps, configuration reference, sample stage, document index, acceptance plan, open deviations and requested commercial terms. Ask the supplier to mark each item verified, pending or not applicable, with its revision and owner. Share sensitive commercial and banking information only through the agreed restricted channel.
Discuss the proposed configuration through the OEM/ODM enquiry and use the OEM supplier comparison guide before shortlisting. TZD document availability, model coverage and commercial obligations must be confirmed for the specific project; this page does not promise that every requested document exists before every deposit.
Frequently asked questions
Which documents should I check before a display supplier deposit?
Reconcile seven packs: entity/order, configuration, sample validation, applicable conformity evidence, inspection, warranty and commercial/payment instructions. Define what is required for the current order stage and what remains pending.
Is a proforma invoice enough to define the OEM build?
Not if it omits the configuration and approval references. Link it to the agreed specification revision, options, sample status, acceptance conditions and transaction identity rather than relying on a model name alone.
Does a CE logo mean the supplier has all required documents?
No. Review the model, destination and supporting documentation with the responsible compliance party. A logo or unrelated certificate does not establish the ordered configuration's applicable requirements or evidence.
What should I do if bank details change by email?
Pause the affected payment approval and verify the change through an established independent contact channel. Do not rely on the new contact details inside the change request itself.
Must every final test report exist before a development deposit?
Some evidence can only follow the agreed development or sample stage. Define the funded scope, test responsibility, due point and later release conditions in writing; mark planned evidence as pending, not passed.
Order-evidence handover checklist
- Reconcile the model/configuration revision and transaction references across quotation, sample and order records.
- Track required-now, later-stage and non-applicable evidence separately; name the approver and closure condition.
- Route payment changes to authorised finance verification; retain restricted evidence without placing bank details on public forms.