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.
Strengths and limitations at a glance
Vertical depth for plastics compounders, masterbatchers and recyclers — recipe handling, batch traceability and additive management built in.
DACH-native vendor with German hosting and DATEV integration.
Shop-floor data capture, weighing-station integration and scanner support included.
Considerations:
Vertical focus means outside plastics the product is not the typical fit.
Small vendor footprint and partner network — concentration risk.
Cloud variant exists but most installations remain on-premise.
Best-fit profile and comparable vendors
Best-fit customers are DACH plastics-processing Mid-Market businesses of 20 to 250 employees with recipe-driven production and regulatory traceability requirements. Comparable vendors include PART C.One for SAP-leaning buyers, CSB-System for adjacent process industries and the broader vertical specialists. The ERP for plastics overview is the natural starting point.
Share your experience with Poly.ERP. We publish reviews after a brief editorial check in 1–3 business days. Fields marked with * are required.
Häufig gestellte Fragen
Which modules does Poly.ERP offer?
Poly.ERP typically includes modules for financial accounting, order management, warehousing, purchasing and master data. Industry-specific extensions (PPS, CRM, DMS) are often optional – the vendor profile above shows the exact scope of functions. The exact configuration depends on the industry, company size class and customising depth of the specific ERP setup.
What hardware requirements does Poly.ERP have?
For cloud deployment, modern browsers are sufficient. For on-premises installations, server requirements vary depending on the number of users and document volume – the vendor provides detailed system requirements, often with recommended configurations for 25, 50, 100 or 250 users. The exact configuration depends on the industry, company size class and customising depth of the specific ERP setup.
How does data migration from an old ERP to Poly.ERP work?
Data migration typically runs in 3 phases: mapping (old vs new data model), cleansing (duplicates, master data quality) and a test migration with validation. For specialised migration service providers, see ERP integration providers. The exact configuration depends on the industry, company size class and customising depth of the specific ERP setup.
How expensive is the annual maintenance for Poly.ERP?
On-premise maintenance typically runs at 18–22% of the licence costs per year and covers updates, hotfixes and phone support. Cloud ERPs include maintenance in the subscription price, so there is no separate maintenance contract. Over a typical system lifetime this recurring cost adds up to a significant share of the total cost of ownership, so budget for it from year one.
Which well-known reference customers does Poly.ERP have?
Reference customers are usually listed on the vendor's own website – for specialised industry ERPs, 10–50 showcase customers are well known. Industry-specific references should be requested specifically before making a selection. The exact configuration depends on the industry, company size class and customising depth of the specific ERP setup.