Procurement

PO Release Agent

Filters MRP-planned orders and purchase requisitions into actionable POs — consolidating lines, timing releases, and escalating what needs a buyer's judgment.

Sits between MRP output and actual purchasing. Reviews planned purchase orders and requisitions from the ERP, filters out lines that aren't yet actionable (future need dates, quantities below order minimums, items already covered by open POs), consolidates lines that belong on the same order, times releases against supplier lead times, and converts clear-path items into POs. Escalates ambiguous cases to the buyer with a structured buying plan.

+ Details- Close

MRP and planning systems generate large volumes of planned purchase orders, but many aren't ready to act on — the need date is weeks out, the quantity is below the supplier's minimum order, or an existing open PO already covers the demand. The PO Agent reads all planned orders and open purchase requisitions from the ERP, applies a set of filters to determine which lines are actionable now, and groups the actionable lines into consolidated purchase orders. It checks on-hand inventory, existing open POs, supplier lead times, minimum order quantities, and preferred suppliers before deciding whether to release. Lines that share the same supplier, delivery window, and ship-to location are combined into a single PO to reduce transaction volume and improve terms. Where the sourcing path is clear — known supplier, confirmed deficit, lead time requires release now — the agent generates the PO directly in the ERP. Where the path requires judgment — new supplier, unusual quantity, conflicting planned orders, or a consolidation trade-off — it assembles a buying plan showing the options and escalates to the responsible buyer.

KPI it moves

  • +30–50 pts

    Planned-to-PO conversion rate

    The share of MRP-planned orders and requisitions that convert to released POs without manual buyer intervention.

What it does

  • Filters MRP planned orders to find what's actionable now

    Reviews all planned purchase orders from the MRP run and filters out lines that aren't ready to act on — future need dates, quantities below minimums, demand already covered by open POs — leaving only the lines that need to be ordered now.

  • Consolidates lines into efficient purchase orders

    Groups actionable lines that share the same supplier, delivery window, and ship-to location into a single PO, reducing order volume and improving supplier terms.

  • Times PO releases against supplier lead times

    Calculates when each PO must be released based on the supplier's lead time and the required delivery date, so orders go out at the right moment — not too early, not too late.

  • Converts clear-path items into POs or escalates a buying plan

    Generates POs directly in the ERP when the sourcing path is unambiguous. When the path requires judgment — new supplier, unusual quantity, conflicting demand signals — assembles a buying plan with options and escalates to the buyer.

How it works

  1. Trigger 1

    MRP run completes and generates planned purchase orders

    The ERP's MRP or planning run produces a new set of planned purchase orders, triggering the agent to review and filter the output.

  2. Trigger 2

    Purchase requisitions reach review status

    Manual or system-generated purchase requisitions are approved and ready for conversion, triggering the same triage and consolidation logic.

  3. Step 1

    Filter planned orders and requisitions for actionability

    Reads all planned purchase orders from the latest MRP run and open purchase requisitions from the ERP. Checks each line's need date against the current date plus supplier lead time, compares the requested quantity against the supplier's minimum order quantity, and verifies no existing open PO already covers the demand. Lines that aren't actionable yet are deferred to the next cycle.

  4. Step 2

    Consolidate actionable lines into purchase orders

    Groups actionable lines by supplier, delivery window, and ship-to location. Evaluates whether combining lines into a single PO meets minimum order thresholds, qualifies for volume discounts, or reduces freight costs. Calculates the release date for each consolidated PO based on supplier lead time and required delivery date.

  5. Step 3

    Generate POs or escalate buying plans

    For consolidated orders with a clear sourcing path (known preferred supplier, confirmed stock deficit, standard terms), generates the PO directly in the ERP. For lines requiring judgment — new supplier, unusual quantity, conflicting planned orders, or a consolidation trade-off between cost and timing — assembles a buying plan showing the options and routes it to the responsible buyer for decision.

  6. Resolution

    Actionable demand converted to POs, remainder deferred or escalated

    Every actionable planned order or requisition has either been converted into a consolidated PO in the ERP or escalated to the buyer with a structured buying plan. Non-actionable lines are deferred to the next MRP cycle.

Why it matters

  • MRP noise filtered before it reaches buyers

    so that procurement teams work a clean, actionable list instead of sifting through hundreds of planned orders that aren't ready to release.

  • Fewer, larger POs through automatic consolidation

    so that suppliers receive consolidated orders with better terms instead of a stream of small, fragmented POs that increase transaction costs on both sides.

  • Orders released at the right time based on lead times

    so that materials arrive when needed without tying up working capital in premature orders or causing shortages from late releases.

What it needs

Read/write access to the ERP
Connects to the ERP (e.g. Infor LN/M3/CloudSuite, Microsoft Dynamics 365, IFS Cloud, or SAP S/4HANA) to read MRP planned orders, purchase requisitions, stock levels, open POs, supplier lead times, and minimum order quantities, and to write back generated purchase orders. Without this connection the agent cannot filter, consolidate, or release POs.
Supplier master data with lead times and order minimums
Reads supplier records including preferred supplier per item, lead times, minimum order quantities, and contract terms. Without this data the agent cannot calculate release timing or evaluate consolidation options.
MRP output feed or scheduled scan
Access to the MRP planned order output, either via a triggered feed after each MRP run or a scheduled scan of the planned orders table. Without this the agent has no demand signal to act on.
Related agents