A low ex-factory price can be the correct choice for a stable, proven standard programme. It is not a complete comparison when the buyer also needs branding, firmware changes, an app route, interface validation, market documentation, spare stock or a support process. Those are operating costs and delivery risks, not optional footnotes.
Compare the OEM programme by workstream
| Workstream | Purchase-price view | TCO view |
|---|---|---|
| Configuration | Base product price. | Hardware revision, accessories, firmware, packaging and approved variants. |
| Validation | Sample unit cost. | Representative tests, acceptance criteria, rework ownership and release record. |
| Brand and software | Artwork or app fee. | Account, update, data, store and exit responsibilities. |
| Compliance | Document supplied or not supplied. | Exact model, destination, label, importer and revision evidence. |
| Lifecycle | Warranty statement. | Spare parts, repair route, change control and service ownership. |
Ask the supplier to separate scopes
Request one written quote that separates standard supply, private-label changes, OEM engineering, ODM development, tests, documentation, samples, tooling and exclusions. That prevents a buyer from comparing an incomplete standard offer against a configured offer that carries more obligations.
Lifecycle costs need an owner
Before release, define who owns firmware maintenance, account administration, technical intake, RMA approval, spare parts and any transition when a model changes. A product range can be commercially attractive yet still be unsuitable if that operating ownership cannot be supported in the target market.
What to put in the decision record
- Selected model, revision and destination.
- Confirmed and excluded features.
- Sample and acceptance results.
- Documentation and compliance evidence required.
- Support, warranty, spare-parts and change-control owner.
- Commercial assumptions that must be revisited before repeat orders.