### Response behaviour

The HTTP response body is always a single resource.  Check `resourceType` to determine the outcome:

| `resourceType` | Condition | Details |
|----------------|-----------|---------|
| `Bundle` (type `transaction-response`) | Order is directed and successfully processed | All fulfillment Tasks had an `owner` and the transaction committed. |
| `OperationOutcome` (severity `error` or `fatal`) | Order failed validation or cannot be processed | `issue.details` describes the problem; do not retry without correcting the reported issues. |
| `OperationOutcome` (severity `information`) | Order is undirected — no fulfillment Task has an `owner` | The order has been lodged for later routing. This is not an error; no corrective action is required. |
{: .table-bordered}

### Response examples

| Example | Description |
|---------|-------------|
| [Directed Order Success](Bundle-eorders-submit-response-success.html) | Transaction-response Bundle returned when all fulfillment Tasks have an owner and the order is successfully processed. |
| [Error Response](OperationOutcome-eorders-submit-response-error.html) | OperationOutcome returned when the submitted Bundle fails validation or cannot be processed. |
| [Undirected Order Response](OperationOutcome-eorders-submit-response-undirected.html) | Informational OperationOutcome returned when no fulfillment Task has an owner; the order has been lodged for later routing. |
{: .table-bordered}
