ERP for Dental Laboratories — software for Zahntechnik labs and CAD/CAM dental production
Dental laboratories (zahntechnische Labore) sit between fine craft and regulated medical-device production. Each case is per-patient, pricing follows the German GOZ and BEMA fee schedules and the resulting work is a Class I, IIa or IIb medical device under EU MDR with full UDI obligations. An ERP for dental laboratories has to combine per-patient case management, GOZ/BEMA pricing, tight integration with dental CAD systems (3Shape, exocad, Sirona), material traceability for implants, and a clean billing path to dental practices that expect itemised, fee-schedule-compliant invoices.
Requirements
The unit of work is a per-patient case, not a product. A typical case starts with an impression or intraoral scan from a dental practice, runs through design, milling or 3D printing, finishing, quality check and despatch. The ERP models the case end-to-end, including pseudonymised patient identifier, case type (crown, bridge, abutment, denture, splint), prescribing dentist and a target delivery date in days, not weeks. Pricing follows GOZ (private) and BEMA (statutory health insurance) fee schedules — each work item maps to a fee-schedule position with BEL II material surcharges. Dental CAD systems — 3Shape Dental System, exocad, Sirona inLab, Dental Wings — produce digital case data and the milling instruction; the ERP consumes the design file (STL, project file) and links it to the case record. MDR adds UDI labelling, batch genealogy on materials and a UDI chain that survives the patient handover.
Mandatory functions
Mandatory features start with case management: case intake (paper Heil- und Kostenplan, digital order via VDDS-mobile, intraoral-scanner upload), status tracking, work-order generation per technician and a clean delivery workflow back to the dental practice. Pricing requires native handling of GOZ, BEMA and BEL II fee schedules with automatic position-based pricing, material surcharges and individual lab agreements. Dental-CAD integration covers consuming design files, posting milling and printing jobs to in-house equipment, and capturing the finished design for the patient record. UDI labelling and batch genealogy on biocompatible materials (zirconia disks, PMMA, CoCr alloy, titanium pre-mills) is mandatory under EU MDR. QMS documentation has to satisfy ISO 13485 and the German Medizinprodukte-Durchführungsgesetz. Billing supports private patients, statutory health insurance via the dental practice and Direktabrechnung where applicable. DATEV interface and a working link to the Zahnärztliche Verrechnungsstelle close out the financial side.
Vendor landscape
The DACH dental-laboratory vertical has a small, focused specialist field. dentalaim, Aera Dental, ZahnArztPlan, T-Plus and Labolution are long-standing branch products built around GOZ/BEMA pricing and case management. CARDeX, Loblab and DentalEDV target smaller labs. On the CAD side, 3Shape, exocad and Dentsply Sirona dominate; the ERP shortlist depends partly on which CAD ecosystem the lab uses, because integration depth varies by vendor pairing. Generalist ERPs are rare in the dental vertical: a Microsoft Dynamics 365 Business Central or weclapp deployment can work for very small labs prioritising standard accounting over case depth, but loses ground quickly on GOZ/BEMA precision and MDR documentation. For dental groups with multiple labs and centralised production, custom ERP setups on SAP Business One or Microsoft Dynamics 365 occasionally appear. Selection typically pivots on case throughput and on whether the lab does its own implant work, which raises the MDR bar significantly.
Trends and outlook
Three trends are reshaping the vertical. First, full digital workflow: intraoral scans from the practice, dental CAD in the lab, in-house 3D printing or milling, and digital despatch to the practice are replacing the traditional impression-and-cast workflow, which raises the data-integration bar substantially. Second, in-practice production: chairside milling and printing in the dental practice itself compresses the value chain and forces labs to rethink the higher-value complex work. Third, EU MDR enforcement and the looming end of grace periods mean that smaller labs, in particular, have to upgrade their UDI and design-history documentation. The ERP's ability to hold that documentation cleanly becomes a real selection criterion.
Related Topics
Frequently Asked Questions
Why does a dental lab need a vertical ERP rather than a generic small-business ERP?
Because GOZ and BEMA pricing, BEL II material surcharges and MDR-grade case traceability are not optional. A generic small-business ERP forces parallel pricing tables and parallel quality documentation, which becomes unmanageable above ~10 cases per day and risks audit findings under ISO 13485 or MDR review.
How does dental-CAD integration work in practice?
The CAD system — 3Shape Dental System, exocad, Sirona inLab — sits beside the ERP. The ERP feeds case intake data to CAD; CAD produces the design file and the milling/printing instruction; the ERP captures the finished design and the production posting. Integration depth varies by vendor pairing, and tight bidirectional integration (status updates, milling-job feedback) is now a selection criterion rather than a nice-to-have.
How does MDR affect a small dental lab?
Every custom-made dental device is subject to MDR. UDI labelling, technical documentation, post-market surveillance and a designated person responsible for regulatory compliance (PRRC) under Article 15 are mandatory. The ERP must hold the technical documentation file per case and provide an audit trail of materials and processes — otherwise the lab maintains a parallel paper or document-management system, with the usual drift risks.
How are private and statutory health-insurance cases handled differently?
Private cases are billed against GOZ with a Privatrechnung directly or via the Zahnärztliche Verrechnungsstelle. Statutory health-insurance cases are billed against BEMA and BEL II via the dental practice, which then settles with the KZV (Kassenzahnärztliche Vereinigung). The ERP must handle both flows, with separate fee schedules and separate documentation requirements per case type.
