Hardware and enclosure
Adapt the product form, interfaces, power, accessories, installation, labeling and packaging.
- Industrial-design and enclosure changes
- Interfaces, accessories and installation
- Labeling, packaging and documentation
Home / OEM/ODM
Keep Product, Software and Production Decisions in One Delivery Path.
Start from the closest finished-product system, then define the device, software, validation and release work around one approved project baseline.
OEM/ODM starting pointOne approved product configuration
Coordinate the device, software, integration and production test boundary before the sample becomes the pilot baseline.
Fewer handoffs. One approved product baseline.
Hanwu coordinates the device, embedded behavior, branded software, validation evidence and production-test release around the same product definition.
Start from the closest finished product—not from a blank specification.
The product category gives the team a practical hardware, software and validation baseline to review before customization begins.
Alarm and detection devices
Alarm or detection device + branded app + monitoring platform
For brands that need a defined device event to reach the right user, monitoring workflow and factory test.
Find the Right Detection Starting Point
V16 Emergency Warning Lights
V16 light + cellular module + DGT reporting software
For roadside-safety brands that need the device, reporting path and authorized project files reviewed together.
Check V16 Project Fit
Smart lock products
Lock + branded user app + management portal
For access brands that need every credential, permission and event record to match the physical lock.
Check Smart Lock Product Fit
GPS pet tracking devices
Tracker + branded mobile app + service console
For pet brands turning a connected tracker into an owned customer service—not just a piece of hardware.
Check Pet Tracking Product Fit
AI holographic projection booths
Booth + operator controls + content platform
For venues and solution providers that need an AI experience their operators can approve, run and maintain.
Check AI Booth Pilot FitConfigure the product around your market—not around a generic demo.
Start from the closest product system, then agree what changes across the device, software, brand experience, deployment and production release.
Firmware and connectivity
Configure radio choice, device behavior, reporting, power, recovery and production programming.
- Wi-Fi, Bluetooth, NB-IoT or Cat.1 where applicable
- Device states, reporting and update logic
- Programming and functional-test release
App, web and brand experience
Define branded mobile and browser experiences, roles, languages, workflows, alerts and support.
- App identity and interface language
- User, operator and administrator workflows
- Dashboard fields, alerts and reports
Cloud, API, deployment and data
Agree interfaces, hosting, accounts, tenancy, source-code scope and product-data ownership.
- API and third-party integration
- Public, dedicated or private deployment
- Account, hosting, source-code and data ownership
Make the first sample answer a real product question.
A useful sample lets the buyer review the physical product, connected software and acceptance criteria against the same requirements.
Configured device sample
The selected enclosure, interfaces, connectivity, firmware and product identity prepared for review.
Reviewable software build
The agreed app, operator interface or web workflow connected to the sample configuration.
Defined interfaces
The device data, API, third-party services, accounts, hosting and ownership boundaries recorded for the program.
Acceptance criteria
The checks the sample and pilot must pass before hardware, software and tests are released for production.
Close each decision before it becomes a production change.
The configuration becomes more specific as representative use, interfaces and factory checks are validated.
Define the configuration
Choose the closest product and record the market, users, hardware, software, integration and validation requirements.
- Product configuration boundary
- Software and ownership scope
- Sample acceptance criteria
Build the configured sample
Combine the agreed device, firmware, app or web workflow, cloud connection and initial production-test method.
- Configured device sample
- Reviewable software build
- Interface and test records
Validate the pilot
Test representative installation, connectivity, user workflows, data behavior and operating responsibilities.
- Pilot issue list
- Approved configuration changes
- Release criteria
Release production
Lock the approved materials, firmware, software versions, programming, functional tests and delivery records.
- Release baseline
- Production test package
- Delivery documentation
What affects schedule, MOQ, certification scope and quotation
These inputs define the work to be priced and planned. They are not fixed by the product category alone.
Product configuration
Hardware, enclosure, firmware, software and accessories determine what must be changed and validated.
Target market
Countries, radio bands, installation conditions, language and compliance needs affect the development boundary.
Order estimate
Sample quantity, pilot size and an annual volume estimate help define sourcing and production planning.
Certification scope
Required reports, tests and applicant responsibilities depend on the final configuration and target market.
Software and integration
Branded interfaces, account models, third-party services, APIs and deployment choices affect the delivery scope.
Pilot requirements
Representative sites, users, connectivity and acceptance checks determine the validation work before release.
Who owns source code, accounts, hosting and product data?
Ownership and delivery rights are defined in the program agreement. They must not be assumed from a product sample or a general OEM/ODM label.
- Source-code access and handover boundary
- App-store and service accounts
- Cloud hosting and operating responsibility
- Tenant, user and product-data ownership
- Third-party licenses and recurring services
- Support, update and maintenance responsibility
Start with what you know today.
If the program is early, send the product goal, market, users, required functions and what the first sample should prove. Existing drawings or specifications are helpful, not mandatory.
- Closest product system
- Target market and intended users
- Required device and software functions
- App, web, API and deployment expectations
- Sample goal and pilot environment
- Order estimate and known compliance needs
The worksheet stays in your browser and does not transmit an inquiry.
Prepare My Project Brief