Kontor MED

Kontor MED is a specialised industry ERP from codegarden software GmbH, a German vendor based in Bavaria that has worked on medical-device-specific business processes for more than two decades. Unlike horizontal ERP platforms that try to cover many industries through configuration, Kontor MED is shipped pre-configured with best-practice processes, master-data structures and regulatory building blocks that map MDR (the EU Medical Device Regulation), IVDR (the In Vitro Diagnostic Regulation) and UDI (Unique Device Identification) requirements directly. The product is positioned for medical-device manufacturers, distributors and importers in the DACH region (Germany, Austria, Switzerland) that need a short time-to-value combined with deep regulatory coverage. The vendor cites over one hundred active customer organisations using the system in production.

Functional sweet spot

Kontor MED ships with more than thirty modules pre-aligned to medical-device workflows: quote-to-cash, purchasing, multi-site inventory with serial and batch tracking, complaint and CAPA handling, supplier and customer master data with regulatory attributes, and the documentation infrastructure required by notified bodies during audits. The system covers manufacturer, distributor and importer roles within the same data model, which matters because most DACH medical-device organisations occupy more than one of these regulatory roles simultaneously. Functional depth around the manufacturing process itself is competent but not the deepest in the market — the differentiator is the regulatory and traceability layer that horizontal ERPs typically push to add-ons or partner solutions.

DACH positioning

Kontor MED is a Tier-3 specialist vendor — relatively narrow in scope, deliberately not trying to be a horizontal ERP, and competitive primarily within the German-speaking medical-device industry. The product's strength is regulatory depth: MDR Article 10 manufacturer obligations, post-market surveillance, vigilance reporting structures, UDI assignment and submission to EUDAMED, IVDR coverage and the traceability that notified bodies expect during certification audits. DATEV integration for bookkeeping export to German tax advisers is part of the standard scope, and GoBD-compliant audit trails are built into the document and accounting structures. Compared with adapting SAP Business One or Microsoft Dynamics 365 Business Central with a partner regulatory layer, the implementation effort is considerably lower because the regulatory scaffolding is part of the core product.

Pricing and implementation

codegarden does not publish list prices and quotes per project. For an indicative 25-user medical-device manufacturer or distributor, all-in five-year TCO typically falls between roughly 250,000 and 600,000 euro, depending on the deployment model, the number of regulatory modules activated and the customisation appetite of the buyer. Deployment is available as cloud, on-premises or hybrid, which is unusual flexibility for a specialist vendor and matters for customers with internal data-sovereignty constraints. Implementation timelines for a focused medical-device scope are typically four to nine months, materially shorter than retrofitting a horizontal ERP with the same regulatory depth, because the standard product already covers the critical paths.

Selection considerations

Kontor MED is a defensible choice for DACH medical-device organisations with between roughly 10 and 200 users where MDR, IVDR and UDI coverage are core requirements and the buyer prefers a pre-configured industry product over customising a horizontal ERP. It is less compelling for organisations that need deep multi-entity international consolidation (where SAP S/4HANA, Microsoft Dynamics 365 Finance or NetSuite fit better), for very small businesses below 10 users where the regulatory scaffolding is more than the workflow needs, or for organisations whose primary requirement is complex discrete manufacturing rather than regulatory compliance. Buyers should test the system against their concrete UDI submission workflow and post-market surveillance reporting needs during evaluation.

Comparable vendors

Direct functional comparables in DACH include Aptean's medical-device industry editions and IFS Cloud with a medical-device partner layer, both of which target a similar regulatory profile but with broader functional ambition. Horizontal alternatives such as SAP Business One, Microsoft Dynamics 365 Business Central or Sage X3 can cover the workflow but only with significant industry-add-on customisation. CSB-System and Asseco APplus are sometimes considered for process-industry adjacent medical-device makers, although the regulatory specificity of Kontor MED is harder to match. The sister product Kontor R4 from the same vendor targets wholesale and B2B trade rather than the medical-device niche.

Vendor homepage of Kontor MED

Current view of the website https://codegarden.de/

Screenshot of the homepage of Kontor MED

Reviews for Kontor MED

No published reviews yet for Kontor MED on erp-software.org yet.

Be the first to write a review →

Write your own review for Kontor MED schreiben

Share your experience with Kontor MED. We publish reviews after a brief editorial check in 1–3 business days. Fields marked with * are required.

Häufig gestellte Fragen

How long does it take to implement Kontor MED?

An ERP implementation takes 3 to 18 months depending on complexity. Cloud solutions are often live within 4–12 weeks, while classic mid-market ERPs need 6–12 months for requirements analysis, customising, data migration and training. Find out more under ERP implementation.

How secure is Kontor MED when it comes to data protection?

For cloud ERPs, the server location (ideally EU/Germany), a data processing agreement (DPA) and BSI C5 or ISO 27001 certifications are key criteria. GDPR compliance should be explicitly documented by the vendor. The exact configuration depends on the industry, company size and customising depth of the specific ERP setup.

How is Kontor MED being developed further?

Cloud ERPs typically receive monthly to quarterly releases automatically. On-premise ERPs have annual major releases with active patch maintenance. Release notes and the roadmap are available from the vendor.

What happens to my data if I cancel Kontor MED?

With cloud ERPs, a good vendor guarantees data export in an open format (CSV, JSON, SQL dump). The contract should explicitly stipulate the data return obligation, the deletion period and the format. The exact configuration depends on the industry, company size and customising depth of the specific ERP setup.

What support SLAs does Kontor MED offer?

Standard support usually covers business days from 8 a.m. to 6 p.m. with a response time of around 4 hours. Premium/24x7 SLAs cost extra. With cloud providers, availability SLAs (e.g. 99.9%) are important — check the contract!