Customizing Epicor for make-to-order manufacturing in 2027 requires a focused approach on four high‑ROI areas: Business Process Management (BPM) rules to automate job creation from customer orders, Application Studio modifications to add engineer‑to‑order (ETO) fields and workflows, MES integration for real‑time shop floor data collection, and dashboard customization for job‑level profitability tracking.

Standard Epicor configurations often fail MTO manufacturers because they cannot handle variable BOMs, engineering changes during production, or customer‑specific pricing and routing without customization. The strategies in this guide – including automated quote‑to‑job conversion, engineering change order (ECO) workflows, and predictive scheduling – reduce lead times by 20‑40% and improve job cost accuracy by 30%+ for U.S. custom manufacturers.

This guide provides step‑by‑step customization instructions, BPM examples, MES integration patterns, cost expectations, and risk mitigation strategies for Epicor Kinetic (formerly Epicor ERP 10) and legacy Epicor 9/10 environments.

Why Make‑to‑Order Manufacturers Need Epicor Customization

Make‑to‑order manufacturing differs fundamentally from make‑to‑stock or configure‑to‑order production. Each job is unique, with customer‑specific specifications, engineering requirements, materials, and production routing. Standard ERP configurations assume repeatable processes and predictable BOMs – assumptions that break MTO operations.

Unique MTO challenges that demand customization:

The 2027 imperative: U.S. custom manufacturers face pressure from customers demanding shorter lead times (average requested lead time dropped from 6 weeks to 3 weeks since 2020) and real‑time order visibility. Without Epicor customization, you cannot meet these expectations.

Understanding Epicor Kinetic Architecture in 2027

Epicor Kinetic (the rebranded Epicor ERP 10) provides a modern cloud‑capable platform with customization tools that do not require deep programming expertise.

Key customization layers:

2027 enhancements relevant to MTO customization:

• AI‑assisted BPM recommendations – Epicor now suggests BPM rules based on usage patterns (e.g., “90% of users add a line item note after saving sales order – automate this field?”)
• Low‑code Application Studio updates – Drag‑and‑drop customization of production entry screens without C# coding
• Enhanced REST API – Real‑time bi‑directional sync with PLM, CAD, and MES platforms
• Cloud‑native BPM execution – Custom rules run in microservices architecture with sub‑second latency

Important distinction: Epicor customization should focus on configuration and low‑code (80% of needs) versus custom code (20%). Over‑customization with C# extensions creates upgrade risks. This guide emphasizes BPM, Application Studio, and dashboard customizations that survive version upgrades.

Core Epicor Modules That Should Be Customized for MTO

Not every module requires customization. Focus on these eight high‑impact areas.

1. Quote Management (Sales module)

Standard Epicor quotes assume standard products with fixed price lists. MTO requires:

• Custom fields for customer specifications (material grade, dimensions, finish, certifications)
• Automated costing engine (material + labor + overhead based on spec)
• Quote‑to‑job conversion (one click creates job, BOM, operations)

2. Job Management (Production module)

MTO job customization needs:

• Dynamic BOMs (line items added/changed during job life)
• Engineering revision tracking (revision level on each job operation)
• Customer approval holds (job cannot proceed past specific operation without customer sign‑off)
• Partial shipment workflows (ship completed sub‑assemblies before final assembly)

3. Engineering Change Control (Product Management module)

MTO manufacturers issue ECOs weekly, not annually. Customizations required:

• ECO approval routing (engineering → production planning → sales → customer approval)
• Production order updates (automatically apply ECO to open jobs)
• Revision comparison reports (show changes between BOM versions)

4. Scheduling (Planning module)

Standard MRP assumes infinite capacity. MTO requires:

• Constraint‑based visual scheduling (drag‑and‑drop operations across work centers)
• Customer commitment dates (schedule backwards from promised delivery)
• Bottleneck work center dashboards (real‑time load vs capacity)

5. Inventory Control

MTO inventory challenges include customer‑supplied material (CSM) and project‑specific purchased items. Customizations:

• CSM tracking (material owned by customer, tracked separately)
• Job‑allocated inventory (reserved for specific job, not available for others)
• Kitting automation (auto‑pick materials when job released)

6. Quality Assurance

MTO quality requirements vary by job. Customizations:

• Job‑specific inspection plans (different tests per customer)
• Certificate of Analysis (CoA) generation (automatically from test results)
• Non‑conforming material workflows (disposition by job, not generally)

7. Supply Chain Management

MTO procurement needs:

• Vendor RFQ integration (auto‑send spec to qualified vendors, compare quotes)
• Drop‑ship workflows (vendor ships direct to customer, records in Epicor)
• Long lead time material alerts (flag purchases required before job release)

8. Financial Management

MTO costing and billing customizations:

• Progress billing (invoice by percentage complete, milestone, or shipment)
• Job cost forecasting (estimate remaining cost vs actual to date)
• Retainage tracking (hold percentage of invoice until customer acceptance)

How to Customize Epicor for Make‑to‑Order Manufacturing: Step‑by‑Step

Step 1: Map Your MTO Manufacturing Workflows

Customization without workflow mapping creates fragmented, unusable systems. Spend 2‑4 weeks documenting current state.

Workflow mapping template:

Deliverable: Process flow diagrams for quote‑to‑cash, engineering‑to‑production, and procurement‑to‑payment.

Step 2: Analyze Production Bottlenecks Using Epicor Data

Use Epicor standard reports to identify where customization delivers highest ROI.

Run these reports before customizing:

• Job queue time report – Average days between job creation and first operation start
• Engineering change frequency – Number of ECOs per job, average processing time
• Quote conversion rate and time – Percentage of quotes converted to jobs; average conversion days
• Job cost variance – Estimated vs actual material, labor, outside processing by job type

Prioritize customizations that address the largest variance. Example: If job cost variance exceeds 15%, focus on real‑time labor and material tracking customizations first.

Step 3: Configure BPM Automation for Quote‑to‑Job Conversion

BPM (Business Process Management) is Epicor’s low‑code automation engine. Create rules that trigger on data events.

Example BPM: Auto‑create job from approved sales order

Trigger: Sales order status changes to “Approved” AND Order Type = “MTO”

Conditions: Order line has non‑blank “Customer Spec” custom field

Actions:

1. Create Job record (copy Job Name = Sales Order Number + “-JOB”)
2. Create BOM from Sales Order line items (set material quantity = order quantity)
3. Create Operations based on default routing (modify later per job)
4. Set Job Status = “Planned”
5. Assign to production planner by work center load (custom function)

Epicor implementation path: System Management → Business Process Management → Create New BPM → Data Directive on Sales Order table → After Update event

Expected outcome: Job created within 2 seconds of sales order approval. Zero manual data entry. 30 minutes per job saved.

Step 4: Customize Dashboards for Real‑Time Production Visibility

Epicor Kinetic dashboards use Kinetic UI and can be customized without code.

Dashboard 1: Production Control (Planner view)

Cards to include:

• Jobs released today vs target (red/yellow/green)
• Work center load (capacity chart by center for next 2 weeks)
• Late jobs (jobs with scheduled finish date > customer promise date)
• Material shortages (jobs waiting on PO receipts)

Dashboard 2: Job Cost vs Estimate (Management view)

Components:

• Jobs over/under estimate (table: Job #, Estimate ,Actual,Actual, Variance %, Reason code)
• Labor efficiency (actual hours vs standard hours by department)
• Material usage variance (actual quantity issued vs BOM quantity)

Dashboard 3: Customer Order Status (External portal or sales view)

Show customers:

• Job progress (%) by operation
• Estimated ship date (real‑time)
• Quality inspection results (pass/fail per test)
• Invoice status and payment due date

Epicor implementation path: Application Studio → Dashboards → New Dashboard → Add data views from existing BAQs (Business Activity Queries) or create new BAQs.

Step 5: Integrate MES Systems for Shop Floor Visibility

Standard Epicor lacks native real‑time production data. MTO manufacturers need MES integration for accurate job costing and scheduling.

MES integration options:

Minimum viable MES customization for MTO:

1. Create custom data collection entry screen (Application Studio) for shop floor terminals
2. Add barcode scanning for job, operation, employee, quantity
3. BPM rule: When labor transaction posted, recalculate job remaining hours and update schedule
4. Dashboard showing real‑time job progress by operation

Expected outcome: Labor and material reporting accuracy improves from 70‑80% (manual entry) to 95‑99% (barcode/MES). Job cost variance drops from ±20% to ±5%.

Step 6: Automate Engineering Change Orders (ECO)

ECO automation is the highest‑ROI customization for engineer‑to‑order manufacturers.

ECO workflow customization:

Trigger: Engineering Change Order created (ECO header record)

BPM rule actions:

1. Send notification to affected departments (sales, production planning, purchasing, quality)
2. Identify open jobs using the revised part/revision (SQL query across open jobs)
3. For each open job:
   • Create task for production planner: “ECO #12345 affects Job #67890 – review changes”
   • If ECO is “critical” (flag set), auto‑pause job operations (set status = “On Hold – ECO Review”)
   • Generate job change order (JCO) document comparing old vs new BOM/operations
4. Update future jobs (jobs not yet released) automatically with new revision
5. Log ECO in audit trail with timestamp, approver, affected jobs

Custom BAQ for ECO impact analysis:

Create Business Activity Query showing:

• Part number
• Current revision
• Open jobs using this part
• Job status (planned, released, started, completed)
• Customer commitment date

Expected outcome: ECO processing time reduces from 2‑5 days to 2‑4 hours. Production errors caused by missed ECOs drop to near zero.

Step 7: Optimize Job Costing with Real‑Time Actuals

Standard Epicor job costing updates in batches (daily or weekly). MTO requires job‑level visibility in real time.

Job costing customizations:

Custom field additions (Application Studio):

BPM rule: Recalculate job estimate on labor posting

Event: Labor transaction posted to job operation

Action:

1. Calculate actual hours to date for this operation
2. Calculate actual hours to date for entire job (sum all operations)
3. Calculate remaining hours = original estimate – actual
4. Update job field “Estimated Remaining Hours”
5. If remaining hours < 0 (over budget), send alert to production manager

Job cost dashboard (real‑time):

Visualize for each active job:

• Budgeted cost (original estimate)
• Actual cost to date (labor + material + subcontract + overhead)
• Committed cost (POs not yet received)
• Forecast at completion (actual + committed + estimate to complete)
• Variance (forecast – budget) and percentage

Expected outcome: Job cost variance identified within hours of overage, not weeks after job completion. Corrective action taken before job loses money.

Step 8: Deploy KPI Monitoring and Production Alerts

Proactive alerts prevent schedule slips and cost overruns.

Alert configuration (BPM + Task Scheduler):

Epicor implementation path: BPM Data Directive for real‑time alerts; Task Scheduler for daily/weekly summary reports.

Expected outcome: Exceptions managed in hours, not days. Production planners focus on problem jobs, not hunting for them.

Epicor BPM Customization Examples

Example 1: Automated Quote Approval for High‑Value MTO Jobs

Trigger: Quote total > $100,000 OR Quote contains non‑standard terms

BPM Conditions: Quote total > 100000 OR Quote custom field “NonStandardTerms” = True

Actions:

1. Set Quote Status = “Pending Approval”
2. Send approval request to Sales Director (email with link to quote)
3. If approved, set Status = “Approved” and notify sales rep
4. If denied, set Status = “Denied” and log reason
5. If no response in 48 hours, escalate to VP of Sales

Example 2: Automated Job Release Based on Material Availability

Trigger: Job status changed to “Ready to Release” (custom status)

BPM Conditions: All job material lines have “On Hand” >= “Required Quantity” AND Job operation “Engineering Complete” = True

Actions:

1. Print job traveler and pick list
2. Set Job Status = “Released”
3. Send notification to production scheduler
4. Reserve materials (allocate to job, reduce available inventory)

Example 3: Production Exception Notification

Trigger: Job operation quantity completed < planned quantity (scrap)

BPM Conditions: Scrap quantity > 0 AND scrap quantity > BOM scrap factor

Actions:

1. Create Quality Issue record linked to job
2. Send email to quality manager with job #, operation, scrap quantity, reason code (if entered)
3. If scrap quantity > 10% of planned quantity, set job status = “On Hold – Quality Review”

Example 4: Engineering Change Customer Notification

Trigger: ECO approved AND ECO line “Customer Notification Required” = True

Actions:

1. Generate customer change order document (PDF from report)
2. Send email to sales rep: “ECO #12345 requires customer approval – attach document”
3. Create task for sales rep: “Get customer signature on ECO”
4. When customer approval logged (custom field on ECO), update production jobs

Example 5: Vendor RFQ Automation

Trigger: Purchase requisition created for MTO job

Conditions: Requisition line “Material Type” = “Custom Fabrication” (requires quote)

Actions:

1. Identify qualified vendors from approved vendor list by commodity
2. Generate RFQ email with part drawing (attached from job document storage)
3. Set RFQ due date = today + 5 days
4. When vendor quotes received, update requisition with quoted price and lead time
5. If only one quote received, escalate to purchasing manager

Epicor Dashboard and Reporting Customization

Executive Dashboard (CFO, Plant Manager)

Production Supervisor Dashboard

• Work center load Gantt – Visual schedule with color coding (green = on schedule, yellow = at risk, red = late)
• Job queue by priority – Sort by customer promise date, estimated hours remaining
• OEE (Overall Equipment Effectiveness) – Availability × Performance × Quality by work center
• Top 10 late jobs – With reason codes and recovery plan links

Job Cost Dashboard (Estimator, Controller)

• Estimate vs actual waterfall – Starting from original estimate → approved changes → actual → variance
• Cost breakdown by category – Material, labor, subcontract, overhead, outside processing
• Trend chart – Job margin percentage by month, by customer, by product family
• Alert log – All cost overrun notifications for the job

Report customization recommendations:

• Use SSRS (SQL Server Reporting Services) for complex, multi‑page reports (job travelers, pick lists, invoices)
• Use Kinetic Dashboards for real‑time operational views
• Use Power BI for executive analytics with external data sources (sales forecasts, market trends)

Epicor MES Integration for Shop Floor Visibility

Epicor’s native MES add‑on provides real‑time data collection. For custom manufacturers, configure these MES modules.

Epicor MES modules (configure, not custom code):

Integration without full MES (REST API approach):

For manufacturers with existing MES or custom shop floor systems:

1. Expose Epicor REST endpoints for job operations, material requirements, labor posting
2. From MES, call Epicor API to:
   • Get list of jobs scheduled for work center today
   • Post labor transaction (employee, job, operation, hours, quantity)
   • Post material consumption (scan barcode, decrement inventory)
3. From Epicor, call MES API to:
   • Send updated schedule (when job dates change)
   • Send engineering changes (when ECO released)

Epicor API setup: System Management → REST Services → Configure endpoint → Generate API key → Test with Postman

Expected outcome: Shop floor data entry time drops from 5 minutes per transaction to 15 seconds (barcode scan). Data accuracy exceeds 99%.

Epicor Automation Strategies for 2027

AI‑assisted demand forecasting for MTO

Standard MTO has no historical demand for identical products. However, Epicor 2027 can analyze component‑level usage patterns.

Customization: Create BAQ that aggregates material usage by commodity code across all jobs. Use Epicor Data Analytics (embedded Power BI) to forecast replenishment for common materials (fasteners, raw stock, consumables).

Predictive scheduling

Customization: BPM rule that recalculates job estimated completion date based on current work center load + material availability + historical operation times.

Example: When job released, BPM calls custom function that:

1. Queries current load at each required work center
2. Queries material availability dates from POs
3. Calculates earliest start date for each operation
4. Sets job scheduled dates accordingly
5. If projected completion > customer promise date, flag for planner review

Digital manufacturing / smart factory integration

For advanced customizers, connect Epicor to:

• CAD/CAM systems (SolidWorks, AutoCAD) – Automatically generate BOM and routing from CAD assembly
• CNC machine monitoring – Capture actual cycle times, tool wear, maintenance alerts
• Warehouse robotics – Autonomous material movement triggered by job release

Epicor Automation Studio (low‑code RPA): Automate repetitive data entry tasks – printing job travelers, emailing ship notices, generating invoice PDFs – without BPM or code.

Common Epicor Customization Mistakes

Epicor Customization Cost Expectations

One‑time customization costs (U.S. dollars, 2027):

Ongoing annual costs:

• Epicor maintenance (20% of license cost) – $10k‑$50k typical
• Internal ERP administrator – $70k‑$120k salary (0.5‑1 FTE)
• Consultant support retainer – $10k‑$30k for priority response
• Hosting/cloud – $20k‑$100k depending on environment

ROI calculation example (mid‑sized MTO manufacturer, $20M revenue):

Less one‑time customization cost ($150k) = payback period 4 months. Five‑year ROI > 1,500%.

Best Practices for Long‑Term Epicor Success

1. Establish a customization governance process

• Change request form – Business case, estimated hours, priority, sponsor
• Weekly review – Epicor Change Advisory Board (IT, operations, finance, sales)
• Monthly backlog prioritization – Align with business strategy

2. Maintain a customization inventory

Document each customization:

3. Schedule regular Epicor health checks

Quarterly review:

• BPM execution logs (errors, timeouts)
• Database performance (slow queries, blocking)
• User adoption metrics (% of users active, feature usage)
• Security audits (role review, inactive accounts)

4. Train power users in low‑code tools

Invest in Epicor training for 2‑3 internal super users:

• Epicor BPM Fundamentals (2‑3 days)
• Application Studio for Developers (2 days)
• BAQ and Dashboard Design (2 days)

Internal capability reduces consulting costs by 50‑70% after first year.

5. Participate in Epicor user groups

• Epicor User Webinar Series
• Epicor Community forums
• Regional Epicor user group meetings
• Epicor Insights conference (annual)

Learn what customizations other MTO manufacturers have built – and what to avoid.

Frequently Asked Questions

Can Epicor support engineer‑to‑order (ETO) manufacturing?
Yes. Epicor Kinetic includes ETO capabilities through customizations: dynamic BOMs, engineering change workflows, project‑based job costing, and CAD integration. Standard Epicor supports make‑to‑order; full ETO (unique engineering per job) requires the customizations described in this guide (ECO automation, dynamic BOMs, customer‑spec tracking). Many ETO manufacturers successfully run Epicor with 100‑300 hours of initial customization.

Is Epicor Kinetic better than legacy Epicor ERP for MTO?
Yes. Epicor Kinetic (version 10+) provides low‑code customization tools (Application Studio, enhanced BPM) that reduce development time by 50‑70% compared to legacy Epicor 9. Kinetic also offers cloud deployment, REST APIs, and modern dashboards. For new MTO implementations in 2027, choose Kinetic. For existing Epicor 9, evaluate migration cost vs benefit.

What customization tools are available in Epicor?
Epicor offers five primary customization tools: (1) Business Process Management (BPM) for workflow automation, (2) Application Studio for UI changes, (3) BAQ (Business Activity Queries) for data extraction, (4) Kinetic Dashboards for visualization, and (5) REST API for external integration. C# extensions and direct SQL modifications are available but not recommended for most customizations due to upgrade risks.

How much does Epicor customization cost?
Simple customizations (BPM approval rule, dashboard) cost $2k‑$10k. Complex customizations (MES integration, ECO automation) cost $20k‑$100k. Full MTO transformation package (BPM + dashboards + MES + ECO + API integrations) ranges $120k‑$300k one‑time. Hourly rates for Epicor consultants: $150‑$300/hour. Internal staff time adds $50‑$100/hour opportunity cost.

Can Epicor integrate with MES platforms?
Yes. Epicor offers native MES add‑on (Epicor MES) with pre‑built shop floor data collection. For third‑party MES (Plex, Prodsmart, Tulip, etc.), use Epicor REST API for bi‑directional sync: send jobs/operations to MES, receive labor/material transactions back. Integration cost typically $30k‑$100k depending on MES platform and complexity.

Does customization affect future Epicor upgrades?
It depends. Low‑code customizations (BPM, Application Studio, BAQs, dashboards) are designed to survive upgrades – Epicor’s upgrade tools preserve them. Custom C# code, direct SQL modifications, and third‑party add‑ons may break on upgrade and require redevelopment. Always test upgrades in sandbox environment before production.

What is Epicor BPM?
Business Process Management (BPM) is Epicor’s low‑code automation engine. BPM rules trigger on data events (e.g., “after sales order saved”) and execute actions (send email, create record, update field, call external API). BPM requires no C# programming for 80% of use cases. Complex logic can use custom functions (C# snippets) but increases upgrade risk.

How long does Epicor customization take?
Simple BPM rules: 1‑2 weeks (design, test, deploy). Dashboard customization: 1‑3 weeks. MES integration: 6‑12 weeks. Full MTO transformation: 3‑6 months with dedicated internal team and consultant. Timeline varies significantly based on data quality, internal resources, and customization complexity.

Can Epicor automate production scheduling for MTO?
Partially. Epicor’s standard scheduling is MRP‑based (infinite capacity). For constraint‑based scheduling, manufacturers add Epicor Advanced Planning and Scheduling (APS) add‑on or third‑top systems (e.g., Preactor, PlanetTogether) integrated via API. Custom BPM rules can provide basic visual scheduling and bottleneck alerts without APS cost.

**Is Epicor suitable for small MTO manufacturers (under $10M revenue)?**
Yes, but with caveats. Epicor is a tier 2 ERP – implementation and customization costs ($100k‑$300k) may exceed value for very small shops. Consider lower‑cost alternatives (JobBOSS, E2, ShopVue) for sub‑$5M manufacturers. For $5M‑$10M MTO manufacturers with complex products and growth plans, Epicor with targeted customization delivers strong ROI.

Conclusion

Customizing Epicor for make‑to‑order manufacturing in 2027 transforms a standard ERP into a competitive weapon. The strategies and examples in this guide – BPM automation for quote‑to‑job conversion, dashboards for real‑time production visibility, MES integration for shop floor accuracy, and ECO automation for engineering change control – deliver measurable improvements: 20‑40% lead time reduction, 30%+ job cost accuracy improvement, and 4‑6 month payback periods.

Key takeaways:

• Start with workflow mapping, not coding. Understand current processes before automating. Most MTO manufacturers discover 30‑50% of “required” customizations become unnecessary after process improvement.
• Prioritize high‑ROI customizations first. Quote‑to‑job automation and ECO workflows deliver the fastest payback (4‑6 months). Dashboards and reporting follow (6‑12 months). Full MES integration delivers strong ROI but requires larger upfront investment.
• Use low‑code tools (BPM, Application Studio, BAQs) for 80% of needs. Avoid custom C# and direct SQL modifications except for unique, competitive‑advantage logic. Low‑code customizations survive Epicor version upgrades; custom code often breaks.
• Budget for ongoing governance and training. The most successful Epicor MTO shops dedicate 0.5‑1 FTE to ERP administration, maintain a customization inventory, and train internal power users in low‑code tools.

Strategic recommendations for 2027:

1. If you are implementing Epicor for the first time: Use the standard MTO templates in Epicor Kinetic (SuiteSuccess manufacturing). Customize only after 3‑6 months of live use. What you think you need before go‑live is usually wrong.
2. If you have legacy Epicor (version 9 or earlier): Evaluate migration to Kinetic for low‑code customization benefits. Migration cost $50k‑$150k typically pays back in 12‑18 months through reduced consulting and maintenance costs.
3. If you are already on Epicor Kinetic: Audit your current customizations. Decommission unused ones. Convert high‑risk custom code to BPM where possible. Document everything. Your future self (and successor) will thank you.

The future outlook (2027‑2028): Epicor continues investing in AI‑assisted customization (automated BPM recommendations, predictive scheduling). MTO manufacturers who build internal low‑code capability today will outcompete those dependent on external consultants. The gap between customized Epicor and “vanilla” ERP will widen – and so will the competitive advantage of those who invest wisely in customization.

Final recommendation: Customize Epicor for MTO with discipline. Target the 20% of workflows that cause 80% of your pain. Automate with low‑code tools. Measure before and after. Then move to the next 20%. This iterative, data‑driven approach delivers sustainable competitive advantage without the risk of massive, multi‑year “digital transformation” projects.

Ready to begin? Start with Step 1: Map your MTO manufacturing workflows. Print this guide. Gather your production, engineering, and sales teams. Walk through each step. The path to 30% shorter lead times and 5% higher margins starts today.