{"id":3571,"date":"2026-10-21T22:09:47","date_gmt":"2026-10-22T10:09:47","guid":{"rendered":"https:\/\/footworklab.net\/?p=3571"},"modified":"2026-10-22T15:02:25","modified_gmt":"2026-10-23T03:02:25","slug":"foot-scanner-oem","status":"publish","type":"post","link":"https:\/\/footworklab.net\/ar\/news\/3571\/","title":{"rendered":"Foot Scanner OEM: What Private Label Actually Requires From Both Sides"},"content":{"rendered":"
\n

About the author<\/strong> \u2014 FOOTWORK LAB is a manufacturer of foot assessment equipment and custom orthotic insoles, based in Ruichang, Jiangxi Province, China. Founded in 2014, with its own production plant since 2018. Certified to European Union and ISO quality system standards. See the factory<\/a> or view certification<\/a>.<\/p>\n<\/div>\n

Private label sounds like a labelling exercise and behaves like a manufacturing project.<\/strong> The badge on the housing is the smallest part of it. What actually decides whether a private-label scanner reaches a market intact is a set of agreements about tooling, firmware, documentation, first-article approval, spare parts and who answers the phone when an end user has a problem. Those agreements are boring, and they are the whole project.<\/p>\n

The second thing that decides it is vocabulary. Buyers arrive asking for OEM when they mean ODM, or the reverse, and the two are not the same purchase. In one, the buyer brings the design and the factory builds it. In the other, the factory’s design is rebranded and the buyer takes it to market. The difference changes who pays for tooling, who carries the technical file, and how much of the product the buyer actually controls.<\/p>\n

We are on the manufacturing side of this conversation, so read what follows as one party’s account of the requirements rather than a neutral survey. Our position is specific: for machines we accept ODM, and machine OEM is negotiated separately rather than offered as a catalogue item. For insoles we accept both. That asymmetry is not an accident, and understanding why it exists is a reasonable way to understand what private label demands from each side.<\/p>\n

OEM, ODM and the difference that decides the project<\/h2>\n

In ODM, the factory’s existing design is adapted for the buyer. The buyer chooses a platform, specifies a housing finish, a brand, a language set, a packaging format and a market position, and the factory builds to that specification. The engineering is largely done before the buyer arrives. What the buyer is buying is a configured product with their name on it.<\/p>\n

In OEM, the buyer’s design is built by the factory. That can mean a fully new housing, a different plate geometry, a bespoke software front end, or a variant of an existing platform with enough change that it is effectively a new product. The factory’s job becomes process: tooling, assembly instructions, test procedures, documentation. The intellectual content of the design sits with the buyer, and so does much of the risk.<\/p>\n

The practical test is a single question: whose drawings are these? If the answer is the factory’s, with the buyer’s brand applied, it is ODM. If the answer is the buyer’s, it is OEM. Most projects that describe themselves as OEM turn out to be ODM with a strong brand layer, which is fine \u2014 but the two carry different expectations about cost, exclusivity and change, and those expectations cause trouble when they are never made explicit.<\/p>\n

There is a third arrangement worth naming, because it appears in almost every serious conversation: a joint development where the buyer’s market knowledge shapes a platform the factory then owns. This is the most productive version for both sides and the hardest to write down, because it requires agreeing in advance what happens to the result. Who holds the design? Can the factory sell it to someone else? In which territories? For how long? A project that skips those questions has not avoided them; it has postponed them to the worst possible moment.<\/p>\n

What the buyer has to bring<\/h2>\n

A brand, first. Not a name and a logo, but a position: who the product is for, what it replaces, what the buyer will say about it, and what the buyer will refuse to say. That last item matters more than it sounds, because it determines the claims on the packaging and in the manual, and claims are where private-label projects acquire legal exposure.<\/p>\n

A specification, second, in buildable terms. Housing colour and finish, labelling language, packaging format, accessories included in the box, the manual’s language and reading level, the software’s language set and any brand strings inside it. Each of these is a line item. Each of them is cheap before tooling and expensive after.<\/p>\n

Third, a volume expectation with a shape. Not a single number, but a first order, a reorder pattern and a ceiling. This matters because a machine line that builds a handful of units a day cannot absorb an unlimited private-label run without displacing everything else. A buyer who needs a large first batch needs to book production capacity rather than assume it. Our own line runs at three to five units a day, and that figure is the honest constraint on any private-label schedule.<\/p>\n

Fourth, the regulatory picture in the destination market. We hold European Union certification and ISO quality system certification, and that is the full extent of what we can document. Anything else the buyer’s market requires is the buyer’s responsibility to establish, and a private-label project should settle that before tooling rather than after the first consignment. A supplier who promises to “handle certification” for an unfamiliar market is usually promising to ask someone else.<\/p>\n

Finally, the buyer has to bring a decision about service. Who handles the end user: the buyer’s own team, a distributor, or the factory’s engineers? Each answer changes the documentation, the spare-parts kit and the training package. It also changes the warranty conversation, because a buyer who fronts the service needs the technical depth to do it, and that depth has to be transferred rather than assumed.<\/p>\n

\"X5
FOOTWORK LAB X5 foot, ankle & posture system. Product photography of our own output; specifications are confirmed in writing before an order.<\/figcaption><\/figure>\n

What the factory has to bring<\/h2>\n

Tooling and process control, first. For a machine, the parts that carry the buyer’s identity \u2014 housing, badge, packaging \u2014 need tooling or at least a controlled finishing route. The parts that carry the function need to stay identical to the validated platform, because a cosmetic change that alters the plate’s mounting or the camera’s position is a functional change wearing a cosmetic label.<\/p>\n

Second, a test regime that survives a private label. Every machine we build runs for seven days before it leaves the factory, and a private-label unit goes through the same regime, with the buyer’s serial numbers recorded against the results. That record is what allows a fault in month eight to be traced to a build date and a test outcome rather than to a general impression.<\/p>\n

Third, documentation. A private-label machine needs a manual in the buyer’s language, a label with the buyer’s identity and the required legal wording, a declaration set that matches what the buyer can actually claim, and a serial-number scheme that lets both parties identify a unit years later. Documentation is where private-label projects most often run late, because it depends on decisions the buyer has not yet made.<\/p>\n

Fourth, change control. Once a unit carries someone else’s brand, an unannounced change to a component or a firmware behaviour becomes the buyer’s problem in their market. A factory that supports private label has to be able to say what changed, when, and which serial numbers are affected. Our connected units take over-the-air updates, which makes this more important rather than less: an update that reaches a branded fleet without the buyer’s knowledge is a commercial incident.<\/p>\n

Fifth, honesty about capacity and priority. A factory that accepts a private-label programme and then fills its line with its own brand has told the buyer something. Ask how production slots are allocated, ask what happens when the two compete, and get the answer in writing. This is the least romantic question in the project and the one that most often decides whether the second order arrives on time.<\/p>\n

Where the cost sits in a private-label project<\/h2>\n

The unit cost is the visible line and rarely the largest. Tooling and set-up come first, and they are one-off, which means they behave badly at low volume and disappear at high volume. A buyer planning a small first batch should expect the set-up to dominate the arithmetic, and should plan the second batch before signing the first.<\/p>\n

Packaging is a persistent cost that buyers underestimate. A private-label box, insert, manual and label set has its own minimum quantities, its own artwork approvals and its own storage problem. A thousand units of product with ten thousand units of packaging is a familiar and expensive mistake.<\/p>\n

The fourth line is the warranty reserve, and it is the one buyers prefer not to fund. A private-label programme carries the end-user promise in the buyer’s name even when the factory performs the work. Set aside a provision per unit at the start, sized by what a realistic failure rate would cost, and you will usually find the number is modest and that having it removes most of the argument about who pays for a repair. A buyer who has not provisioned negotiates every claim from a position of discomfort, and suppliers learn to build that discomfort into their terms.<\/p>\n

Then there is the cost of the buyer’s own time. A private-label project consumes management attention: approvals, artwork rounds, translation checks, first-article review, and the ongoing work of being the brand that answers the end user. That cost never appears in a quotation and is usually the reason a private-label programme stalls in year two.<\/p>\n

Finally, the cost of a weak change-control process. If the buyer cannot tell which units carry which revision, every field issue becomes a negotiation, and every negotiation costs more than the component that caused it. A revision scheme agreed at the start costs an afternoon. Reconstructing one after eighteen months of deliveries costs considerably more.<\/p>\n

Machine OEM and insole OEM are different conversations<\/h2>\n

Machines are electromechanical products with firmware, calibration and a service life measured in years. A machine OEM project therefore involves tooling, validation, a technical file, and a support plan that has to survive several years of use in someone else’s market. That is why we handle machine OEM as a separate negotiation rather than a catalogue option: the terms depend on volume, on how much of the design the buyer is actually changing, and on who carries the support obligation afterwards.<\/p>\n

Insoles are a consumable product with a shorter cycle and a much simpler validation path. Both ODM and OEM are accepted, the minimum is 200 pairs with mixed styles and sizes allowed inside it, and capacity runs at roughly 500 to 1,000 pairs a day. A buyer can therefore test a private-label insole line at modest volume, learn what the market does, and scale without renegotiating the fundamentals.<\/p>\n

That difference in maturity is useful. A buyer new to private label is usually better served by starting with insoles, where the loop from specification to delivery is short enough to learn from, and moving to a machine programme once the brand has a market position and a service story. Starting with a machine OEM project as a first private-label venture concentrates every risk in the hardest category.<\/p>\n

For a machine programme built on an existing platform, the X5 line<\/a> is the usual starting point, because a configured platform carries far less tooling and validation than a new design. That is not a compromise on the product; it is a recognition that a first private-label order is a test of the arrangement as much as of the hardware.<\/p>\n

\"X5
FOOTWORK LAB X5 foot, ankle & posture system. Product photography of our own output; specifications are confirmed in writing before an order.<\/figcaption><\/figure>\n

Running the project: milestones that keep both sides honest<\/h2>\n

Start with a written specification that both parties sign, including what is explicitly out of scope. The out-of-scope list is the most useful page, because it is where the assumptions would otherwise hide. If the buyer expects a particular market approval, a particular language, or a particular response time on service, it belongs on that page or it does not exist.<\/p>\n

Then a first article. One unit, built to the agreed specification, reviewed by the buyer before any batch begins. The review should cover the physical build, the labelling, the manual, the packaging and the software strings. Approve it in writing, keep one unit as the reference, and check every later unit against that reference rather than against a memory of it.<\/p>\n

Then a pilot batch, at a size the buyer can actually sell or place. The pilot is where the documentation, the packaging and the service story get tested in the field, and it is much cheaper to discover a problem in a pilot than in a full consignment. Our insole samples leave within three days, which makes a pilot loop practical; machine pilots are slower because each unit runs the seven-day test, and the schedule should reflect that.<\/p>\n

Set the approval calendar before the first article, not after it. Artwork, translation, label wording and manual review each need a named person on the buyer’s side and a date. In our experience the manufacturing steps are the predictable part of a private-label schedule and the approvals are the variable one, which is why a project plan that shows only production milestones is missing the steps most likely to slip.<\/p>\n

Then a review with numbers. What arrived when, what failed, what the end users said, what the buyer had to explain more than once. That conversation is the real first-article approval for the second order, and a programme that skips it repeats its own mistakes with more confidence.<\/p>\n

Last, an exit that both sides can live with. What happens to the tooling, the spare-parts stock, the firmware update path and the outstanding warranty obligations if the arrangement ends? A private-label project that cannot answer that question is a hostage situation with a delivery schedule. Writing the answer down at the start costs an hour and removes the single largest source of bad behaviour later.<\/p>\n

\"X5
FOOTWORK LAB X5 foot, ankle & posture system. Product photography of our own output; specifications are confirmed in writing before an order.<\/figcaption><\/figure>\n

Frequently asked questions<\/h2>\n
\n

What is the difference between OEM and ODM here?<\/h3>\n

In ODM the factory’s existing design is configured with your brand, housing finish, language set and packaging. In OEM your design is built by the factory, which means your drawings and your technical content. The test is whose drawings the product is built from.<\/p>\n

Do you accept OEM on machines?<\/h3>\n

Machine OEM is negotiable separately rather than offered as a catalogue option, because the terms depend on volume, on how much of the design changes, and on who carries support afterwards. Machine ODM we accept as a standard arrangement. For insoles, both OEM and ODM are accepted.<\/p>\n

What is the minimum order for a private-label insole line?<\/h3>\n

200 pairs, with mixed styles and sizes allowed inside that quantity. Capacity runs at roughly 500 to 1,000 pairs a day, so a pilot order and a production order use the same process rather than two different ones.<\/p>\n

Can you build a batch large enough for a national launch?<\/h3>\n

That depends on the schedule, not only the total. Our machine line builds three to five units a day, so a large first batch has to be booked as production capacity in advance. Tell us the shape of the demand, not just the first number.<\/p>\n

Who handles certification for our market?<\/h3>\n

We can document European Union certification and ISO quality system certification, and that is the full scope of what we hold. Any additional requirement in your market is yours to establish. We will tell you what we can and cannot provide rather than imply more.<\/p>\n

Whose brand appears in the software?<\/h3>\n

That is part of the specification. Brand strings, language sets and the manual’s identity are agreed before the first article is built, and changes afterwards are handled as a revision rather than a new design.<\/p>\n

What happens to tooling and spares if we stop ordering?<\/h3>\n

It should be written down before the first batch, not discussed afterwards. Agree the disposition of tooling, the spare-parts arrangement and the firmware update path while everyone is still being polite.<\/p>\n<\/div>\n

What we would do next<\/h2>\n

Send us a one-page description of the product you want to put your name on, the market it goes to, and the volume shape you expect over two years, and we will tell you whether it is an ODM configuration or a separate machine OEM negotiation \u2014 and say so plainly if it is neither. The X5 product page<\/a> shows the platform most first programmes are built on; the partner page<\/a> covers how we work with distributors and brands; and the insole range<\/a> is the faster route into private label if this is your first programme. For the commercial terms behind all of it, the FAQ page<\/a> is the shortest read.<\/p>\n

This article is intended for professional and educational reference. It is not medical advice. Foot assessment equipment produces measurements and images; clinical interpretation and any decision about care remain the responsibility of a qualified professional. Certification scope is limited to the documentation we hold: European Union certification and ISO quality system certification.<\/em><\/p>\n

\n

Related reading<\/h2>\n