A purchase order for one nominal module wattage can still produce several different receiving and installation decisions. Some modules may belong to different measured-current groups. Pallets may combine production dates. A replacement shipment may use the same commercial family name with a revised cell layout, connector or electrical table. None of those questions is answered by a quotation that states only a positive power tolerance.
Direct answer: specify module matching as a controlled allocation process. Identify the exact module model and document revision, define the power-tolerance basis, obtain the supplier's current-bin definition where binning is offered, and connect each delivered serial number to its measured electrical record and pallet. Have the system designer approve the grouping and substitution rules for the actual strings and inverter inputs. A shared wattage label or current-bin letter alone does not establish electrical, mechanical or warranty compatibility.
This guide addresses buying, receiving and allocating a module lot. For measurement-report authenticity and image traceability, use the solar panel flash-test and EL evidence guide. For the distinction between laboratory rating conditions and operating output, use the STC and NMOT datasheet guide. Here, the practical question is how to turn those documents into an order that can be installed and later maintained without losing module identity.
Manufacturer examples below explain document interpretation. They do not establish a SINAWATTS product rating, current-bin scheme, certification, testing service, inventory, price, MOQ, delivery promise or project result. Any offered configuration needs its own written quotation and evidence.
Separate power class, tolerance, current bin and production lot
Treat these as different fields in the comparison sheet. A supplier may record all four, but they answer different questions and should not replace one another.
On small screens, swipe or scroll sideways to read every column. Keyboard users can focus the table and use the arrow keys.
| Field | Meaning for procurement | Required evidence | What it cannot establish alone |
|---|---|---|---|
| Nominal power class | Commercial wattage assigned to the exact model | Model suffix, label and matching datasheet | Identical current or voltage among all pieces |
| Power tolerance | Declared permitted relationship between rated and assessed power under the stated conditions | Units, lower and upper bounds, measurement and decision basis | Field output, current spread or shipment homogeneity |
| Current bin | Supplier-defined group based on a specified current parameter | Parameter, numeric boundaries, units, method and bin label | Compatibility with another supplier's identically named bin |
| Manufacturing lot | Traceability grouping defined by the producer | Lot identifier and its declared meaning | A guaranteed electrical grouping |
| Shipment or pallet | Logistics grouping | Packing list connected to serial numbers | A single production lot or current class |
| Installation group | Approved allocation to a string, input or array area | Designer-approved mapping and revision | That an unreviewed replacement is interchangeable |
A label such as H, M, L, A or B has no useful purchasing meaning until its owner supplies a definition. Ask whether the grouping uses maximum-power current, short-circuit current, another measured quantity or an internal production classification. Also ask whether boundaries differ by model, nominal wattage, plant or document revision. Record the response beside the identifier instead of keeping it in an email disconnected from the order.
If the supplier does not offer current sorting, record that explicitly. The next decision belongs to the designer: whether the available electrical dispersion and evidence support the proposed configuration, whether additional assessment is justified, or whether another offer is necessary. Do not invent bin assignments from rounded datasheet values simply to fill an empty column.
Read the tolerance as a statement with units and a scope
A tolerance expressed in watts and one expressed as a percentage are not the same procurement commitment. The basis must also be clear: nameplate rating, individual measured result, batch average, contractual minimum or a separate warranty measure. A positive number printed near a power table does not eliminate these distinctions.
For a bounded manufacturer example, the official LONGi Hi ROOF T page, checked on 2026-10-09, lists a 0 to +3% power tolerance and separate STC power, voltage and current entries for LGi7-72HYD power classes. This shows why a buyer must read the parameter columns and units separately. It is evidence for that named page and family; it is not a universal tolerance, an offered SINAWATTS specification or an approval to mix the listed classes in one system.
Consider a purely arithmetic illustration: if an agreed specification for a hypothetical 500 W module states a power band of 0 to +5 W, the corresponding stated band is 500 to 505 W. If another hypothetical specification states 0 to +3%, its arithmetic band is 500 to 515 W. Those calculations do not predict a shipment distribution or decide whether a measured result passes. The agreed measurement uncertainty and acceptance rule remain separate questions.
Ask the seller to state whether the quoted wattage is the minimum model class supplied or an average used to describe a mixed shipment. If mixing classes is proposed, require quantities by class before comparing the price. An order for a named class and an order for an aggregate nominal capacity can create different receiving obligations even when the total wattage looks similar.
Do not silently offset an individual shortfall with another module's surplus. A lot average may be useful information, but it is not a substitute for an individual acceptance requirement unless the contract actually defines acceptance that way. Likewise, the initial rating basis and a long-term power warranty should be compared as distinct obligations with their own documents and procedures.
Use current data without turning it into an unsupported yield claim
The official PVsyst explanation of array mismatch describes series combination through a shared current and parallel combination through shared voltage. It defines mismatch by comparing the independent devices' maximum powers with the maximum power of their combined electrical characteristic. That is the relevant conceptual reason to request matching information; this guide does not adopt the older help page's generic numerical assumptions as an acceptance threshold or prediction for a current project.
A single current number cannot describe the whole current-voltage curve. Maximum-power current and short-circuit current describe different operating points. A numerical similarity in one column therefore cannot authorize a module substitution across different technologies, cell arrangements or voltage characteristics. Nor does a narrower current group automatically produce a known annual-energy increase.
Keep the sales question separate from the engineering question. Purchasing can require a readable file, stable identity, agreed grouping and controlled changes. The designer evaluates the proposed allocation against module instructions, inverter limits, environmental conditions, shading, circuit topology and the project's performance model. A supplier's sorting claim is an input to that review, not its conclusion.
Avoid a promise such as "this bin eliminates mismatch" or "sorted modules produce a fixed extra percentage." Such claims require defined comparison systems, conditions and credible evidence. A more defensible purchasing objective is that the shipment provides the information and grouping needed to implement the approved design without unnecessary re-sorting or undocumented substitutions.
Specify the data dictionary before requesting thousands of rows
A spreadsheet becomes useful when its columns have stable definitions. Agree the format using a small representative example before asking for the complete shipment file. That prevents a late discovery that the current column is a rounded nominal value copied from a datasheet rather than an individual measurement.
On small screens, swipe or scroll sideways to read every column. Keyboard users can focus the table and use the arrow keys.
| Data field | Question to resolve before release | Practical receiving check |
|---|---|---|
| Serial number | Which identifier is physically readable on the module? | Match exact strings, preserving leading zeros |
| Model and revision | Does the record distinguish approved variants? | Compare against the order and label |
| Nominal class | Is this a wattage class or an actual result? | Confirm units and allowed class quantities |
| Measured Pmax, Vmp and Imp | What conditions and processing produced the values? | Check completeness and plausible data relationships |
| Voc and Isc | Are values measured, nominal or translated? | Keep their meaning distinct from Vmp and Imp |
| Current group | Which revision defines the boundaries? | Reconcile group with the stated parameter |
| Test record identity | Can the source record be retrieved? | Trace a sample without substituting another module |
| Pallet and lot | Which logistics and production groups apply? | Reconcile counts and missing identifiers |
| Disposition | Released, held, replaced or returned? | Prevent an exception from entering an installation list |
The official IEC 60904-1:2020 publication page, checked on 2026-10-09, identifies the standard's scope as measurement of photovoltaic current-voltage characteristics in natural or simulated sunlight. That scope supports asking which measurement procedure was used. It does not supply a buyer's lot-acceptance rule or prove that an unnamed factory, report or instrument complies with the standard.
Request the applicable procedure and uncertainty statement from the party responsible for the measurements. If data have been translated to reference conditions, record that basis. If a retest is planned, agree the laboratory, conditioning, handling, uncertainty treatment and disposition process before shipping samples. A disagreement near a boundary should not be resolved by choosing whichever spreadsheet has more decimal places.
Design the receiving decision around identity first
An efficient receiving process does not begin by sorting every pallet physically. Begin with document reconciliation while the shipment remains identifiable. Confirm that the expected serial list, pallet list and document revisions belong to the arriving shipment. Preserve the original files before importing them into a working allocation sheet.
Check for duplicated serial numbers, blank identifiers, missing rows, unexpected model suffixes and inconsistent class totals. Treat these as exceptions requiring explanation. A missing record does not automatically prove a defective module, but it can prevent that module from being released under a traceability-based purchasing requirement.
Next, compare a documented sample of physical labels against the digital list using a sampling approach agreed for the order. The example here does not prescribe a universal inspection sample size. The appropriate coverage depends on the contract, risk, supplier evidence and receiving arrangements. Record who checked the sample, which serial numbers were checked and what happened to any discrepancy.
Finally, release modules to the installation allocation only after exceptions have an approved disposition. Keep the original record and an audit trail of corrections. If the seller changes a value, request the reason and replacement source record. Overwriting the old spreadsheet without retaining the correction history makes later disagreements much harder to investigate.
Send the proposed module list, current-bin definition and shipment requirements for an RFQ.
Build the allocation plan before pallets are opened
A useful allocation plan answers where each approved group will be used, who may change that plan, and how leftover pieces will be managed. It should be based on the actual system design rather than a generic instruction to keep every pallet together. Pallets are logistics containers; their contents may or may not correspond to the best approved installation groups.
Use an allocation table with project area, inverter identifier, input identifier, string identifier, approved module variant, permitted current groups and a reference to the designer's decision. Where serial-level placement is required, add the assigned serial numbers and actual installation record. Where group-level placement is sufficient, define how group identity remains visible during handling.
The allocation plan should also explain whether an incomplete group can be combined with another group, and who approves the decision. Do not leave installers to interpret a bin letter as permission. If adjacent bins may be combined, the permission should identify the exact product and scheme, affected location and any conditions. If such permission is absent, retain the exception for review.
Keep enough operational detail to make the plan usable: pallet-opening sequence, staging locations, labels visible after unpacking, temporary identification method and the handover to installation staff. The method should preserve manufacturer labels and follow handling instructions. A technically complete spreadsheet offers little protection when unpacked modules become indistinguishable on site.
Compare three purchasing arrangements fairly
The right purchase arrangement depends on the design and the supplier's documented offering. Ask bidders to describe their actual commitment rather than accepting the same shorthand from all of them.
On small screens, swipe or scroll sideways to read every column. Keyboard users can focus the table and use the arrow keys.
| Arrangement | What the quotation must define | Decision risk to address |
|---|---|---|
| One model and one nominal class | Exact model, quantity, tolerance basis, data delivery and substitutions | Same class may still include current dispersion or component revisions |
| One model with several declared classes or bins | Quantity by group, bin definitions, pallet identification and allocation support | Insufficient quantity in one group can disrupt the installation plan |
| Staged deliveries or replacement supply | Approved variants, change notice, compatibility review and record continuity | Later deliveries may not match the original electrical or mechanical configuration |
For example, two hypothetical offers can each total 120 modules in the same nominal class. Offer A supplies a single documented current group. Offer B supplies 80 pieces in one group and 40 in another. There is no basis here to declare A better or B unacceptable. The buyer needs the group boundaries, the designed grouping sizes, the permitted mixing rule and the installation plan before comparing them.
To make the allocation issue concrete, assume solely for a logistics illustration that a designer has already approved ten strings with twelve modules each, and has required each string to use a single declared group. This is not a string-design recommendation. Offer B's counts above produce the following arithmetic:
On small screens, swipe or scroll sideways to read every column. Keyboard users can focus the table and use the arrow keys.
| Declared group | Pieces available | Complete twelve-piece groups | Pieces left over |
|---|---|---|---|
| First group | 80 | 6 | 8 |
| Second group | 40 | 3 | 4 |
| Total | 120 | 9 | 12 across two groups |
There are enough modules in total, but only nine complete groups satisfy this hypothetical no-mixing rule. The remaining eight plus four cannot be assigned to the tenth string without changing that rule or the supplied allocation. Possible questions are whether the seller can rebalance quantities, whether the designer approves a specific mixed group, or whether another documented allocation is appropriate. None of those options is assumed to be available or technically acceptable. The example shows why quantities by bin should be reviewed before shipment, even when model, nominal class and total quantity match the order. The commercial comparison should identify the cost of any agreed grouping, documentation, storage separation or retest without inventing a premium. Ask whether the offer includes those activities and request any exclusions in writing. A lower headline unit price can be difficult to compare if one bidder has assumed unrestricted mixing while another has priced a controlled allocation requirement.
Control replacements and split deliveries as new decisions
A replacement with the same nominal wattage is not automatically equivalent. Require the complete model identity and compare the current-voltage data, physical dimensions, mounting interfaces, cables, connectors and applicable instructions. Route electrical and system compatibility to the designer, and route product or warranty questions to the responsible manufacturer or contractual supplier.
Retain the original serial-to-location record so that the replacement review starts with the installed configuration. Record which module was removed, why, the replacement serial number and the approved reason for accepting that replacement. Do not recycle an old serial number or quietly replace the original record with the new one.
For split deliveries, agree whether a product revision change requires notice even when the trade name remains unchanged. Ask for the evidence before release of the later shipment, not after it has been unpacked. If exact continuation cannot be committed, make the substitution review process part of the quotation so schedule and evidence obligations remain visible.
Spare quantities are a project-specific commercial decision. This guide does not prescribe a fixed spare percentage. Ask the project team to consider approved alternatives, storage conditions, service strategy and the consequences of an unavailable original variant. Document whether stored spares belong to a particular electrical group and how their identity will remain connected to the installation records.
Use a release matrix that distinguishes holds from rejections
An unresolved document question should have a named owner and next action. This prevents two unhelpful extremes: installing an unreviewed substitution because the module appears undamaged, or rejecting a whole shipment because a correctable data-format error was discovered.
On small screens, swipe or scroll sideways to read every column. Keyboard users can focus the table and use the arrow keys.
| Observation | Initial disposition | Evidence needed for closure |
|---|---|---|
| Physical serial absent from shipment file | Hold the affected identity from allocation | Correct source record and reconciled packing list |
| Current-bin letter has no numeric definition | Hold the bin-based matching decision | Authorized definition with parameter, units and revision |
| Model suffix differs from the order | Refer for substitution review | Datasheet, drawings, compatibility decision and commercial acceptance |
| Retest result conflicts near a contractual limit | Follow the agreed dispute procedure | Method, conditions, uncertainty and original records |
| Pallet contains more than one declared group | Check against packing and allocation requirements | Accurate identification and approved handling disposition |
| Aggregate power meets the order but individual criteria do not | Apply the actual contract | Written acceptance basis; no silent averaging |
The matrix is a proposed procurement workflow, not a test standard. The signed order and approved engineering instructions govern the actual decision. Where no acceptance rule exists, obtain one before turning an ambiguous observation into either an automatic pass or a universal rejection.
Prepare a compact RFQ package
The package should let the supplier answer precisely without requiring the buyer to guess missing parameters. Include the following information and mark genuinely unknown items as questions.
- Intended project and destination, including the party responsible for system design.
- Exact proposed module family, model, class and applicable document revisions.
- Quantity and delivery stages, with any required allocation groups stated separately.
- Power-tolerance units and basis, plus the proposed acceptance and dispute procedure.
- Whether current sorting is required, optional or subject to the designer's review.
- Requested definition of every bin and the parameter used to assign it.
- Serial-level electrical file, pallet mapping and traceability expectations.
- Proposed grouping, substitution, split-shipment and spare-module rules.
- Required delivery timing for documents so they can be reviewed before shipment.
- Requested price, MOQ, lead time, exclusions and evidence availability for the actual offer.
Request a response in three columns: confirmed, proposed alternative and evidence reference. This makes deviations visible without treating an unconfirmed request as a capability claim. Resolve differences before changing the purchase order, and preserve the approved version with the shipment records.
Buyer FAQ
Does positive power tolerance mean every module has the same current?
No. It describes the stated power relationship under its defined basis. Current grouping is a separate matter requiring a named parameter and numeric boundaries. Ask for the actual current data and the supplier's grouping definition if matching is part of the procurement requirement.
Is maximum-power current the same as short-circuit current?
No. They describe different points on the electrical characteristic. A bin based on one must not be interpreted as a bin based on the other. Preserve the parameter name in files, labels and approval records rather than shortening both to "current."
Can I compare bin H from two suppliers?
Only after comparing their definitions and the actual module configurations. The letter may represent different numerical ranges or internal rules. An identical label is insufficient evidence for mixing, equivalent output or system compatibility.
Should every module in one string come from the same pallet?
A pallet is a logistics group, so that rule is not inherently meaningful. Follow the approved allocation plan and manufacturer instructions. If pallet contents are deliberately grouped for installation, require a packing list that proves the relationship and preserves it during unpacking.
Will narrow current bins guarantee higher annual generation?
No fixed gain follows from the bin label alone. Annual performance depends on the system, operating conditions and other losses. A credible comparison needs a defined design and evidence-based analysis. Procurement should secure reliable grouping information without promising a universal yield improvement.
Can modules with the same watts but different models be substituted?
Not without review. Compare the electrical characteristics and relevant mechanical, connector, installation and warranty details. The designer and responsible product parties need to approve the actual substitution; purchasing should retain the decision and updated identity records.
Is a lot-average power result enough for receiving acceptance?
Only if the order specifically defines acceptance on that basis. A good average does not erase a failed individual requirement. State individual and aggregate obligations separately, including how measurement uncertainty and disputes are handled.
What if the supplier will not provide raw flash-test files?
Ask what traceable evidence can be supplied and when. Then determine whether it meets the agreed procurement requirement. Do not present a nominal datasheet table as serial-level measured evidence. If the requirement remains unmet, resolve it before release or choose an acceptable documented alternative.
Is an IEC reference on a report proof that this lot passed?
No. A reference identifies a claimed procedure or basis; the report still needs identities, results, conditions and accountable issuance. The cited IEC public scope does not certify an unnamed lot or decide the buyer's contractual acceptance rule.
How should a missing serial record be handled?
Keep the affected module identifiable and outside the approved allocation until the discrepancy is resolved. Request the correct source record and reconcile related lists. Preserve the correction trail so the receiving decision can be reconstructed later.
Do current bins replace inverter input checks?
No. Binning does not establish the inverter's voltage, current or operating limits, and it does not replace string-design review. Give the designer the exact module evidence and intended allocation, then retain the approved configuration.
Can SINAWATTS confirm price, sorting availability and lead time from this guide?
No. Those are offer-specific matters. Send the model requirements, quantities, grouping rules and evidence needs for a written response. Any unconfirmed item should remain an open RFQ question until the responsible supplier provides supporting information.
Close the order with an allocation-ready record
The useful deliverable is not just a tolerance number. It is a controlled connection between the ordered configuration, delivered serial numbers, electrical evidence, approved grouping and installed locations. Keep the interpretation simple enough that purchasing, receiving and installation teams use the same definitions.
Send your PV module class, current-bin and lot-allocation requirements to SINAWATTS.