Vendor PO Acknowledgement — Assessment

1. What is the main purpose of Vendor PO Acknowledgement?

To keep purchase order fulfilment visible and accountable from the vendor side To move supplier decisions outside AWRA To give vendors access to every workspace record To replace RFQ and PO audit history

2. What should a vendor or buyer check before acting?

Only the PO confirmation without reviewing the delivery note Nothing if the relationship is familiar Only the newest email thread PO status, lines, delivery, decision reason, shipment proof, and communication protocol

3. Why do portal attachments and status notes matter?

They remove the need for source records They hide the supplier response from buyers They make purchase orders optional They prove what the vendor accepted, rejected, shipped, or delayed

4. What risk does this workflow reduce?

Deleting RFQ history after submission Unreviewed access to all suppliers Silent PO delays, unclear vendor commitments, and missing shipping evidence Faster informal buying outside the portal

5. What should happen before the workflow is closed?

The PO should show vendor decision, reason, and current shipment status Attachments should be disconnected from the source record The buyer should ignore unresolved portal errors The supplier should guess the next status

Your details for the certificate

This is the name that will appear on your certificate.

Full name

Email

We email your result to this address with a link to confirm it is yours. If you are signed in, or once you confirm, the administrators of an organisation this email belongs to on AWRA OpsHub can see your attempts and certificate. Your name is as you type it here; only the email is confirmed.

Send me AWRA’s monthly email: new guides, product updates and courses. Unsubscribe anytime.

Graded server-side. No peeking at answers in the page source.