cXML Orders

OrderRequest The cXML OrderRequest document is used for sending orders from eProcurement systems to eCommerce systems. The requests are sent from the eProcurement server to the eCommerce server over HTTP(S). Each cXML OrderRequest document consists of header information (OrderRequestHeader) and a series of items (ItemOut). The cXML[@payloadID] should be stored in both the eProcurement and eCommerce systems so it can be referenced by change orders and cancelled orders. OrderRequestHeader The OrderRequestHeader element contains header-level information for the order. Read more →

cXML Overview

Receiving/Sending cXML The majority of cXML documents are sent server-to-server via HTTP(S) POST requests where the POST body is the cXML. The only exception is the shopping cart (PunchOutOrderMessage) which is transmitted from the shoppers browser to their eProcurement system as part of an HTML form. Best Practice: HTTPS with TLS 1.2 should be used whenever possible Example cXML HTTP POST Request POST /cxml HTTP/1.1 Host: www. Read more →

cXML PunchOut

PunchOutSetupRequest The cXML PunchOutSetupRequest document is the first document exchanged in the PunchOut process. It is sent from the shoppers eProcurement system to the suppliers eCommerce site via an HTTP(S) POST request with the XML in the POST body. Credentials See the Credentials section of the cXML Overview for more information. Operation The PunchOutSetupRequest[@operation] attribute is set to "create" when a user is accessing a PunchOut site to create a shopping cart. Read more →

cXML PunchOut Carts

PunchOutOrderMessage The cXML PunchOutOrderMessage document contains the shopping cart items the shopper checked out from the eCommerce site. It is possible that the document will not contain any items if the shopper is returning from the eCommerce site with an empty cart. Cart Transmission The PunchOutOrderMessage must be sent back to the eProcurement system from the shoppers web browser. Upon submitting the cart via an HTML form, the user will return to the eProcurement system and no longer be on the suppliers site. Read more →

cXML PunchOut Edit/Inspect

Overview The cXML Edit/Inspect feature allows shoppers to return to a PunchOut site to make changes or view a cart that was previously checked out. This is accomplished by setting the value of the PunchOutSetupRequest[@operation] attribute to "edit" or "inspect" instead of the usual value of "create". A common use case for this feature is to allow shoppers to adjust the quantities of items in their cart when the quantity changes may effect shipping costs or unit prices (tiered pricing). Read more →

cXML Quote Request

Overview The cXML QuoteRequest and QuoteMessage documents provide a standard for buyers sending RFQ’s to suppliers and suppliers responding with quotes. Read more →

Frameless PunchOut v1

Below is a draft specification proposed by EqualLevel for solving two common problems with PunchOut that are typically solved by wrapping the PunchOut site in a frame. Currently this functionality is supported by the EqualLevel eProcurement system and a number of suppliers that have opted to provide a better PunchOut experience to their users. Frameless PunchOut Specification v1 When punching out from an eProcurement system to a punchout site, a frame may be placed around the punchout site. Read more →

OCI RoundTrip

What is OCI RoundTrip? OCI RoundTrip is SAP’s version of PunchOut. OCI RoundTrip only covers the catalog/shopping part of eProcurement. Electronic orders, order confirmations, ship notices, and invoices are not covered by the OCI specification. Using a gateway solution to map between OCI and cXML should be considered before adding support for OCI RoundTrip to an eCommerce store that supports cXML PunchOut. Login Request Authentication is done via an HTTP request sent from the users browser to the eCommerce website. Read more →

PunchOut Catalogs

What is PunchOut? PunchOut is a technology that connects a buyer’s eProcurement application (used to purchase goods and services) directly to their suppliers’ eCommerce sites. PunchOut enables a buyer’s employees to shop on suppliers’ eCommerce sites, but complete their purchase in their organization’s eProcurement application, where approval workflows can be applied and spending can be tracked. PunchOut Workflow An employee logs in to their company’s eProcurement system. The employee selects a supplier eCommerce site to " Read more →

Transactions

Overview Electronic orders and invoices can streamline processes for both buyers and suppliers. Electronic transactions can replace traditional forms of communication such as Phone, Fax, and Email. cXML and EDI are the most commonly used standards for B2B transactions. Transaction Types Type cXML ASC X12 EDIFACT Order OrderRequest 850 ORDERS Change Order OrderRequest Read more →