PunchOut Integration (OCI & cXML)

DJUST supports PunchOut integration to seamlessly connect with enterprise procurement systems (ERPs), allowing B2B buyers to access the DJUST catalog directly from their purchasing tools.

PunchOut offers a frictionless and secure experience where product selection is done on DJUST’s interface, while order validation and submission remain controlled by the buyer’s procurement system.


💡What is a PunchOut?

A PunchOut is a B2B integration pattern where a customer’s procurement platform (e.g., SAP Ariba, Coupa, Oracle, Jaggaer…) opens a secure session to a supplier’s catalog — in our case, DJUST — and allows users to:

  1. Browse products in real time
  2. Add them to a virtual cart
  3. Send the selection back to the ERP for order approval and processing

This enables centralized purchasing governance while maintaining up-to-date product, price, and stock information.


🎯 Key Use Cases

  • Buyers access their personalized catalog on DJUST (supplier's catalog) with negotiated prices and availability.
  • Purchasing flows remain entirely controlled by the ERP, including budgets, validations, and invoicing.
  • No double entry: data selected on DJUST is directly transferred back into the ERP.
  • Ideal for large enterprise customers, especially those with strict procurement workflows.

🔌 Standards Supported

DJUST currently supports two major PunchOut standards:

ProtocolDescriptionCommonly used with
OCIOpen Catalog Interface (SAP standard)SAP ECC / S/4HANA
cXMLCommerce XML standard for catalog + order exchangeAriba, Coupa, Oracle, Jaggaer
ℹ️

Note

Each standard has its own flow, payload structure, and authentication method. DJUST adapts to both and offers customization capabilities as needed.


🛠️ Typical Workflow

  1. The buyer launches the PunchOut session from their ERP
  2. DJUST opens a session and presents a storefront with prefiltered catalog data
  3. The buyer browses and selects products
  4. Upon submission, the cart is sent back to the ERP via:
    1. OCI Hook_URL redirect (in OCI)
    2. cXML PunchOutOrderMessage (in cXML)
  5. The ERP finalizes the order and can trigger a downstream API call to DJUST (optional)
sequenceDiagram
    participant Buyer ERP
    participant DJUST
    participant Storefront
    participant ERP System

    Buyer ERP->>DJUST: 🔗 Initiate PunchOut session (OCI / cXML)
    DJUST-->>Storefront: Open personalized catalog
    Storefront-->>Buyer ERP: Display products

    Buyer ERP->>Storefront: 🛍️ Select and submit cart

    alt OCI
        Storefront-->>Buyer ERP: 🔁 Redirect with cart data (HOOK_URL)
    else cXML
        Storefront-->>Buyer ERP: 📨 Send PunchOutOrderMessage
    end

    Buyer ERP->>ERP System: 📥 Validate and register order

    opt Optional integration
        ERP System->>DJUST: 📡 Call DJUST API to place order
    end

📌 Requirements

To enable PunchOut on DJUST, you will need:

  • A configured buyer account (with appropriate catalog access)
  • A store configured for PunchOut use
  • The appropriate authentication setup (shared secret, static token, etc.)
  • If applicable: mapping rules for custom fields, cost centers, or delivery info