PunchOut
PunchOut: standards, procurement systems and store platforms
cXML, OCI and Level 2 PunchOut, the procurement systems that request them, and what each store platform needs to support a buyer session.
Procurement systems
-
PunchOut for Ariba
PunchOut for SAP Ariba suppliers: routing through SAP Business Network, the PunchOut URL, authentication, session rules, size limits and the tests SAP lists.
-
PunchOut for Coupa
What Coupa asks of a PunchOut supplier: setup fields, the BuyerCookie rule, create and inspect only, 60 seconds per purchase order and 5 retries.
-
PunchOut for SAP
What an SAP buyer asks of a PunchOut catalog: the OCI call structure, ISO unit codes checked against T006, material groups, price validation and the PO route.
Standards
-
cXML PunchOut
The cXML documents of a PunchOut order in the order they travel: setup request, setup response, cart and purchase order, with samples and status codes.
-
Level 2 PunchOut
How Level 2 PunchOut works: the index catalog and its fields, store, aisle, shelf and product levels, SelectedItem, and what the store has to support.
-
OCI PunchOut
OCI PunchOut field by field: the call-up parameters, the NEW_ITEM fields with their lengths, a worked cart example, Secure OCI and where sessions fail.
-
PunchOut supplier checklist
The 38 things a supplier store needs for cXML and OCI PunchOut, in six groups: session, purchase orders, documents back, SAP, Level 2 and testing.
Store platforms
-
PunchOut for BigCommerce
What BigCommerce offers for PunchOut and what has to be built: login by JWT, one session per customer, price lists per plan, the cart API and the PO number.
-
PunchOut for Magento
What Magento offers for PunchOut and what has to be built: sign-in, shared catalogs, the 3,600-second cookie, frames, cart to cXML and the PO number.
-
PunchOut for Shopify
What Shopify offers for PunchOut and what has to be built around it: sign-in on Plus, B2B catalogs per plan, /cart.js to cXML, frames and the PO as draft order.
-
PunchOut for WooCommerce
What WooCommerce offers for PunchOut and what has to be built: sign-in by auth cookie, contract prices, the Store API cart in cents and the PO as REST order.
Tell us what you need
Tell us which systems you use and what needs to work better. We reply personally within one working day. We help you define the work, then agree the price and timing before you commit.
- You know the price and the timeline before you commit to anything
- We work out the connection that takes the work off your hands
- We handle the build, hosting, monitoring and maintenance
- Your team has less information to retype and fewer discrepancies to chase