Poly.ERP is a vertical industry ERP for plastics compounders, masterbatchers and recyclers in the DACH (Germany, Austria, Switzerland) Mid-Market — the broad mid-market segment of German-speaking SMBs. The product is built specifically for the recipe-driven plastics-processing value chain: complex recipes with grades and additive variants, compounding production, masterbatch manufacturing, plastics recycling and technical compound production. For customers in this niche, the alternative is typically a generic ERP plus extensive customisation, which Poly.ERP's standard product covers out of the box.
Functional scope
Poly.ERP is built around the realities of recipe-based plastics production. The recipe-management module distinguishes between base, production, customer-specific and calculation recipes, supporting differentiated views on materials, surcharges and special conditions. Production planning is recipe-aware with batch-and-lot tracking, raw-material and additive consumption tracking, and yield management. Quality control covers inspection plans, sampling, certificate-of-analysis generation and deviation handling. Comprehensive batch and serial-number management ensures forward and backward traceability — mandatory for technical compounds going into automotive, medical or food-contact applications.
Target audience and verticals
Poly.ERP targets Mid-Market plastics businesses with approximately 30 to several hundred employees, active in compounding, masterbatch manufacturing, plastics recycling and technical compound production. Manufacturers of technical compounds, polymer blends and engineering plastics also fit. The product is most defensible where the customer needs recipe-driven production, precise quality assurance and clear batch traceability as core process requirements rather than nice-to-haves — which is the typical pattern in regulated plastics applications.
Architecture and deployment
Poly.ERP is built on a client-server architecture with Microsoft SQL Server and is optimised for Windows server and client environments. The solution is offered both on-premise and as a cloud SaaS variant, so customers can choose the deployment model that fits their IT strategy. Most production installations remain on-premise because of the deep integration with production-floor systems (process-control, weighing systems, laboratory data), where on-premise infrastructure simplifies the integration path.
DACH localisation and DATEV
Poly.ERP is built for German Mid-Market finance and tax workflow. DATEV integration — DATEV is the cooperative of German tax advisors whose data format is the SME finance-exchange standard — is supported through standard exporters. GoBD compliance — the German principles for proper digital bookkeeping — is part of the standard audit-trail and archiving features. ZUGFeRD and XRechnung e-invoicing are covered, which matters as the phased German B2B e-invoicing mandate rolls out. The product's primary localisation is Germany; Austrian and Swiss customers are supported but the centre of gravity is clearly Germany.
Pricing and selection
Poly.ERP is licensed project-specifically. Classical perpetual licences for on-premise installations and subscription models for cloud deployment are both available. Concrete pricing depends on user count, module selection, interfaces and implementation scope. Poly.ERP competes with other process-industry ERPs (CSB-System for food and beverage with parallel patterns, oxaion process, abas ERP with process extensions) and with SAP Business One plus process-industry add-ons like PART C.One. The strongest selection signal is a plastics business where recipe management, batch traceability and quality control are the central operational pain points.
Write Sie uns Ihre experience with Poly.ERP. We publish reviews after a brief editorial check in 1–3 business days. Fields marked with * are required.
Frequently Asked Questions
Which industries does Poly.ERP fit?
Plastics compounders, masterbatch manufacturers, plastics recyclers and technical compound producers. The recipe-driven production and batch-traceability functionality is the central differentiator versus horizontal Mittelstand ERPs.
Does Poly.ERP support batch traceability?
Yes, comprehensively. Forward and backward batch and serial-number traceability is mandatory for technical compounds going into regulated applications (automotive, medical, food-contact), and Poly.ERP handles this in the standard product.
Can Poly.ERP run in the cloud?
Yes. Cloud SaaS is available alongside the classical on-premise option. Most production installations remain on-premise because of the deep integration with production-floor systems (process-control, weighing, laboratory data).
Does Poly.ERP support DATEV?
Yes. Standard DATEV exporters let the customer's external tax advisor receive posting data in the format that the DATEV cooperative of German tax advisors uses as the SME finance-exchange standard. This is important because most German Mittelstand plastics businesses still work with external accountants whose primary tool is DATEV, and a clean exporter removes the manual-re-keying friction.
How does Poly.ERP handle recipe versions and additives?
The recipe-management module distinguishes between base, production, customer-specific and calculation recipes, with versioning so that historical batches remain traceable to the exact recipe variant under which they were produced. Additive variants are first-class master objects with their own properties.