A Kanban ordering system can be a game-changer in Epicor, but only if it’s set up to match how your shop actually works. If you skip the decisions up front, you’ll end up with stockouts, “emergency buys,” and a Kanban process nobody trusts.
Epicor supports lean Kanban as a pull approach (not push), and it’s meant to work alongside modern, flow-based manufacturing practices.
TeccWeb services can help you set up Kanban efficiently with Epicor standards.
Kanban is a Japanese word that means “signboard” or “visual signal.” In manufacturing, it often refers to a simple signal that tells a team when to make or reorder something.
Kanban ordering in Epicor is a way to replenish materials based on consumption. Instead of planning everything far in advance (push), Kanban replenishes when inventory hits a trigger, like a bin getting empty or a min/max threshold being reached.
Kanban is a part of lean manufacturing with pull-based material flow and hybrid approaches to help companies transition to lean.
Before you touch settings, make these five decisions. This is what separates a Kanban system that works from one that becomes another workaround.
Not everything should be Kanban. Kanban works best for parts that are used often and predictably, especially low-cost items that cause big headaches when they run out. If demand is highly irregular or the part is expensive and rarely used, Kanban can create too much inventory.
A practical rule: start where stockouts hurt the most, but planning doesn’t need to be perfect.
A Kanban system needs a clear “signal moment.” That signal can happen on the shop floor (empty bin), at receiving, in a supermarket area, or at a picking location. The key is that people can’t miss it.
If the signal location is vague, the process turns into “I thought someone else ordered it.”
You need to decide what replenishment means for each Kanban item:
Epicor environments commonly treat Kanban as the trigger that starts the next replenishment step, but you still have to decide which team responds and how the work gets created.
Your trigger rules are the heart of the system: min/max, container size, number of bins, or reorder thresholds. If your trigger is too aggressive, you overstock. If it’s too tight, you get stockouts.
This is where teams often fail because they set rules once, then never update them as demand changes.
Kanban falls apart without ownership. Someone must own:
Without ownership, exceptions pile up until Kanban becomes optional.
A Kanban setup that looks great in a meeting can still fail on the floor if it’s too complex or unclear.
Start with parts that cause daily pain when they’re missing. Think: consumables, fasteners, packaging, common components, or anything that stops a work center when it’s out.
If you start with complicated items first, the project drags and people lose interest.
Choose one signal method per area and make it hard to ignore. Whether you use cards, bins, scanning, or a defined Epicor transaction, the main point is the same: everyone should know what “the signal” looks like.
If your shop uses multiple methods in the same area, people get confused and the system becomes inconsistent.
Don’t build a perfect model on day one. A simple system that gets used beats a perfect system that gets bypassed.
Using hybrid approaches to transition to lean, which is a good reminder to start simple and improve over time.
Demand changes. Lead times change. Operators change how they consume parts. If your Kanban settings don’t change too, the system slowly drifts into either overstock or stockouts.
A monthly or quarterly review is usually enough for most items.
Every Kanban system has exceptions: rush jobs, supplier issues, engineering changes. The trap is when exceptions become normal and nobody fixes the root cause.
If you’re constantly bypassing Kanban, that’s a signal that settings, ownership, or inventory accuracy needs work.
Keep it simple:
You’re not trying to build a dashboard empire. You just want proof the system is working.
Most Epicor teams avoid running both for the same part in the same location because you can create conflicting signals (MRP plans ahead, Kanban reacts to consumption). A common approach is to choose one method per part per location, or separate planning methods by site/warehouse.
In plain terms: production Kanban triggers internal replenishment (you make it), and purchase Kanban triggers external replenishment (you buy it). The important part is choosing the right replenishment path based on how the item is sourced.
In a working Kanban setup, users typically interact with whatever your “signal” process is (for example: scanning or confirming consumption) and whatever process confirms replenishment. Epicor environments often use a receipt/confirmation step for Kanban activity, but the exact screens vary by version, role, and how your shop is configured.
Start small enough that you can win quickly. Many shops begin with a short list of high-pain, high-usage items in one area, then expand once the process is stable.
You need three things: clear ownership, simple rules for adding/changing Kanban items, and a recurring review. If you don’t schedule reviews, settings will drift and people will create workarounds.
TeccWeb helps manufacturers set up Kanban in Epicor in a way that holds up in real life. We start by choosing the right items and the right signal method for your shop floor.
Then we help define replenishment rules that match your lead times and usage, and we put ownership and review habits in place so Kanban doesn’t decay into exceptions and spreadsheets.
Ready to set up Kanban in your Epicor ERP?
