The Workday PunchOut pattern
The common pattern is a procurement-launched session: the buyer selects the supplier catalog in Workday, shops on the Shopify or Shopify Plus store, returns the cart to procurement and completes the buyer's approval process. The supplier receives the approved purchase order through the configured connection and can create the related store order.
The sequence to validate
- 01
Buyer launch
The buyer opens the supplier catalog from its Workday procurement environment using the buyer-specific setup.
- 02
Supplier shopping
The buyer sees the assigned Shopify store and relevant catalog access, then selects products and quantities.
- 03
Cart return
The selection returns to the procurement system. This is a review point, not proof that the supplier order exists.
- 04
Approval and PO
The buyer applies its own approval process and sends the approved PO through the agreed connection.
- 05
Store order
PunchOut Central records the PO-to-order handoff and the Shopify order can be reviewed with the earlier activity.
What is buyer-specific
- Workday account, tenant, credentials and catalog-launch settings.
- The protocol details and required fields used by the buyer connection.
- Approval routing, PO references, shipping and billing expectations.
- Invoice format and delivery requirements after the order is created.
What the supplier should test
Use the buyer's test instructions and confirm the same product, quantity and account context can be followed through the full transaction. Record where the test stopped if the buyer reports that the catalog opened but the order did not arrive.
Questions to clarify
No. Buyer configuration, credentials, approval rules and required document details can vary. Confirm the buyer's own setup instructions.
No. The cart returns for buyer review and approval. The approved PO is the handoff to the Shopify order.
No. This article explains the buyer question or workflow. Use the linked integration page for PunchOut Central implementation scope.
No. The buyer system, credentials, document requirements and approval process vary by buyer environment and must be confirmed during onboarding.