Required buyer fields
| Field | Purpose | Check |
|---|---|---|
| Buyer name | Human-readable account label | Use the company or buyer portal name. |
| Sender ID / Identity | Matches incoming cXML credential | Must match buyer-provided value exactly. |
| Shared Secret | Authenticates incoming setup request | Never publish or export unmasked. |
| BrowserFormPost URL | Where the cart is returned | Use HTTPS unless buyer specifies otherwise. |
| Status | Controls buyer availability | Disable unused buyer profiles instead of deleting too early. |
Setup process
- Create buyer profile.
- Enter buyer identity values supplied by the procurement team.
- Set Shared Secret.
- Add BrowserFormPost / Return URL.
- Save and re-open the buyer profile to confirm persistence.
- Run PunchOutSetupRequest test.
- Review masked logs for identity match and setup response.
Edition and buyer count
Single Buyer is suitable for one company / one buyer portal. Business 1:5 is better for suppliers that expect multiple buyer profiles. Enterprise or add-on scope can be used for mapping, OCI, or additional buyer-specific requirements.
Sales clarity
Business 1:5 should be positioned as “support up to five buyer profiles,” not as unlimited procurement integration.Support data to collect
- Buyer system name and buyer contact.
- Sender ID / credential domain with secrets masked.
- Return URL with sensitive query strings removed if needed.
- Sample setup request if buyer can provide it.
- Masked PunchOutHub logs after the test.