# dispatch_not_available_for_channel (/en/docs/errores/dispatch_not_available_for_channel)

The empresa’s emission channel cannot express this `dispatch` field.

|                |                                                               |
| -------------- | ------------------------------------------------------------- |
| **Code**       | `dispatch_not_available_for_channel`                          |
| **Type**       | `unprocessable_error` — Well formed, but breaks a domain rule |
| **HTTP**       | `422`                                                         |
| **Retriable?** | No                                                            |

## What to do [#what-to-do]

Two `dispatch` fields are refused on `emission_channel=sfg` and accepted on `emission_channel=mercado`, both because the SII portal’s guía form has nowhere to put them. `dispatch.destination`: that form carries a single address — the receptor’s — so a separate destination could not be printed; put the delivery address in `receptor.address`. `dispatch.dispatch_type`: the form’s only traslado select is the kind of movement, and it has no TipoDespacho input at all, so on whose account the despacho moves cannot be stated there. On the mercado lane the engine writes them into the DTE’s `IdDoc/TipoDespacho` and `Transporte` block. Both are refused rather than silently dropped.

> **Warning**
>
> Retrying the same request will fail the same way. Change the request, not the frequency.

## The envelope [#the-envelope]

```json
{
  "error": {
    "type": "unprocessable_error",
    "code": "dispatch_not_available_for_channel",
    "message": "…",
    "hint": "Two `dispatch` fields are refused on `emission_channel=sfg` and accepted on `emission_channel=mercado`, both because the SII portal’s guía form has nowhere to put them. `dispatch.destination`: that form carries a single address — the receptor’s — so a separate destination could not be printed; put the delivery address in `receptor.address`. `dispatch.dispatch_type`: the form’s only traslado select is the kind of movement, and it has no TipoDespacho input at all, so on whose account the despacho moves cannot be stated there. On the mercado lane the engine writes them into the DTE’s `IdDoc/TipoDespacho` and `Transporte` block. Both are refused rather than silently dropped.",
    "retriable": false,
    "doc_url": "https://docs.facturia.cl/errors/dispatch_not_available_for_channel",
    "request_id": "req_01K2R7Q9M4T2VB"
  }
}
```

Program against `code`, never against `message` — the prose can be rewritten, the code cannot (§5.8).

`hint` and `retriable` arrive in the response with these exact values: they are a function of `code` and come from the same dictionary `GET /v1/error_codes` serves, so the envelope and the dictionary cannot disagree. Both are English on the wire by design — one registry, one language. More in [The error envelope](/en/docs/errores).

## See also [#see-also]

- [Every code](/en/docs/errores/codigos): The full table, grouped by where you will run into it.

- [The error envelope](/en/docs/errores): The nine types, the request_id and how to handle them in practice.

The machine-readable copy of this page lives at `GET /v1/error_codes`, unauthenticated.