Website Administrators should refer to this document went they are considering adding capabilities to their Commerce Vision powered website to allow access via Procurement Punchout by their customers.
Punchout capability is supported by the Customer Self Service Web Application but is not 'out-of-the-box' functionality. As such, Website Administrators should contact Commerce Vision to express their interest in having this functionality added.
This document provides a set of questions to be used as the basis of this process.
Questions to ask your customers when queried about puchout
- We support multiple Punchout functionalities through Customer Self Service, what is the punchout technology that is to be utilised?
- OCI – This is typically used by SAP systems
- CXML – Generally for non-SAP based systems
- How will the products be accessed by the customer?
- Will they be accessing a custom catalogue or the global catalogue?
- Is there mapping required between the Unit of Measure utilised by the customer system and yours? For example the customers system they are punching out from uses ‘Each’ whereas the CSS website uses ‘Pair’
- Is there mapping between Product Codes required? For example does the customer’s system use product code ‘A’ which is referencing product code ‘B’, or is the mapping relationship the same.
- Will there be differences in pricing or product availability based on location?
- In some cases, the pricing, availability and product types can differ depending on office, location and region. Is this required? For example Perth may only be able to purchase red shirts whereas Sydney may only be able to purchase blue.
- Is there an existing testing environment available?
- Can their ERP connect to the staging environment? - Although testing can be done by manually logging in, when punching out the interface may be different therefore testing is required.
