Retrieving your scanner impressions automatically: 4 methods compared
Every morning, the same ritual: opening three, five, sometimes eight manufacturer portals to fetch yesterday's impressions. Retrieving scanner impressions automatically is no longer a comfort once a laboratory handles dozens of cases a day. But not all approaches are equal. Here are the four possible methods, compared on what really matters: time, errors, data security and the ability to scale.
Why impression intake has become a production issue
Intraoral scanning has won on the practice side. According to Mordor Intelligence, the intraoral scanner market is growing by around 11% a year through 2031. More broadly, Fortune Business Insights expects digital dentistry to double in size by 2034. In practice, your practitioners scan more and more — and each with their own camera brand.
And the number of brands keeps growing. New scanners arrive every year, each with its own proprietary cloud. So the problem is not just case volume: it is the diversity of sources. Even a lab with stable volume sees its logistics burden climb as its practitioners adopt different brands.
The bottleneck has moved. It is no longer in taking the impression, but in its logistics: fetching the file, identifying it, filing it, retyping it into the management software. In France alone there are more than 3,500 dental prosthesis laboratories and close to 18,000 professionals, and the sector consolidates every year. They all live the same tension: an incoming flow scattered across platforms that do not talk to each other. How you retrieve those impressions decides part of your margin.
This logistics has a hidden cost. A misfiled impression is a case you search for instead of producing. An order forgotten in a portal is a deadline that slips and a practitioner who gets annoyed. Multiplied by weekly case counts, this time eats into profitability without ever showing up on an invoice.
There is also a constraint many labs still underestimate. A digital impression identifies a patient: legally, it is health data. Its intake and storage therefore fall under certified-hosting rules and the GDPR. The retrieval method you choose is not just about comfort — it also commits your compliance. Keeping this double criterion in mind — productivity and security — lets you compare the four methods on the same grid.
Method 1 — Logging in manually to manufacturer portals
This is the default situation. Every ecosystem pushes its own cloud. Medit Link handles Medit cameras, 3Shape Communicate the TRIOS, the iTero portal belongs to Align, and DS Core covers the Dentsply Sirona universe. You log in to each one, retrieve cases one by one, then file them by hand.
And these portals are not equal. Medit Link exports STL files fairly freely. 3Shape Communicate, on the other hand, is mostly for viewing and exchanging cases; getting a usable impression out of it requires a 3Shape licence and a trip through its proprietary cloud. Download rights vary from one manufacturer to the next, which complicates collection further.
The mechanism is simple, but the cost climbs with the number of sources. Each portal has its own logic, its own credentials and its own notifications. Hopping between them is a daily gymnastic that adds no value to the case being produced.
The method works, but it does not scale. A lab receiving from five practitioners equipped with different brands juggles as many accounts, passwords and untimely logouts. The lost time is invisible but daily, and every manual download adds a risk of omission or misfiling.
There is also a traceability blind spot. When three people log in to the same portal, nobody knows anymore who retrieved which case. An order forgotten the night before slips under the radar. Manufacturer notifications drown in mailboxes, and an urgent case can sleep for hours before being seen.
Take a lab receiving from five practitioners across three different brands. Every morning: open three interfaces, check each one, download, rename, file. This approach suits a single-brand, low-volume lab. Beyond that, it turns intake into a morning chore and rests the continuity of the flow on one person's memory.
Method 2 — Receiving STL and PLY files by email or shared folder
Second approach: the practitioner exports an STL or PLY file and sends it to you by email, WeTransfer or a shared folder. The advantage is universality — every scanner can export an STL, as field reports on the digital prosthetics workflow remind us. These files can also be heavy: a full scan quickly exceeds a mailbox's attachment limit, which pushes you to stack yet another transfer service on top.
The downside is serious. Files scatter across mailboxes, with no filing by practitioner and no traceability of the order. The prescription often arrives separately: a message on one side, the file on the other. And versions get mixed up as soon as the practitioner re-sends a corrected scan. Finding the right STL a week later becomes a treasure hunt.
Above all, a digital impression is health data. Sending it in the clear through a consumer mailbox exposes the laboratory legally. You step outside any certified hosting framework without even realising it. This method is fine for the odd one-off case. It becomes unmanageable and risky in regular production.
Method 3 — Installing point-to-point connectors
Third route: automating the bridge between one specific cloud and your business software. Gateways exist that fetch a manufacturer's orders and inject them into the lab's management system. For the covered brand, intake becomes transparent and retyping disappears.
The problem is structural: one connector per brand. You plug in one for Medit, another for 3Shape, a third for iTero. Each addition requires configuration and maintenance. The slightest manufacturer update can break the bridge overnight.
This approach also creates dependency. You rely on the connector's vendor for every evolution and every fix. The result soon looks like a fragile assembly. It becomes hard to evolve as soon as a new practitioner arrives with an unplanned camera, and every added brand restarts the same project.
Method 4 — Centralising every scanner in one universal inbox
The fourth method changes the logic. Instead of going to fetch impressions on each platform, a "universal inbox" aggregates them automatically. Whatever the scanner brand, the case lands in the same place. The platform then pushes it straight to your CAD tools and your ERP. One interface replaces the eight portals.
This is the approach Digilab takes. The platform connects natively to the market's main clouds, files every case by practitioner and removes retyping. The file does not just arrive — it leaves again automatically towards the production chain, for instance as a project directly usable in Exocad, with no intermediate handling. Status tracking and exchanges with the practitioner happen in the same place, rather than scattered between email, phone and sticky notes.
The benefit goes beyond the time saved. By centralising, you rebuild complete traceability: who sent what, when, and where every case stands. To assess multi-brand coverage in practice, the Digilab features page details the supported scanners.
Since impressions are health data, hosting is addressed head-on. French regulation is explicit on this point, as the Agence du Numérique en Santé details. Digilab, for its part, reports up to one full-time equivalent saved per month and a start-up in under ten minutes. The initial investment is that of changing a habit. It pays for itself quickly as volume rises and brands multiply.
The 4 methods compared
To decide, look at the same criteria across all four methods. Four really matter day to day. The time spent retrieving cases each day. The risk of errors and retyping. The ability to handle several scanner brands. And compliance with health-data rules. The table below puts them side by side — no surprise: the more you automate and centralise, the more boxes you tick.
| Criterion | Manual portals | STL files / email | Point-to-point connectors | Universal inbox |
|---|---|---|---|---|
| Daily time | High | Medium | Low (covered brands) | Very low |
| Retyping and errors | High | High | Reduced | Eliminated |
| Multi-brand | Manual | Universal but improvised | One gateway per brand | Native, all brands |
| HDS / GDPR security | Varies by portal | At risk | Depends on the tool | Built for it |
| Ability to scale | Low | Low | Medium | High |
How to choose for your laboratory
The right choice depends on your volume and your practitioner mix. The more numerous and heterogeneous your impression sources, the more profitable centralised automation becomes. Three scenarios stand out. Most offers are priced per case, which aligns cost with actual volume.
The small artisan lab
With one or two practitioners on the same brand, manufacturer portals are sometimes enough. The switch becomes worthwhile as soon as a third practitioner arrives with another camera. As long as sources stay homogeneous, the tooling effort is not yet justified.
The growing lab
When the incoming flow diversifies, retyping starts costing real hours and errors. That is the moment to evaluate a universal inbox rather than stacking connectors. The maths is simple: compare the hours spent retrieving cases each week with the cost of a platform.
The multi-site lab or group
For a network of sites, only a centralised platform offers the visibility, traceability and HDS compliance expected at that scale. Manual methods no longer hold. Standardising the flow also becomes an asset when practices must be harmonised across several teams.
FAQ
Can you really retrieve impressions automatically from every scanner?
Yes, provided you use a platform with multi-brand connectors. Manufacturer portals remain single-ecosystem; a universal inbox aggregates the various clouds into one entry point.
Do you need to change CAD software to automate intake?
No. Centralisation solutions plug into your existing chain. They push files to your CAD tools and your ERP without forcing you to replace what already works.
Are digital impressions subject to certified health-data hosting?
An impression identifies a patient: it qualifies as health data. In France, hosting it must go through a certified provider, a requirement reflected in the HDS certification built on ISO 27001.
How long does it take to set up a universal inbox?
Configuration mostly means connecting your existing scanner accounts. Digilab reports a start-up in under ten minutes; allow a short adaptation period for the team afterwards.
Conclusion
Retrieving your scanner impressions automatically is not about choosing one more tool: it is about deciding where your technicians' time goes.
Manual portals and email transfers quickly show their limits. Point-to-point connectors help one brand at a time. The universal inbox is the only method designed for a durable, compliant multi-brand flow. Now weigh it against your actual volume.
To see how to centralise all your scanners into a single flow, try Digilab for free — 100 cases included to test on your own orders.
Centralise all your impressions in Digilab
One single inbox for every scanner your practices use