Short answer

You can only outsource an implant case to a partner whose library includes your scan body. The CAD software matches the scan body's known geometry to a library file to calculate the implant's position, angulation and platform. No library match means no accurate design, so confirm system support before sending.

Implant volume keeps climbing across the industry, and the labs that can say yes to nearly any case are pulling ahead of the ones that can't. The gap usually isn't skill — it's compatibility. A design partner without the right implant system in their library can't design the case correctly, full stop, no matter how good their crown & bridge work is.

What a scan body library actually is

When an intraoral or lab scanner captures an implant case, it's not scanning the implant itself — it's scanning a scan body, a temporary marker screwed into the implant that has a known, precise geometry. The CAD software recognizes that geometry against a library of reference files and uses it to calculate the implant's exact position, angulation, and platform in 3D space. No match in the library, no way to place the abutment or crown correctly.

This is why "we do implants" isn't a useful answer on its own. The real question is which systems, which scan bodies, and whether that specific combination is actually in the library being used.

What to check before sending an implant case

Asking these questions before your first case, not after a rejected file comes back, is the difference between finding out you have a reliable partner and finding out you don't — on a deadline.

Broad library support isn't the same as unlimited library support. Any partner worth using can name their supported systems specifically. Vague reassurance is the sign to keep asking.

Curious if your implant system is covered? Upload Your Free First Case →

Why this is the real reason labs turn away implant work

It's rarely that a lab lacks the skill to handle an implant case — it's that the specific system showing up on a given day isn't one they or their design resource support. That's a solvable problem, but only if it's addressed directly rather than assumed away. A design partner with a genuinely wide library turns "sorry, we can't take that system" into a rare exception instead of a weekly occurrence.