Purpose
Replace every bracketed placeholder, confirm the supplier and Optiply EDI contact addresses, and prepare your introduction. The template itself sends no message. Configuration, approval and testing are separate steps before using the connection.
Email template
To: [supplier contact email]
CC: [confirmed Optiply EDI contact email]
Subject: Optiply EDI integration setup
Dear [supplier contact],
We would like to discuss an EDI connection between our purchasing process and your system. We have copied our Optiply contact so we can discuss the requirements and next steps together.
Please let us know who should join the setup conversation from your team. Keep our Optiply contact copied when replying so we can coordinate the questions and agree which data will be exchanged before the connection is put into use.
- Best regards,
- [Your name]
- [Your company]
Before you start
Have the supplier contact details and your sender/company details ready. Confirm the appropriate Optiply EDI contact before sending; if you need help finding that contact, contact Support.
Information to include
- Supplier contact: the person who can coordinate the connection with your supplier, plus their email address.
- Optiply EDI contact: the confirmed address to copy on the setup conversation.
- Your name and company: the sender details the supplier needs to recognise your request.
Steps
- Copy the subject and message into your email client.
- Replace every bracketed placeholder, including the To and CC addresses.
- Check the recipients and message, then send it through your own email client.
What happens next
Keep the agreed contacts copied during setup coordination. Confirm the data to be exchanged before using the connection. See Configure EDI purchasing for a supplier for the separate supplier settings.
Limitations
Sending this email starts the discussion; the connection still needs configuration, approval and testing before use.
Troubleshooting
If a recipient or placeholder is unclear, check it before sending. Do not include passwords, API keys or other sensitive setup information in the introduction. Share those details only through the secure channel agreed with the EDI team.