Even if a supplier labels their offer of certified flooring in a tender offer with one line of text, the subsequent delivery of three or so papers may not all be of equal value. One may be a product certificate, another a test report, and even a management-systems document or professional membership certificate could be considered as not covering the exact goods and services listed in the Purchase Order against which the tender was offered.
The core compliance task is to link a document to an issuer of that document, to link that issuer to a scope of that document and to link that scope to the products and markets you have ordered. For Multi-Layer Engineered Wood Flooring and a Unique artistic parquet floor product the possible variations in configuration of a product need to be distinguished from in another.
What a flooring document is meant to prove
Certification, test report, and declaration are different
There are four separate terms that should be recorded in the compliance register. A certification is an independent assessment to a specific scheme or standard. A test report records results obtained using a specific method. A declaration is a supplier’s/manufacturer’s statement concerning a product or process. A professional credential is a document of assurance that pertains to an individual or organization. Such a credential does not automatically cover all of the products an organization sells.
I start by recording the document type followed by the title of the document, document number, issuer and date issued together with the date of expiry or review of the document. The specific product or process described in the paper also needs to be recorded. If a supplier supplies a scan of a document then the original file name of that document should also be recorded. Where the scope is not clearly readable then a clean copy of the scope should be requested prior to its use in tender submission.
The document should be matched to the ordered product
The product line in the report should match the product line in the order. The model, construction, dimensions, surface treatment, and factory name should be compared. A report for one engineered wood flooring construction does not automatically cover another construction simply because both sit under one brand.
YEHUI lists custom sizes, several surface treatments, thickness choices, and herringbone, chevron, and parquet patterns. That option range means the request needs sufficient detail. YEHUI‘s engineered wood flooring category helps identify the family. The selected model and configuration should still be written in the order file.
Before a certificate is requested, the product choices should be included in the request. YEHUI describes custom sizes, a wide range of colours and finishes, matte, glossy, hand-scraped, and brushed surface treatments, and various thickness options. Herringbone, chevron, and parquet designs are also listed. A project brief that calls for a deeper custom wear layer can specify a 3mm or 4mm option for confirmation. Those are product choices, not certification claims. The final check is whether the size, thickness, surface, and pattern in the evidence file match the selected order.
A buyer-side verification sequence
1. The issuing body should be identified
Begin by recording the issuer’s legal name and address together with a link to their website. In addition, record reference to their accreditation or scheme. For laboratory reports record the name of the facility at which the test work was carried out and the test method used. The International Laboratory Accreditation Cooperation explains how accreditation bodies and accredited laboratories are recognised.
The ILAC system is an international network of accreditation bodies which operate under the rules of ISO/IEC 17011 and accredit conformity assessment bodies. The above reference to a laboratory does not automatically transform every product report into a product certificate.
A paper should not be approved simply because its logo is familiar. The issuer’s own directory or verification page should be checked where one exists, with the page, date, and result recorded. If the issuer cannot be found independently, the item should remain open for clarification.
2. The scope should be reviewed line by line
The scope should identify the product model, construction, finish, dimensions, manufacturing site, and test method. Exclusions, sample description, and conditions attached to the result should also be checked. A document can be authentic and still be too narrow for the product ordered.
For a Chevron wood flooring order, the report should be checked to determine whether it covers the boards, the surface treatment, the pattern assembly, or another component. “Chevron” alone is not a product identifier. YEHUI‘s Chevron flooring category helps locate the product family; the requested document still needs a model-level match.
3. Dates, revisions, and continuity should be checked
Record the issue date and any expiry date. Also record what revision of the document was used for the tender. Check the impact of any change to model, finish, factory or manufacturing process and treat current paper with old product scope content as you would expired paper.
An ISO reference by a supplier needs to be checked against the ISO catalogue for the relevant standard and its scope. Such a reference does not act as a product certificate. The supplier’s document needs to link to the relevant standard reference and describe how it relates to the purchased goods and/or services and related processes.
4. Open items should be recorded instead of guessed
Use five status choices: verified, clarification requested, expired, out of scope or not supplied. Each open item must have an owner and a due date. This will enable the project team to clearly see what is blocking the approval process. A file full of documents without status information does not provide the same degree of control.
Common document types in a project file
Product and performance reports
These reports include results from specific test methods. Check the sample description, laboratory, test date, sample conditioning, units reported and results table before copying any numbers into the specification. Compare with alternative methods being used by the project and request a comparison or new test as appropriate – similar wording does not mean identical methods have been used.
Environmental or indoor-air documents
Environmental documents contain information about the environmental characteristics of a document such as material origin, emissions, recycled content and environmental management. The name of an environmental document does not provide sufficient information of the scope of the document. You should request information on the scheme rules, the certificate holder, the covered sites and the covered products. Environmental characteristics must be distinguished from other performance characteristics. One paper typically does not provide sufficient evidence to support all the characteristics required in a tender..
Quality-management certificates
A quality-management certificate usually refers to a management system. Even if such a system has been audited, the certificate in itself does not guarantee the quality of individual planks or parquet components. This is why the site, scope, audit time and issuing body need to be recorded. A product test required by the project must be applied for separately.
OEM and private-label records
Another way OEM work creates an identity crisis is between the catalogue name, private label and factory name. YEHUI defines OEM work as manufacturing to a client’s exact specifications. Hence for an OEM order, approved artwork, model code, product specification and supporting report should all be filed under that OEM order. Private labels are linked to the relevant factory and model name in the compliance file and therefore can be traced after shipment.
A usable B2B compliance checklist
One row per document should be used, with these fields:
| Field | What to record |
| Document type | Certificate, test report, declaration, or credential |
| Issuer | Legal name, website, accreditation or scheme reference |
| Holder and site | Certificate holder, factory, and covered location |
| Product scope | Model, construction, dimensions, finish, and pattern |
| Method or standard | Exact number, edition, and test method where relevant |
| Dates | Issue, expiry, review, and revision dates |
| Verification | Directory or issuer page checked, date, and result |
| Status | Verified, clarification requested, expired, out of scope, or not supplied |
A second reviewer should compare the register to the purchase specification before tender submission. Typically the specification document would be compared line by line to the register. In many cases a document exists but the scope belongs to a different product selected by the design team.
Questions buyers often ask
Does a certificate prove every product from the same supplier?
No, scope controls claim. Verify that product, site, construction and dates match before you use the document.
Is a test report the same as a certification?
No, a test report is a record of results from a test method. Certification is an assessment to a specific certification scheme or standard. Therefore keep these two document types separate in your register.
What if a supplier sends only a logo or a certificate number?
Request the complete document and the issuer’s verification route. A logo without scope does not enable a product approval.
How should a buyer handle a custom size?
Size and thickness should be added to the request. Is this already covered by the existing document? If not, this needs to be captured as a gap and relevant evidence requested to obtain approval.
For a B2B order, certification review is a matching exercise: document to issuer, issuer to scope, scope to product, and product to the project specification. YEHUI’s OEM and ODM information can support a conversation about custom requirements. The compliance register keeps the evidence tied to the exact order. For a review of an engineered parquet flooring package, YEHUI can be contacted with the model, pattern, dimensions, and document list required by the project.

