OEM and ODM Soccer Trackers, Built Under Your Brand

OEM and ODM describe two depths of collaboration. In an OEM arrangement we manufacture the TROPS-1 sensor and supply the platform with your brand on the product, the packaging and the software. The measurement core stays the same because it is already proven on training pitches; what changes is everything the buyer sees.

In an ODM arrangement the starting point is the same core, but the scope extends into how the product is configured, presented and delivered: firmware configuration for a coaching model, a different accessory set, a software surface built for your market. We agree the boundary in writing before production, so neither side guesses what "custom" includes.

Every unit measures the same way. A 25 g sensor sits at the ankle, where the foot does the work, and a 9-axis IMU records motion at high frequency with edge computing on the device. The platform turns that stream into 20+ football metrics per player per session: ball contacts, passing and shooting actions, left/right balance, sprints, top speed, distance and training load.

Three properties matter to OEM partners. The TROPS-1 sensor exports raw IMU data, so your team can run its own models. An open API pushes sessions and player metrics into systems your customers already run. And the platform can be deployed privately, so the product you sell is not a closed box with your sticker on it.

Customisation works in layers. The identity layer covers logo placement, product naming, box design, quick-start documentation and the app icon. The configuration layer covers which metrics are surfaced first, which report templates a customer sees, and how squads and age groups are structured. The integration layer covers API access, data residency and export formats.

The layer that does not change is physics. Placement, the IMU specification and the definition of a sprint or a ball contact stay fixed, because a metric that means something different in your market than in ours is a support problem for both of us.

1. Scope. You describe the market, buyer type, expected volumes and the brand assets you have. We reply within 24 working hours with a proposed configuration.
2. Sample evaluation. Sample orders start from 10 units so your team can test sensor, app and reports on a real pitch before committing.
3. Specification. Packaging artwork, app naming, firmware configuration, accessory list, documentation language and acceptance criteria are written down.
4. Pilot run. A first batch is produced against that specification and checked against those criteria.
5. Volume production. Standard OEM orders start from 100 units; larger programmes are scheduled against your launch plan.
6. Delivery and handover. Units ship worldwide, with shipping terms and documentation agreed before production. Platform accounts and staff onboarding follow.

To turn a conversation into a quotation we need six things: the market and buyer type you target, the number of units in your first order, the branding assets you already have, whether packaging is retail or academy-oriented, the software scope (white-label, private deployment, or both), and your target launch window. If some are still open, say so — two scenarios are more useful than one number built on assumptions.

We do not publish list prices, because an OEM configuration is not a catalogue item. If you are still comparing shapes of partnership, the solutions overview maps them by buyer type. Send the outline through the contact form and you will get a written configuration and quote.