Templates Overview
PunchOut ships 22 mapping fixtures. Magento synchronizes them during setup:upgrade and marks them as active reusable templates in All Store Views.
Select a template only while creating a mapping profile. Its rules are copied into the new profile, where you can review and change them. A future package update may refresh the reusable system template but does not silently rewrite the copied runtime profile.
Runtime boundary
Buyer profiles can use only active outbound, non-template profiles. The six inbound fixtures document expected setup fields and support future/custom normalization work, but the current OCI login and cXML setup controllers parse their supported fields directly. Assigning an inbound profile to a buyer is not supported by the core runtime.
Template names describe an intended starting point. They do not certify an integration with SAP, SAP Ariba, Coupa or Oracle Procurement. Confirm protocol versions, mandatory fields, classification schemes and custom extrinsics with the buyer.
Complete template catalog
| Template | Direction | Intended starting point | Runtime note |
|---|---|---|---|
oci_inbound_core |
Inbound | Generic OCI login fields | Reference/custom use; not assigned to buyers |
oci_outbound_core |
Outbound | Six required OCI cart fields | Copy to a runtime profile |
oci_outbound_extended |
Outbound | Optional OCI enrichments | Combine with required core rules as needed |
sap_oci_v4_inbound_login |
Inbound | SAP OCI 4 login fields | Reference/custom use; not assigned to buyers |
sap_oci_v4_outbound_core |
Outbound | SAP OCI 4 cart return | Copy to a runtime profile |
sap_oci_v5_inbound_login |
Inbound | SAP OCI 5 login fields | Reference/custom use; not assigned to buyers |
sap_oci_v5_outbound_core |
Outbound | SAP OCI 5 cart return | Copy to a runtime profile |
sap_oci_v5_outbound_hierarchy |
Outbound | OCI 5 hierarchy/material-group fields | Copy when the buyer requires those fields |
sap_oci_v5_outbound_secure |
Outbound | Eight mandatory OCI 5 fields | Use only with complete source data |
cxml_inbound_posr_core |
Inbound | Generic PunchOutSetupRequest fields |
Reference/custom use; not assigned to buyers |
cxml_outbound_core |
Outbound | Core PunchOutOrderMessage item data |
Copy to a runtime profile |
cxml_outbound_level2 |
Outbound | Optional level-2 enrichments | Add required core rules as needed |
ariba_cxml_inbound_posr_1_2_x |
Inbound | Ariba-oriented setup fields | Reference/custom use; not assigned to buyers |
ariba_cxml_outbound_core |
Outbound | Ariba-oriented core item data | Copy to a runtime profile |
ariba_cxml_outbound_level2 |
Outbound | Manufacturer and buyer extrinsics | Copy when required by the buyer |
ariba_cxml_outbound_level2_strict |
Outbound | Same 12 fields, all mandatory | Use only with complete source data |
coupa_cxml_inbound_posr_1_2_014 |
Inbound | Coupa-oriented setup fields | Reference/custom use; not assigned to buyers |
coupa_cxml_outbound_poom_1_2_023 |
Outbound | Coupa-oriented order message | Copy to a runtime profile |
coupa_cxml_outbound_poom_1_2_023_strict |
Outbound | Same 10 fields, all mandatory | Use only with complete source data |
oracle_cxml_inbound_posr_1b |
Inbound | Oracle-oriented setup fields | Reference/custom use; not assigned to buyers |
oracle_cxml_outbound_1b_core |
Outbound | Oracle-oriented order message | Copy to a runtime profile |
oracle_cxml_outbound_1b_core_strict |
Outbound | Same 10 fields, all mandatory | Use only with complete source data |
Continue with the Template Selection Guide and the detailed protocol pages: