Order Inject (transmitting orders to Unite)
The Order Inject interface is an automated way for transmitting purchase orders from your ERP or procurement system directly to Unite. Instead of emailing or uploading orders manually, your system sends them to us in a structured electronic format.
A PunchOut interface (OCI or cXML) is required. It enables you to transfer the basket you created on Unite back into your ERP system for approval. Once the order is approved, your system transmits it to us through the Order Inject interface.
When we receive the purchase order, we automatically send an order confirmation to the buyer’s email address or to a default email address stored in the system. Note: This confirmation only reflects that the order was received and doesn’t count as official acceptance.
Key data fields for processing
Below you’ll find the key data fields required for processing. Mandatory fields are marked with an asterisk (*). The fields are grouped into header level (which covers the entire order) and line level (which relates to individual line items).
Important: Please check the data is complete and follow the guidance in the tables so we can process your orders smoothly.
Header level data
Description | |
Unite customer number* | For example: 60123456 |
Order number* | Up to 10 characters are recommended; a maximum of 25 characters can be processed. |
Buyer contact details | Buyer contact details (name, email address and telephone number) help us resolve queries quickly. We use the email address to send order updates such as order confirmations. |
Invoice address* | Must include name, house number and street, postcode, town/city and country code. Please provide PO boxes as street information (e.g. ‘PO 1234’). If your organisation uses several invoice addresses, each order must include the correct one. If no invoice address is transmitted, we use the default invoice address from your Unite account. The invoice address must match the buying legal entity. Some countries (Belgium, Italy, Poland) require a VAT ID as part of the invoice address. If needed, we can also send invoices to the email address you transmit. |
Delivery address* | Must include name, house number and street, postcode, town/city and country code. Only one delivery address is permitted and must be transmitted at header level. Address name fields must not exceed 35 characters. We recommend placing key delivery details in the first 20 characters of name fields 1 and 2 so they appear correctly on parcel labels. Longer entries or additional name fields may not be processed. |
Supplier address* | We require at least one supplier ID or the supplier’s name. |
Currency* | For example: EUR for euros |
Line level data
Description | |
Line number* | Sequential number of the line item within the order |
Item number* | Unite item ID (transferred from OCI or cXML PunchOut) |
Basket ID | Depending on your PunchOut setup, the Unite basket ID is transmitted either separately (e.g. ‘a56bc7.1’ when using cXML) or as part of the item number (e.g. ‘56bc7.1@123-45678910’ when using OCI). |
Item description | Optional: short description based on the basket/PunchOut information |
Quantity* | Number of items ordered |
Order unit* | Coded unit (for example piece, pack, bottle) based on the basket/PunchOut information |
Unit price* | Net unit price based on the pricing quantity |
Line price* | Net price for the entire line (line price = quantity × unit price ÷ pricing quantity) |
Pricing quantity* | Quantity of items to which the unit price refers |
Cost centre | Optional |
Cost type | Optional |
Supported formats and transport protocols
We support the following formats and protocols:
Formats:
SAP IDoc XML (e.g. ORDERS05, Unite standard)
cXML (Unite standard)
openTRANS 1.0
openTRANS 2.1
EDIFACT (e.g. D96A & D10A)
Protocols:
HTTPS (Unite standard)
AS2 via HTTP or HTTPS
FTPS (server provided by you)
SFTP (server provided by you)
POP3/SMTP
Sample files
Below you’ll find commented samples in Unite’s standard formats: SAP IDoc ORDERS05 and cXML.