Data needed for the workflow
The product may process workspace users, supplier business contacts, PO headers and lines, message metadata, response events, buyer decisions, commitments, configuration, and audit events. Teams should avoid uploading data unrelated to the purchasing job.
Purpose limitation
Information supports authentication, order review, supplier delivery, acknowledgment, exception resolution, reminders, reporting, billing, security, and support. Supplier links display only the order-scoped information needed for response.
Customer responsibilities
Customers choose users, suppliers, contacts, order content, retention practices, exports, integrations, and message templates. They should configure access and communications under applicable contracts and law.
Exports and integrations
Downloaded CSV and audit files leave the application’s access boundary. Store, transmit, and delete them according to company policy. Connected providers have their own terms and data handling.
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
Does Pacteva need supplier bank data?
No. Banking and payment onboarding are outside the product scope.
Can suppliers see other orders?
Order links are scoped to the assigned order.
Who controls exports?
Authenticated customer users initiate exports and remain responsible for downstream storage and sharing.