OEM / ODM
Some requirements are a bounded change to a part we already make. Others are a new electronic product with its own hardware, firmware and test plan. We establish which one yours is before any price is discussed — and we say when a project is not a fit.
Two depths of customization
They use different engineering time, different tooling decisions and different test plans. The first question in every inquiry is which of the two is being asked for — because the answer changes the whole route.
Depth 01 / Part level
Dimensions, thread or fit, material, surface treatment, a mounting that has to match your machine, or a variant of a part already in our range. The change is bounded by the existing design, so tooling and validation stay proportionate.
See the project stagesDepth 02 / Product level
A new feeder, a control or detection function: hardware, firmware, mechanical integration and the test plan that proves it on a real machine. Longer, reviewed as a full project, and not offered on every request.
See what it involvesTwo depths of customization
A bounded change to an existing part and a new electronic product use different engineering time, different tooling decisions and different test plans.
The project route
Both depths follow the same sequence; what changes is how much engineering each stage holds, and how early a project that does not add up can be stopped.
Machine type and model, yarn, application, quantities, and the problem the change is meant to solve. Photos or drawings of the current part answer more than a written description.
Whether it fits the machines and the process, whether it can be made repeatable, and whether it conflicts with an existing agreement. A no is given here, deliberately, rather than after tooling.
What is delivered, what is excluded, who owns what, and the quantity expectation — recorded in writing before any design work starts.
Mechanical structure and, where electronic, hardware and firmware. Drawings and specifications are shared for your comment before anything is manufactured.
A sample, or a small first batch, built to the agreed specification — your configuration, not a catalogue item with a different label.
Function, run-in and, where the application requires it, validation on the machine — under the same control chain as standard supply.
Results are reviewed together, points that do not meet the requirement are corrected, and the sample configuration is signed off as the production reference.
Production runs to the confirmed reference, with the same inspection, batch record and traceability as standard supply.
Product level, in detail
Developing an electronic feeder means hardware, firmware, mechanics and test planning at the same time. It is a longer project than a part adaptation, and it is reviewed and priced as one.
Board, enclosure and wiring designed around the real working conditions: temperature, vibration, power supply and duty cycle.
Tension, speed and detection behaviour defined, with parameters the mill can set, repeat and record on its own machines.
Mounting, yarn path and service access designed for the machine the unit goes on, not for a catalogue photograph.
The measured values that decide whether the design works: function, run-in, ageing and validation on the machine it was made for.
Drawings, settings and the confirmed reference handed over with the production batch, so the configuration is not lost when a unit needs replacing.
Every unit released under a custom project passes the same control chain as standard supply. See Quality & Testing
Sample before volume
A sample, or a small first batch, is built to the agreed specification, tested under the same control chain as standard supply, and signed off as the production reference before volume runs.
Boundaries and intellectual property
Custom projects go wrong on assumptions never said out loud: who owns the tooling and the design, what happens if the project stops. Those are settled at the scope stage, in writing, while they are cheap to discuss.
The wording here describes how projects are run. It is not a quotation and not the agreement itself — the signed document, reviewed with you, takes precedence.
Feasibility, honestly
Not every inquiry becomes a project, and pretending otherwise uses the engineering time another customer is waiting for. Four cases where the assessment usually ends in a no.
A no at the feasibility stage costs a conversation. A no discovered after tooling costs a project — which is why the assessment comes before the quotation, not after it.
Next step
Machine type and model, yarn, application, quantity, and what the current part or product cannot do. An engineer will come back with the depth of customization the job actually needs — and, if it is not a project we should take, the reason for that.