Intraoral Scanner Integration for Dental Laboratories

Published 16 April 2026 · 7 min read

An intraoral scanner is only as useful to your laboratory as the path between the chair and the technician's screen. If a clinic captures a beautiful digital impression and then emails the STL file to a generic inbox, you have automated nothing.

The point of integrating intraoral scanners with the lab platform is to remove every manual step between the moment the dentist clicks "send to lab" and the moment your CAD designer opens the case. This article covers how that integration looks today, scanner by scanner.

What "scanner integration" actually means

Real integration covers four things:

1. The clinic selects your lab from inside the scanner software and creates a case there.
2. The STL file (or proprietary scan) lands automatically attached to the case in your platform.
3. Case metadata travels with the file: patient initials, prescription, indication, prep teeth, antagonist.
4. Status updates flow back to the clinic from the platform.

Anything less than that is a download and re-upload, which means somebody at your lab is renaming files at 9 am every morning.

The major intraoral scanners and how they connect

3Shape TRIOS

3Shape's communication layer is 3Shape Communicate. The lab gets a free Communicate account, the clinic adds the lab as a connection, and from then on every TRIOS case can be sent to the lab with one click. The platform polls or receives a webhook with the case and pulls the STL.

What works: the workflow is mature, the file quality is excellent, and most clinics already use it.

What to watch: the lab must be set up correctly in the Communicate organisation. Let one technician own that mapping.

Align iTero

iTero connects through MyiTero / iTero Lab. The clinic sends the case to "your lab" by name. The lab receives a notification and downloads the STL pair (upper / lower). For aligner cases, iTero exposes occlusal photos that the lab platform can store with the case.

What works: dominant in clinics doing aligners. If you produce aligners, this is non-negotiable.

What to watch: file naming inside iTero is not always patient-friendly. The platform should rename automatically based on case ID.

Medit

Medit Link is the channel. The clinic shares the case with the lab and the platform consumes the STL via the Medit Link API or via a watched folder if the integration is local. Medit's open ecosystem is the easiest of the major brands for labs.

What works: open files, no extra licensing fees, growing market share.

What to watch: clinics sometimes share the wrong case. Build a verification step in the platform.

Carestream and others

CS ScanFlow uses CS Connect, exocad-compatible scanners use exocad's communication features, and most other scanners ultimately export an STL the lab platform can ingest through email-to-case or a watched folder.

The standard the platform should support

A serious dental lab platform supports at least:

• Direct API integrations with 3Shape Communicate, iTero, Medit Link.
• Email-to-case ingestion with attachment parsing for legacy or smaller scanners.
• Watched folder import for on-premises receiving stations.
• STL, PLY and proprietary file storage attached to the case.
• Automatic mapping of clinic identifiers to platform clinics.

The lab platform's role

The lab platform is the conductor. When the STL arrives, the platform:

• Creates or matches the case using the prescription metadata.
• Attaches the file with the correct naming convention.
• Notifies the responsible technician.
• Logs the file as the source impression so audit traceability stays clean.
• Triggers the next phase: design, milling, printing, depending on the product.

This is the loop that turns a pile of STLs in a folder into a managed digital workflow. We cover the broader workflow in the guide on digitizing a dental laboratory.

Validation: never trust an incoming scan blindly

Even with perfect integration, scans arrive that are unusable. Build a validation step at reception:

• Open the STL in a viewer before accepting the case.
• Check that prep margins are visible.
• Confirm the antagonist is included for crown and bridge work.
• Verify bite registration if needed.
• If the scan is incomplete, reject the case from inside the platform with a message to the clinic. Do not call.

Onboarding clinics on scanner integration

Most resistance from clinics is not about the scanner, it is about the change in habit. The pattern:

1. Pick the three clinics with the most active scanner.
2. Schedule a 20-minute call with each. Walk them through "send to DoYourLab" in their scanner software.
3. Have them send a test case immediately. Confirm it arrived correctly.
4. Then expand to the rest.

A clinic that successfully sends one case digitally never goes back to alginate.

Common pitfalls

• Letting clinics download and re-upload STLs. The whole point is to skip that step.
• Not mapping clinic IDs. If "Dr. Smith" in 3Shape does not match "Smith Clinic" in your platform, every case has to be matched manually.
• Storing STLs locally. Files belong in the case, in cloud storage, with the rest of the case context.
• Not telling the clinic when something is wrong. Silent rejection breeds angry phone calls.