Communication Channel basics
Communication Channels are the connections that you and Orderful use to send and receive data. Other terms you may be familiar with are "Connectivity" or "Protocol".
Most Orderful customers connect to Orderful using our RESTful APIs, but many of their partners use legacy Communication Channels like AS2, VAN, or FTP. This means that you'll likely need some knowledge of these legacy systems in order to:
- Communicate with your partners while onboarding them.
- Understand your partner's Communication Channel requirements.
- Troubleshoot live delivery issues brought up by your partners.
Pros and Cons of Legacy Communication Channels
Legacy Communication Channels | Pros | Cons |
---|---|---|
AS2 (Recommended) Transmission over HTTP or HTTPS with certificate to encrypt and sign data |
|
|
FTP / SFTP / FTPS |
|
|
VAN Third-party services using electronic mailboxes to deliver data. |
|
|
Requirements for Legacy Communication Channel set up
Orderful will need different information Communication Channel type requires different information
Legacy Communication Channels | Information required by Orderful | Notes |
---|---|---|
AS2 (Recommended) Transmission over HTTP or HTTPS with certificate to encrypt and sign data |
| Orderful only supports synchronous, encrypted AS2 transmission with no compression using HTTPS or HTTP. |
FTP / SFTP / FTPS |
| Orderful supports Self-hosted FTP/SFTP and Orderful-hosted SFTP. |
VAN Third-party services using electronic mailboxes to deliver data. |
| Orderful supports VAN |
Updated over 1 year ago