Epicor Customization Code Review Checklist
Customizations in Epicor reach into the same transactions as standard code, so a careless one can slow saves, block imports or damage data. This checklist gives a second developer a repeatable way to review before promotion.
0 of 36 items complete
13 critical items still open - these are the highest-risk gaps.
Design and documentation
Safety and data integrity
Performance
Security and compliance
Testing and promotion
Every critical item should be met before promotion. Anything else not met needs a recorded reason and an owner.
Customization review
An optional independent review of your Epicor custom code and directives.
Optional. The tool and every export work without this. No spam.
How to use the checklist
Work through each group with the author, ideally in a short review session. Mark each item as met or not met, and record who will fix those that are not. Critical items protect data and availability and should be met before anything goes to live. Export the completed checklist and attach it to the change record.
- Review with the author present
- Fix critical items first
- Record reasons for exceptions
- Attach the result to the change
Safety for non interactive callers
Epicor logic runs not only from screens but from DMT, scheduled tasks, web services and integrations. A message that waits for a user click is fine at a screen and fatal in an import. Review each directive and code block by asking who else calls this method and what happens when no human is there.
Performance and upgrade
Queries in loops, unfiltered reads of large tables and slow external calls inside a save are the usual causes of complaints. Check them with realistic data volumes. For upgrade, favour documented approaches, record dependencies on specific fields and keep an export of each customization so it can be reapplied or rebuilt.
Common mistakes
Reviews often focus on whether code works for the happy path and skip security roles, large volumes and import behaviour. Another is reviewing only the code and not the conditions that trigger it. Review both, and make the checklist part of the promotion process so it is not optional.
Frequently Asked Questions
Who should perform the review?
A second developer or technical lead who did not write the change, together with the process owner for the acceptance part. Independence matters: authors tend to test the paths they thought about and miss the ones they did not.
Do small directives need a full review?
Use judgement. Directives that write data, block saves or run on busy methods deserve the full list. Simple read only notifications can use the critical items only. Record which level you applied so the decision is traceable.
How does this help with upgrades?
Documented, narrow and well tested customizations are easier to retest and rebuild. The checklist also forces you to record dependencies and keep exports, which saves discovery time when you move to a newer version.
Can the checklist be extended?
Yes. Add items for your own standards, such as logging conventions, naming rules or approval flows. Keep the critical group small so it stays meaningful, and review the list after any production incident to see what it should have caught.
If you want an independent review of your Epicor customizations before an upgrade, Netray can assist.
Related Tools
Epicor BPM Directive Design Template
A fill-in design document for BPM method and data directives covering trigger, conditions, actions, testing and rollback.
EpicorEpicor Customization Change Request Template
A change request form for Epicor customizations that captures the business need, impact, test plan and approvals before anyone opens the tool.
EpicorEpicor BPM Directive Inventory Worksheet
Inventory your BPM directives, score complexity and retest effort, and see total upgrade retest hours. Export to Excel.
EpicorEpicor UAT Test Script Worksheet
An editable UAT script for Epicor with expected results, tester, status and defect counts. Track pass rate and export to Excel.
More Epicor tools
See all- Epicor Kinetic Customization Change Request Form Template
- Epicor Kinetic Go-Live Cutover Plan Template
- Epicor Kinetic User Access Request Form Template
- Epicor Kinetic BPM Directive Inventory Worksheet
- Epicor Kinetic Scheduled Task Register Worksheet
- Epicor Kinetic Custom Report Inventory Worksheet
- Epicor Kinetic Data Migration Mapping Worksheet
- Epicor Kinetic Data Load Effort Calculator
- Epicor Business Object Services Reference
New to Epicor ERP? Start with the Epicor ERP guide and toolkit, or plan with Training Path Builder, ERP Certification Study Planner, Upgrade Path Planner.
Keep exploring
Free tools
- Epicor Kinetic Customization Change Request Form TemplateA fill-in change request form for Application Studio customizations, BPM directives and Epicor Functions, with test and rollback sections.
- Epicor Kinetic BPM Directive Inventory WorksheetAn editable register of your Epicor directives with owner, purpose, risk score and review date, exportable to Excel.
- Epicor Customization Change Request TemplateA change request form for Epicor customizations that captures the business need, impact, test plan and approvals before anyone opens the tool.
ERP fixes and how-tos
- Epicor BPM Data Directives and the Workflow Designer: When to Use Each, With an ExampleEpicor BPM data directives versus method directives, how the BPM Workflow Designer canvas works, and a worked example that blocks a save when data is missing.
- Epicor BPM Custom Code Examples: Set, Query, Validate, Call and RefreshWorking Epicor Kinetic BPM custom code examples: set a field, query the database, validate input, call a service, and refresh data after changes.
- Preserving Customizations When Upgrading to Epicor KineticMoving Epicor 10 classic customizations to the Kinetic web UI is a conversion, not an automatic carry-over. Here is the checklist for what survives, what needs rework, and how to sequence the upgrade.
Guides
- Epicor vs Infor: Should You Switch ERP Platforms?Compare Epicor Kinetic vs Infor CloudSuite for manufacturing. Functional analysis, migration costs, and decision framework for switching platforms.
- AI-Powered Code Review for ERP CustomizationsReview ERP customizations with AI agents detecting code quality issues, upgrade risks, security vulnerabilities, and performance problems in custom ERP code.
AI on your ERP
- AI for Epicor Kinetic, Beyond What Prism CoversAdd AI to Epicor Kinetic beyond Prism: private LLM over BAQs, BPM data, and REST v2, on-prem or private cloud, with honest guidance on when Prism already covers you.
- Private AI for Epicor Kinetic Cloud, Outside the Multi-Tenant BoundaryRun a private LLM on Epicor Kinetic private cloud or Kinetic Cloud data via BAQs, REST v2 and Data Fabric, keeping sensitive manufacturing data off shared AI.
Integrations
- How to add WhatsApp to Epicor KineticHow to connect WhatsApp Business to Epicor Kinetic: REST and BPM triggers, template messages, opt-in rules and two-way replies that post back to the ERP.
- How to use ChatGPT with Epicor KineticConnect ChatGPT to Epicor Kinetic through a custom GPT with Actions, an exported dataset, or a private gateway. Covers BAQs, auth, data controls and when to go private.
Software
- Epicor KineticEpicor Kinetic explained for manufacturers: modules, REST API, BAQs, deployment, strengths, limits and alternatives to compare before choosing or upgrading.
- Epicor CPQEpicor CPQ is a cloud configure-price-quote product with visual 3D configuration for manufacturers. Modules, ERP integrations and alternatives explained.