How to Amend a Purchase Order: Revisions and Change Orders
Jul 11, 2026
Jul 11, 2026
Convert a purchase order to Excel, CSV, or JSON
Submit your purchase orders
Drop documents here, or click to file
Up to 50 files per batch
Uploading...
To amend a purchase order, issue a revision to the existing PO rather than canceling it: open the fields that changed, edit the quantity, price, delivery date, or line items, label the new version clearly (for example PO 4567 Rev. 1), route it for any approval the new dollar amount triggers, and send the revised PO to the supplier for acknowledgment. A revision keeps the original PO number and its audit trail intact, so both sides can see exactly what changed and when.
Last updated July 2026.
Orders change after they are placed. A price moves, a quantity needs bumping, a delivery date slips, or a line has to be added or dropped. The question is not whether a PO will change but how you record the change so the order, the receipt, and the invoice still line up later. The tool above reads the line items off any supplier PO, including a revised one, so a new version does not mean retyping the whole order. Below is how to handle the amendment itself.
When something about an issued PO needs to change, the efficient move is a revision: reopen the order, change only what needs changing, and keep the same PO number. Canceling the PO and cutting a fresh one breaks the link between the order and everything already tied to it, receipts, partial deliveries, and the supplier's own records. A revision keeps that chain intact while giving you a clear before-and-after. Most procurement and ERP systems support this directly by letting you open an issued PO, edit the changed fields, and save it as a new revision number.
The two terms get used loosely, but they are not the same thing. A purchase order revision is contained to one PO: it updates the quantity, price, delivery date, or specifications on that order and nothing else. A change order is a broader, more formal modification, common in construction and project work, that changes the scope and the budget of the whole project or contract, and a PO revision may be one downstream result of it. In plain buying, you revise the PO. In a project with a baselined budget, a change order authorizes the scope and cost change, and the PO revision records it against the specific order.
| Purchase order revision | Change order | |
|---|---|---|
| Scope | One purchase order | A project or contract budget |
| Typical use | Change a quantity, price, date, or line | Change project scope and cost |
| Where it is common | General procurement and buying | Construction and project work |
| Record it creates | A new PO revision number | A signed change document, then a PO revision |
Whatever your system, the sequence is the same. First, confirm the change with the supplier so both sides agree on the new terms before anything is issued. Second, open the PO and edit only the fields that change, quantity, unit price, delivery date, ship-to, or the line items themselves. Third, label the revision so it is unmistakable, most teams append a revision tag such as Rev. 1 to the original PO number and note what changed, for example "quantity increased from 50 to 75 units." Fourth, route it for approval if the new amount crosses an authorization threshold. Fifth, send the revised PO to the supplier and get an acknowledgment so the amendment is accepted, not just proposed.
A small edit within the same budget usually flows through on the original authorization. A change that raises the dollar value materially, adds scope, or extends the term typically needs fresh approval, and the larger the increase, the more sign-offs it may require. The safe rule: if the revision would have needed approval had it been in the original PO, it needs approval now. Routing the revised PO back through the same approval path keeps spend authority honest and gives auditors a clean record of who approved the change.
The whole point of amending rather than replacing is the audit trail. Keep every revision, do not overwrite the original, and make sure each version shows what changed and who approved it. When the supplier's invoice arrives, it should match the latest revision, not the original order, and that is only possible if the revision history is intact. If you capture PO data into a spreadsheet or accounting system, pull the fields off the revised version so your records reflect the current terms, and the amended amount is what gets matched against the supplier invoice before payment.
You amend a purchase order by issuing a revision to the existing PO rather than canceling it. Confirm the change with the supplier, open the order and edit only the fields that change, label the new version clearly such as Rev. 1, route it for any approval the new amount triggers, and send the revised PO to the supplier for acknowledgment. This keeps the original PO number and its audit trail intact.
A purchase order revision is an update to an existing PO used when the quantity, delivery date, pricing, or item specifications need to change. Rather than canceling the order and starting over, a revision keeps the same PO number, edits only what changed, and records the update as a new version. It maintains a clear before-and-after and preserves the link to any receipts or invoices already tied to the order.
A purchase order revision is contained to a single PO and changes its quantity, price, date, or line items. A change order is a broader, more formal modification, common in construction, that changes the scope and budget of the whole project or contract. A change order often authorizes the change, and a PO revision records it against the specific order. In routine buying you revise the PO; in project work a change order comes first.
Yes. An issued purchase order can be changed by revising it, as long as the supplier agrees to the new terms. Because a PO becomes a binding contract once the supplier accepts it, a material change should be confirmed with the supplier and acknowledged, not just edited on your side. Recording it as a labeled revision, rather than an untracked edit, keeps the order enforceable and the audit trail clean.
It depends on the change. A small edit within the existing budget usually flows through on the original authorization, but a revision that raises the dollar value materially, adds scope, or extends the term generally needs fresh approval, sometimes several sign-offs for a large increase. The practical test is whether the change would have required approval in the original PO. If so, route the revision through the same approval path.
Document it by creating a labeled revision that keeps the original PO number, notes exactly what changed, and records who approved it and when. Keep every version rather than overwriting the original, so the revision history shows the full before-and-after. When the supplier invoice arrives, it should match the latest revision, which is only possible if the trail from original order to current revision is intact and auditable.
For the fields that live on the order you are revising, see purchase order fields, and for how a supplier accepts a change, see the purchase order acknowledgment guide. To capture the line items off a revised supplier PO as clean data, see purchase order line item extraction or the purchase order PDF to Excel converter.
This article is general information, not legal advice. For changes to high-value or high-risk purchase orders, follow your organization's procurement policy and have counsel review material amendments. PurchaseOrders reads purchase orders and returns structured data; it does not create, revise, or approve them.