B2B project purchasing
Large chargers, BESS, microgrids, and distributor purchasing use RFQ, quote, PI, deposit, final payment, logistics, and after-sales states.
RFQ intake
Dynamic project questionnaire and source attribution.
Quote + PI
File-based quote approval and PI state tracking.
Distributor path
Partner pricing, resources, and account roles.
Compliance
Certifications, export checks, GDPR, and audit logs.
Purchasing route
B2B project purchasing and how each step works
Project buyers follow one published route from requirement to delivery. This page describes each step and what the site publishes at that step.
Project request intake
A project request starts with the site conditions, the required power, the connector standard and the target market. The request then maps to a published architecture. Published architectures include split DC systems from 240kW to 1600kW and a 1.2-3.2MW split system.
Quote and proforma invoice
The quote is issued against the requirement file, and the proforma invoice records the commercial terms. Status is visible in the account route, from a submitted request to delivery. The same record keeps the model and the market attached to the order.
Distributor route
Distributor enquiries use a separate route with partner pricing and account roles. The published product records stay identical on both routes, so specifications and datasheets do not change with the sales channel.
Compliance and export screening
Certificates and export screening are confirmed per project and per market. This site publishes no general certification list. No page here replaces a market certificate, a test report or an import approval.
Purchase routes and project systems
Standard modules use a project inquiry route. Project systems use the project request route.
Common questions
What should a project request contain?
Include the site conditions, the required power, the connector standard, the target market and the delivery plan. Add the documents needed for project qualification. These fields map the request to a published architecture and model.
Do project systems use a different route on this site?
Yes. Project systems use the project request route. Standard modules use the project inquiry route.
Does this site publish a certification list?
No. Certificates and export screening are confirmed per project and per market. Request the model-specific certificate and test report that apply to your market.
How does the distributor route differ from direct purchasing?
The distributor route uses partner pricing and account roles. The published product records, specifications and documentation stay the same on both routes.
How is request status tracked?
The account route shows the published status steps, from a submitted request through quotation, proforma invoice and delivery. The record keeps the model and the target market attached.