Answer
Solar procurement can stall when a BOM uses a stale design, vague item identities, wrong units, hidden packaging rules, missing ancillary parts, unreviewed substitutions, assumed availability, unclear delivery dependencies or an unowned release. Tie each line to a current revision and a required-on-site event. Verify quantities, compatibility, supplier commitments and receiving constraints before authorizing an order; a generated BOM is not a purchase approval.
A solar BOM can be internally consistent and still fail to support an order. The design may be current while the purchasing unit is wrong, the supplier has not allocated stock, or a required mounting accessory has no delivery plan. Procurement needs a materials list whose engineering, commercial and delivery states are distinguishable.
This guide focuses on the release and delivery dependencies that can hold an order or installation. The material-list error guide covers defects and rework in more detail. Neither checklist replaces qualified design review, manufacturer instructions, local requirements or contractual authority.
1. Ordering against an unidentified or stale design
The BOM should be tied to a revisioned design, not rebuilt from memory. Record site reference, layout revision, equipment selections, release purpose, reviewer and open items. A preliminary estimate and a purchasing release are different states.
Before authorizing an order, compare the module count, inverter selection, mounting approach and electrical accessories to the referenced design. If roof geometry or stringing remains provisional, identify which quantities depend on it and who may release them.
NASA’s configuration-management guidance describes identification, controlled changes and current and historical configuration records. It is a cross-industry reference for record control, not a solar purchasing standard.
2. Using a product family instead of an exact item
A description such as “rail,” “connector” or “inverter” may be insufficient for a supplier to identify the intended item. Use the exact manufacturer and part or model reference, variant, relevant specification and document revision. Distinguish an assembly from its separately purchased components.
Have the responsible designer verify required compatibility and installation conditions against the actual equipment and mounting documentation. Similar names, dimensions or ratings do not establish interchangeability. Do not let a purchasing description silently select the technical design.
3. Confusing design units and purchasing units
Record whether a quantity means pieces, pairs, assemblies, metres, reels or another defined unit. Keep installed requirement, stated allowance, available usable stock and purchase quantity in separate columns.
Cable route length is not necessarily the sum of every conductor’s length. Count the conductors and termination allowances from the reviewed design. A purchasing unit conversion does not determine conductor sizing or installation compliance.
4. Hiding packaging, minimum orders and allowances
A supplier may sell only whole packs or reels or apply a minimum order. Preserve the engineering requirement before converting it to purchasing quantities. Document pack size, rounding rule, excess stock and the purpose of each allowance; do not add a blanket percentage without a project basis.
Hypothetical pack calculation: a reviewed requirement of 47 pieces plus an explicitly approved 3-piece allowance requires 50 pieces. If the exact item is sold in 12-piece packs, ordering whole packs requires 5 packs, or 60 pieces. The 10-piece packaging excess is separate from the 3-piece allowance. This demonstrates arithmetic only, not a recommended allowance or a live supplier term.
5. Leaving ancillary parts outside every scope
Modules and inverters do not describe the complete installation. The DOE system-design overview explains the roles of modules, mounting and inverters; it does not provide a project-ready parts list.
Use a completeness map for the actual design: structural and mounting interfaces, electrical connections and protection, monitoring, labels and documentation where required, and other project-specific interfaces. Each category needs an included line, a documented exclusion with a responsible party, or an open decision. Do not interpret a blank category as “not needed.”
6. Treating a substitute as a purchasing-only change
An available alternative may change dimensions, electrical limits, mounting conditions, software configuration, warranty conditions or the quantity of related parts. Record the proposed substitution and the affected artifacts before issuing it to the field.
The qualified owner decides whether the alternative is suitable; the commercial owner checks price and contract consequences. Update the approved design and BOM together. A supplier’s claim that an item is equivalent does not complete the project review.
7. Assuming a quote or catalog is a stock commitment
Separate listed products, indicative lead times, quoted terms, allocated stock, accepted orders and committed delivery events. Record the supplier, exact items, confirmation date, validity and conditions. An undated screenshot is not evidence of material reserved for the project.
NIST MEP’s supply-chain guidance discusses mapping risk, supplier relationships and procurement strategy. Apply those general ideas to the project’s actual evidence: who will confirm critical parts, what event triggers rechecking, and what happens if the supplier cannot fulfill the requirement? A secondary source still requires technical and commercial review.
8. Ignoring receiving and installation dependencies
Define when material must be available for the task that needs it. A dispatch date is not necessarily arrival, inspection, acceptance or readiness for installation. Record the delivery location, receiver, access restrictions, storage responsibility, inspection criteria and approved sequence.
A replacement inverter arriving early does not make a project ready if the reviewed mounting or electrical interface is unavailable. Conversely, do not expedite every item merely because one task is urgent. Link each line or assembly to the relevant installation dependency and responsible schedule owner.
9. Releasing changes without an owner or disposition
A task list alone does not resolve exceptions. The record needs an owner, the decision required, a clearing event and affected project artifacts. Questions involving engineering, interconnection, contractual scope or site safety go to the designated qualified person.
Retain sent revisions and identify the current release. For material already ordered or received, record whether the authorized disposition is use, return, replacement, cancellation or another treatment. Internal revision status does not amend the supplier contract or cancel an order.
A procurement-release record teams can reuse
| Record | What to retain | Hold or narrow when |
|---|---|---|
| Design basis | Project, revision, release purpose and reviewer | Quantities rely on an unreviewed change |
| Item identity | Exact reference and applicable document | A family name or vague description controls selection |
| Quantities | Requirement, allowance, unit and purchasing conversion | Units or allowance basis cannot be reconstructed |
| Completeness | Included, excluded and open interface categories | A required part has no responsible scope |
| Substitutions | Approval and affected drawings, parts and terms | Compatibility or authority is unresolved |
| Supplier evidence | Current confirmation, conditions and owner | Availability is only assumed |
| Delivery | Required event, receiving and task dependencies | Arrival and installation readiness are conflated |
| Exceptions | Decision, owner, clearing event and disposition | A material change reaches orders without review |
Keep the BOM, drawings and commercial scope in agreement. A proposal tied to an earlier layout may describe a different system from the one being purchased. Compare the current system size, equipment, scope and exclusions before communicating a procurement change to the customer.
Test the release using a controlled example
Use a fictional project record to test stale revisions, a missing accessory, an unavailable item, a pack conversion and a proposed substitute. Ask the receiving owner to reconstruct the quantity and find the approval and supplier confirmation. The test assesses record quality; it does not establish actual delivery performance.
Measure observed exceptions with defined events and populations: purchasing holds, quantity corrections, substitution reviews and delivery changes. Count revisions consistently and distinguish an order hold from an installation delay. A supplier delay on a non-critical task does not automatically equal project delay; the schedule owner must review dependencies. No universal delay benchmark follows from this checklist.
Where SurgePV fits
SurgePV supports solar design, material output and proposal workflows. A generated BOM remains an input to responsible purchasing review. It does not establish inventory allocation, supplier promises, technical approval or an executed order. Teams need the actual supplier documents, qualified reviewers and commercial systems for those decisions.
Review design and material workflows together
Explore how SurgePV connects solar project design with material and proposal outputs.
Book a guided demoFrequently Asked Questions
What should a solar BOM contain before procurement release?
It should identify the project and design revision, exact item references, required quantities and units, allowances, purchase quantities, approved substitutions, supplier evidence, required delivery events and unresolved decisions. Applicable project engineering and manufacturer instructions control suitability; a complete-looking list does not establish approval.
Does a supplier quote establish material availability?
Not by itself. Record what the supplier has actually confirmed, such as stock allocation, order acceptance or a delivery commitment, and the conditions and date of that confirmation. Distinguish an indicative lead time from a project-specific commitment and assign an owner to unconfirmed items.
How should a BOM change affect material already ordered?
Review the affected drawings, specifications, order lines, received stock and installation sequence before implementing the change. Record approved use, return, replacement, cancellation or another disposition under the actual contract and project authority. A new BOM revision does not automatically cancel an order or make received material suitable.
Sources
Primary research and reference material used for this desk-research article.
Where this fits
This article is part of SurgePV's Solar Business & Operations hub, which works through the topic from first principles to the decisions a project team actually has to make.
