Written by Informic Engineering Team. Technical claims require documented source review before publication.
When a procurement team sends us a bill of materials for an IoT product, the first question is rarely about price. It is about clarity. We need to know what you actually want to build, how you plan to sell it, and where you expect to face delays. That information shapes our quotation more than any component price list.
Our job in a PCBA factory is to turn a parts list into a production plan. For IoT hardware, that plan is often messy. You might have 40 line items from three different distributors, a custom antenna that needs a special assembly step, and a microcontroller that has a 20-week lead time. We see this daily. This article explains how we make purchasing clearer for your team, what to send us in an RFQ, and how we consolidate your BOM to reduce risk.
What we need from you in the first RFQ
We are not looking for a perfect document. We are looking for a complete one. A good RFQ for IoT hardware production should answer five operating questions:
Technical reference: For related engineering context, see IPC standards and industry resources.
- What is the target annual volume? Not the forecast from a slide deck, but the number you actually plan to order in the next 12 months.
- Which components are already sourced or approved? If you have a preferred distributor, tell us. If a part is already in stock at your warehouse, say so.
- What is the board revision? We need the current version, not the one from last year.
- Are there any approved alternate parts? This helps us avoid a dead stop when a capacitor goes end-of-life.
- What is the delivery target? A date, not a quarter.
Send us the BOM in Excel or CSV. A PDF is fine for review, but we cannot consolidate a PDF into our purchasing system without rekeying data, which invites errors. If you have a schematic or a layout file, include it. We do not need the full design files for a quotation, but we do need to see the board outline and the connector positions to estimate assembly time.
How we read your BOM for IoT risk
An IoT BOM has a distinct shape. It usually contains a wireless module or a system-on-chip, sensors, a battery management circuit, and a power supply. The risk is not in the main IC. It is in the passive components around it. A 0402 resistor is a 0402 resistor, but a specific value from a single manufacturer with a long lead time can stall your entire line.
When we review your BOM, we look for three things:
- Single-sourced parts, especially for memory, wireless modules, and voltage regulators.
- Parts with long lead times that are not yet on order.
- Components that require special handling, such as moisture-sensitive packages or fine-pitch connectors.
We then check our own inventory and our distributor networks. We do not promise stock we cannot see. We tell you what we have, what we can get in two weeks, and what will take ten weeks. That is the core of BOM consolidation.
BOM consolidation: one purchase order instead of five
Most IoT hardware teams start by buying components themselves. They order the microcontroller from one distributor, the sensors from another, and the PCB from a fab. Then they ship everything to an assembly house. This works for a prototype, but it fails at scale. You pay for freight multiple times, you manage multiple invoices, and you carry the risk of a missing part.
We consolidate your BOM into a single purchase order. That means we source all the components, buy the bare pcbManufacturing service, and assemble the board in one flow. You receive one shipment and one invoice. For a production run of 1,000 units, this usually saves more in logistics and administration than in component price.
Consolidation also gives us visibility. When we buy all the parts, we can see a shortage coming. If a specific capacitor is delayed, we can swap to an approved alternate before your line stops. We cannot do that when you hold the inventory.
A practical example of BOM structure
Here is a simplified view of how we categorize an IoT BOM for sourcing. This is not a real product, but it shows the logic we use.
| Category | Example parts | Sourcing strategy |
|---|---|---|
| Core logic | MCU, wireless module, memory | Order early, confirm lead time, consider alternates |
| Power | Battery connector, PMIC, LDO | Check stock, verify voltage tolerance |
| Passives | Resistors, capacitors, inductors | Consolidate by value, use standard sizes |
| Interface | USB connector, antenna, SIM holder | Confirm mechanical fit with enclosure |
| Special | Sensor, crystal oscillator, ESD protection | Verify calibration, check moisture sensitivity |
When you send us a BOM, we map every line to one of these categories. Then we tell you which parts need your approval before we buy. This is not a delay. It is a control point.
DFM feedback before you commit to a quote
A quotation is only useful if the board can actually be built. That is why we run a design for manufacturability review on every IoT BOM we quote. We do this before we send a final price, not after you place an order.
Our DFM check covers the basics: pad sizes, solder mask openings, component spacing, and thermal relief. For IoT boards, we pay extra attention to the antenna area. If your PCB layout has copper under the antenna, the wireless range will suffer. We will flag that in the review, and we will suggest a fix.
We also check for testability. IoT boards often need firmware programming and RF testing after assembly. We need test points on the board. If you do not have them, we can add them, but that changes the board cost. We tell you this before you commit.
What to expect in a quotation from us
Our pcba quotation is a single document with three sections:
- Component cost, broken down by line item. You can see what we pay and what our margin is.
- Assembly cost, based on the number of components and the board complexity.
- Lead time, with a clear date for when the first batch ships.
We do not hide fees in the unit price. If there is a setup charge for stencil or programming, it is listed separately. If freight is extra, you will see it. This transparency is why procurement teams in the Middle East work with us repeatedly. You know what you are paying for.
How we handle the Middle East market specifically
We are based for the Middle East, and we understand the logistics of this region. Shipping components from Shenzhen to Dubai is different from shipping to Berlin. Customs clearance, temperature control, and humidity levels matter. We handle that on our side, so you do not have to.
For IoT hardware, we often see projects that must operate in extreme heat. That affects component selection. An electrolyte capacitor rated for 85 degrees Celsius will fail in a junction box in Riyadh. We will recommend a higher temperature rating, even if it costs a little more. This is not a sales tactic. It is a reliability requirement.
We also know that payment terms in this region vary. We work with letters of credit, bank transfers, and trade credit. We will discuss terms during the RFQ stage, not after you have approved a quote.
Practical steps to get a faster, more accurate quote
If you want a clear quotation from us, follow this sequence:
- Send the BOM in Excel format. Include manufacturer part numbers, quantities, and any reference designators.
- Add your target delivery date and annual volume. We will adjust our sourcing plan accordingly.
- Upload the PCB layout files if available. We use them for the DFM check.
- List any approved alternates. This gives us flexibility.
- Ask questions. If you are unsure about a component lead time, ask us to check before you send the full RFQ.
We respond to complete RFQs within two business days. If we are missing information, we will tell you exactly what we need, not send a generic reply.
When to contact us directly
If you have a BOM but no layout yet, contact us anyway. We can review the component list and flag long lead time parts before you finish the design. That is the best time to fix a sourcing problem. Once the layout is done, changing a component is more expensive.
If you are still selecting components for a new IoT product, we can help you choose parts that are in stock and have multiple sources. This is a free service. We do it because it makes our production job easier later.
When you are ready, use our quote page to send us the BOM. We will reply with a clear, itemized quotation and a delivery date we can defend.
FAQ: IoT hardware production and sourcing
What is the difference between a PCBA quote and a BOM quote?
A BOM quote is just the cost of the components. A PCBA quote includes the bare board, assembly labor, testing, and any setup charges. We always provide both separately. That way you can compare our component pricing against your existing distributor pricing, and you can see the true cost of assembly.
Can you source components we already have in stock?
Yes. If you have parts in your warehouse, you can consign them to us. We will use your components for assembly and only source the missing parts. This reduces your cash outlay and avoids double buying. The quotation will show a credit for the consigned parts, so you know the net cost.
How do you handle long lead time components for IoT boards?
We identify long lead time parts during the DFM review. We then give you two options: buy them now and store them, or let us order them on your behalf with a deposit. We do not wait until the full BOM is ready. If a microcontroller has a 20-week lead time, we order it in week one, not week ten.
FAQ
What do we review first for iot hardware production?
We begin with the functional requirement, the current revision-controlled data package, critical components, expected volume, quality requirements, and delivery deadline.
How do we make purchasing risk easier to compare?
We compare date code, traceability, lead time, MOQ, substitute status, quality checks, and the supplier assumptions behind each quotation instead of comparing only a unit price.
What do we need for an accurate quotation?
We need the correct document revision and, where relevant, the BOM, Gerber or ODB++ files, centroid data, target quantity, application, test expectation, quality requirement, and requested delivery date.