{"id":3527,"date":"2026-10-21T21:47:49","date_gmt":"2026-10-22T09:47:49","guid":{"rendered":"https:\/\/footworklab.net\/?p=3527"},"modified":"2026-10-22T15:02:18","modified_gmt":"2026-10-23T03:02:18","slug":"3d-foot-scanning-for-orthotics","status":"publish","type":"post","link":"https:\/\/footworklab.net\/fr\/news\/3527\/","title":{"rendered":"3D Foot Scanning for Orthotics: How a Digital Measurement Travels From Clinic to Finished Pair"},"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

Most of the failures in this category happen in the handover, not in the measurement and not in the build.<\/strong> A clinic produces a good record, sends it out, and receives a pair that is well made and wrong for the client. Nothing in the chain was careless. The information simply lost its meaning somewhere between two systems that were never designed to talk to each other.<\/p>\n

The phrase 3D foot scanning for orthotics suggests a single act, and that is the source of most of the trouble. In practice it names a chain: capture in one room, interpretation in a second system, production in a third, and a review that closes the loop months later. Digital measurement is often described as if it removes the risk in that chain. It does not. It moves the risk from plaster and postage to file formats, units, orientation and the assumptions that each side makes about what the other one sent. A cast that arrives physically distorted is obvious. A file that arrives rotated, in a different unit convention, or missing the shoe context looks perfectly normal and produces a pair that does not fit.<\/p>\n

We build both ends of this chain in one plant: the assessment equipment that produces the record and the insoles that are built from it. That position makes the handover visible in a way it rarely is from either side alone. This article follows one measurement from the clinic to the finished pair and names the places where meaning is lost.<\/p>\n

The handover is the weakest link, and it is invisible<\/h2>\n

Two organisations meet at a file. The clinic knows the client, the shoe, the history and the reason the pair is being ordered. The factory knows materials, tooling, tolerances and what can be built in a production run. Neither knows what the other one does not know, and the file is the only place where the two kinds of knowledge can meet.<\/p>\n

Most files carry less than the clinic assumes. A geometry file describes a surface and nothing else: no load, no posture, no shoe, no note about the place on the foot that must not be pressed. The factory receives a shape and builds to it, because that is what was sent, and the result is technically faithful and practically wrong.<\/p>\n

The clinic, in turn, often assumes the factory will notice what is missing. A factory cannot notice a missing clinical note, because the absence of a note is not visible in a file. It can notice an unusual posting angle or an implausible arch height, and a good one will ask. But it cannot ask about a question that was never raised.<\/p>\n

The result is a category of complaint that both sides find baffling. The clinic says the pair does not suit the client. The factory says the pair matches the file. Both are telling the truth, which is the definition of a handover problem rather than a quality problem.<\/p>\n

There is a version of this problem that appears only with digital records, and it is worth naming because it is counter-intuitive. A paper form that arrives blank is obviously blank. A digital record that arrives with an empty field looks complete, because the software has rendered a tidy document around the gap and the gap has no visual weight. Files therefore fail quietly, and quiet failures travel further into production before anyone notices them. A clinic that switched from casts to files two years ago and still sees the occasional pair returned has probably been living with a quiet failure of exactly this kind, and has been reading it as a fitting problem rather than a data problem.<\/p>\n

The remedy is not more technology. It is a written specification of what travels with the file, agreed once, and used every time. That document is worth more than a better sensor, because a better sensor sending an incomplete record still produces the same failure with more detail attached.<\/p>\n

Step one: what the clinic should actually send<\/h2>\n

Start with the load record. A pressure capture taken standing and walking describes where the sole carries weight and how that changes through the step. It is the single most useful input for deciding how a pair should share load, because it is the only record that describes the foot doing its job rather than resting.<\/p>\n

Add the shape record. Length, width, arch height, heel width and the contours that a shell will be built against. If the shape was captured off weight, say so explicitly, because a factory that assumes weight-bearing geometry will build a pair that is too full, and the client will feel the insert rather than the ground.<\/p>\n

Add the posture record. A camera capture of stance and gait tells the designer how the lower limb is arranged above the foot, which changes how much support the pair should provide and where it should be placed. Without it, the design is derived from a footprint, and a footprint is a shadow of a decision the body has already made.<\/p>\n

Add the shoe record, and be specific. Internal length, width at the ball, depth at the heel, whether the sockliner lifts out, how much room is left above the instep. A photograph of the shoe with a tape measure in frame is crude and enormously useful. Two pairs built to the same foot file and dropped into different shoes are different products.<\/p>\n

Finally, add the notes that no instrument can produce. Where the pair must not press. What the client does all day. Which shoe the pair will live in. What was tried before and what happened. A single paragraph of that kind prevents more remakes than any improvement in capture quality, and it costs the clinic four minutes.<\/p>\n

\"FX
FOOTWORK LAB FX custom orthotic insoles. Product photography of our own output; specifications are confirmed in writing before an order.<\/figcaption><\/figure>\n

Step two: the design file, and the questions that should come back<\/h2>\n

The factory’s first job is not to build. It is to read, and then to ask. A design file is an interpretation of the records: where the shell rises, how much fill sits under the midfoot, whether the heel is posted and by how much, what the top cover is, where the accommodation is cut. Each of those is a decision with a reason, and the reason belongs in the file next to the decision.<\/p>\n

A good handover produces questions. The posting looks unusual for this shoe. The arch height in the shape record does not sit well with the load pattern in the pressure record, which happens when a foot is captured in a position it does not hold while walking. The requested shell thickness will consume more volume than the shoe appears to have. A factory that asks those questions is doing design work; a factory that never asks is doing reproduction.<\/p>\n

The clinic’s side of this step is sign-off. Someone who has seen the client should confirm the interpretation before the pair is built, because a misunderstanding caught at this stage costs an email and a misunderstanding caught after production costs a remake, a return transit and a fortnight of the client’s patience.<\/p>\n

It also helps to decide, once, who owns the design file. A file that lives only inside the manufacturer’s system is a file the clinic cannot take elsewhere, cannot audit, and cannot use to brief a second supplier. A file the clinic holds, in a format it can open, is an asset that survives a change of supplier and a change of staff.<\/p>\n

There is one question at this stage that separates a supplier from a partner, and it is easy to ask. When a file arrives that looks buildable but seems wrong, does anyone say so before the run starts? A supplier builds what was sent and invoices for it. A partner builds what was sent, but only after an email that says the arch height and the pressure record appear to disagree, and asks whether the capture was taken with the client seated. The first behaviour is defensible and the second is worth paying for, because the cost of that email is a few minutes and the cost of the alternative is a remake plus a client who has now waited a month.<\/p>\n

Version control is the unglamorous half of the same subject. If a client is measured again in a year, the second file should be identifiable as a successor to the first rather than as a separate object. A naming convention agreed at the start, with the client reference and the date in it, saves an argument later when someone needs to know which of three files was actually built.<\/p>\n

Step three: the build, where tolerances replace intentions<\/h2>\n

Production converts a design into an object, and the conversion has a tolerance. The shell is formed, trimmed, the cover is bonded, the edges are finished, and each of those operations has a range within which the result is considered acceptable. The width of that range is a commercial decision as much as an engineering one, and it should be stated rather than assumed.<\/p>\n

The material choice determines how the pair behaves under load. A stiff shell resists more and passes less through, which changes what the wearer feels and how the shoe fits around the insert. A softer construction is more forgiving in a tight shoe and provides less resistance. Neither is better in the abstract; the choice follows from the load record and from the shoe, which is why both belong in the same conversation.<\/p>\n

Volume is the constraint that decides whether the pair gets worn. Every millimetre of shell and cover consumes space inside a shoe that was designed for a foot. A pair that is excellent in isolation and too full for the shoe will be abandoned, and the clinic will record it as a fitting failure when it was a volume calculation made too late.<\/p>\n

Then there is repeatability. Two pairs built to the same file should resemble each other, because a replacement in six months should be the same object as the original. Ask how that is checked, and ask to see two pairs from one file side by side. The comparison takes a minute and answers a question that no certificate addresses.<\/p>\n

Finishing is where the client’s first impression is formed, and it is also where the cheapest failures occur. A cover that lifts at the edge, an edge that is left sharp, a heel cup that is proud of the shell: none of these are design errors, and all of them end with the pair in a drawer. A factory that inspects the finished object rather than only the formed shell is doing the last ten percent that decides the outcome.<\/p>\n

\"FX
FOOTWORK LAB FX custom orthotic insoles. Product photography of our own output; specifications are confirmed in writing before an order.<\/figcaption><\/figure>\n

Step four: what comes back with the pair<\/h2>\n

The return leg of the handover is usually empty. A pair arrives in a bag with no reference to the file, no summary of what was specified and no note about what to watch for in the first two weeks. The clinic then has to reconstruct the reasoning from memory, which is exactly the condition that produced the original ambiguity.<\/p>\n

What should travel back is short: the file reference, the design summary in plain language, the intended shoe, and the staged wearing schedule. That is half a page. It gives the practitioner something to check the pair against and something to hand to a client who asks what is inside.<\/p>\n

It also makes the review appointment possible. A practitioner holding the design summary can decide whether a reported pressure point is a specification issue, a build issue or a shoe issue, because the three look different when the specification is in front of them. Without it, every complaint looks the same and the only available response is a remake.<\/p>\n

The review should then feed back into the file, not into a conversation. If the fill was reduced, the file should say so. If the shoe was the problem, the file should record that the client’s footwear changed. A file that accumulates those notes becomes genuinely useful by the third pair, which is when the arrangement starts to pay for itself.<\/p>\n

Finally, the return leg is where a remake policy is tested. The distinction that matters is between a pair that does not match its file and a pair that matches its file and does not suit the client. The first is a manufacturing question and should be rebuilt without argument. The second is a design question and should be answered by changing the design. Suppliers who blur the two end up rebuilding the same mistake.<\/p>\n

Writing the handover into the agreement<\/h2>\n

Most of what this article describes can be settled in a page of terms, and settling it before the first order is worth more than any single improvement to the equipment. The page should name the records that travel with each order, the format they travel in, who converts them into a design, and who signs the design off before production.<\/p>\n

It should also name the commercial facts that shape the arrangement. Our insole orders start at two hundred pairs, with styles and sizes mixed inside that number. Samples leave within three days, which is what makes a trial possible before a production run. Capacity runs roughly five hundred to a thousand pairs a day, so a mixed order is a normal order rather than a favour. We accept ODM and OEM on insoles, which covers both building to a partner’s design and building to ours under a partner’s brand.<\/p>\n

Transit belongs on the same page, because it sets the review cycle. Express takes six to seven working days, air ten to twelve, sea thirty to thirty-five. A clinic that plans a two-week trial and orders by sea has planned a two-month trial, and the mismatch is nobody’s fault but the calendar’s.<\/p>\n

Ask, too, how the factory handles the file after the order closes. Retained, archived, deleted on request: any of those can be reasonable, and none of them is discoverable after the fact. A clinic that holds its own copy is protected either way, which is the simplest argument for keeping the file in house.<\/p>\n

\"FX
FOOTWORK LAB FX custom orthotic insoles. Product photography of our own output; specifications are confirmed in writing before an order.<\/figcaption><\/figure>\n

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

Can we send the scans our clinic already produces?<\/h3>\n

Yes, in most cases. What matters is that the record describes the foot under load and includes the shoe it will sit in. The accepted formats and the conversion step are confirmed at the first order, before production rather than after it.<\/p>\n

How long does it take from file to finished pair?<\/h3>\n

Samples leave within three days, and production capacity runs roughly five hundred to a thousand pairs a day. Transit is six to seven working days by express, ten to twelve by air and thirty to thirty-five by sea.<\/p>\n

What is the minimum order for insoles?<\/h3>\n

Two hundred pairs, with styles and sizes mixed within the order. That threshold comes from the production run rather than from the number of designs, so a clinic working across several shoe categories can still fill one order.<\/p>\n

Who owns the design file?<\/h3>\n

That is agreed in writing, and we recommend the clinic holds its own copy. A file you can open without a supplier’s system is an asset; a file that only exists inside someone else’s software is a dependency.<\/p>\n

What happens if a pair does not match the file?<\/h3>\n

The pair is compared against the file and the shoe before anything is rebuilt, because that comparison separates a build difference from a design question. A build difference is remade. A design question is answered by changing the design.<\/p>\n

Can you build to our own design and brand?<\/h3>\n

Yes. We accept both ODM and OEM on insoles, which covers building to your design as well as building to ours with your branding. The specification is signed off before the first production run.<\/p>\n

What certification do you hold?<\/h3>\n

European Union certification and ISO quality system certification, covering the plant where both the equipment and the insoles are produced. We list no other approval, because we hold no other documentation.<\/p>\n<\/div>\n

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

If you are building a handover process, begin with the measurement end: the F2 plantar pressure system<\/a> records load and posture in one session, and our article on reading a plantar pressure map<\/a> explains what the output can and cannot support. The insole range<\/a> shows the constructions we build from that record, and the contact page<\/a> is where a format question gets answered in a single exchange.<\/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