Check the module in front of you against the manufacturer's identity record and the purchase documents. A readable QR code, a familiar logo or a successful serial-number lookup is only one part of that comparison. Record the exact serial, complete model, nameplate photograph, manufacturer response and shipment reference. Resolve mismatches before treating the shipment as accepted; keep authenticity, specification, condition and warranty questions separate.
This guide is for buyers, distributors and project procurement teams comparing solar module offers and preparing receiving records. It explains how to request a traceable identity package without inventing a universal serial-number format or declaring a product counterfeit from a photograph. The workflow is a proposed purchasing method, not a manufacturer certification service or a claim that any named supplier has supplied suspect goods.
The objective is to answer four questions clearly: what was ordered, what arrived, what the manufacturer can confirm, and which unresolved differences still affect release. This is useful even when the shipment is genuine. A wrong model suffix, incomplete serial list or mismatched pallet record can create a procurement problem without establishing counterfeiting.
Define identity, authenticity and acceptance separately
Identity connects a physical module to a recorded model and serial number. Authenticity verification asks the manufacturer or its documented service route what that identity represents. Acceptance asks whether the delivered item meets the purchase agreement and the project's approved requirements. These decisions overlap, but treating them as one yes-or-no box can hide important gaps.
For example, a database response may identify a serial number while the photograph supplied by the seller shows a different model. A genuine module may also be unsuitable for the ordered configuration or destination. Conversely, a failed query can require further investigation rather than proving that the physical product is counterfeit. Preserve the exact observation and request the appropriate confirmation.
Use separate columns in the receiving register for identity match, manufacturer response, ordered specification and physical condition. Add a release decision only after the responsible reviewers have considered the required evidence. This prevents a positive result in one column from automatically filling the others. It also makes a hold decision easier to explain to the supplier.
On small screens, swipe or scroll sideways to read every column. Keyboard users can focus the table and use the arrow keys.
| Evidence item | Question it helps answer | What it does not establish alone |
|---|---|---|
| Nameplate photograph | What is marked on this module? | Independent confirmation of origin |
| Manufacturer serial response | What does the official record say? | Condition of the item being delivered |
| Purchase order and invoice | What did the parties order and bill? | Physical identity of every module |
| Pallet or shipment list | Which identities are assigned to the shipment? | Correctness without receiving reconciliation |
| Inspection or test record | What was observed under its stated scope? | Every commercial or warranty condition |
Read the model and serial from the appropriate locations
Use the relevant manufacturer's installation or identification information to locate module markings. Do not assume that every brand uses the same label position, number length or coding system. Keep the complete model designation, including suffixes and punctuation, in the record. A shortened marketing family name may be useful for conversation but is not enough for an exact procurement comparison.
JinkoSolar's referenced installation manual distinguishes the nameplate, which identifies module type and principal electrical and safety information, from the unique serial-number and barcode identification. It also describes the identifier's location for the modules covered by that manual. Apply those instructions within their stated scope rather than turning them into a universal rule for other brands. JinkoSolar installation manual, identification section.
Photograph the entire nameplate and a wider view connecting it to the module. When more than one marking location is relevant, record them without removing, scraping or altering the markings. Ask the manufacturer how to resolve a damaged or unreadable identifier. Avoid a destructive authenticity experiment that could harm the product while still failing to establish its origin.
Keep the distinction between a human-readable serial and a scanned value visible. If the scan includes additional fields, save the original output and identify which field is being used as the serial. Do not silently delete characters until a portal accepts the entry. Confirm the expected input with the manufacturer's guidance, and preserve any correction as a documented transcription change.
Reach verification through the manufacturer's own route
Start from the manufacturer's official website or an independently confirmed service contact. Follow its stated authenticity or customer-service route rather than trusting a link solely because it appears in a seller's message or inside a QR code. Record the destination domain and the date of the check. This gives the evidence a source another reviewer can recognize and revisit.
AIKO's official authenticity page links to its product verification service and directs users to contact the company when a correctly entered serial still fails the query. That is a useful example of an escalation route, rather than a rule that every failed lookup proves counterfeiting. AIKO official module authenticity page.
A buyer should also verify the scope of the response. Does it identify the product, provide a destination-related message or ask for additional information? Save the actual response instead of reducing everything to “passed.” If the service requires a country selection, record the selected country because it forms part of the query context. Do not change that selection just to obtain a more favorable message.
JinkoSolar's European serial-check guidance explains responses that refer to original sales destination and regional warranty or service eligibility. One illustrated adverse response includes both non-genuine product and unofficial-channel possibilities. The wording therefore deserves careful reading before assigning a cause. JinkoSolar European serial verification guidance.
For a substantial shipment, agree how bulk verification or manufacturer clarification will be handled. A public single-item form may not be the appropriate route for sending an entire project inventory. Ask for the documented service process, required file format and response scope. Do not automate excessive queries or invent serial numbers to probe a system.
Treat QR codes as data carriers, not a complete verdict
A QR or barcode can help capture an identifier or open a webpage. The procurement decision still depends on where the data came from, which physical item it describes and what the official response says. A successful scan establishes that the reader decoded something; it does not independently establish the seller's authority, the module's condition or compliance with the purchase order.
Use a scan review that preserves both the decoded value and a photograph of the marking. If a code opens a webpage, check the destination through the manufacturer's official route before relying on its content. If it supplies text, compare that text with the human-readable marking and the required query field. Document differences instead of choosing whichever value produces a convenient result.
Do not use code presence or absence as a universal rejection rule. The relevant model documentation should explain the expected identification arrangement. If the supplied product differs from that arrangement, request a manufacturer clarification tied to the actual photographs and serials. An undocumented label variation needs investigation; a buyer should not convert uncertainty into a public accusation.
Keep scans associated with the receiving event. A seller's earlier screenshot can be supporting evidence, but it should not replace the buyer's reconciliation of the actual delivered identities. Record who captured the information and when, without exposing a complete project serial inventory publicly. Share the necessary identifiers with authorized parties through the agreed procurement or service channel.
Build a serial register that resists ordinary data errors
Store serial numbers as text. Preserve leading zeros, punctuation and letter case as supplied until the manufacturer's rules justify a normalized comparison. A spreadsheet can otherwise change long identifiers or display them in a format that makes manual checking unreliable. Maintain a raw-value column and a separate comparison column when normalization is necessary.
Assign each physical module a receiving reference, then connect it to a pallet or shipment reference. This allows a discrepancy to be located without rewriting the manufacturer's identity. Use one row per module where the project requires individual traceability. If the supplier provides only a range or carton total, identify the missing level of detail and agree how it will be supplied before delivery release.
Check for blank values, exact duplicate serials, unexpected model values and quantities that do not reconcile with the packing list. These are data-quality checks, not automated counterfeit findings. For example, a duplicate row may be an import error or may reflect two items carrying the same recorded identifier. Locate the physical items and original records before deciding the cause.
Protect the original supplier file. Save a dated copy and perform reconciliation in a working copy, with changes recorded. When a supplier corrects a list, retain both versions and the explanation. A clean final spreadsheet is useful, but deleting the history can make it difficult to understand which module or shipment the original discrepancy concerned.
Add a clear exception status such as “awaiting photograph,” “manufacturer clarification pending” or “model mismatch under review.” A blank cell should not mean approved. Name the owner of each unresolved item and its next required action. This makes the register actionable without turning it into a complex software implementation.
A fictional reconciliation example makes the distinction concrete. Store the invented identifier 00-DEMO-UNIT-A as text in the raw-value column; it illustrates preservation of leading zeros and is not any manufacturer's serial format. If two spreadsheet rows both reference receiving item R1 and the same photograph, investigate a duplicate import. If receiving items R1 and R2 have separate photographs showing that same identifier on two physical modules, retain both records and escalate the physical identity conflict. Do not delete one row merely to make the duplicate warning disappear, and do not declare counterfeiting before the evidence is resolved.
Match manufacturer results to the purchase documents
Compare the returned identity with the complete model and ratings recorded in the purchase package, within the information the service actually provides. Do not assume every portal returns the same fields. If a field is absent, mark it unavailable from that source and request the relevant document or confirmation. Absence is not evidence that the field matches.
Canadian Solar's public authenticity interface displays fields including module type, power, grade and shipment destination, and provides an escalation contact for an unrecognized serial. This describes the interface and its stated assistance route; no real module serial was submitted for this guide, and no shipment has been authenticated here. Canadian Solar module authenticity service.
Use a document map rather than a loose folder. Connect the purchase-order line to the offered model, its applicable datasheet, the supplier's shipment list and the receiving register. If the model changes during negotiation, record the approved change and the affected quantity. A later datasheet should not silently replace the model that was commercially agreed.
Where technical production records are required, connect them by the relevant identity and document revision. The flash-test and EL report traceability guide addresses that evidence in detail. A serial match helps organize the records; it does not turn a report into proof of a condition outside its stated test or inspection scope.
Keep warranty applicability in a separate review. An authenticity result and a warranty statement can both be relevant, but neither should be summarized beyond its actual terms. The PV module warranty document guide explains how to connect model, destination and claim records without declaring coverage from a brand name alone.
Define the shipment verification plan before purchase release
Specify the evidence expected before shipment and the checks expected on receipt. Ask who supplies the serial inventory, when it becomes final and how replacements are recorded. State whether the buyer requires individual reconciliation, selected physical checks or another agreed method. The scope should reflect the project requirement and responsible review, not a generic sample size copied from an online article.
Do not present a small sample as proof that every module in the lot has been authenticated. Record exactly which identities were checked and how they were selected. If a discrepancy triggers wider review, document that decision. Where full individual verification is required, arrange a practicable manufacturer-supported route before committing to a process the receiving team cannot complete.
Separate the administrative hold from the technical conclusion. A shipment can remain unreleased while a serial is being clarified without anyone yet declaring it counterfeit or defective. The purchase terms should identify the parties responsible for clarification, storage, replacement or other disposition. Commercial commitments require explicit agreement; this guide does not supply universal deadlines or legal remedies.
Require updated records when modules are swapped before shipment. A replacement that resolves physical damage can still leave an inaccurate serial list if the documents are not revised. Ask the supplier to identify removed and added serials, the affected pallet reference and the approved reason. The receiving register should reflect what actually arrives rather than what was originally planned.
Send your proposed module identification and shipment-record requirements with the model list and destination. Related solar accessories and solar power connectors also need their own component identification; module authenticity does not establish accessory compatibility.
Handle exceptions without guessing the cause
When a query fails, first preserve the result and check the input against the original marking. Review ambiguous characters, the selected region if applicable and the official service instructions. If the discrepancy remains, send the necessary photographs and purchase references through the manufacturer's stated support route. Avoid repeated speculative changes to the serial string.
When a returned model differs from the label or order, record all three values separately. Ask the supplier and manufacturer to explain the relationship. The relevant issue may involve transcription, document applicability, shipment substitution or another cause; the purchasing team should not select a cause without evidence. Keep the affected identities on hold according to the agreed release procedure.
If the database recognizes a serial but two physical modules appear to carry it, isolate the records and obtain clear photographs identifying both items. Check whether the apparent duplication arose during scanning or spreadsheet import. If physical duplication remains, escalate the exact evidence. A recognized serial should not be used to dismiss a contradiction between two delivered items.
If the portal is unavailable, record the access problem separately from product status. Use the manufacturer's documented alternative contact where available and retain the pending state until the necessary evidence arrives. A temporary service outage is not a product-authenticity result. Equally, it should not be relabeled as a completed check just to release paperwork on schedule.
Hypothetical case: a valid lookup with the wrong shipment record
Imagine a buyer expecting two pallets of one approved module model. The seller supplies a serial file and screenshots showing successful queries. On receipt, the buyer finds that several physical serials are absent from the file, although the photographed nameplates show the ordered model. This is a hypothetical document-reconciliation example, not a reported shipment or a claim about any manufacturer.
The buyer records the missing identities and holds the affected release lines pending clarification. The existing screenshots remain useful for the identities they actually cover, but they do not cover the newly observed modules. The buyer requests a corrected shipment list, the reason for the substitutions and the agreed manufacturer verification evidence for the replacement identities.
Suppose the seller explains that a pallet was rebuilt after a handling incident and supplies a revised list. That explanation should be connected to the physical records and reviewed; it is not automatically accepted or rejected. The receiving team then reconciles the updated list, confirms the agreed verification scope and records the responsible release decision.
The lesson is about evidence continuity. A valid query can coexist with an incomplete shipment record, and a corrected record can resolve a discrepancy when the supporting evidence is adequate. The process does not require a speculative fraud conclusion. It requires a clear link between the approved purchase and the modules actually delivered.
Compare supplier offers on traceability obligations
Include document delivery as a quotation requirement. Ask whether the supplier will provide an individual serial inventory, complete model list, manufacturer verification support and a documented correction route. Request explicit exceptions. A supplier who cannot provide a particular record should say so before the buyer assumes it is included in the commercial offer.
Compare the timing of those obligations as well as their names. A serial list supplied only after installation may not support the buyer's receiving process. Agree when the list is available, how final changes are identified and who answers discrepancies. Do not infer a guaranteed response time, delivery date or service capability from a website description.
On small screens, swipe or scroll sideways to read every column. Keyboard users can focus the table and use the arrow keys.
| RFQ obligation | Evidence or response to request | Decision supported |
|---|---|---|
| Exact offered model | Complete designation and applicable datasheet | Compare the proposed product |
| Individual identity records | Agreed serial inventory format and timing | Reconcile the shipment |
| Verification route | Manufacturer service reference and response scope | Plan authenticity review |
| Substitution control | Removed/added identity record and approval | Preserve purchase-to-delivery continuity |
| Exception handling | Named contact and disposition process | Close unresolved release items |
Assess price only after understanding those differences. A lower quotation with undefined traceability obligations is not automatically equivalent to a documented offer. Conversely, a large document package is not valuable if none of its records can be matched to the delivered identities. Ask for an example of the proposed record format without treating sample records as evidence for the future shipment.
Buyer FAQ
Does a successful serial-number check prove the delivered panel is genuine?
It is useful manufacturer evidence for the queried identifier, but the buyer must connect that identifier to the physical module and read the response within its stated scope. Compare the nameplate, model and shipment records. Do not let a positive lookup replace checks of condition, ordered configuration or unresolved identity conflicts.
Does no result mean a module is counterfeit?
Do not jump to that conclusion. Preserve the response, verify the transcription and follow the manufacturer's clarification route. AIKO and Canadian Solar publish assistance routes for unresolved queries. Keep the affected release decision pending where required, and describe the issue accurately as unverified until evidence supports a more specific conclusion.
Can I rely on a QR code that opens a branded page?
Confirm the destination through the manufacturer's official website or verified service route. Record what the code contains and match it to the module markings. A branded appearance alone is insufficient evidence, and scanning successfully does not establish every procurement requirement. Treat the scan as one input to the identity record.
Should every manufacturer use the same serial-number length?
No universal format is established by this guide. Follow the applicable manufacturer's instructions for the relevant module. Do not reject or accept an identifier only because it resembles another brand's format. If the expected format is unclear, provide photographs and request clarification rather than guessing which characters should be removed.
Can one checked module represent the whole pallet?
Only describe the actual scope of the check. Verification of one identifier does not authenticate every other identifier on the pallet. Agree the shipment review method with the responsible parties, record which modules were checked and define how discrepancies trigger further action. Do not invent a universal sample quantity or claim statistical confidence without a justified plan.
Is module authenticity the same as warranty eligibility?
Keep them separate. Read any region or service limitations in the manufacturer response and review the applicable warranty documents for the actual purchase. A genuine module can still raise destination, contracting-party or document-applicability questions. Ask the relevant issuer for clarification rather than inferring coverage from a recognized serial alone.
What if a module is replaced after the serial list is issued?
Request a controlled update identifying the removed and replacement serials, the affected shipment reference and the reason for the change. Reconcile the replacement against the approved model and required verification scope. Preserve the earlier list so the change remains understandable; do not overwrite history and leave the receiving team with unexplained differences.
Prepare a module identity RFQ with clear release evidence
Start with the full offered model and destination, then define the serial inventory, nameplate evidence, manufacturer verification route and exception process. Link the final records to the actual shipment and retain unresolved questions visibly. This makes the request useful for procurement while respecting the limits of photographs, portal results and supplier statements.
Send your module model list, destination and traceability requirements for a scoped inquiry. Include the record format you need and any existing discrepancy that requires clarification. Keep sensitive project serial inventories within the agreed business channel, and request evidence for the actual offered configuration before making claims about origin, acceptance or warranty coverage.