Most stalled charger quotations are not missing a request for a price. They are missing a bid package. A logo file and an “up to 65 W” headline leave a factory to invent ports, PDOs, packaging and document ownership, and two factories will invent them differently. A charger OEM RFQ that a factory can quote without guesswork is a complete bid package, not a price enquiry.

This page is a process path for sourcing and product managers who need comparable OEM or ODM responses. It is a bid-package RFQ, not a reprint of a specification-sheet explainer. For program context, see charger OEM, ODM and wholesale.

The RFQ fields a factory cannot honestly quote without

A factory cannot honestly quote a charger OEM RFQ without a frozen electrical and protocol table, a mechanical and packaging pack, a certification and document-ownership list, and clear questions on tooling, samples, payment and forecast bands. Without those fields, the unit price is a guess, and two responses cannot be compared on the same BOM.

Those four blocks should be on the first page of the RFQ, with a revision letter and a date. A request that only names a wattage, a colour and a target price invites the factory to fill every other line in its own favour. The sections below are the fields that stop that happening, written so a factory can answer rather than interpret.

RFQ blockWhat the factory must be able to answerWhat a missing field usually becomes
Electrical and protocolPorts, PDOs, PPS, single- and multi-port mapsAn “up to X W” headline with no split
Mechanical and packagingDrawings, colour, logo, carton and inlaysA later artwork charge, or a housing that was never agreed
Certification and ownershipMarkets, standard editions, who holds the reportsA factory file that the brand cannot use
Commercial conditionsTooling, NRE, samples, payment, forecast bandsA unit price that hides unpaid steel and tests

Electrical and protocol tables: ports, PDOs, PPS, and what “up to X W” is not

“Up to X W” is a headline, not a table. The RFQ should name each port, the Power Data Objects that port must advertise, whether Programmable Power Supply is required and in which voltage range, and the allocation map when two or more ports are loaded together. A 100 W brick that delivers 100 W on one port and collapses under two laptops is a different product from a brick that holds a published split. The factory cannot quote those two products as if they were one.

The table should also say which additional protocols, if any, must remain available, and which firmware revision will be frozen for the quotation samples. USB Power Delivery behaviour should be written against the current USB-IF Compliance Program and the published USB-IF documents the program intends to follow, not against a marketing name. For protocol language a team already maintains, see USB-C PD and PPS only as a hub; the RFQ itself still has to carry the numbers for this SKU. For platform context, GaN charger manufacturing and sourcing sits beside the electrical sheet, not in place of it.

Mechanical, color, logo and packaging attachments that belong with the RFQ, not after

Artwork and packaging are cost and lead-time items. They belong in the RFQ, not in an email after the unit price is agreed. Attach a mechanical drawing or an approved 3D file, a colour reference, logo placement and finish, and a packaging specification: inner carton, outer carton, inlay, labels and any in-box literature. A factory that quotes without those attachments is quoting a housing and a box it has not yet seen.

White 100W GaN wall charger with a European two-pin plug, showing a plain housing face printed 100W GaN+
A housing colour, a logo face and a plug variant are RFQ attachments, not afterthoughts once a unit price exists. Photograph from the WEP-100-C product page.

Certification, target markets and document ownership, stated as line items

Each target market should be a line item: the safety standard edition, any national registration, USB-IF work if a logo will be used, and any energy or EMC filing. For a Union market, name the applicable instrument, such as the EU common charger rules in Directive (EU) 2022/2380, as a line, not as a slogan. For energy-efficiency filings, name the applicable external power supply rule the program must meet, again as a line the factory can price. The RFQ should say who applies, who pays, and who owns the reports and listings if the program moves. A CB report is useful planning evidence for a multi-market safety file; it is not, on its own, a national mark. For the document path, see charger compliance and certification. Do not attach unverified certificates as if they already existed for the SKU being quoted.

Tooling, NRE, samples and payment — asked in a way a factory can answer

Ask for tooling and NRE as separate figures, with a statement of what the steel and the fixtures cover, who owns them, and how they are amortised if at all. Ask how many quotation samples are included, what a further sample costs, and on which revision they will be built. Ask for payment terms as a schedule the factory can accept or redline, not as a slogan. This page does not publish sample prices, NRE figures or payment norms. The RFQ should leave a blank the factory fills, so two responses can be compared on the same questions.

Forecast and MOQ bands, without treating a site claim as a negotiated fact

Give a forecast band the factory can plan against, and ask for price breaks at quantities the buyer is actually prepared to discuss. A quantity that appears on a website, including a starting-order claim, is a site statement until it is negotiated in the response. Do not copy such a figure into the RFQ as if it were already the contract minimum. The honest field is a set of bands and a first-order quantity the buyer can defend, with a note that each factory should state its own minimum and its own break points.

How to compare two RFQ responses on the same BOM, not on unit price alone

Two responses are comparable only if they answer the same electrical table, the same attachments and the same certification list. Line up the BOM assumptions, the tests included in the unit price, the tooling and NRE, the sample terms, and the document ownership. A lower unit price that omits a burn-in, a hipot, a cable or a national filing is not cheaper until those lines are added back. A charger-supplier due-diligence checklist can carry the rest of the commercial file once the quotations sit on the same sheet.

Redlines a buyer should refuse: missing firmware freezes, missing test lists

Refuse a response that does not freeze the firmware and the hardware revision of the quoted samples, or that has no test list for incoming, production and outgoing gates. Refuse a protocol table that only repeats “up to X W.” Refuse a certification line that names a market without a standard edition and an owner. Those redlines are not hostility. They are the conditions under which a factory can still be a candidate, after it has completed the missing fields.

Plain brown corrugated shipping carton shown from several angles, used as a packaging specification example
Packaging dimensions and materials belong in the RFQ with the housing, because they move freight and unit cost. Photograph from the WEP-100-C product page.

A one-page RFQ cover sheet that keeps revisions traceable

A one-page cover sheet should carry the RFQ number, the revision letter, the date, the SKU name, the buyer’s contact, and a short list of attachments with file names. Every later change to a PDO, a colour or a market should issue a new revision, not a silent mark-up in a chat. The factory’s response should cite the same revision. That is how a program later explains which quotation belongs to which drawing.

What not to put in an RFQ: invented prices, unverified certificates, vague “world-class” QC

Do not put a target unit price invented from a retail listing, a certificate that has not been seen, or a quality slogan with no test list. Do not ask the factory to “meet all international standards” without naming them. Those lines waste both sides’ time and make two responses incomparable. The RFQ should ask for evidence, not for adjectives. Document review after the quotation can follow the supplier document-and-sample evaluation page.

Conclusion

A factory can quote a charger honestly when the RFQ is a bid package: electrical and protocol tables, mechanical and packaging attachments, certification ownership, and commercial questions that can be answered in figures and revisions. Unit price is the last line on that sheet, not the first. Leave invented prices and unverified certificates out of the request.

If your team is preparing a charger OEM RFQ and wants to discuss a bid package for a specific SKU, you can send the intended scope through the charger OEM, ODM and wholesale page. This is a request for a project discussion.

FAQ

What should a charger OEM RFQ include besides a logo file?

A factory needs a frozen electrical and protocol table, mechanical and packaging attachments, a certification and document-ownership list, and commercial questions on tooling, NRE, samples, payment and forecast bands. A logo and a wattage headline leave those fields open, so two factories will quote two different products. Put a revision letter and a date on a one-page cover sheet, and attach drawings and packaging files with the RFQ, not after a unit price is agreed. Leave invented prices and unverified certificates out of the request.

Why is “up to X W” not enough for a factory to quote a charger?

“Up to X W” does not state which port delivers that power, which Power Data Objects it advertises, whether Programmable Power Supply is required, or what happens when two ports are loaded together. A brick that holds 100 W on one port and collapses under two devices is a different product from a brick with a published split. The RFQ should carry a port-by-port table and a multi-port map so two responses can be compared on the same BOM, not on a headline wattage.

How should forecast and MOQ appear in a charger OEM RFQ?

Give a forecast band the factory can plan against, and ask for price breaks at quantities the buyer is prepared to discuss. A starting quantity that appears on a website is a site statement until it is negotiated in the response; do not copy it into the RFQ as if it were already the contract minimum. Ask each factory to state its own minimum and its own break points against the same bands, so the comparison is on disclosed terms rather than on an assumed figure.

What redlines should a buyer refuse in an RFQ response?

Refuse a response that does not freeze the firmware and hardware revision of the quoted samples, that has no test list for incoming, production and outgoing gates, or that repeats only “up to X W” instead of a protocol table. Refuse a certification line that names a market without a standard edition and an owner of the reports. Those redlines give the factory a chance to complete the missing fields; they are the conditions under which a quotation can still be a candidate.

{
“@context”: “https://schema.org”,
“@type”: “FAQPage”,
“mainEntity”: [
{
“@type”: “Question”,
“name”: “What should a charger OEM RFQ include besides a logo file?”,
“acceptedAnswer”: {
“@type”: “Answer”,
“text”: “A factory needs a frozen electrical and protocol table, mechanical and packaging attachments, a certification and document-ownership list, and commercial questions on tooling, NRE, samples, payment and forecast bands. A logo and a wattage headline leave those fields open, so two factories will quote two different products. Put a revision letter and a date on a one-page cover sheet, and attach drawings and packaging files with the RFQ, not after a unit price is agreed. Leave invented prices and unverified certificates out of the request.”
}
},
{
“@type”: “Question”,
“name”: “Why is “up to X W” not enough for a factory to quote a charger?”,
“acceptedAnswer”: {
“@type”: “Answer”,
“text”: ““Up to X W” does not state which port delivers that power, which Power Data Objects it advertises, whether Programmable Power Supply is required, or what happens when two ports are loaded together. A brick that holds 100 W on one port and collapses under two devices is a different product from a brick with a published split. The RFQ should carry a port-by-port table and a multi-port map so two responses can be compared on the same BOM, not on a headline wattage.”
}
},
{
“@type”: “Question”,
“name”: “How should forecast and MOQ appear in a charger OEM RFQ?”,
“acceptedAnswer”: {
“@type”: “Answer”,
“text”: “Give a forecast band the factory can plan against, and ask for price breaks at quantities the buyer is prepared to discuss. A starting quantity that appears on a website is a site statement until it is negotiated in the response; do not copy it into the RFQ as if it were already the contract minimum. Ask each factory to state its own minimum and its own break points against the same bands, so the comparison is on disclosed terms rather than on an assumed figure.”
}
},
{
“@type”: “Question”,
“name”: “What redlines should a buyer refuse in an RFQ response?”,
“acceptedAnswer”: {
“@type”: “Answer”,
“text”: “Refuse a response that does not freeze the firmware and hardware revision of the quoted samples, that has no test list for incoming, production and outgoing gates, or that repeats only “up to X W” instead of a protocol table. Refuse a certification line that names a market without a standard edition and an owner of the reports. Those redlines give the factory a chance to complete the missing fields; they are the conditions under which a quotation can still be a candidate.”
}
}
]
}

Related Posts