Qualify
Turn a broad hardware request into a named customer, workflow, market, device profile and next decision.
ISV / SI hardware enablement
SUNMI POS Hardware Partner for OEM, ODM and Software Teams
Turn device complexity into a clear partner motion: qualify the opportunity, validate the workflow, coordinate supply and keep ownership visible from the first sample to the installed base.
Discuss a partnershipPartner motion
Make hardware easier to sell with your software.
UnitWeave gives software teams and channel partners a practical operating layer around SUNMI devices. We connect the commercial path to the engineering evidence, so a promising demo can become a supported deployment.
Enable
Connect your application to the right SUNMI interfaces, validate the critical paths and leave a record your team can reuse.
Scale
Carry an approved configuration into repeatable purchasing, staging, delivery and lifecycle support as the installed base grows.
For ISVs and system integrators
A useful role for every kind of partner.
Choose the level of involvement that fits your opportunity. We can support a single evaluation, a repeatable channel motion or a larger custom programme.
01
Software companies
Add reliable SUNMI hardware to your POS, commerce, hospitality or field-service offer without building a device supply function from scratch.
- Target-device shortlist
- Interface and permission guidance
- Application validation record
02
System integrators
Give each customer a clear hardware workstream while your team owns the solution architecture, implementation and acceptance conversation.
- Multi-site rollout planning
- Peripheral and network mapping
- Named handover and escalation path
03
Resellers and channels
Protect the customer relationship and add a dependable technical back office for device selection, quotes, samples and delivery coordination.
- Lead registration and ownership
- Market-specific commercial review
- Repeatable fulfilment route
04
Product and brand teams
Explore private label, OEM or ODM when standard SUNMI hardware needs a different identity, specification or operating model.
- Feasibility and volume brief
- Existing-platform and new-product routes
- OEM / ODM development gates
Select -> Validate -> Deploy -> OEM / ODM -> Lifecycle
From requirement to lifecycle, in five practical layers.
Each stage leaves a concrete artifact. Your engineering, operations and procurement teams can work from the same version instead of relying on a verbal handoff.
- 01
UnitWeave Select
Select
Match the workflow to SUNMI form factor, Android version, printer, scanner, payment and display requirements. We state what is manufacturer-supported, tested, or still to be confirmed.
Output: device shortlist + assumptions - 02
UnitWeave Validate
Validate
Run the application on target hardware with the real permissions, firmware, MDM policy and peripherals. Capture repeatable steps, results, limitations and an acceptance owner.
Output: compatibility record + risk log - 03
UnitWeave Deploy
Deploy
Prepare the approved profile for pilot and production waves: golden image, naming rules, accessories, country terms, shipment manifest and customer handover.
Output: deployment profile + handover pack - 04
UnitWeave OEM / ODM
OEM / ODM
When the standard path is not enough, define the product brief, branding, enclosure, firmware, certification, tooling, volume and ownership questions before a development gate.
Output: scoped OEM / ODM brief + gate plan - 05
UnitWeave Lifecycle
Lifecycle
Keep the installed base understandable with spare planning, replacement candidates, version reviews and an explicit end-of-life revalidation path.
Output: lifecycle review + service route
Partner enablement
Bring the workflow, app and deployment constraints.
We return the decisions and records that make your next customer conversation more specific.
01
Evaluation access
A practical sample path for the exact SUNMI model, app build and peripherals that matter to the customer workflow.
02
Compatibility evidence
A versioned conclusion that names the device, Android, firmware, SDK, application build, method and known limitations.
03
Project support
Commercial, configuration, staging and delivery coordination with responsibilities visible before a shared opportunity proceeds.
04
Lifecycle continuity
A plan for replacements, spares, accessory changes and revalidation when the fleet or software release changes.
Operating models
Structure the relationship before the opportunity gets busy.
There is no one-size-fits-all partner contract. These starting models make the first commercial conversation concrete and expose the decisions that still need an owner.
01Recommended starting point
Referral + managed fulfilment
You open a qualified opportunity and stay close to the customer relationship. UnitWeave manages the agreed device, validation and supply work behind it.
- Best fit
- ISVs with a clear application and occasional hardware demand.
- Commercial basis
- referral fee or agreed project margin; lead protection, payment, import and support are documented per market.
Written before launch: Software follows the workflow: your system, a qualified third-party platform or a focused Android application scoped with UnitWeave can own the business logic. We map the named workflow to the named device and keep integration, acceptance and support responsibilities explicit.
02Scoping option
Joint presales enablement
Your team brings application and industry expertise while our team joins the device shortlist, sample review and technical-commercial conversation.
- Best fit
- integrators designing a complete solution across several sites.
- Commercial basis
- scoped presales and engineering effort, with a named opportunity owner.
Written before launch: Software follows the workflow: your system, a qualified third-party platform or a focused Android application scoped with UnitWeave can own the business logic. We map the named workflow to the named device and keep integration, acceptance and support responsibilities explicit.
03Scoping option
Channel supply + escalation
A reseller or distributor owns the commercial transaction while UnitWeave provides the agreed SUNMI hardware and technical back office.
- Best fit
- regional partners that already manage customer procurement.
- Commercial basis
- distributor pricing, delivery terms, warranty route and escalation response agreed up front.
Written before launch: Software follows the workflow: your system, a qualified third-party platform or a focused Android application scoped with UnitWeave can own the business logic. We map the named workflow to the named device and keep integration, acceptance and support responsibilities explicit.
04Scoping option
OEM / ODM programme
Use a separate feasibility route when an existing-product OEM change or a new ODM product makes branding, certification, tooling, firmware maintenance, volume or IP ownership part of the project risk.
- Best fit
- product teams planning a repeatable, differentiated device offer.
- Commercial basis
- NRE, MOQ, tooling, certification and lifecycle commitments decided per project.
Written before launch: Software follows the workflow: your system, a qualified third-party platform or a focused Android application scoped with UnitWeave can own the business logic. We map the named workflow to the named device and keep integration, acceptance and support responsibilities explicit.
Support levels
Increase support depth as the installed base grows.
Start with the smallest useful operating model and add responsibilities only when the project, region and service capability are explicit.
01
Focus on the opportunity. We run the agreed hardware path.
For qualified introductions, your team stays close to the customer and application while UnitWeave coordinates selection, samples, quote and delivery.
- Partner role
- qualified lead, customer context and expectations.
- UnitWeave role
- device workstream, project record and scoped hardware triage.
02
Give the customer one hardware contact.
Add a named hardware route when the project needs more than selection and delivery, with response expectations agreed in writing.
- Partner role
- software ownership, workflow acceptance and application support.
- UnitWeave role
- remote device triage, replacement path and RMA coordination within scope.
03
Add operational depth as the fleet grows.
Extend the relationship into staging, spares, replacement planning and EOL revalidation for repeat deployments.
- Partner role
- release plan, site acceptance and customer-side service promise.
- UnitWeave role
- configuration baseline, batch coordination and lifecycle review.
Opportunity flow
One shared sequence, six clear owners.
Joint logos, compatibility marks, cases and customer references require both parties' approval. Commercial rules are agreed before a shared opportunity proceeds.
- 01
Register the opportunity
Share customer context, workflow, market and the decision currently blocked.
UnitWeave role: Partner - 02
Qualify the scope
Align customer ownership, target region, software responsibility and support expectations.
UnitWeave role: Joint - 03
Select and validate
Create a shortlist, evaluation route and acceptance criteria for the actual workflow.
UnitWeave role: Joint - 04
Agree the commercial path
Document pricing, lead protection, payment, import, delivery and support boundaries.
UnitWeave role: Joint - 05
Fulfil the project
Coordinate configuration, accessories, shipment and the customer handoff record.
UnitWeave role: UnitWeave - 06
Support and review
Route hardware issues, replacements and revalidation through the agreed service path.
UnitWeave role: Scoped agreement
Boundary: No warehouse, fixed stock level, local repair centre or response SLA is implied until the operating capability and contract are confirmed.
Claims and customer ownership
A result is useful when the method is visible.
Every validation record ties the conclusion to a model, firmware, app build and date. That gives your team a defensible answer without overstating what was tested.
Workflow evidence
Printer, scanner, payment, display, network and recovery paths tested against the acceptance script.
Claim discipline
Manufacturer-supported facts are separated from our measurements, customer results and items still awaiting confirmation.
Handover evidence
Configuration, ownership, credentials, limitations and escalation route are recorded before production release.
Before you start
Questions we close in the first review.
A short, specific brief is faster to route than a broad request for "full partner support."
01Do I need to be an existing SUNMI customer?
No. A partnership review can start with an application, customer opportunity or defined deployment brief. We will confirm the appropriate commercial and technical route before making any commitment.
02Can UnitWeave validate our existing application?
Yes. Share the application build, target workflow, required peripherals and preferred SUNMI models. The validation scope will name the environment, test method, acceptance criteria and any limitations.
03Who owns the customer and the software?
That is agreed per opportunity. Your team normally retains application ownership and the customer relationship you introduced; UnitWeave does not imply ownership of credentials, code, data or customer commitments.
04Do you provide inventory or a fixed support SLA?
Not by implication. Stock, importer, warranty, local service, response window and SLA are confirmed per country and contract. This keeps the operating promise aligned with the capability actually purchased.
Project intake
Bring the workflow. Leave with a partner plan.
Tell us what your software does, where it is sold, which SUNMI devices or new product you are considering and what is slowing the opportunity down.