OEM · ODM · Joint Development

OEM ODM Robot Lawn Mower: Three Engagement Depths on One UNICUT Platform

Brands launching a robot lawn mower SKU pick one of three engagement depths with SmartMowBot. The UNICUT platform stays the same underneath all three; what changes between depths is how much of the spec the brand owns and how much SmartMowBot engineers from the platform side.

Read the depth spectrum, then open the three tracks.

Discuss your programme Talk to engineering
Shallow · Fast · Lower risk Deep · Longer · Higher differentiation
OEM
Badge on the UNICUT platform
Platform · majorityBuyer · brand layer
ODM
Spec customise on the UNICUT platform
Platform · spec baseBuyer · spec input
Joint Development
Co-engineer on top of the UNICUT platform
Platform · baseBuyer · engineering scope

Three tracks, one platform

OEM, ODM and joint development tracks on the UNICUT platform

Each track describes what the brand brings, what SmartMowBot brings, what is customisable on that depth, the buyer profile that track fits, and the volume cadence that programme tends to follow.

OEM · Track 1

Badge on the UNICUT platform

Brand layer on top, full UNICUT stack underneath, fastest path to a shelf-ready own-brand SKU.

Designer applying a brand badge on a robot lawn mower shell during an OEM programme review

What you bring

  • A defined brand name, logo and packaging direction.
  • A target market and channel mix for the SKU launch.
  • Approved on-product copy and any region-specific manual content.

What SmartMowBot brings

  • The full UNICUT platform across the H1, H3, H3 PRO and H5 coverage classes.
  • Whole-machine assembly, in-house QC and shipping documentation.
  • Continuous OTA support for the platform after launch.

Customisable on this track

  • Brand badge placement on the unit shell and dock.
  • Packaging design, manuals, accessory pouch contents.
  • Region-specific app screens for support contact and warranty terms.

Best fit

  • Brands moving fast on a single market window where time-to-shelf matters more than visible product differentiation.
  • Distributors converting an existing channel into an own-brand SKU on a proven platform.
Volume cadence

Starts with a small pilot batch to validate badge placement, packaging fit and unboxing flow. Moves to a first production run sized to the launch market. Settles into a rolling supply cadence aligned to the brand's reorder rhythm.

For pure badge-on-platform programmes with a thinner brand layer, see the private-label track →

ODM · Track 2

Spec customise on the UNICUT platform

A recognisable own-product look without rebuilding the navigation stack or the cloud layer.

Engineer reviewing a custom-tuned mechanical accent on a robot lawn mower during an ODM spec walk

What you bring

  • Brand, channel and market positioning.
  • A partial spec list covering mechanical accents, app cosmetics and accessory bundle.
  • Buyer-side review on key engineering decisions.

What SmartMowBot brings

  • The UNICUT platform base.
  • ODM spec engineering on the buyer's customisation list, including DFM feedback.
  • Tooling adjustments and QC plan revisions tied to the customised parts.

Customisable on this track

  • External mechanical parts within the platform's modular boundaries.
  • App skin colours, app screen copy, and a defined set of mowing parameter defaults.
  • Accessory bundle composition (charging dock variants, blade kits, optional 4G modules).

Best fit

  • Brands that want a recognisable own-product look without rebuilding the navigation stack or the cloud layer.
  • Brands launching across multiple regions that need region-tuned spec variants on the same platform.
Volume cadence

Begins with a pilot batch run against the customised tooling and the revised QC plan. First production run lines up with the brand's launch calendar across the targeted regions. Programme ramp continues as the brand expands SKUs across the UNICUT coverage classes.

Joint Development · Track 3

Co-engineer on top of the UNICUT platform

The buyer's engineering team writes against the platform alongside the SmartMowBot platform team.

Joint engineering meeting between a buyer brand team and the SmartMowBot platform team

What you bring

Brand, a multi-year roadmap and the buyer's own engineering team. A defined engineering contribution scope that covers vision parameters, firmware modules, PCBA sub-modules or mechanical accessory development. A joint review cadence with the SmartMowBot platform team that runs through the programme.

What SmartMowBot brings

The UNICUT platform as the engineering base, with cross-discipline access to the hardware, firmware, vision and app teams. A platform-side engineer assigned to the programme as the technical counterpart on the SmartMowBot side. Production capacity already in place to receive the jointly engineered modules into the platform line when validation completes.

Customisable on this track

Vision tuning on top of the platform's perception stack. Firmware modules in the buyer's engineering scope. PCBA sub-modules added or revised on the platform. Mechanical accessory development that reaches beyond the standard ODM boundary, signed off against the engineering scope at intake.

Best fit

Brands with a multi-year product roadmap and engineering resource committed to the category. Brands that need a differentiated capability the platform's standard ODM track cannot reach, and that are ready to share the engineering load alongside the platform team across the joint scope.

Volume cadence

Longer pilot phase to cover DV and PV on the jointly engineered modules. First production run lines up after the joint engineering scope is signed off and validated. Programme ramp follows the buyer's roadmap, with OTA support for the jointly engineered capabilities through the platform's update channel.

One platform underneath. Three engagement depths on top.

Manufacturing scope

Manufacturing capability behind every UNICUT programme

The same six in-house capability cells back every engagement depth. The depth determines how much of the spec the brand owns; the cells below describe what stays on the SmartMowBot side regardless of depth.

Whole-machine assembly

Final assembly of the unit and the dock runs in-house, on the same line that builds the standard UNICUT SKUs across the four coverage classes; OEM and ODM units share the line cadence with standard SKUs, joint-development units run on dedicated stations during the validation window.

PCBA design and SMT

PCBA design and SMT for the platform control boards stay on the platform side; ODM programmes may add sub-board variants; joint-development programmes may revise the platform PCBA against the buyer's signed engineering scope.

Tooling and molds

Tooling and injection molds for the platform shells and dock body sit in the SmartMowBot tool inventory; ODM tooling adjustments and joint-development tooling additions are scoped against the programme's mechanical change list.

Firmware and motion control

Firmware for the platform's motion control, sensor fusion path and dock-return logic is owned and maintained on the platform side; programme-side firmware modules added under joint development integrate through a documented interface, not as forks.

Vision tuning

Vision tuning across the platform's stereo and mono camera SKUs runs on the perception stack maintained by the platform team; ODM tuning targets and joint-development perception extensions plug into the same stack.

GFLS platform deep-dive →

App, cloud and OTA

The SmartMowBot app, cloud control plane and OTA update channel cover every UNICUT unit in the field; OEM units inherit the standard app, ODM units pick up the cosmetic and copy revisions in their spec, joint-development units receive the jointly engineered capabilities through the same OTA channel.

All four UNICUT models stay on one platform, see the full range →

How the programme runs

Co-development flow for an OEM ODM robot lawn mower programme

The flow below applies to every engagement depth; the difference between OEM, ODM and joint development shows up in the size of each stage's scope, not in the order of the stages.

  1. Programme intake

    Brand and platform agree on the coverage-class fit and the engagement-depth preference at kickoff.

    Buyer side

    Brand, target market, channel, target launch window and engagement-depth preference.

    Platform side

    UNICUT coverage-class fit review, capability scope review and a kickoff agenda for the programme.

  2. Spec lock

    Customisation scope and IP boundary are recorded in writing against each part of the spec.

    Buyer side

    Sign off on the customisation scope for the chosen depth, including brand assets and any spec variants.

    Platform side

    Spec document with platform parts, customised parts and the IP boundary recorded against each part.

  3. Engineering review and DFM

    Buyer-side review windows close inside the agreed change cadence on the locked spec.

    Buyer side

    Engineering review on the locked spec, raise objections or change requests inside a defined window.

    Platform side

    DFM feedback on every customised part, tooling impact assessment and BOM impact assessment.

  4. Tooling, sample and pilot batch

    First samples go through cosmetic, mechanical and packaging sign-off on the buyer side.

    Buyer side

    Review of the first samples and sign-off on cosmetic, mechanical and packaging fit.

    Platform side

    Tooling readiness, pilot batch on the platform line and in-house QC reports per sample.

  5. DV and PV testing

    Design and process validation reports tie back to the programme record on the platform side.

    Buyer side

    Witness test plan review and optional buyer-side parallel testing on retained samples.

    Platform side

    Design validation and process validation on the pilot batch, with reports tied to the programme record.

  6. Production ramp and OTA support

    Production ramp on the standard line; OTA continuity stays inside the platform's update channel.

    Buyer side

    Rolling reorder cadence into the production line and brand-side marketing release.

    Platform side

    Production ramp on the standard line and continuous OTA support for the units in the field.

Why direct from the factory

Direct factory vs trading company on a robot lawn mower OEM manufacturer programme

Six dimensions where a direct factory engagement reads differently from a trading-company engagement on a robot lawn mower programme. The dimensions are operating-side reality, not marketing claims.

Engineering access

Programme questions reach a platform-side engineer assigned to the account.

Questions cross a non-engineering broker layer before reaching anyone on the production side.

IP boundary

Recorded in writing against each customised part inside the spec document.

Recorded against a sourcing agreement that does not directly bind the engineering owner.

Spec change response

A change request enters the platform's change-control with named owners on hardware, firmware and tooling.

A change request is re-broadcast to whichever factory in the broker's network has open capacity.

QC ownership

QC plan, in-house testing, DV and PV reports tied to the programme record on the platform side.

QC delegated to whichever sub-factory built the run, often without continuity between runs.

Supply continuity

Backed by Sunteam Group, founded 1997, publicly listed on the Shenzhen Stock Exchange in 2015, with the Wuhan-based facility behind the UNICUT platform. Sunteam Group facility →

Backed by the broker's commercial agreements; the underlying factory rotation is opaque to the buyer brand.

Long-term programme support

OTA platform updates reach every unit in the field through the same channel that supports standard UNICUT SKUs.

OTA continuity depends on which factory in the network is still active at update time.

Programme intake

Open an OEM, ODM or joint-development conversation

Tell us which engagement depth fits the launch, the target market, and the launch window. An engineer will reply with the next-step questions and the programme intake brief.

An engineer replies within one business day at the brand's local time.

The information stays inside the SmartMowBot programme team and is not shared with other brands.