SAMPO LABS Contact us

Backlog Map: supply-chain pegging for Epicor Kinetic. In development

The problem

When a customer asks “where is my order?”, the answer is buried: the sales order points to a job, the job to material demands, the demands to purchase orders or stock, and the trail is spread across a dozen Kinetic screens. MRP pegging exists, but it reflects last night's run and it doesn't tell you which link in the chain is the one that's late.

How it works

Backlog Map reads live data from Kinetic and builds the full supply chain under every open sales order release (jobs, stock, purchase orders), level by level. Each link is checked against the dates above it: late links get flagged Late, demand with no supply at all gets flagged Gap. One screen shows the whole backlog and where it hurts.

Status

In development against Epicor Kinetic.

If your planners spend their mornings chasing pegging by hand, we would like to talk

FAQ

What is supply-chain pegging in Epicor Kinetic?

Pegging links each open sales order to the supply that fulfills it (jobs, stock, purchase orders), level by level. Kinetic's MRP pegging reflects last night's run; Backlog Map builds the same chain from live data.

How can I see where a customer order stands in Epicor Kinetic?

Out of the box the trail is spread across a dozen Kinetic screens: the sales order points to a job, the job to material demands, the demands to purchase orders or stock. Backlog Map shows the full chain under every open sales order release on one screen and flags where it hurts.

Why doesn't MRP pegging show which link in the chain is late?

MRP pegging reflects last night's run and stops at linking demand to supply. Backlog Map checks each link against the dates above it, flags the late links, and flags demand with no supply at all as a gap.

© 2026 Sampo Labs LLC North Carolina, USA Privacy Established 2026