ESP32 Small-Batch Manufacturing: Custom PCB, Programming and Testing

Move an ESP32 prototype toward a repeatable small batch by defining the custom PCB, component configuration, firmware release, programming method and test requirements.

Define the product beyond the development board

A working prototype demonstrates a configuration, but the manufactured board still needs a defined power input, interfaces, mounting arrangement and external connections. Record which functions must remain and which development-board features can be removed.

Provide the exact ESP32 device or module identification rather than just “ESP32.” Record memory requirements, antenna arrangement, enclosure constraints, connector positions and the expected power source. If the custom PCB does not yet exist, use PCB design assistance to discuss the requirements before requesting assembly.

Release one hardware configuration

Supply the schematic, PCB revision and manufacturing outputs. For PCBA, add the BOM, placement file and assembly drawing. Identify connectors and modules that must be fitted, supplied loose or purchased separately.

Review antenna placement and enclosure integration against the selected module or device documentation. Reusing a development-board circuit does not establish that a changed PCB or enclosure preserves its RF performance. Where product testing or certification is required, define that work separately.

State whether part substitutions are permitted. Changes to flash, modules, peripherals or pin assignments can affect firmware and should be reviewed together with the hardware release.

Specify firmware programming as a deliverable

Give the exact firmware release, target and binary files, with the image addresses and programming settings required by the project. Provide a repeatable command or procedure and identify the connections, boot sequence and tools needed.

State how a programmed board is verified and which version identifier should be recorded. If commissioning depends on a mobile app, network or server, describe that dependency. Do not place production credentials or private keys in public project downloads; agree a secure provisioning process if unique device data is needed.

Firmware development, image preparation, programming and secure provisioning are different tasks. Ask which are included instead of treating “firmware support” as a complete scope.

Write a test that another person can run

Define supply voltage and current limits, required peripheral connections and the expected behavior. Include pass/fail criteria for the functions that matter: for example, boot identification, a sensor response, an interface loopback or connection to a specified test network.

State whether each board is tested or a sample is evaluated, and describe fixtures, test firmware, reports and rework handling. Visual inspection, electrical checks and an application-level functional test are different acceptance activities.

Use the functional test specification guide to prepare the test brief. Test scope and feasibility are confirmed in the quotation.

Approve a pilot before the repeat batch

Agree whether the first build is an engineering sample, a pilot batch or the full order. Use the first articles to check mechanical fit, programming access, firmware behavior and the agreed test method before authorizing the next step.

Record accepted hardware and firmware revisions together. A later repeat order should identify any change in components, firmware, test limits or packaging. Keep estimated future quantities separate from the quantity being ordered now.

What to send for a small-batch quote

• Board files and revision, or a design brief if the PCB is not ready.
• Exact module/device, BOM and assembly variant.
• Initial quantity and clearly labeled quantity alternatives.
• Programming files and procedure, if requested.
• Test instructions, fixtures and acceptance criteria.
• Required accessories, enclosure work, destination and requested delivery date.

There is no universal small-batch price or schedule: component supply and the agreed programming, testing and mechanical scope determine the reviewed offer.