PunchOut with M-Power — Guide for Procurement Teams – M-Power Software Help Centre

Audience: Customer procurement / IT administrators
Last updated: July 2026

What PunchOut does for you

PunchOut connects your procurement system (SAP Ariba, Coupa, Oracle, and similar) directly to your M-Power supplier catalogue. Your buyers shop your agreed products at your agreed pricing without leaving your procurement system, and the cart flows straight back for approval — no manual re-keying, no separate logins.

What we need from you

To set up the connection, please provide your M-Power contact with:

Item	Notes
Your Network ID (ANID)	Your procurement system's identity. In SAP Ariba this is your Ariba Network ID.
Supplier Identity	The identity you will address the connection to (we will confirm the exact value).
Test vs production	Let us know whether you're configuring your test or production environment.

We will generate a shared secret and send it to you securely, along with the exact setup URL to enter in your procurement system. Please use the full URL we provide (it ends in /punchout/setup/) — entering only the website address will prevent the connection from working.

What to expect

A buyer starts a PunchOut session from your procurement system and is taken to your M-Power catalogue.
They add items and click Return to Procurement System; the cart appears back in your requisition automatically.
After your normal approval, your system sends us the purchase order and we confirm receipt.

Product classification (UNSPSC)

Every line we return carries a UNSPSC classification code, so items are categorised correctly in your procurement reporting. Where a product has a specific code it is used; otherwise a sensible default for our catalogue is applied. If your organisation requires particular UNSPSC codes for our products, let us know and we can set them per product.

Support

If a buyer has trouble starting a session or a cart doesn't return correctly, contact M-Power support with the date/time and the buyer's name so we can trace the session. It helps to note whether the catalogue opened at all, and whether the issue was on starting the session or returning the cart.