OCI Flow
The OCI flow covers login/setup, cart interaction, and outbound cart transfer.
Step 1: OCI login request
The OCI login endpoint validates buyer profile, security constraints, buyer authentication, and return URL constraints.
If successful, Punchout creates a session context with token and correlation identifier.
Step 2: Catalog and cart interaction
The user or procurement process works in Magento while the session context remains bound to the Punchout token.
Cart operations can also be driven through tokenized cart endpoints.
Step 3: OCI transfer
Transfer builds outbound payload based on current cart data and mapping rules.
The response is an OCI-compatible transfer payload (typically form-post based) that returns data to the procurement side.
Document feedback scope
Post-order document feedback is handled through dedicated document endpoints (PO inbound, ASN outbound, invoice outbound).
There is no separate generic "return-transfer" controller in the Punchout transfer path.
Reliability notes
- transfer can enforce idempotency keys
- repeated calls can return deterministic replay behavior
- failures include structured error payloads for easier handling
Template references
For production onboarding, use the template library instead of building mappings from scratch: