A useful BOM RFQ template gives each supplier the same item revision, drawing, quantity, required date and acceptance scope. Keep that request separate from the supplier's price, tooling, minimum order quantity, lead time and assumptions. A comparable quotation needs an identifiable scope and explicit exceptions before a buyer can assess its commercial terms.
The CSV below contains two clearly marked, removable fictional harness lines for R-01. All example values and identifiers are fictional, and all supplier-response columns are blank. Delete the example lines to use the header for your own request. Download the BOM RFQ CSV.
Establish the requested release before collecting prices
R-01 is the fictional indoor inspection robot from Arc's BOM series. CFG-R01-A and BOM-R01 A select HR-300 A with DW-HR-300 A for robot serials 001–002. ECO-017 approves the strain-relief manufacturing revision B. CFG-R01-B and BOM-R01 B select HR-300 B with DW-HR-300 B for 003–005. Both configurations retain DW-R01 A, ECAD CB-200 A and firmware 1.2.0. The change retains the installation interfaces and acceptance requirements, with no automatic retrofit of earlier serials. Revision and configuration matrix
This request covers complete bought harnesses. It excludes controller programming, whole-robot assembly and other BOM parts. The gross requirement is two A and three B harnesses. A materials owner must reconcile accepted stock, open orders and any additional samples before converting that requirement into a real order quantity. Robotics BOM purchasing quantities
The RFQ identifiers and need-by date introduced here are fictional. RFQ-R01-HR, issue Q01 requests delivery by 2027-01-15 for this worked example. That date illustrates a planning field and makes no claim about supplier capacity or shipment timing.
Inspect the two filled request lines
Each row needs its own revision and effectivity. The shared item number HR-300 cannot carry the whole requirement once the pilot selects two revisions.
| line_id | release_id | configuration_id | item_id | item_revision | drawing_id | drawing_revision | effectivity_value | requested_quantity | unit |
|---|---|---|---|---|---|---|---|---|---|
| 001 | BOM-R01 A | CFG-R01-A | HR-300 | A | DW-HR-300 | A | 001-002 | 2 | ea |
| 002 | BOM-R01 B | CFG-R01-B | HR-300 | B | DW-HR-300 | B | 003-005 | 3 | ea |
Both CSV rows use example_status of Fictional removable example, rfq_id of RFQ-R01-HR, rfq_issue of Q01 and description of Complete robot harness. Their effectivity_basis is Robot serial, their need_by is 2027-01-15 and their requested quote_currency is USD.
| line_id | acceptance_scope | exception_scope |
|---|---|---|
| 001 | Complete harness to DW-HR-300 A, including drawing-defined inspection and identification | No substitution authorised. List every exception for engineering review. |
| 002 | Complete harness to DW-HR-300 B, including drawing-defined inspection and identification | No substitution authorised. List every exception for engineering review. |
The request totals 2 + 3 = 5 harnesses. It contains no supplier MOQ, availability or price. A supplier offering five B harnesses changes the requested revision scope even if its total quantity is five. Keep that response identifiable for engineering disposition.
Fill the buyer fields and preserve their meaning
The template has 29 columns. Its request fields define the comparison basis. Its response fields capture what the supplier actually offers. Keep one row per independently quoteable item, revision and scope. Add rows where a different drawing, acceptance package or required date changes that scope.
| Request fields | What the buyer controls |
|---|---|
example_status |
Clear the fictional marker when replacing the examples with a real request. |
rfq_id, rfq_issue, line_id |
Identify the request, its issued scope and the line used in correspondence. Preserve prior issues when scope changes. |
release_id, configuration_id |
Identify the selected BOM release and product configuration from which the quantity and revision came. |
item_id, item_revision, description |
State the internal item and exact revision to quote. Add manufacturer and orderable part numbers for catalog parts where those are the controlling identity. |
drawing_id, drawing_revision |
Identify the controlled drawing supplied with the request. Check that the attachment resolves to that revision. |
effectivity_basis, effectivity_value |
Explain which serials, lots or variants use the quoted line. The example uses robot serial ranges. |
unit, requested_quantity |
Define numeric demand and its unit. Supplier MOQ and quoted prices use that same unit unless an explicit conversion is recorded. |
need_by, quote_currency |
State the requested delivery date and comparison currency. Record the delivery destination and shipping basis in the accompanying request. |
acceptance_scope, exception_scope |
Identify the required inspection, identification and other controlled deliverables, plus the rule for proposed exceptions. |
The acceptance field points to the drawing-defined scope. It does not replace the complete controlled drawing or inspection specification. Attach those documents in a real request and resolve missing criteria before treating quotations as equivalent.
Supplier formats vary. East West Manufacturing's RFQ checklist asks for part and revision information, quantities, drawings, testing requirements, tooling information and packaging details. Those are supplier-specific inputs. Use them to check the requested scope and ask your selected supplier which format and documents it requires. The checklist does not require this CSV or establish that R-01 needs every certification it lists. East West Manufacturing RFQ checklist
Read supplier terms without changing the request
Leave all ten supplier_ columns blank until an identifiable response arrives. Blank means unanswered or unresolved. Zero is a stated numerical value and needs a supporting response. If something is inapplicable, record that explicitly in the supplier assumptions instead of letting a reader infer it from an empty price.
| Supplier-response fields | What to establish from the response |
|---|---|
supplier_quote_reference, supplier_quote_valid_until |
The quotation identifier and date through which its terms remain offered. |
supplier_moq |
The minimum order quantity in the request's unit, including any revision-specific minimum. |
supplier_currency, supplier_unit_price |
The offered currency and price per requested unit. A currency difference needs an explicit comparison basis. |
supplier_tooling_cost |
The separately offered tooling or setup charge. Record what it covers and tooling ownership in assumptions. |
supplier_lead_time_calendar_days |
The offered duration in calendar days and its starting condition, such as order acceptance, defined in assumptions. |
supplier_available_quantity, supplier_available_date |
The quantity and timing the supplier states it can supply, linked to the quotation and its conditions. |
supplier_assumptions |
Exclusions, packaging, shipping, payment, price-break basis and every proposed technical or commercial exception. |
Ask for quantity breaks as separate identifiable offers when useful. Preserve the requested two-A and three-B comparison first. Buying a larger pack or paying for tooling is a purchasing decision. Accepting a changed material, revision or inspection scope belongs to the authorised engineering review.
Disposition an offer for a different revision
In a fictional response scenario, a supplier states that five HR-300 B harnesses are available for line 002 and leaves A unavailable for line 001. The buyer records supplier_available_quantity of 5 only on the B line, with the supporting quote reference and conditions. Its requested_quantity remains 3. The offered five B harnesses exceed the B requirement and leave the two-A requirement unresolved.
The engineering owner assesses any proposed B use for 001–002 against the complete configuration and affected evidence. The supplier cannot authorise it by pricing it. Until a change or scoped exception is accepted, the buyer preserves line 001's A requirement and seeks an answer for that scope.
If engineering changes the approved requirement, the buyer issues a new RFQ scope and obtains a quotation for it. The retained Q01 and supplier response explain why the comparison changed. They remain distinct from the later purchase order and material acceptance record.
Import and check the CSV before using it
The file uses a header, a consistent field count, CRLF record endings and double-quoted fields. These follow RFC 4180's documented CSV conventions. The file carries no spreadsheet formatting, formulas or cell protection. RFC 4180
Import IDs, revisions, dates and effectivity values with explicit column types. Treat line_id and serial references as text to preserve 001. Quotation marks in a CSV do not force a spreadsheet application to keep a value as text. Treat quantities and prices as numbers only after checking the unit and currency.
- Confirm the file contains the intended RFQ issue and required attachments.
- Check that drawing revision A stays paired with harness A and B with B.
- Reproduce the two-A, three-B, five-total requirement.
- Confirm blank supplier fields have stayed blank during import.
- Have the buyer and engineering owner review the requested scope before any external issue.
BOM RFQ template questions
Can I delete the fictional rows and reuse the CSV?
Yes. Retain the header, delete both marked example rows and add your own controlled request lines. Check the fields required by your chosen supplier and add them where necessary.
Should I combine A and B when the installation interface is unchanged?
Keep them separate while the approved pilot selects different revisions. Their shared interface does not authorise changing the selected revision or its manufacturing documentation.
What does a blank supplier tooling cost mean?
It means no tooling value has been captured. Ask whether tooling is included, separately charged or inapplicable. Record a supplier-stated zero only when the response supports it.
Does an accepted quote release the robot build?
A quote supplies offered terms for its identified scope. Engineering release, purchasing authorisation, receipt acceptance and permission to build remain attributable decisions in the team's process.
Continue the purchasing preparation
Use the robotics BOM template to derive the controlled quantity view. Use the revision and configuration guide to resolve which builds select each revision.
When the request extends beyond supplied parts into assembly, define the responsibilities and deliverables with the robotics assembly outsourcing guide.