Give every line an explicit response
Suppliers can accept as ordered, propose a new date, quantity, or price, decline, and add context. The order can show partial progress while unanswered lines remain visible instead of treating the first response as completion.
Validate before submission
The external form checks required responses and proposal values before it records the acknowledgment. This prevents an apparently completed order from containing silent blank lines or an unqualified change.
Preserve the commercial record
Ordered, proposed, decided, and committed values remain separate. A buyer can inspect exactly what changed and why, then accept or reject the proposal with an attributable disposition.
Use acknowledgment as an early-risk signal
A moved date or reduced quantity is visible immediately after submission, before receipt or invoice. Operations can focus on the lines that threaten a production or customer commitment while confirmed lines remain stable.
Define completion and correction behavior
A complete acknowledgment should mean that every required line has an explicit disposition and every proposed value passes validation. Test a partial response, duplicate click, browser refresh, expired link, and supplier correction request. Confirm which event is current, which prior response remains in history, and who can issue a replacement request. Decide whether notes are required for declines or commercial differences. These rules prevent a completed status from hiding unanswered lines and give buyers a repeatable way to handle honest supplier mistakes without deleting the original response.
Validate the workflow with one real purchase order
Before buying or replacing software, run one representative multi-line PO from reviewed source through supplier response and buyer resolution. Include at least one accepted line, one proposed date or quantity change, and one delivery or reminder edge case. Confirm that every participant can identify the current owner and next action, that the original order remains unchanged, and that the final commitment can be exported and traced to its response and decision. Also verify the supplier experience on a normal phone and desktop browser, revoke and reissue a response link, inspect a failed delivery, and test the role boundary with a non-owner buyer. This evidence is more useful than a feature checklist because it exposes adoption friction, hidden authority, and incomplete system boundaries before the workflow reaches production volume.
Keep source, proposal, decision, and commitment distinct
Pacteva records supplier responses and authorized buyer decisions. It does not silently alter the reviewed purchase order or claim an ERP changed unless a configured write-back is verified. Requisitions, budgets, receipts, invoices, payments, inventory, and shipping remain in their systems of record.
What buyers usually ask
Can a supplier accept some lines and change others?
Yes. Responses are line-level and the order aggregates the resulting state.
Does a proposed change update the PO?
No. It creates a pending buyer exception and preserves the source value.
Is an account required?
No. The supplier uses a secure order-scoped response link.