In today’s global economy, tariffs can shift overnight — and for distributors, those changes ripple quickly across pricing models, supplier relationships, and customer expectations. While tariffs are nothing new, the pace and complexity of trade updates in recent years have made it harder for teams to react quickly and plan confidently.
Strategy: Establish contingency plans for sourcing and logistics
Strategy: Collaborate closely with trade compliance experts and consultants
The Tariff Challenge: Limited Visibility, High Stakes
Tariff exposure often hides in plain sight. Vendor records might show countries of origin or product categories, but few ERP systems offer a clean, consolidated view of which suppliers are likely to be impacted by new tariffs — and what those impacts could mean financially.
Procurement and finance teams are often left piecing together spreadsheets, customs data, and supplier intel to make urgent decisions. And by the time a potential risk becomes clear, the cost implications may already be felt.
Oversight, Strategy, and Control: Three Ways to Get Ahead of Tariff Risk
1) Invest in Strategic Supplier Diversity
By diversifying your supplier base across multiple countries or regions, you reduce reliance on any one source that may become tariffed. Your ERP system should help track and categorize suppliers by region, and your team should regularly audit where your critical parts or products are coming from.
2) Improve Cross-Functional Visibility
Tariff risk isn’t just a procurement issue — it touches pricing, forecasting, inventory, and even customer experience. Integrating trade visibility into dashboards accessible to operations and finance leadership is key. This means making tariff exposure a regular part of your supply chain reporting, not a fire drill when changes hit.
3) Use Purpose-Built Tools for Trade Risk Management
Rather than rely solely on generic ERP reports, modern distributors are turning to specialized tools that augment their ERP environment. These tools often bring in external data, enrich vendor records with AI insights, and suggest actionable strategies like pre-purchasing inventory or temporarily shifting pricing models.
If you use Epicor Prophet 21, there’s a new solution available that may be worth exploring: the Recurrency Tariff Manager.
This lightweight dashboard plugs directly into your P21 system and uses AI to analyze your vendor list for likely tariff exposure. In under 15 minutes, it can show you where you’re at risk — and help you take action, whether that means sourcing alternatives, adjusting purchasing, or planning pricing changes.
It’s a smart way to bring clarity into a complex challenge — without requiring months of development or a full system overhaul.
Managing tariff risk isn’t just about compliance or cost control. It’s about building resilience into your operations — so that when change comes, you’re prepared. By improving visibility, sharing insights across teams, and using the right tools, you can turn tariff challenges into strategic opportunities.
If you don’t want to explore things like how to manage tariff risk in distribution ERP without industry experts helping you the mitigate risks, our team at EstesGroup is always available to help you make sense of your data and identify the right tools for your ERP and business strategy.
Get valuable cloud technology & ERP insights delivered directly to your inbox. Receive exclusive updates, practical guidance, and expert tips tailored specifically for your business.
As of version 2026.1, Epicor’s Kinetic ERP will no longer contain a smart client deployment, and the user base will communicate with the application exclusively through a web browser.
Depending on the extent of customizations to the UI and to components like dashboards, conversions may take a significant amount of time in modification and testing.
That said, what are key differences?
The user communicates with Epicor in a new User Interface (UI)
Runs in a browser instead of a fat client
Runs on web-centric devices—not limited to a traditional computer screen and now available on tablets, phones, etc.
Epicor components and business objects can be accessed through a mobile app—not limited to Epicor’s own apps
UI can be customized, but has no C# code, so heavy lifting must be off-loaded to BPMs and Functions
So you want to know more Epicor Kinetic UI tips and tricks for when the rubber meets the road? The EstesGroup Epicor Kinetic consulting team recently covered some technical areas of concern that can help you migrate to a better place moving forward.
In helping customers move to Kinetic, we’ve encountered countless requests for various items of the Epicor Kinetic UI “tips and tricks” variety—something like: “Can Classic dashboards be automatically converted to Kinetic?”
The answer is “yes, but…”
An easy way to generate the Kinetic application is via the Tools/Deploy Dashboard option. You can preview the dashboard or generate the application when you’re satisfied with it. This does convert a lot of things well, but you’ll notice something immediately with the trackers when you preview the Kinetic dashboard.
The filter field(s) in the very first tracker will appear in a slide-out panel when the dashboard opens. Filtering may or may not actually work. Notice there is no OK button in this example.
Other panels have had different issues. And once the panel is discarded, the user can never access it again until the dashboard is restarted. Also, if there are multiple queries/trackers on the dashboard, the subsequent trackers will never fire. It might seem disheartening at first blush, but there are workarounds.
A relatively easy way to do this is this procedure in Dashboard Entry:
Copy the dashboard to avoid changing the original, perhaps add a “K” to the end of the dashboard ID, or some other scheme
Load the new copy of the dashboard
Delete all trackers on the dashboard
Preview the dashboard and make sure it runs okay, other than the missing trackers
Save the dashboard
Create the Kinetic application (Tools/Deploy/Application)
Open the new Kinetic application and add the trackers back in
Adding the trackers manually may sound like a lot of work, but it’s not too bad. Plus, you can add some nice functionality.
Need more guidance? Sign up to get our Ultimate Epicor Kinetic UI Tips and Tricks Guide!
GET THE GUIDE
Fill out the form below to receive your copy of Uplift Epicor Classic UI to Kinetic UI – Questions and Answers. We’ll send our help guide straight to your inbox so you can start planning your upgrade with confidence.
"*" indicates required fields
Stay Ahead with EstesGroup Insights
Get valuable cloud technology & ERP insights delivered directly to your inbox. Receive exclusive updates, practical guidance, and expert tips tailored specifically for your business.
No Native Handshake, No Problem: Making Epicor Kinetic and Prophet 21 Work Together
Running both manufacturing and distribution operations? You might find yourself juggling Epicor’s two flagship systems: Epicor Kinetic (for manufacturing) and Prophet 21 (for distribution). While these platforms weren’t designed to talk to each other out of the box, getting them to communicate doesn’t have to give your IT team nightmares.
Different ERP Systems, Different Strengths
Think of Epicor Kinetic as your manufacturing maestro – handling production schedules, materials, and shop floor activities with robust features for BOMs and shop floor control.
Meanwhile, Prophet 21 excels at distribution – managing inventory, supply chains, and sales orders with streamlined workflows designed specifically for distributors.
They’re like siblings raised in different households – related but with distinct personalities and skill sets. Both use Microsoft SQL Server behind the scenes but speak somewhat different languages when it comes to sharing information. Epicor Kinetic uses a service-oriented architecture with a comprehensive REST API, while Prophet 21 operates through its Middleware API with OData services for queries and transaction processing. So, how do you get Epicor Kinetic and Prophet 21 to join forces?
Option 1: Use Epicor’s Own Toolbox
Automation Studio: This low-code platform is embedded in both systems and lets you build “recipes” that automatically sync data between systems without heavy programming.
Integration Cloud: Epicor’s cloud solution offers pre-built connectors for both platforms, though P21’s connector has some limitations with filtering capabilities.
Option 2: Bring in a Mediator
Third-party platforms like DCKAP Integrator can bridge the gap with drag-and-drop simplicity and pre-built error handling.
Custom API integrations work well for companies with technical resources who need complete control over their data mapping.
Traditional EDI exchanges can handle batch transfers of orders and invoices when real-time sync isn’t required.
Best Practices for Using Kinetic and P21 Systems Together
If you’re taking on this integration project, keep these best practices in mind:
Divide and conquer: Let each system do what it does best – Epicor Kinetic for manufacturing, P21 for distribution.
Start simple: Use Epicor’s built-in tools before diving into custom development.
Establish clear rules: Decide which system “owns” which data (your “source of truth” for customers, inventory, etc.).
Map your journey: Document which fields need to sync, how frequently, and in which direction.
Test thoroughly: Simulate real-world scenarios to ensure the integration handles both successful transactions and errors gracefully.
Roll out gradually: Start with master data sync before tackling complex transactions.
Keep an eye out: Monitor your integration points and optimize as needed.
Case Study: Seamless Order-to-Manufacturing Flow
A metals distributor using Prophet 21 for sales and inventory acquired a fabrication company running Kinetic. Rather than forcing everyone onto one system, they integrated the two platforms:
Customer orders entered in P21 automatically create work orders in Kinetic.
As manufacturing progresses, status updates flow back to P21.
When products are completed, inventory is updated in both systems.
The sales team can provide real-time production updates without switching applications.
They used Epicor’s Automation Studio to build this workflow, allowing each division to keep using the software best suited for their operations while maintaining a single view of the customer order.
Result: Order fulfillment time decreased by 35%, and customer satisfaction scores jumped by 22%.
Case Study: Building Business Intelligence
A building materials company with manufacturing (Kinetic) and distribution (P21) divisions struggled with inconsistent reporting until they integrated their systems:
Sales data from P21 now automatically feeds production planning in Kinetic.
Inventory levels stay synchronized across both platforms.
Financial reporting consolidates data from both systems for accurate forecasting.
Result: Inventory carrying costs decreased by 18%, and the time to generate company-wide reports dropped from days to minutes.
Do you have a good reason to use Epicor Kinetic and Prophet 21 together?
EstesGroup is here to help! While Epicor didn’t design these systems to seamlessly integrate, new tools make connecting them entirely achievable. With the right approach, you can create a unified ecosystem that handles both manufacturing and distribution without missing a beat. The result? Less manual data entry, fewer errors, and a smoother operation from production floor to customer door.
It’s a natural human tendency to put off unpleasant tasks like mowing the yard, taking out the trash, or addressing the deadline to move entirely from Epicor’s Classic user interface to their new browser-based Kinetic framework.
Entirely understandable, the attachment to years’ worth of carefully tailoring the ERP environment to your company’s needs is hard to give up. Just when you’ve gotten it “just right,” you’re being reset back to level 1, like a video game that suddenly loses all the lives you’ve built with great effort and ingenuity.
But like a lot of things in life, change doesn’t have to be bad. For one, it gives us a chance to reevaluate the choices we’ve made in the past.
That process you installed ten years ago—is it still meeting your needs? Could it be ditched or improved? Is there a better way?
And some of the modifications done to your system might have been tortured into the old user interface in ways that weren’t optimal, but were a way you COULD get what you wanted. And that code was often s-l-o-w.
Since the latter days of ERP10, Epicor has been introducing new tools like the REST API and Epicor Functions that give us better ways to interact with Epicor Business Objects and better places to put heavy-lifting development on the server side where it belongs.
And all your old work isn’t lost. BPMs still work the same way. Dashboards, and even some screen customizations, can be converted with some tweaking. Yes, all that C# code will disappear, but you can convert most all of its functionality to better forms in the new customization layers and functions.
The secret weapon in this fight?
prep·a·ra·tion – the action or process of making ready or being made ready for use or consideration
The time to begin the journey is likely not a month before the deadline, for several reasons.
The learning curve for transitioning from old to new can be steep. Although many of the concepts are the same or similar between the two environments, they can be expressed in very different ways.
Before starting to convert a Classic application’s customization that has very much complexity, you’ll likely want to document what the old one does and how it does it, complete with data accessed, UD fields added, C# script processes, and so on. Many Epicor ERP installations are not well documented, and this is a good excuse to do a good thing.
Evaluating the old processes and decisions about whether to promote them or instigate some redesign will take a while.
And then, the actual conversion work can be a slow slog if you have a lot of it to do.
All this might seem insurmountable, if not merely daunting. But there’s still time—the first deadline is still over a year away at this writing.
Gather your resources. Identify your team. Get support from management. Make a plan—and realize it might evolve. And as if eating an elephant, take one bite at a time.
Epicor has good documentation for their Application Studio environment via the Help information accessed from the Kinetic menu. Going to Insights will help, as will joining online user groups like www.epiusers.help.
As always, we’re here you help when you need it. The EstesGroup ERP and IT teams will extend assistance in whatever form you need, a jumpstart, specific application conversions, or project management.
Just give us a shout when you need us.
What does Epicor 2026.1 mean for your business?
EstesGroup is a leading Epicor ERP consultancy that blends elite Epicor Kinetic expertise with cutting-edge technology, AI, and cloud services. There are a bundle of technical challenges to work through and decisions to make when uplifting any custom elements of your Epicor Classic UI to Kinetic. Get your questions about Epicor 2026.1 answered now by our ERP experts. Don’t miss out on insights gained in our “Uplifting Epicor Classic UI to Kinetic” webinar with industry experts.
What are the hardware system requirements for Epicor Prophet 21?
Enterprise Resource Planning (ERP) systems like Epicor Prophet 21 (P21) play a crucial role in streamlining operations and driving business growth in the distribution industry. However, the hardware requirements for on-premise ERP deployments present an ongoing challenge, constantly evolving with technological advancements and software updates.
Epicor P21 – Background and Evolving Capabilities
Epicor positions Prophet 21 as a solution “made by distributors for distributors.” As the distribution industry continues to change, P21’s capabilities expand to meet new challenges. These include advanced Customer Relationship Management (CRM), Order Management, eCommerce integration, and Business Intelligence features. With each new version and feature set, the demands on hardware infrastructure often increase.
The Moving Target of Hardware Requirements
The performance of on-premise Epicor P21 systems is intrinsically tied to the underlying hardware infrastructure. As the software evolves, so do its hardware needs. This presents a significant challenge for IT teams, who must continually reassess and potentially upgrade their hardware to maintain optimal performance.
Key Things to Consider When Addressing Hardware System Requirements for Epicor Prophet 21
While specific requirements may shift, some general hardware considerations for P21 deployment include the following:
Servers: Both database and application servers need regular evaluation to ensure they meet the latest requirements.
Processing Power: The demand for more powerful, multi-core processors (such as the Intel Xeon series) tends to increase over time.
Storage: The shift towards faster storage solutions like SSDs and advanced RAID configurations is ongoing.
Memory: RAM requirements typically trend upwards with each major software release.
Networking: As more features become web-based or cloud-integrated, network infrastructure becomes increasingly critical.
Back to the Basics of P21
Servers
Database Server: Responsible for managing and storing data that the ERP system uses; key features for optimal functionality and performance include robust storage and memory, ensuring users can quickly access and process data
Middleware/Web Applications Server: Essential for organizations that utilize P21’s web-based components; requires minimal to moderate processing capability and memory, depending on the number of users
Processing
Server CPU capabilities determine performance
Multi-core processors are recommended
Storage
Solid-State Drives (SSDs) perform the best
Redundant Array Independent Disks (RAID 10) enhance data processing
Memory
Adequate RAM is essential for operation
For the Database Server, 32 GB RAM or greater is recommended
For the Web Server, 8 GB RAM or more is needed, depending on the number of users
Networking
Web-based or cloud-integrated network infrastructure becomes necessary
Scalability has become one of the greatest challenges when addressing hardware system requirements for Epicor Prophet 21.
One of the biggest challenges in on-premise ERP deployment is planning for scalability. As businesses grow and P21 capabilities expand, the hardware infrastructure must be able to scale accordingly. This often requires significant foresight and investment, as upgrading hardware can be costly and disruptive.
Cloud vs. On-Premise ERP: A Shifting Landscape
The evolving nature of hardware requirements is pushing many organizations to reconsider the total cost of ownership for on-premise deployments. Cloud-based solutions, which offload the burden of hardware management and upgrades, are becoming increasingly attractive. However, this shift introduces new considerations around data security, customization, and control.
Staying Ahead of the Cloud
To manage the ever-changing hardware requirements for on-premise P21 deployments, organizations should do the following:
Maintain close communication with Epicor about upcoming releases and their potential hardware impacts.
Regularly audit current hardware against the latest requirements.
Develop a long-term hardware upgrade strategy that aligns with both business growth projections and P21’s development roadmap.
Consider hybrid approaches that leverage both on-premise and cloud resources to balance performance, cost, and flexibility.
The hardware system requirements for Prophet 21 deployments are not static.
They represent an ongoing challenge that requires constant attention and adaptation. While this document outlines some general considerations, it’s crucial to recognize that these may change rapidly. Organizations must stay informed about the latest requirements, plan proactively for hardware upgrades, and continually evaluate their deployment strategy to ensure they’re maximizing the benefits of their P21 system while managing the complexities of evolving hardware needs.
A warning message that most SYSPRO users will commonly see is the “Operator already logged in” prompt. Under normal circumstances, this message means exactly what it says! The operator is already signed in.
However, the error message can appear for other reasons that may be puzzling to the user. It is most typically associated with users not exiting SYSPRO through normal means (crashes, forced computer shutdown, etc). It is good for both the ERP administrator as well as the end-users to know what this error means and why it may appear despite the user not being signed in.
What does this “SYSPRO Error Message – Operator Already Logged In” message mean?
SYSPRO’s database has a table called AdmOperator. Inside this table there is a column used to indicate whether a SYSPRO operator is currently signed in. The column value is set to “Y” when a user signs in and is cleared when SYSPRO is closed out normally by the user. The “Y” value can linger in the database if the user fails to close out of SYSPRO “gracefully”.
In that case, the “Operator already logged in” message will appear. The user has the option to proceed which will clear any lingering operator entries. If the user is in fact already signed in, any previous session is terminated by the system.
What causes this “Operator already logged in” message?
Besides the intended circumstance of the operator already being signed in on another computer, the message also appears if a user fails to close out of SYSPRO “gracefully”. Examples of this could include:
The user shuts down their PC while SYSPRO was running.
The user closes SYSPRO forcefully using the Windows Task Manager. This is common in the event of SYSPRO freezing or crashing.
If the user closes their web browser when using SYSPRO Avanti without using the logout functionality in the application.
Some of these events may also result in “Unknown Processes” lingering in SYSPRO. These will have to be closed out using administrative tools in SYSPRO. To learn about these processes, see our article on Handling Unknown Processes in SYSPRO.
So, what should you do about this message?
Clicking “OK” to proceed is all you need to do! If the warning appears because the user is in fact already signed in, that previous session will simply be terminated. If it appeared for any of the other reasons outlined above, the database fields are cleaned up from any incorrect flags and reset to their intended status. It is good to inform users that this error means no harm and that they can safely proceed if they do not believe that their operator is signed in anywhere else.
