What you need before you start
Coupa's punchout configuration is self-contained in the admin area, so a well-prepared enablement is quick. Have the supplier's cXML credentials and endpoint agreed in writing, decide which content groups should see the catalogue, and line up a test user with requisitioning rights.
With Lapasar, the supplier side arrives ready: credentials and the punchout URL are provided for your instance, catalogue views and contract pricing are scoped to your organisation, and the integration team supports session and cart-return testing until every field maps cleanly.
- Agreed cXML identities, shared secret and punchout URL
- Decision on which content groups get the catalogue
- A test user with requisitioning rights
- Commodity code and unit-of-measure mappings confirmed
Common issues and how to avoid them
Authentication failures are almost always credential mismatches — check the identity values and shared secret character for character on both sides. If the session opens but the cart fails to return, the culprit is usually the return (BrowserFormPost) handling or field mappings; testing with a small single-line cart isolates this quickly. Finally, confirm currency and unit-of-measure conventions with the supplier before go-live so requisition lines land clean.

