Purchase Order Integration (OrderRequest) Overview

  • Updated

The OrderRequest integration is used to transmit Purchase Order (PO) details between Unimarket and external systems. It follows the cXML standard, ensuring compatibility across a wide range of procurement and financial platforms.

 

Why Use This Integration?

This integration automates the communication of order details, reducing manual entry and errors. It is most commonly used for:

  • Outbound Updates: Unimarket sends PO details to a Supplier's system for fulfillment.

  • ERP Integration: Unimarket updates an external Finance/ERP system once a PO is generated to ensure financial records are synchronized.

 

Supplier Integration Setup

To enable electronic order dispatch, Community Administrators must configure the integration settings within the Supplier eStore.

  1. Navigate to the supplier eStore and select Edit Store.

  2. Go to the Integration tab and complete the following fields:

FieldPurpose
Dispatch Mechanism
  • The technical method used to send the message. Must match what the supplier supports (ask the supplier).
URL
  • This is the URL where the electronic PO's will be sent. The supplier will provide the URL. The destination address provided by the supplier or a Gateway (like Tranzsoft). 
  • If a Gateway is used to pass messages (between Unimarket and the supplier), the URL will be the gateway URL not the supplier URL. The supplier or Gateway service provider will provide
FROM Credential Domain
  • Identifies the sender's domain (e.g., "DUNS" or "NetworkID"). Key information for the supplier to identify the customer the order. 
  • If the supplier sets the 'FROM Credential Identity' as their DUNS number, this is usually set to the word DUNS (but can be anything).
FROM Credential Identity
  • Unique to each Community. This identifies exactly which customer is sending the order. It can be set to anything, but is commonly set to the Communities DUNS number.
TO Credential Domain
  • Identifies the supplier's domain. Where the orders are being sent to. 
  • If the supplier sets the 'TO Credential Identity' as their DUNS number, this is usually set to the word DUNS (but can be anything). It is rarely verified by the supplier.
TO Credential Identity
  • Identifies the specific supplier (often their DUNS number). It is rarely verified by the supplier.
Shared Secret
  • A secure password that must match in both Unimarket and the supplier's system. Both must match.

Note: While many settings remain static across a supplier's network, the FROM Credentials must be unique for every Community to ensure the supplier can distinguish between different customers.

 

Technical Documentation

For detailed XML schemas and message examples, refer to:

Integration > Transactions: Orders, Receipts, Invoices and More > OrderRequest Technical Documentation

 

Important Considerations

  • Gateway Usage: If a supplier uses a gateway service, the URL will be the gateway's endpoint rather than the supplier's direct server.

  • Authentication: The Shared Secret acts as the primary authentication layer. Ensure it is handled securely and matches the supplier-side configuration exactly.