The delivery status of a transaction informs users if the receiver of the transaction successfully received the transaction in their Orderful organization and in their communication channel, which are then forwarded to their backend system.
The meaning of the delivery statuses in Orderful depends on the direction of the transaction:
- For outbound transactions (transactions you send to your partners), the delivery status will inform you if your partner’s communication channel received the transaction correctly.
- For inbound transactions (transactions you receive from your partners), the delivery status will inform you if your communication channel received the transaction correctly.
| Delivery Status | Outbound Transactions | Inbound Transactions |
| Pending | The transaction has been successfully created. The transaction is only available in your organization and hasn’t been sent to your trading partner yet. | The transaction is visible to your organization. It hasn’t been sent to your communication channel yet. |
| Sent |
The transaction has been sent to your trading partner, meaning it’s now available to your partner's organization in Orderful. It doesn’t mean your partner has sent this transaction to their communication channel yet. |
The transaction has been sent or resent to your communication channel. We don’t know yet if the delivery of this transaction has been successful. |
| Delivered |
The transaction was successfully delivered to your partner's communication channel.
|
The transaction was successfully delivered to your communication channel. |
| Failed |
Your partner tried to send the transaction to their communication channel. The transaction permanently failed to be delivered to their communication channel or failed to deliver the transactions after 3 retries. For more information see Definition of permanent delivery failures. Orderful won’t attempt to resend failed transactions automatically. Learn how to fix this issue with this article: Resolve a Failed Outbound Transaction |
You tried to send the transaction to your communication channel. The transaction permanently failed to be delivered to your communication channel or failed to deliver the transactions after 3 retries. For more information see Definition of permanent delivery failures. Orderful won’t attempt to resend Failed transactions automatically. Learn how to fix this issue with this article: Resolve a Failed Inbound Transaction |
Notes:
- You can only send a transaction with a Valid validation status.
- A transaction becomes Delivered or Failed depending on the type of communication channel used by the receiver.
See below to learn more about the definitions of a successful delivery, a temporary delivery failure, the Orderful retry system, as well as permanent delivery failures.
Definition of successful deliveries
| Communication Channel Type | Definition of successful delivery |
|
AS2 |
|
|
HTTP |
|
|
FTP/SFTP |
|
| Poller |
|
Definition of temporary delivery failures and Orderful retry system
| Communication Channel Type | Definition of temporary delivery failures | Details about delivery retries |
|
AS2/FTP/SFTP |
|
|
|
HTTP |
|
|
| Poller | It’s up to the integrator to define temporary failures and a retry system before confirming a transaction delivery. |
|
Orderful runs a retry system when a transaction temporary delivery failure is detected. Orderful retries sending a transaction to a communication channels 3 times:
- If a transaction is successfully delivered on the original delivery or on one of the delivery retries, the transaction delivery status becomes Delivered and the retry system stops.
- If a transaction fails to be delivered on the 3rd delivery retry, the transaction delivery status becomes Failed.
Each delivery failure or success during retries is captured in the audit trail and is available for both the sender and the receiver.
Definition of permanent delivery failures
| Communication Channel Type | Definition of permanent delivery failures |
|
AS2 |
|
|
HTTP |
|
|
FTP/SFTP |
|
| Poller |
|