{"id":3746,"date":"2026-10-23T15:04:11","date_gmt":"2026-10-24T03:04:11","guid":{"rendered":"https:\/\/footworklab.net\/?p=3746"},"modified":"2026-10-23T15:04:11","modified_gmt":"2026-10-24T03:04:11","slug":"3d-scanning-instrument-insole-footwear","status":"publish","type":"post","link":"https:\/\/footworklab.net\/fr\/news\/3746\/","title":{"rendered":"A 3D Scanning Instrument for Customised Insoles and Footwear: Where the File Goes After Capture"},"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

Buyers spend most of their attention on the capture, and almost none on what happens next, which is where the cost and the quality actually live.<\/strong> A scan takes seconds. The file it produces then travels through design, review, tooling and molding, and each step can lose something the previous step assumed.<\/p>\n

The phrase itself is worth unpacking, because a 3D scanning instrument for customised insoles and footwear is a search term that covers several different products. Some capture shape from the outside, some capture load from beneath the foot, and some combine the two. The file that comes out is not interchangeable between them, and neither is the work that follows.<\/p>\n

This article follows one measurement through that chain from the point of view of the factory that has to build from it, and describes the checks we make before a pair goes into production.<\/p>\n

Capture is the shortest part of the chain<\/h2>\n

In a well-run clinic the capture is over in a couple of minutes. The client stands, the operator confirms the position, the system records, and the next appointment begins. It feels like the main event because it is the visible part, but in terms of labour it is the smallest step in a chain that ends several days later in a box.<\/p>\n

The chain has five links: capture, file check, design, production and delivery. Failures in the first link are cheap to detect and expensive to inherit, because every later link builds on the file without re-examining it. A capture taken with the foot loaded differently from the intended condition produces a file that looks perfectly normal and a pair that does not fit the way the design intended.<\/p>\n

That is why the useful question is not which instrument has the better specification, but which instrument produces a file that the rest of your chain can consume without translation. A clinic that designs in house needs an export format its design software opens cleanly. A clinic that sends files to a lab needs a format the lab accepts without a phone call each time.<\/p>\n

Our own position is that the instrument should record conditions as part of the record: stance, footwear state, whether the capture was static or during movement, and the time. Conditions are not decoration. They are what makes a file interpretable six months later when the same client returns and the pair has to be compared with something.<\/p>\n

A simple test of whether your chain is ready for a capture system is to trace one file by hand, from the moment it is exported to the moment a pair is boxed. Note every conversion, every re-entry, every phone call. Each of those is a place where information can change without anyone noticing, and the sum of them is the real reason a pair sometimes arrives and does not fit.<\/p>\n

What a scanning file actually contains<\/h2>\n

A shape capture records geometry: the surface of the foot, usually as a mesh, sometimes with landmarks marked by the operator. What it does not record is how the foot behaves under load, because the foot in a scanner is standing in one particular way at one particular moment. Geometry is a snapshot of a posture, not a description of a gait.<\/p>\n

A pressure record is the complement: it describes how load is distributed across the sole during standing or walking, in time and space, but it says much less about the three-dimensional shape that a last or a molding blank has to match. Neither record is complete on its own, which is why clinics that do both tend to describe their setup as a pair of instruments rather than one.<\/p>\n

The distinction matters commercially as well as technically. A buyer who expects a shape capture to answer questions about load distribution will be disappointed by every product on the market, and will conclude that the technology is immature when in fact the expectation was wrong.<\/p>\n

When we receive a file, the first question is therefore what it is a record of. Shape, load, or both. Static or dynamic. Which foot, which date, which conditions. A file without those answers is still usable, but it has to be read as an approximation, and the design has to leave room for adjustment rather than committing to a single interpretation.<\/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

From file to a design a molding step can build<\/h2>\n

Design is where the file becomes an intention. The designer decides how much support belongs under the arch, where the heel cup sits, how the forefoot is posted, how thick the base has to be to hold the shape, and what the top cover will do to the fit. Every one of those decisions narrows what the production step can do.<\/p>\n

This is the step most often skipped in a hurry. A file sent straight to production with a template applied produces a pair that is custom in name and generic in behaviour. A file that passes through a review produces a pair that can be explained: this feature is here because the record showed this, and it is this thickness because the shoe has this much volume.<\/p>\n

The review is also where incompatibilities surface. A design that needs more depth than the shoe allows has to change before molding, not after. A design that assumes a firm shell cannot be built from a soft blank. Catching these in review costs an email; catching them after production costs a remake and a conversation with a client.<\/p>\n

Our workflow keeps the review as a gate rather than a formality. Nothing enters production until the specification is agreed in writing, with the file reference, the shoe reference and the intended use. That gate is the single most effective quality measure we have, and it costs no material at all.<\/p>\n

Footwear: the second input most files lack<\/h2>\n

A foot file describes a foot. An insole has to live inside a shoe. Between those two statements sits a set of constraints that decide whether a technically excellent pair is wearable: internal length, internal width at the ball, heel counter height and stiffness, whether the original footbed is removable, and how much vertical space remains above the toes.<\/p>\n

Clinics that capture feet diligently often send no shoe information at all, and the factory then builds to an average. The average is wrong often enough to matter. A device designed for a running shoe placed in a safety boot raises the heel and changes the fit of the whole boot; a device designed for a deep walking shoe rattles inside a low-profile trainer.<\/p>\n

The practical answer is a two-line field in the order form: shoe type, and whether the original footbed comes out. Two lines, filled in at the point of capture, prevent a category of remake that no amount of scanning precision can address.<\/p>\n

For footwear rather than insoles, the same logic runs in reverse. The last has to be built from the foot record plus the intended use, and the volume allowance has to be decided early. A shoe built from a shape file without a use case is a shoe built for standing still, which is rarely what the buyer wanted.<\/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

Checks before production starts<\/h2>\n

Before a pair enters production we check four things: that the file opens and is complete, that the design matches the file within the agreed tolerance, that the shoe information is present, and that the materials specified are in stock in the required thickness. Each check takes minutes and each one has prevented a production run that would have been wasted.<\/p>\n

The tolerance question deserves a plain explanation. No process reproduces a file exactly; molding introduces small deviations, and hand finishing introduces smaller ones. What matters is that the deviation is known, bounded and consistent, so that a pair built today matches a pair built next month from the same file. Consistency is what makes a remake possible; an exact match is not achievable and should not be promised.<\/p>\n

The materials check is commercial rather than technical. A specification that calls for a material we do not hold will either delay the order or quietly change the pair. We would rather tell a buyer on day one that a cover is unavailable than ship a substitute and explain it afterwards, because the second conversation is always worse than the first.<\/p>\n

Finally, we check that the specification can be repeated. If a clinic orders twenty pairs across a size range in one year, the twentieth should feel like the first. That is a records question, not a production question, and it is the reason the fit file is stored with the order rather than in an email thread.<\/p>\n

It is also why we ask for a photograph of the shoe alongside the file when a buyer cannot send the shoe itself. A photograph is not a measurement, but it answers the questions that measurements cannot: how deep the heel counter is, whether the original footbed lifts out, how much room is left above the toes. Cheaper than a remake, and faster than a shipment.<\/p>\n

Where automation ends and judgement begins<\/h2>\n

Software can now suggest a design from a record, and suggestions are genuinely useful as a starting point. They are not a substitute for review, because the suggestion is built from what the record contains and knows nothing about the client’s activity, the shoe, or the professional’s intent.<\/p>\n

The boundary is easiest to state in terms of responsibility. The instrument measures. The software organises and presents. The professional interprets and decides. The factory builds to the decision. When any one of those steps claims the authority of the next, the chain becomes indefensible, and the failure is usually discovered by the client rather than by the supplier.<\/p>\n

We describe our equipment as foot assessment systems: a pressure-sensing layer, camera-based posture capture and analysis software. We are careful about that description because precision in the language protects the boundary. A system that measures is a tool; a system described as making decisions is a liability for everyone who owns it.<\/p>\n

This is also the honest answer to a common question about automation replacing staff. It does not, in this category. It changes what the staff spend their time on: less transcription, more interpretation, and a record that can be shown to the client while the conversation is happening rather than reconstructed afterwards.<\/p>\n

For a buyer, the test of that boundary is simple. Ask the supplier to show you the screen where a design decision is made, and ask who is expected to make it. If the answer is the software, the product is being oversold. If the answer is the professional, with the software presenting the evidence, the chain is described honestly and can be relied on in a clinical setting.<\/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

What to ask a supplier who offers a scanning instrument<\/h2>\n

Ask what the export looks like. File format, whether landmarks travel with the mesh, whether the record includes conditions, and whether the export can be automated or has to be clicked through for each client. The last point decides whether the instrument fits a busy day or only a quiet one.<\/p>\n

Ask how the software behaves without a network, where records are stored, and how a backup is taken. Ask who owns the data and what happens to it if the relationship ends. These questions are unglamorous and they are the ones that separate a tool you control from a subscription you depend on.<\/p>\n

Ask what the instrument does not do, and listen for a specific answer. Ours measures pressure distribution and captures posture; it does not interpret, and it does not replace a clinical assessment. A supplier who can state that boundary without hedging has thought about how their product is used, and that thought usually shows up in the workflow as well.<\/p>\n

Finally, ask to see a file from a case like yours, not a demonstration case. A record from a stiff midfoot or a wide forefoot tells you more about the instrument than any brochure, because it shows how the system behaves when the input is not ideal, which is most of the time in a real clinic.<\/p>\n

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

Does the scanning instrument design the insole for us?<\/h3>\n

No. It captures a record, a shape, a load map or both, and the analysis software organises and presents it. Design decisions and interpretation stay with the qualified professional, and the factory builds to the specification that professional approves.<\/p>\n

What file format do you need to build a pair?<\/h3>\n

Tell us the system and the export format before the order and we will confirm in writing whether we can open it directly. We also ask for the capture conditions, the foot side and the shoe information, because those decide how the file should be read.<\/p>\n

Can you build from a scan taken on a different brand of system?<\/h3>\n

In most cases yes, provided the export is a format we can open and the record includes conditions and scale. A file without scale or conditions can still be used, but it has to be read as an approximation and the design has to leave room for adjustment.<\/p>\n

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

Design review comes first and usually takes the longest, because that is where questions are answered. Production then runs at roughly five hundred to a thousand pairs a day depending on the mix, and transit runs six to seven working days by express, ten to twelve by air and thirty to thirty-five by sea.<\/p>\n

Do you need the shoe as well as the foot file?<\/h3>\n

Yes, and it is one of the most common omissions. Internal volume, heel counter and whether the original footbed is removable all constrain what can be built. Two lines in the order form prevent a category of remake that scanning precision cannot address.<\/p>\n

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

Two hundred pairs, mixed across styles and sizes, so a first order can test a range rather than commit to one specification. Samples leave within three days of confirmation.<\/p>\n

Who owns the scan data?<\/h3>\n

You do. We store the file with the order so that reorders and remakes can be built from the same record, and it can be exported in a usable format if you move the work elsewhere.<\/p>\n<\/div>\n

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

If you are choosing between capture systems, start with what your chain needs to consume: the core technology page<\/a> explains how the pressure layer, the camera capture and the software fit together, and the insole categories<\/a> show what the production side can build from a file. Send us a sample export<\/a> and we will confirm in writing whether we can open it.<\/p>\n

For a second view, see how one measurement travels from capture to a finished pair<\/a> and how a digital measurement reaches a lab<\/a>.<\/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