All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

  1. Procurement
  2. Process
  3. Change orders
Process · Change orders

Change orders

An order change can affect price, quantity, delivery dates and the capacity left under an agreement. Change orders preserve the original commitment and every approved revision, with enough line detail to understand both the individual change and its cumulative effect.

Step by step

  1. Raise Buyer

    Buyer records a quantity, price, date, line-addition, line-removal or cancellation request against the current order revision. Requester can initiate the need through Buyer. The reason and original revision remain attached. Sent commercial lines cannot be edited directly, and a superseded base revision requires recalculation before the change can proceed.

    • draft change tied to current order revision
    • Updates PO amendments, Purchase orders
  2. Detail Buyer

    Buyer records before and after values for every affected line. Added lines include item or free-text description, category, unit, quantity, price, need-by date and coding. Their old total is zero; a fully removed unfulfilled line has a new total of zero. Received obligations cannot be reduced below net accepted fulfilment. A changed price applies to a split unfulfilled portion, preserving the accepted portion’s value.

    • proposed total and cumulative increase calculated
    • Updates PO amendment lines, PO line items
  3. Approve Approver or Controller or Procurement Manager

    Approver, Controller and Procurement Manager decide their assigned matrix tiers. Routing uses the greater of the proposed total and original approved total plus cumulative gross increases. Positive line increases accumulate before netting, so reductions on other lines cannot hide them. Required higher tiers and new category rules apply. Procurement Manager separately decides pricing exceptions; a larger agreement ceiling needs its own approval before it can support the change.

    • required scope and cumulative authority reviewed
    • Updates Approval steps, Approval matrix, Spend approvals, Spend approval lines
    ApprovalA person approves before the work moves on.
  4. Apply Buyer

    Buyer applies only the approved version. The order and line totals, revision, authority allocations and any blanket-release commitment update together. Positive amendment capacity belongs to that order. Fulfilled value remains consumed; only supported unfulfilled reductions release capacity. The new revision and its outbound update are recorded once, so retry cannot apply the amendment again.

    • revision and commitment changes applied once
    • Updates PO line items, Purchase orders, PO amendments, Commitment allocations, Blanket releases, Master agreements, Procurement events, Integration deliveries
  5. Acknowledge Supplier

    Supplier reviews and acknowledges the issued revision through the configured channel. The recorded revision identifies what was accepted. A new promise made during expediting is proposed as a date amendment; it does not change the agreed order date until the corresponding approval and application complete. Earlier acknowledgements remain part of the history.

    • supplier acceptance identifies issued revision
    • Updates PO amendments, Purchase orders
  6. Cancel Buyer

    Buyer follows the same approved amendment path for cancellation or partial reduction. Open obligations and their expediting rows close only to the extent cancelled. Accepted deliveries, returns, invoice-match evidence and fulfilled commitments remain traceable. Cancellation cannot erase a received liability or reopen spent agreement capacity as if the delivery never happened.

    • approved unfulfilled obligation released; fulfilled history retained
    • Updates PO line items, Expediting, Commitment allocations, Blanket releases

Checks built in

What Procurement enforces at each step.

  • Review cumulative growth. Routing on the individual delta alone would miss repeated increases. The approved baseline and gross increase history remain available after reductions.
  • Preserve existing fulfilment. Remove only unfulfilled quantities. Corrections and returns use their own linked events rather than rewriting the receipt history.
  • Respect agreement limits. A PO amendment does not itself increase the agreement ceiling. The capacity check and allocation update must succeed together.
  • Keep revisions consistent. The supplier and configured accounts-payable mirror receive the applied revision. Delivery failure stays visible without repeating the local change.
  • Recheck eligibility. Suspended or blocked suppliers cannot receive increased commitments. Permitted reductions and returns retain their normal evidence and approvals.
Buyer
Prepares and applies approved changes.
Approver
Decides assigned business tiers.
Controller
Decides its financial tier.
Procurement Manager
Decides procurement tiers, pricing exceptions and agreement changes.
Supplier
Acknowledges the issued revision.
Requester
Supplies the reason for requested changes.

Set up Procurement your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appProcurement

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.