Power Automate for purchase orders: what it handles and where it stops

Why this question comes up

If your company runs on Microsoft 365, you probably already have Power Automate. It sits next to Outlook, Teams and Excel, and Microsoft pitches it for exactly the kind of work an order desk does. So when someone asks "can we stop retyping customer POs?", the first idea is usually "let's build it in Power Automate."

That's a fair place to start. This guide walks through what a PO flow in Power Automate looks like, what it handles well, and where it stops, using Microsoft's own documentation, checked on Oct. 13, 2026. It's the same kind of look we took at Zapier for order entry.

What a PO flow in Power Automate looks like

A typical build has five steps:

1. Watch the inbox. A cloud flow starts when an email with an attachment lands in the orders mailbox.
2. Read the PDF. The flow calls AI Builder's Process documents action, which returns each field you trained it to find, plus a confidence score between 0 and 1.
3. Check the data. Conditions in the flow compare what was read against your rules.
4. Ask a person when something's off. An approval goes to a buyer or CSR.
5. Enter the order. If your ERP has a connector, the flow writes to it. If not, a desktop flow types the order into the ERP screens the way a person would.

Every piece of that exists in the product today. The question is how much work each piece takes for your documents and your rules.

What it handles well

POs from customers who never change their layout. AI Builder's custom document model has a "Fixed template documents" option that Microsoft says is ideal when fields and tables can be found in similar places, with a quick training time. You group samples by layout into "collections." Each collection needs at least five sample documents, and a model can hold up to 200 collections. If your top ten customers each send the same PO every time, that's ten collections and about fifty samples.

A built-in way to measure doubt. Every field and every table cell comes back with a confidence score, where values close to 1 mean the model is more sure. You can send anything below your threshold to a person instead of the ERP. That's a good habit, and it's built in.

Approvals where people already work. Power Automate's approvals let a person respond from an Outlook email, a Teams card, or the Power Automate action center. You can require everyone to approve, take the first response, or route approvals in a set order. Microsoft says the approvals connector is a standard connector, so any license that includes standard connectors can build approval flows.

ERPs with no connector. Desktop flows are Microsoft's robotic process automation (RPA). Microsoft's own example user is "an employee of a large enterprise who automates data entry on an ERP system," and it works with older apps, including terminal-style screens. So an on-premises ERP isn't a dead end.

Documents that vary, with more training. AI Builder also has a "General documents" option, which Microsoft describes as ideal when there's no set structure or the format is complex. It's more flexible, but Microsoft notes it has a long training time.

Where it stops

None of the limits below are hidden. They're in Microsoft's documentation. They just don't show up in a demo with one clean sample PO.

The page-break limit deserves a second look. Microsoft's requirements page says plainly that rows that break from one page to another aren't currently supported. Many distributors' biggest orders are their longest. If line 31 of 40 sits at the bottom of page one and continues on page two, you want something that notices. Adding up the lines and comparing them with the PO total is the simplest way.

Power Automate gives you the parts. Your rules are still yours to build.

Reading the PO is the easy half

Getting a part number off a page is one problem. Knowing whether it's the right part number is another. For order entry, the checks that matter are about your business:

• Customer part number to your part number. Usually a cross-reference table someone keeps up.
• Price against the contract or price list. With a rule for how far off is too far.
• Ship-to on file. A new address goes to a person.
• Line totals against the PO total. That catches a missed page.
• Quantity against what this customer normally orders. Ten times the usual deserves a call.
• Revised POs. A "Rev 2" of an order already entered should change it, not create a second one.

In Power Automate, each of these is a condition, a lookup, or a loop that someone builds and keeps working. That's doable. But it's where most of the work lives, and it's where a flow built by one person becomes hard for anyone else to change. Before you start, decide who owns the flow when that person is out or leaves.

Microsoft's own guidance points the same way. For its generative AI prompts, which can also pull details out of emails, it says a human should review the content before you send it to a customer or use it to make a business decision.

The credit change on Nov. 1, 2026

If you're planning a Power Automate build now, know this. AI Builder features run on credits. Microsoft's licensing page, updated Oct. 8, says new customers can no longer buy the AI Builder capacity add-on and must buy Copilot Credits instead. Existing customers can renew the add-on up to Nov. 1, 2026. The credits that came included with some premium licenses will be removed on that date.

What happens when a month's credits run out matters for an order desk. Microsoft says the system tries to use Copilot Credits next. If there are none, running models in flows is blocked, and AI Builder actions fail with errors. Usage resets on the first of each month and unused credits don't carry over. Microsoft also says the usage count is refreshed ideally daily but sometimes isn't computed for as long as seven days, so the number you see can lag.

We don't publish prices here, and Microsoft's rates differ by model and license. The practical step is simple: ask your Microsoft partner or admin how many POs a month your plan covers, what happens on the day it runs out, and who gets alerted.

If you run Business Central: the Sales Order Agent

If your ERP is Dynamics 365 Business Central, Microsoft has a ready-made option worth a look before you build a flow. Its Sales Order Agent watches a mailbox, reads the email and, if configured, PDF or image attachments, finds the customer, checks inventory and creates a sales quote. A few details from Microsoft's page stand out:

• It always creates a quote first, even when the customer asks for an order, because quotes don't affect planning or availability. You can set it to convert quotes straight to orders.
• Designated users review and approve every outgoing message before it reaches the customer.
• It finds the customer only by matching the sender's email address. A PO your salesperson forwards to the mailbox won't match until someone links it by hand.
• It runs on Copilot Credits. When they run out, it stops processing new emails and catches up when credits return.

That's a thoughtful design, and for Business Central shops with clean item data it may cover a lot. Microsoft also notes that the quality of your product descriptions affects how well it finds items.

Where Power Automate is the right call

To be fair to it, Power Automate is a good choice when:

• You have a few customers who send most of your orders, in layouts that rarely change.
• You already have Microsoft 365 and someone on staff, often in IT or finance, who enjoys building flows and will own this one.
• Your ERP has a connector, or its screens are stable enough for a desktop flow.
• The volume is modest, so a person can still look at every order before it's entered.

For a single customer portal or one big customer's clean PDF, a fixed-template model and an approval in Teams can work well for years.

When you need more than a flow

It gets harder when the order desk looks like most of the ones we see: dozens of customer layouts, scans mixed in with clean PDFs, long orders, revised POs, and an ERP that needs part numbers, prices and ship-tos to match exactly. Then the work isn't really reading documents. It's the rules, the exceptions, and keeping it all running when nobody who built it is around.

That's the case for a custom build: a reader that handles any layout, your checks written down once and tested, a review screen where a person approves exceptions, and someone accountable for keeping it working. That's how we built order entry for a food-equipment manufacturer that supplies national grocery chains: the software reads each customer order and fills it in, and their team approves it.

What to do this week

1. Pull last month's POs and count the distinct layouts, the scans, and the orders longer than one page.
2. Write down your checks: part cross-reference, price rule, ship-to, totals, revised POs. Whoever builds this needs that list, whatever tool you use.
3. Ask about credits before Nov. 1: what your licenses include after the change and what happens when the month runs out.
4. Name an owner. One person who's accountable when an order goes in wrong.
5. Read the related guides: why template parsers break when PDFs change and how to automate without replacing your ERP.