Understanding the Override Button in Epicor Kinetic

If you’ve ever worked with parts in Epicor Kinetic, you’ve likely come across the Override button that appears next to the Make Direct and Buy to Order options. While it might seem minor, this feature plays an important role in how Epicor determines fulfillment logic. Understanding when and how to use Override helps maintain system accuracy while managing special cases efficiently.

The Default Logic Behind Part Configuration

Epicor relies on part configuration settings defined in Part Maintenance to determine how a sales order release is fulfilled.

Here’s what happens by default:

• If a part is configured as Buy to Order, Epicor automatically applies that setting to new Sales Order Releases.

• If a part is defined as Make Direct, the system marks it accordingly.

  
  

This ensures consistency across transactions and minimizes user input errors. In most cases, these defaults reflect the intended sourcing strategy for that part and should remain unchanged.

What the Override Button Does

The Override button provides flexibility when an exception is needed. When you enable it, you can manually toggle the Buy to Order or Make Direct checkboxes, even if the part’s master configuration specifies otherwise.

In other words, Override temporarily suspends the standard rules for that order line. It allows you to deviate from the default sourcing logic for a single transaction without altering the part’s global setup in Part Maintenance.

Example:

A part is typically purchased to stock, but a customer requests it for a custom project. In this case, you can activate Override and select Buy to Order for that specific release. The system will then treat that order as a direct purchase rather than drawing from inventory.

How Override Impacts Epicor Processes

When you change fulfillment logic using Override, Epicor adjusts downstream activities accordingly:

• For Buy to Order: The system will generate a direct purchase suggestion or link the part to a purchase order specific to that sales order.

• For Make Direct: Epicor will create a manufacturing job linked to that release rather than using inventory.

• In MRP: The change affects planning results. MRP recognizes the new sourcing method during its next run and generates appropriate demand; for example, converting what would have been a stock replenishment suggestion into a direct demand against a job or purchase.

Override changes apply only to the current release and do not modify the default part setup or future orders.

Why Override Matters

Every business occasionally encounters exceptions. The Override feature allows users to handle these without compromising data integrity or reconfiguring parts unnecessarily. It provides the flexibility to meet unique order requirements while keeping your system logic stable.

For organizations managing both stock and non-stock workflows, Override is particularly valuable. It lets planners, buyers, or customer service teams respond to special customer requests without disrupting standard processes or part classifications.

Common Pitfalls to Avoid

While Override is a powerful feature, it should be used carefully. A few best practices to keep in mind:

• Coordinate with purchasing or production. Changing sourcing logic may affect open jobs, PO suggestions, or MRP results. Always confirm that the exception is intentional.

• Avoid frequent use. If you find yourself using Override regularly for the same parts, it may indicate that the part’s setup in Part Maintenance needs to be reviewed or reclassified.

• Document exceptions. Record when and why Override was used, especially in environments where order traceability or audit trails are important.

Real-World Use Case

A manufacturer regularly sells an assembly that’s normally stocked. However, one customer requires a version with a special material. Instead of permanently setting the part to Buy to Order or Make Direct, the planner enables Override on that single sales release. Epicor then generates a direct demand, ensuring the correct purchase or job is created for that one order while all future sales of the standard version continue to use inventory.

In Summary

The Override button in Epicor is more than a convenience, it’s a control feature that helps manage exceptions efficiently. By understanding how it interacts with Epicor’s fulfillment and planning logic, users can apply it confidently to handle unique customer requirements without compromising overall system integrity.

Use defaults for consistency.

Use Override for exceptions.

And always ensure the change aligns with your company’s fulfillment strategy.