> For the complete documentation index, see [llms.txt](https://docs.maitredpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-17-converter/tools/external-sales-posting/config.-service-web.md).

# Config. Service Web

### External Sales Posting

**Config. Service Web**

The External Order System (EOS) allows transmission of orders over the web.

**Activate Web Service**

Enable this option to setup the different parameters needed to establish communication with the EOS.

{% hint style="info" %}
NOTE: The External Sales Import option must also be enabled and the Directory specified in Converter / Tools / External Sales Posting / General
{% endhint %}

**Address**

Specify the URL of the web service the system must connect to.

**User Name**

Specify the user name to use when identifying the system with the EOS.

{% hint style="info" %}
NOTE: Each restaurant has its own user name and password.
{% endhint %}

**Password**

Specify the password to use when identifying the system with the EOS.

**Confirmation**

Confirm the password that must match the one specified in the above field.

{% hint style="info" %}
NOTE: The content of these two fields is always hidden.
{% endhint %}

**Diagnostic**

**Show Log**

Click this button to display the event journal.

**Verify Binding**

Click this button to confirm the communication configuration with the EOS.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.maitredpos.com/maitred/maitred-complete-online-documentation/chap-17-converter/tools/external-sales-posting/config.-service-web.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.