Research library

Sources checked: November 1, 2026

B2B PunchOut Cart Returns: Session Identity, Requisitions, and PO Handoffs

A business buyer can shop on a supplier's website while preparing a purchase in a separate procurement application. PunchOut connects those experiences: the buyer launches a supplier session, selects items, and returns the basket to the procurement application. The returned basket and the later purchase order are separate records. An integration needs to preserve that distinction when a browser return fails, a requisition changes, or an order arrives days later.

For Educational and Informational Purposes Only — Not Legal or Financial Advice.

Commerce Systems Review is a free, vendor-neutral educational library. This guide describes technical workflow design, not legal, tax, accounting, financial, security, pricing, compliance, or individualized implementation advice. It implements no purchasing service. Partner profiles and configured products determine supported messages and actions; authorized business owners determine approval and commercial decisions.

Sources checked: November 1, 2026.

Define the supplier-to-procurement boundary

Scope this workflow to ordinary cXML PunchOut shopping: setup, supplier browsing, cart return, supported cart reopening, and correlation to a separately received PO. Sourcing RFQs, non-cXML interfaces such as OCI, and downstream fulfillment are separate implementation scopes.

The cXML Reference Guide 1.2.071, chapter 5, distinguishes PunchOutSetupRequest, PunchOutSetupResponse, and PunchOutOrderMessage. Its implementation guidance explicitly says PunchOut transactions produce quotes, not purchase orders. A supplier must receive an order separately. The document's names should not turn a cart export into an accepted supplier order.

SAP's complete PunchOut workflow illustrates that separation in SAP Ariba: after the supplier sends the cart by HTML browser form post, the buyer submits a requisition for approval; a fully approved requisition generates a PO, which travels to the supplier's SAP Business Network account and, where applicable, onward electronically. This is a named-product example, not a universal approval sequence or a promise that every buyer sends the supplier each intermediate status.

Account onboarding covers company and buyer relationships. Customer-specific catalogs covers assortment and approved price ownership. Bulk-order accessibility covers operable entry and recovery interfaces. Here, the uncovered question is how those selections cross back into an external requisition and remain traceable when a PO is later received.

Keep checkpoints and owners separate

Use evidence-backed local states; these labels are illustrative rather than cXML status codes.

CheckpointEvidence and responsible boundary
Setup acceptedBuyer/supplier relationship, request identity, selected operation, configured profile, and setup response; integration owner.
Supplier session openedInternal session reference linked to the accepted setup and intended company context; supplier experience owner.
Cart export attemptedExact cart revision, return-message reference, item scope, and observed browser-transfer result; supplier integration owner.
Requisition import observedBuyer-side requisition/line references and accepted or rejected scope, when the buyer exposes them; procurement integration owner.
Buyer approval observedAuthorized approval evidence supplied by the buyer's process. A supplier may have no visibility while this is pending.
PO received and reviewedSeparate PO identity and revision, line references, cart/configuration correlation, validation and business decision; order-ingestion owner.
Supplier order recordedSaved order and line references, unresolved differences, and supported response; supplier order owner.

A successful setup response proves neither cart import nor order creation. An HTTP response at the return endpoint is not sufficient evidence of an imported requisition line unless the buyer's documented interface establishes that meaning. Keep unavailable buyer-side evidence explicitly unknown. Do not start warehouse work solely because a cart was transferred.

Correlate the session without turning it into a durable order key

Record the buying organization and supplier relationship, sender/receiver identities and domains, setup payload reference, request operation, source/received times, selected profile, and internal session reference. Map any supplied contact or extrinsic purchasing context deliberately. Missing optional context must not silently select another company's catalog.

The reference guide's sections 5.6.2.3 and 5.6.4.1 describe BuyerCookie as an opaque value returned to the originator to match the return to the setup request. Return it unchanged. Section 5.3.4 cautions that it changes between create, inspect, and edit sessions. Use it to correlate that exchange, while maintaining a separate internal cart/configuration identity across reopenings. It is a cXML element, not proof of a browser cookie or a durable PO number.

BrowserFormPost supplies the return destination, while the setup response's StartPage supplies the supplier browsing URL. They serve different directions. Bind the return destination and buyer context to the accepted setup through the implementation's reviewed controls; do not substitute a generic return address from another buyer. Have the responsible integration and security teams review endpoint acceptance, session lifetime, and data handling for the actual environment. This guide establishes no security outcome.

Test two simultaneous sessions for the same buyer and sessions for different organizations. A last-used account or shared browser tab must not determine which requisition receives the basket. Retain correlation evidence in approved systems without exposing credentials, opaque session values, or customer-specific data in public diagnostics.

Preserve item and configuration identity in the returned basket

For each returned line, retain the supplier item identifier, configuration or auxiliary reference where supported, quantity, unit, description and language, classification domain/code when required, and approved price/currency context. Retain the cart revision and original values beside any normalized internal keys. Validate the deployed buyer profile's required fields, encoding, permitted units and quantities, and summary/detail consistency.

The reference guide describes SupplierPartAuxiliaryID as a supplier cookie: procurement applications return it in subsequent edit/inspect sessions and the resulting cXML PO. It can connect a configured item or quote to supplier-side data. The guide notes that procurement applications may use it as part of item identity and advises against changing it during edit/inspect sessions. Treat it as a scoped opaque reference, not a display SKU or an authorization decision. Verify preservation with each buyer integration.

Do not assume one basket will retain its original line numbers in a requisition or PO. The guide's ItemIn discussion says line position is not relevant to the PunchOut return because the supplier cannot control placement in the eventual order. Maintain a crosswalk using supported item/configuration references and the later buyer line identities. Repeated items with different configurations must remain distinguishable.

Illustrative example, not wire syntax: session S-1 exports two configured valves under cart C-7. The buyer later reopens C-7 in session S-2 and exports three valves. Record two session exchanges and the reviewed cart revision relationship. When PO P-100 arrives, compare its actual item/configuration references, quantity, unit, and company context to the intended revision. The most recent browser event alone does not decide what the buyer ordered.

Test the browser return as a data transfer

The return has to carry the basket, not simply navigate the buyer to a URL. SAP's version 2608 example PunchOutOrderMessage shows hidden cxml-urlencoded and cxml-base64 form fields; that page recommends base64 for non-US-ASCII content. It contains historical sample DTD references, so its sample is format evidence rather than the release to copy into a new integration.

Agree the supported field and encoding with the buyer's configured endpoint. Test descriptions containing ampersands, quotation marks, non-ASCII text, and long item/configuration references. Compare the decoded returned values with the selected cart revision. Successful navigation can conceal truncated or rejected lines.

Use an action label that reflects the actual handoff, such as “Return basket to procurement,” where appropriate to the product. Provide a clear pending or failed state and a supported recovery path. If the browser closes or a response is lost, inspect available buyer-side import evidence before sending the same basket again. A repeat form submission and a new shopping session are different events. The buyer application's supported duplicate boundary and replacement behavior must be tested rather than assumed.

Handle create, edit, inspect, and empty returns deliberately

The setup request's operation and the returned header's operationAllowed have different jobs. The former selects the current session operation; the latter controls permitted later reopening. The checked guide defines returned create as disallowing later inspect/edit for those items, inspect as permitting viewing, and edit as permitting viewing and changes. create in that header does not mean create a supplier sales order.

Section 5.6.4.3 also distinguishes empty returns:

  • After a create session, no ItemIn means no items are added from that session.
  • After an inspect session, the procurement application ignores the item list; the supplier should return no ItemIn.
  • After an edit session, an ordinary empty return deletes the existing requisition items from that PunchOut scope.
  • A 204/No Content end-of-session result without items means no change in the edit case, rather than deletion.

These are the checked standard's semantics; confirm how the exact buyer application represents and supports them. “Cancel” cannot always be implemented as the same empty message. Record the requested operation, prior item scope, returned status and item scope, and observed buyer result. Scope any removal to the affected PunchOut items, not an entire multi-supplier requisition. If the configured interface cannot express the intended outcome, route it for review rather than guessing.

Reconcile the separately received PO before order operations

The order receiver needs its own processing contract: buyer/supplier identity, PO number and revision, message identity, allowed functions, line/item references, duplicate rules, and supported business response. Match within the intended relationship and organization; an equal total or similar item description is insufficient.

Compare the actual PO lines with the retained cart/configuration references where provided. Expose differences in quantity, unit, item configuration, delivery context, or approved price instruction to the authorized owner. A buyer may change or split a requisition; a supplier may not receive evidence of rejection or abandonment. Preserve those unknowns instead of manufacturing an “approved” or “cancelled” state from elapsed time.

Record missing cart references, unknown configurations, conflicting PO identities, and uncertain destination writes as exceptions. A repeated PO should not create another supplier order under the configured duplicate rules. Check saved destination references before retrying after a lost response. Retain the PO decision, resulting order identity, rejected scope, and closure evidence.

OMS architecture governs the resulting order's broader state and fulfillment boundaries. PO amendment seller responses govern later changes to already accepted work. PunchOut edit permission is not authorization to amend shipped quantities. Synchronization observability supplies broader monitoring and repair ownership.

Use a lifecycle test matrix

Controlled caseEvidence to compare
Normal setup, cart return, and later PODistinct session/cart/requisition/PO/order identities and actual outcomes.
Two tabs or purchasing contextsReturn lands in the intended session and account; no cross-context item assignment.
Repeated SKU with different configurationsAuxiliary references survive return, reopening, and PO matching.
Edit, inspect, empty edit, and no-change cancellationRequested/allowed operations, affected item scope, status, and buyer-side result.
Unicode or special characters and long basketsDecoded field equality, accepted/rejected lines, and supported size limits.
Browser closure or repeat returnUnknown versus observed import, prior result, and supported duplicate/recovery action.
Changed, split, or unmatched POActual line crosswalk, differences, authorized review, and unresolved scope.
Timeout after order write or repeated POSaved order reference checked before another side effect.

Use synthetic data and an appropriate test environment. Name the next owner and closure evidence for each failure. Activate a bounded buyer/profile scope only after supplier and procurement teams have reviewed the observed results; choose monitoring windows from their own workflow. No universal deadline, performance improvement, price outcome, or compliance result follows from this matrix.

First-party source register and limits

All four sources were accessed on November 1, 2026:

Named-product statements apply only to those sources. The correlation ledger, exception routing, and test cases are proposed educational models. Base cXML capability does not establish support for every buyer's profile or a complete implementation.

Editorial and education-only note

This free guide provides vendor-neutral technical education. It does not provide legal, tax, accounting, financial, security, pricing, compliance, performance guarantees, or individualized advice. Confirm current first-party documentation, deployed buyer profiles, approved commercial instructions, and local operating requirements with the responsible teams. Cart transfer, requisition approval, purchase-order receipt, and supplier order acceptance require separate evidence.

Continue reading