JinkoSolar: How TOPCon Technology Translates into Comparable Product Value for Customers

01 Facts & context

The gap between technology labels and customer tasks

In its annual report for the year 2025, JinkoSolar emphasized technology-driven and value-oriented approaches, developing PV products for centralized and distributed scenarios, and expanding its energy storage business. Taking module procurement as an example, customers face not only technology routes but also site conditions, installation constraints, system design, and project economics. Therefore, a technology brand needs to translate professional differences into selection reasons that customers can compare. JinkoSolar builds recognition with TOPCon technology and the Tiger Neo product series, while explaining product value through different application scenarios. The technology name provides a memory cue, while scenario descriptions help purchasers judge whether it fits their own projects.

However, technology labels themselves do not automatically solve customers' selection problems. When purchasing PV modules, customers typically need to evaluate the power generation performance, durability, maintenance costs, and payback period of modules in specific rooftop or ground-mounted power plants. These evaluations involve numerous variables such as solar irradiance, temperature coefficient, bifaciality, and degradation rate. If a company only promotes the technology name, customers find it difficult to relate it to their own conditions. JinkoSolar's approach is to embed technical parameters into scenarios, for example, the Tiger Neo 3.0 discusses bifaciality and low-light performance separately for rooftop and ground-mounted plants. This essentially translates technical language into the customer's task language, enabling customers to conduct preliminary screening based on their own project conditions. However, whether the translation is accurate and covers all key customer concerns still requires specific examination.

02 GSP analysis

How scenario-based documentation addresses customers' real selection contradictions

GSP analysis suggests that JinkoSolar's Tiger Neo 3.0 product documentation may aim to address the core contradiction customers face during selection: technical parameters are numerous and interrelated, but customers lack a unified comparison framework. The application scenarios for rooftop and ground-mounted plants differ significantly. Rooftop projects may focus more on module dimensions, weight, and low-light performance because rooftop space is limited and orientation is complex; ground-mounted plants may focus more on bifaciality, temperature coefficient, and long-term degradation because projects are large and sensitive to levelized cost of electricity. By distinguishing scenarios, JinkoSolar provides customers with comparison dimensions, enabling them to focus on the most relevant indicators for their own projects.

The value of this approach lies in potentially reducing customers' cognitive burden. When customers face dozens of module models, if the documentation clearly shows which models are suitable for rooftops and which for ground-mounted plants, customers can quickly narrow down their options. Additionally, the documentation emphasizes quantifiable indicators such as bifaciality and low-light performance, providing an objective basis for comparison rather than relying on salespeople's verbal promises. However, the existence of documentation does not guarantee correct usage. Customers may still need technical consultants to interpret parameters or additional simulation tools to estimate power generation. Therefore, the actual utility of scenario-based documentation depends on customers' expertise and decision-making processes.

For companies seeking to learn from this, the key is not to imitate JinkoSolar's product series naming, but to understand the underlying logic: bind technical features to customer tasks and provide verifiable comparison dimensions. Companies need to identify in which scenarios their products have differentiated advantages and ensure that the parameters in the documentation truly reflect these advantages. Otherwise, scenario-based documentation may become mere marketing rhetoric, damaging customer trust.

03 GSP analysis

The specific stages where value is created: from parameters to project judgment

GSP analysis suggests that JinkoSolar's scenario-based product documentation may create value in the early stages of the customer selection process. When customers first encounter product information, the scenario classification in the documentation helps them quickly locate product series that match their project type. For example, a rooftop project owner may directly view the rooftop application section and ignore detailed parameters for ground-mounted plants. This screening process saves customers time and reduces information overload.

Furthermore, the indicators discussed in the documentation, such as bifaciality and low-light performance, provide customers with a basis for evaluating the power generation potential of modules in specific environments. Customers can estimate potential generation gains by combining local irradiance conditions, installation angles, and albedo. Although this estimation is rough, it is sufficient for customers to conduct preliminary ranking among different products. Subsequently, customers may contact sales for detailed datasheets or use professional software for simulation. Therefore, the value of the documentation lies in initiating customers' rational evaluation process, rather than directly providing final answers.

However, the transformation from parameters to project judgment does not occur automatically. Customers need to understand the meaning of each parameter and its impact on power generation. For example, modules with high bifaciality may gain significantly on high-albedo ground, but limited gains in rooftop scenarios. If customers lack this understanding, they may misuse parameters. Therefore, the documentation should not only list parameters but also explain their applicable conditions. Whether JinkoSolar's documentation achieves this is not detailed in the original text, but it is crucial for scenario-based documentation to truly support customer decisions.

04 GSP analysis

The flow of information and responsibility among customers, sales, and technical teams

Product documentation may facilitate information transfer, connecting customers, sales teams, and technical teams. Customers initially learn about products through documentation, sales teams use the documentation for communication, and technical teams provide detailed data and support. A specific handoff point occurs when customers transition from public documentation to sales consultation. At this point, customers may bring questions about specific models, such as 'How does this module perform under low-light conditions?' Sales teams need to answer based on the information in the documentation and may refer to technical teams for more precise data.

The smoothness of this handoff depends on the consistency between the documentation and sales messaging. If the documentation emphasizes bifaciality advantages, but sales teams cannot explain its practical impact in different scenarios, customers may become confused. Therefore, JinkoSolar needs to ensure that sales teams fully understand the documentation content and can translate parameters into customer value. Additionally, technical teams need to update the documentation promptly to reflect product improvements or new data. If this information flow mechanism operates well, it can enhance customer trust in the brand; conversely, it may cause information gaps, leading to customer attrition.

For companies seeking to learn, creating scenario-based documentation is only the first step; more important is designing information maintenance and personnel training processes. Companies should clarify who is responsible for updating documentation, who explains parameters, and who handles customer feedback. Unclear responsibilities may lead to outdated documentation or inconsistencies between sales messaging and documentation, weakening credibility. Therefore, scenario-based documentation should be viewed as a dynamic system, not a static document.

05 GSP analysis

Investment and opportunity costs: economic considerations of scenario-based documentation

GSP analysis suggests that creating scenario-based product documentation requires resource investment, and its economic viability needs to be assessed from three perspectives: investment, opportunity cost, and alternatives. Producing high-quality documentation requires time, manpower, and capital, including product testing, data collection, copywriting, and graphic design. These resources could have been used for other marketing activities such as advertising, trade shows, or customer events. Therefore, companies need to weigh whether scenario-based documentation is more effective in promoting sales than traditional brochures or technical white papers.

The potential benefit of scenario-based documentation is that it may improve the quality of sales leads. When customers conduct preliminary screening based on documentation, the sales team may encounter customers who have a clearer understanding of their needs, thereby shortening the sales cycle. Additionally, documentation may reduce the time sales teams spend repeating basic parameters, allowing them to focus on complex technical issues. However, these benefits are difficult to quantify and may vary by industry and customer segment. For technically complex products, customers may rely more on salespeople's professional advice than self-service documentation.

Alternatives include developing online selection tools, providing customized consulting services, or hosting technical seminars. These approaches may address customer problems more directly but at higher costs. JinkoSolar's choice of scenario-based documentation may be a way to balance cost and coverage. For companies seeking to learn, the key is to assess which stages of the customer decision-making process require the most information support and whether documentation can effectively replace or supplement other sales activities. If customer decisions primarily rely on relationships or price, the value of scenario-based documentation may be limited.

06 GSP analysis

Alternative explanations: documentation effects may stem from other factors

JinkoSolar's Tiger Neo 3.0 product documentation might be interpreted as an effective sales tool, but GSP analysis suggests that multiple alternative explanations exist. First, the effect of the documentation may stem from the brand awareness of JinkoSolar itself, rather than the content. Customers may choose JinkoSolar products because they trust the brand, and the documentation merely serves as a supplementary confirmation. Second, the effect may stem from the product's performance advantages, not the scenario-based expression. If Tiger Neo 3.0 modules indeed lead in indicators such as bifaciality, customers may choose based on parameters alone, and the scenario-based description is just a bonus.

Another alternative explanation is that the effect may stem from industry trends. The PV industry is transitioning from P-type to N-type technology, and customers may already prefer TOPCon products; the documentation merely aligns with this trend. Additionally, the effect may stem from the push of sales channels, not customers' active reading. Salespeople may use the documentation as a communication tool, but their persuasiveness comes from sales skills, not the content.

These alternative explanations remind us that we cannot simply attribute customer choices to scenario-based documentation. To distinguish the true contribution of the documentation, it is necessary to compare customer behavior with and without the documentation, or control for factors such as brand and product performance. However, JinkoSolar has not provided such data, so we can only view the documentation as a potential influencing factor, not a decisive one. For companies seeking to learn, understanding these alternative explanations helps design more rigorous evaluation methods and avoid overestimating the role of documentation.

07 Suggested actions

Application for adopters: how a hypothetical module company can validate scenario-based documentation

Suppose a module company wants to learn from JinkoSolar's approach. It can design a specific application scenario: for distributed rooftop customers, create a scenario-based selection guide that links product parameters to rooftop types (e.g., flat, sloped), orientation, and shading conditions. The validation sequence can be divided into three steps. First, select two similar customer groups in the target market; provide one group with the scenario-based guide and the other with a traditional product catalog, and observe the types and depth of questions raised during consultations. Second, track the conversion rate and cycle time from consultation to order for both groups, and compare whether there are significant differences. Finally, after project installation, collect customer feedback on product performance to assess whether the parameters emphasized in the documentation align with actual performance.

This validation requires controlling other variables such as sales team capability, price, and delivery time. Companies can randomly assign customer groups and ensure that the two groups are similar in project scale and geographic location. The observation period may need a quarter or half a year to accumulate sufficient samples. If the scenario-based guide indeed improves consultation quality or conversion rate, it indicates effectiveness; if the effect is not obvious, adjustments may be needed, or it may be combined with other sales tools.

It is important to note that validation results may be affected by market conditions. For example, during changes in PV subsidy policies, customers may focus more on price than technical parameters, potentially masking the effect of scenario-based documentation. Therefore, companies should test during relatively stable market periods and record external environmental changes for consideration in the analysis.

08 Suggested actions

Organizational division and capability building: maintaining a scenario-based documentation system

For companies seeking to learn, establishing a scenario-based documentation system requires clear organizational division. The product management department should be responsible for defining product application scenarios and key parameters, ensuring technical accuracy; the marketing department is responsible for designing the documentation structure and visual presentation to make it easy to understand; the sales department uses the documentation to communicate with customers and provides feedback on customer questions; the technical support department provides in-depth data support and updates the documentation to reflect product improvements. Each department needs to designate a responsible person and hold regular cross-departmental meetings to ensure information synchronization.

Regarding decision-making authority, the product management department should have the authority to decide which parameters can be disclosed and which need to be kept confidential; the marketing department should have the authority to adjust the expression of the documentation, subject to technical review; the sales department should have the authority to propose modifications based on customer feedback, but the final version must be confirmed by product management. Exception handling processes include: when customers question the content of the documentation, sales should record and forward to the technical department for verification; when product parameters change, product management should notify the marketing department to update promptly and ensure all channels use the latest version.

In terms of capability building, companies should train sales teams to understand technical parameters and their application scenarios, enabling them to answer basic customer questions; train technical support teams to master the documentation update process to ensure data accuracy; train marketing teams to understand product technology so they can design content that is both professional and easy to understand. Additionally, companies can establish a feedback mechanism for documentation usage, collecting opinions from customers and sales to continuously optimize the documentation. These measures help transform scenario-based documentation from a one-time project into a sustainable marketing asset.

09 Suggested actions

Measurement and boundaries: how to evaluate the true impact of scenario-based documentation

When evaluating the impact of scenario-based documentation, choosing the appropriate denominator and observation period is crucial. The denominator can be documentation downloads, page views, or number of consulting customers, but different denominators reflect different levels of effect. For example, downloads reflect the attractiveness of the documentation, consultations reflect customer willingness to act, and orders reflect the ultimate business outcome. Companies should select primary indicators based on their goals and distinguish between leading indicators (e.g., consultation volume) and outcome indicators (e.g., order volume). The observation period should be long enough to cover the complete decision cycle from customer contact to purchase; PV module procurement may take several months, so it is recommended to observe for at least one quarter.

Leading indicators may include the proportion of customer consultations that mention specific parameters, the number of times customers request detailed datasheets, and sales team feedback on customer understanding of the documentation. Outcome indicators include order conversion rate, average order size, and customer satisfaction. Companies should track these indicators simultaneously to determine whether the documentation promotes initial interest or drives final decisions. Expansion conditions: if testing shows that the documentation significantly improves conversion rates and costs are controllable, companies can expand it to more product lines and markets. Pause conditions: if the documentation leads to customer misunderstandings or sales team complaints, it should be paused and revised. Adjustment conditions: based on customer feedback and sales data, continuously optimize scenario classification and parameter explanations.

Applicability boundaries: scenario-based documentation may be more effective for industries with complex technology and rational customer decision-making, such as industrial goods and energy equipment. For fast-moving consumer goods or brands where customer decisions rely on emotion, it may not be applicable. Additionally, the effectiveness of documentation is influenced by market maturity; in markets with insufficient customer education, more pre-sales support may be needed. Therefore, companies should carefully promote such practices based on their industry characteristics, avoiding blind imitation.