embedded world (Nuremberg)

embedded world in Nuremberg is the leading annual fair for embedded systems, IoT, and industrial computing. Like electronica, it is an engineering fair, not a sourcing fair — but the platform decisions you make here determine what you can realistically source from China.

Why it matters for China-sourcing buyers

Industrial IoT products live or die on protocol support and long-term availability. embedded world is where you meet the MCU, gateway, and connectivity vendors whose parts your Chinese ODM will build around. Understanding the reference designs lets you specify a build the factory can actually deliver — Modbus, MQTT, OPC-UA, and wide-temperature operation are easy to ask for and hard to verify without this background.

How we use it

We use it to pressure-test a client’s platform before committing to a Chinese supplier. A gateway spec that looks fine on paper can hide a connectivity module with a 12-month lead time. Seeing the supply situation at the source prevents a sourcing project from stalling on one unobtainable part.

What embedded world is and who should attend

embedded world is an annual, three-day exhibition at NürnbergMesse, usually in early March. It focuses on embedded hardware, IoT connectivity, edge AI, and industrial software, with exhibitors ranging from silicon vendors and module makers to reference-design houses and EMS providers.

Three personas get the most value:

• Industrial IoT engineers and product managers selecting gateways, edge controllers, or sensor networks. You need to know which MCUs, wireless modules, and protocol stacks are real before a Chinese ODM quotes.
• Hardware startups and crowdfunding teams shipping connected devices. Use the fair to pick a platform with second sources, so your first production run does not depend on a single end-of-life chip.
• EU / Japan procurement leads validating long-term supply and certification paths before placing large orders with Chinese manufacturers.

Pure consumer-electronics buyers should skip this show and go to electronica or a China consumer-electronics fair instead.

Electronics-relevant halls and zones

The floor is organized by technology cluster, so route by component category rather than walking every aisle.

• Embedded boards, modules, and systems — MCU vendors, SoM suppliers, and reference-design houses. This zone tells you which chip families are actively supported and which are being phased out.
• IoT and connectivity — wireless modules for BLE, LoRa, Wi-Fi, NB-IoT, LTE-M, and Matter. Compare 3–4 vendors for the same protocol; lead times and MOQs can vary by 6–10 weeks.
• Sensors and measurement — pressure, temperature, gas, current, and motion sensors. Ask for documented accuracy, long-term drift, and whether the sensing element is a named supplier or anonymous grey-market.
• Embedded vision, edge AI, and security — relevant if your hardware runs local inference or authenticated industrial protocols. These booths are more about understanding compute and security assumptions than direct sourcing.

Check the official NürnbergMesse floor plan before you travel; zone names and hall assignments shift between editions.

Engineer-led sourcing strategy at the fair

embedded world is not for signing purchase orders. It is for gathering the technical evidence that makes your later RFQ to a Chinese supplier defensible.

Start by spotting trading booths. A real module maker can show FCC/CE grant letters, protocol conformance reports, and a roadmap. A trader reselling someone else’s module gives vague certification answers and cannot produce original test reports. Ask directly: “Do you design the firmware, or source it from a partner?” and “Can I see the certification file for this exact model?”

Technical questions that matter at the booth:

• What is the published availability roadmap? Anything marked “not recommended for new designs” is a non-starter.
• What is the industrial temperature range, and are the bulk capacitors, crystals, and wireless module certified to the same range? A gateway rated −40°C to +85°C with commercial-grade crystals inside will fail in the field.
• Which protocol stacks are in firmware, and which must the ODM integrate separately? OPC-UA maturity varies widely.
• What are the real MOQ and lead time at 1k, 5k, and 10k units? Show-floor quotes are preliminary, but the range is usually accurate enough to flag problems.

Red flags: vendors who cannot name the chip inside their module, claim “all certifications available” without files, or quote 30% below comparable booths. Capture every answer with booth number and a business-card photo. That note becomes the RFQ spec you send to Shenzhen.

Pre-show prep checklist

A day without preparation is an expensive walk:

• Buyer badge — register online; on-site queues can cost an hour on the first morning.
• Shortlist 15–20 exhibitors from the official list, filtered by MCU family, module type, or protocol, mapped by zone.
• Book 3–5 appointments for critical components. Tier-1 vendors fill up fast.
• Product spec / BOM — include target volumes, markets, and required certifications (CE, FCC, UKCA, PSE, TELEC).
• Certification and environmental requirements — write down temperature range, IP target, EMC class, and required bus protocols.
• Logistics — Nuremberg hotels near the Messe sell out 2–3 months ahead; budget 30–50% above standard rates.

Bring a power bank, a notebook per booth, and a camera for QR codes.

Post-show verification

Booth meetings give you intent, not proof. A friendly application engineer may believe their module works at −40°C, but that does not mean your Chinese ODM’s production units will. The same applies to EMC, protocol conformance, and firmware update cadence.

After the fair, convert your notes into supplier qualification questions and send them to your Chinese shortlist. Then verify on-site. A factory audit checks whether the ODM has the engineering capability, equipment, and certifications to build the platform you selected. A factory tour lets you see the SMT line, review BOM-grade components, and ask the Chinese engineering team the same questions — with the production floor as the answer.

Skip the fair and you lose the side-by-side comparison data that makes RFQ responses comparable.

Practical notes

• embedded world runs annually in early spring — the odd-year complement to electronica’s even-year cycle.
• Strong on industrial and edge-AI hardware; lighter on consumer electronics.
• Confirm exact 2027 dates with NürnbergMesse before booking.

For the China side of the supply chain, see the manufacturing-equipment fair NEPCON China and the components fair China Electronics Fair; electronica in Munich is the even-year complement to this fair. The full list is on the China trade show calendar.

Related resources

• Factory tour — engineer-led visits to Shenzhen and Dongguan factories.
• Exhibition tour — on-the-ground support at Chinese trade shows.
• Industrial IoT hardware sourcing guide — qualification framework for gateways, sensors, and DIN-rail devices.
• Factory audit checklist — 47 checks for Chinese electronics factories.
• China electronics market cities — when to source from Shenzhen, Dongguan, Suzhou, or Shanghai.
• Shenzhen sourcing agent and Dongguan sourcing agent — Pearl River Delta clusters for IoT and embedded builds.
• Suzhou sourcing agent — Yangtze River Delta cluster for industrial-grade electronics and sensors.
• electronica Munich — even-year complement for components and semiconductors.
• NEPCON China — equipment fair that shows what a real PCBA line looks like.

Sourcing an industrial IoT product and unsure the platform is buildable in China? Request a quote.

What to prepare before you go

embedded world is an engineering fair, so arrive with technical homework done. We advise clients to bring:

• A current BOM with critical and long-lead parts highlighted. Mark every component where you do not yet have a qualified second source.
• Target annual volumes and market regions. MOQ and lead-time answers differ at 1k, 10k, and 100k units, and certification requirements change by region.
• A list of must-ask technical questions for each component category: availability roadmap, industrial temperature range, protocol-stack maturity, and certification-file ownership.
• Comfortable shoes and a small backpack. NürnbergMesse is large; you will cover 10–12 km per day moving between halls.
• A notebook or app for structured notes. We use a template with fields for booth number, part number, MOQ, lead time, second source, and certification status.

Book Nuremberg hotels at least two to three months ahead. The fair fills the city, and last-minute rates can double.

Booth conversation checklist

A 20-minute booth conversation should give you enough data to qualify or eliminate a vendor. Ask:

1. What chip or MCU is inside the module? A real designer names it immediately.
2. What is the published availability roadmap? Anything marked “not recommended for new designs” is a non-starter.
3. What is the industrial temperature range, and are all supporting components rated the same? A −40°C to +85°C module with commercial-grade crystals will fail in the field.
4. Which protocol stacks are in firmware versus left to the ODM? OPC-UA and Modbus maturity varies widely.
5. Who owns the FCC/CE/RED grant for this module? Reference-design grants do not always transfer to your end product.
6. What is the real MOQ and lead time at 1k, 5k, and 10k units? Show-floor quotes are preliminary, but the range flags problems.

Red flags: no application engineer present, vague certification answers, or pricing 30% below comparable booths.

After the show

Booth meetings at embedded world give you intent and data, not proof. Before you commit a design to any vendor:

• Order 3–5 sample units of each shortlisted module and test them in your target enclosure.
• Request datasheets, DoCs, and grant files and confirm the model number matches the sample.
• Cross-check part numbers for second-source candidates and confirm pin compatibility.
• Run a factory audit or on-site visit for any Chinese module vendor before volume procurement.

The output of a good embedded world trip is a BOM with qualified part numbers, real lead times, and 2–3 second-source options — not a purchase order.

Common mistakes buyers make at embedded world

Industrial buyers often treat embedded world like a sourcing fair and miss the point. Avoid these pitfalls:

• Bringing a purchase order instead of a BOM. This is a platform-selection show. Vendors will not quote finished-goods pricing here.
• Accepting roadmap slides as guarantees. Ask for written availability statements and check the exact part status online before you leave Nuremberg.
• Ignoring temperature-grade mismatches. A module rated −40°C to +85°C with commercial-grade crystals or capacitors inside will fail in the field.
• Assuming reference-design grants transfer. Always confirm whether the FCC/CE/RED grant for the module transfers to your end-product configuration.
• Skipping sample evaluation. Order evaluation units and test them in your real enclosure before you commit the design.

Realistic costs and logistics

Budgeting for embedded world is straightforward if you plan early:

• Admission badge: Usually free with online registration for trade visitors.
• Hotels in Nuremberg: Book 2–3 months ahead; fair-week rates commonly rise 30–50%.
• Travel within Nuremberg: The U-Bahn serves NürnbergMesse; a day pass is inexpensive.
• Sample orders: Budget $200–500 for evaluation units from 3–5 shortlisted vendors.
• China follow-up: A factory audit for a Chinese module vendor runs $300–800; a Shenzhen factory tour with an engineer is $45/hour USD.

The real return comes from avoiding a single long-lead or end-of-life component. One avoided redesign can save 4–8 weeks and tens of thousands of dollars.

The bottom line: embedded world is where you lock the platform decisions that make or break your China sourcing project. Treat it as engineering intelligence gathering, not purchasing, and convert every booth conversation into a written RFQ checkpoint.

Red flags to drop a vendor: no engineer present, refusal to share a datasheet or certification file, pricing far below comparable booths, unclear availability roadmap, or claims that a reference-design grant automatically transfers to your product. Walk away from any booth that cannot name the chip inside its own module.

Embedded-world platform decisions that shape China sourcing

The MCU, module, and sensor choices made here flow directly into the BOM. Common categories include digital clamp meters, machine vision cameras, collaborative robot cobots, photoelectric sensors, industrial temperature sensors, gas detector transmitters, industrial flow meters, and E40 LED retrofit lamps.

How to turn embedded world notes into a Shenzhen RFQ

A notebook full of booth conversations is useless if your Chinese ODM cannot read it. We convert the fair notes into a locked BOM appendix that becomes part of the RFQ:

• Exact part numbers and package codes. “nRF52840” is not enough; specify QIAA vs QDAA, reel size, and firmware version if relevant.
• Qualified alternatives. List the second and third sources you saw at the fair with the same pinout and temperature range.
• MOQ and lead-time anchors. Write the ranges the vendor quoted at 1k, 5k, and 10k. This gives you a sanity check when the ODM comes back with a 20-week lead time for a part that should be 6 weeks.
• Certification transfer rules. Note whether the FCC/CE/RED grant for a module transfers to your end product or requires retesting.
• Temperature and environmental limits. If the module is rated −40°C to +85°C, state that every supporting crystal, capacitor, and connector must meet the same range.
• Reference-design constraints. If you are using a vendor reference design, list the version number and any deviations.

We attach photos of booth markings, datasheets, and business cards to the RFQ. When the ODM asks “Can we substitute this cheaper part?” the answer is already documented.

Component lifecycle traps that kill China builds

embedded world is where you discover which parts are stable and which are walking toward end-of-life. We flag four lifecycle risks before they become production delays:

• “Not recommended for new designs” (NRND). Even if a module is available today, an NRND status means a redesign is coming. Avoid it unless you have a very short product life.
• Single-source modules without a pin-compatible alternative. A BLE or LoRa module with no second source gives the vendor pricing power and leaves you exposed if they stop production.
• Reference-design grants that do not transfer. Some vendors show FCC/CE grants for their dev kit, not your product. Ask explicitly: “Does this grant cover my end-product configuration?”
• Temperature-grade mismatches inside the module. A module rated for industrial temperatures may contain commercial-grade crystals or flash. Ask for the BOM inside the module, not just the headline rating.
• Long-lead parts that look standard. A sensor or PMIC with a 40-week lead time can stall an entire build. Confirm lead times at multiple volumes before you commit the PCB layout.

The output of a good embedded world trip is a BOM with green, yellow, and red part statuses. Reds are redesigned before tooling; yellows get a second-source plan; greens move to volume.