> ## Knowledge Base Index > Fetch the complete knowledge base index at: https://support.haddock.app/sitemap.xml > Use this file to discover available pages before exploring further. > Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash). # BDP Connector ✨ New and recommended > ⭐ **Recommended method for connecting BDP to haddock** haddock Connector is a small program that is installed on your restaurant computer and automatically sends sales from BDP to haddock. Once configured, it runs by itself and you do not have to do anything else. [📄 Download full PDF guide](https://storage.googleapis.com/haddock-connector/haddock-connector-latest-install-guide-bdp.pdf) --- ## What do I need before starting? * The computer where BDP is installed must be **turned on and running BDP**. * You need **access to that computer** to install the program. If you are not physically at the venue, you can ask someone there to give you remote access with **AnyDesk** or **TeamViewer** - these are free programs that let you see and control the computer from another location. * Have the **BDP username and password** and the **export profile number** handy: they do not exist by default, they are created in the **"Before installing - set up BDP"** section (usually by your BDP reseller or technician). * And the **haddock authentication code** (you will find it in the haddock web app, under Restaurant settings > My integrations > BDP Connector). > 💡 **Tip:** If you do not have all the details or do not feel confident doing the installation, the easiest option is to **send everything to your BDP reseller or technician**. Share the [PDF guide](https://storage.googleapis.com/haddock-connector/haddock-connector-latest-install-guide-bdp.pdf) and the haddock authentication code with them - they will be able to do the installation and setup remotely without you having to handle anything technical. --- ## Before installing - set up BDP The connector reads sales through BDP's local API, **WebLinkRestAPI**. Before installing it, that API has to be enabled, plus a user for haddock and an export profile - usually done by **your BDP reseller or technician**. Those steps produce the three values the connector asks for: **Login**, **Password**, and **Export Profiles**. > ✅ **If a step is already set up, do not change it:** write down the value and move on to the next one. Reconfiguring something that already worked can break another integration. > > 📌 The screenshots come from BDP.NET 33.2 and 38.5; on other versions some menus may live elsewhere. ### A - Activate the WebLinkRestAPI license It is a **free subscription** for the haddock integration; the reseller requests it from BDP. 1. In **[portal.bdpcenter.com](https://portal.bdpcenter.com)** (with the reseller credentials), go to **ADMINISTRACIÓN DE LICENCIAS > SUSCRIPCIONES > LISTAR SUSCRIPCIONES**. A **WEBLINK REST API** subscription must be listed. ![Subscription list in the BDP portal showing the WEBLINK REST API subscription](https://storage.googleapis.com/helpdesk-haddock-images/integrations/point-of-sale/bdp-connector-new-and-recommended/images/pos-setup-01-bdp-portal-subscriptions-weblinkrestapi.png) 2. Activate it inside BDP, under **Utilidades > Control de Licencias > Subscripciones Extendidas**. ![Utilidades > Control de Licencias > Subscripciones Extendidas menu in BDP](https://storage.googleapis.com/helpdesk-haddock-images/integrations/point-of-sale/bdp-connector-new-and-recommended/images/pos-setup-02-bdp-license-control-extended-subscriptions-menu.png) 3. Fill in the form with the **subscription number** and the **client name** shown in the subscription details in the portal. If it is correct, a **green** message appears. ![Subscription details with the number and the client name](https://storage.googleapis.com/helpdesk-haddock-images/integrations/point-of-sale/bdp-connector-new-and-recommended/images/pos-setup-03-bdp-subscription-number-and-client-name.png) > **Already done?** If the subscription is already listed in the portal and BDP has the **Utilidades > Configuración Servicios Web** option, move on to step B. ### B - Configure the service (login and commands) 1. Go to **Utilidades > Configuración Servicios Web**. If this option is missing, the subscription from step A is not properly activated. ![Utilidades > Configuración Servicios Web menu in BDP](https://storage.googleapis.com/helpdesk-haddock-images/integrations/point-of-sale/bdp-connector-new-and-recommended/images/pos-setup-04-bdp-configure-web-services-menu.png) 2. In the **WebLinkRestApi** tab, create a line with **Activo** and **Login Obligatorio** checked, **IP Address** `Any`, **IP Port** `5555`, and a long random **Clave de Encriptación**. The key shown in the screenshots is only an example; do not reuse it. > **Leave the "Conexión Segura" (Secure connection) checkbox unchecked.** Scroll horizontally to the right to find it. ![WebLinkRestApi settings with Activo and Login Obligatorio checked and port 5555](https://storage.googleapis.com/helpdesk-haddock-images/integrations/point-of-sale/bdp-connector-new-and-recommended/images/pos-setup-05a-bdp-weblinkrestapi-service-settings.png) ![WebLinkRestApi settings scrolled to the right with Conexión Segura unchecked](https://storage.googleapis.com/helpdesk-haddock-images/integrations/point-of-sale/bdp-connector-new-and-recommended/images/pos-setup-05b-bdp-weblinkrestapi-secure-connection-unchecked.png) 3. Scroll horizontally back to the left and click **`+` to the left of the service row** to reveal the **Login** and **Password** fields. Fill them in with the credentials you will enter in Step 2 of the connector. Then click **`+` to the left of the login row** to show the commands and enable the **3 commands** haddock needs: *Perfiles de exportación: Exportar Documentos*, *Perfiles de exportación: Exportar Ventas detalladas*, and *Listar artículos*. If one is missing, the connector will connect but sales or articles will not arrive. > 🔒 Use a long, unique password: it grants access to the POS sales and articles. The `test1234` in the screenshot is only an example; do not reuse it. ![Expanded WebLinkRestApi row showing Login, Password, and the three required commands](https://storage.googleapis.com/helpdesk-haddock-images/integrations/point-of-sale/bdp-connector-new-and-recommended/images/pos-setup-05-bdp-weblinkrestapi-login-password-and-commands.png) 4. Save the changes. > **Already done?** If there is already an active line on port 5555 with a Login and Password, **do not change them** (another integration may be using them): write them down as they are, check the 3 commands, and make sure **Conexión Segura is unchecked**. > 💡 **Firewall:** if the connector is installed on the **same computer** as BDP (the recommended setup), there is nothing to change in the firewall or the router. If BDP runs on **another computer**, open port **5555** in the *Windows Firewall* with an inbound **TCP** rule set to **Allow the connection** - restricted to the connector's IP if your firewall or router allows it. ### C - Create the export profile 1. Go to **Utilidades > Importación/Exportación de Datos > Parámetros de Exportación**. ![Utilidades > Importación/Exportación de Datos > Parámetros de Exportación menu](https://storage.googleapis.com/helpdesk-haddock-images/integrations/point-of-sale/bdp-connector-new-and-recommended/images/pos-setup-06-bdp-export-parameters-menu.png) 2. Fill in the form: * **Código:** any free number, for example `1234`. ⚠️ **This is the number to enter in the Connector's "Export Profiles" field.** * **Descripción:** anything, for example "exportación ventas haddock". * **Terminal Inicial / Terminal Final:** with a single terminal, put the same number in both fields; with several, every terminal in the range is exported (`1` to `4` exports terminals 1, 2, 3, and 4). * **Tipo Exportación:** **WebLink**. * **Datos de Venta a Exportar:** **Fra. Simpl. Barra** and **Fra. Simpl. Mesa**. ![Export form with the code, WebLink type, and the bar and table simplified invoices](https://storage.googleapis.com/helpdesk-haddock-images/integrations/point-of-sale/bdp-connector-new-and-recommended/images/pos-setup-07-bdp-export-profile-general-tab.png) 3. Checking those adds two new tabs (**Fra. Simpl. Barra** and **Fra. Simpl. Mesa**). In **each one**, check **all** the boxes in the three columns: if you leave fields unchecked, sales will reach haddock incomplete. ![The three columns of fields with every box checked](https://storage.googleapis.com/helpdesk-haddock-images/integrations/point-of-sale/bdp-connector-new-and-recommended/images/pos-setup-08-bdp-export-profile-all-fields-selected.png) 4. Save with **F5**. > **Already done?** If a profile with **Tipo Exportación: WebLink** already exists, reuse it: write down its **Código** and check that Barra and Mesa are ticked with every field in the three columns. --- ## Step 1 - Download and install 1. On the computer where BDP is installed, download the haddock Connector installer from **[bit.ly/haddockconnector](https://bit.ly/haddockconnector)**. 2. Open the downloaded file. If Windows asks for permission (Windows protection screen), click **"More info"** and then **"Run anyway"**. ![Windows Defender warning](https://storage.googleapis.com/helpdesk-haddock-images/integrations/point-of-sale/bdp-connector-new-and-recommended/images/01-windows-defender-smartscreen-warning.png) ![Run anyway](https://storage.googleapis.com/helpdesk-haddock-images/integrations/point-of-sale/bdp-connector-new-and-recommended/images/02-windows-defender-smartscreen-run-anyway.png) 3. Follow the installer steps: * Welcome screen: ![Installer welcome](https://storage.googleapis.com/helpdesk-haddock-images/integrations/point-of-sale/bdp-connector-new-and-recommended/images/03-haddock-connector-installer-welcome-screen.png) * Select the destination folder: ![Destination folder](https://storage.googleapis.com/helpdesk-haddock-images/integrations/point-of-sale/bdp-connector-new-and-recommended/images/04-haddock-connector-installer-select-destination-folder.png) * Make sure the **"Create a desktop shortcut"** option is checked. ![Additional tasks](https://storage.googleapis.com/helpdesk-haddock-images/integrations/point-of-sale/bdp-connector-new-and-recommended/images/05-haddock-connector-installer-select-additional-tasks-desktop-shortcut.png) * Review the summary and click **"Install"**. ![Ready to install](https://storage.googleapis.com/helpdesk-haddock-images/integrations/point-of-sale/bdp-connector-new-and-recommended/images/06-haddock-connector-installer-progress.png) 4. When installation finishes, make sure **"Launch haddock Connector"** is checked and click **"Finish"**. The program will open automatically. ![Finish installation](https://storage.googleapis.com/helpdesk-haddock-images/integrations/point-of-sale/bdp-connector-new-and-recommended/images/07-haddock-connector-installer-finish-and-launch-application.png) --- ## Step 2 - Configuration When you open haddock Connector, you will complete two screens: first connect BDP, then link your haddock restaurant. **1. Connect your POS** * On the **Which POS do you use?** screen, select **BDP**. * In **Login** and **Password**, enter the credentials of the user created in step **B** of "Before installing - set up BDP". * If you need to change the port or use another computer, expand **Connection settings**. The default port is **5555**. In **BDP Server IP**, enter the IP address of the computer running BDP if it is different from this one. If you leave the IP empty, the Connector will look for BDP on this same computer. * Click **Continue**. ![BDP selection and login and password fields on the Connect your POS screen](https://storage.googleapis.com/helpdesk-haddock-images/integrations/point-of-sale/bdp-connector-new-and-recommended/images/08-haddock-connector-app-connect-bdp.png) **2. Link a restaurant** * **Restaurant name (optional):** enter a name to identify it in the Connector. * **Authentication Code:** go to haddock and open **Restaurant settings > My integrations > BDP Connector**. Copy the 10-character code shown there and paste it here. Each restaurant has its **own** code. * **Export Profiles:** enter the **Código** of the profile created in step **C** (for example, `1234`). For multiple profiles, separate them with commas: `3,7`. ⚠️ **Do not leave it empty:** an empty field uses profile **0**, not all profiles. ![Linking a restaurant with its authentication code and export profiles](https://storage.googleapis.com/helpdesk-haddock-images/integrations/point-of-sale/bdp-connector-new-and-recommended/images/09-haddock-connector-app-link-restaurant.png) **3. Import and sync preferences** You can keep the defaults or expand this section to change them: * **Sales history to import:** defaults to **Last 180 days**. You can also select **Last year** or **Choose dates**. * **Sync interval:** defaults to **30 minutes**. --- ## Step 3 - Connect Click **Connect restaurant**. The Connector will check the connection to BDP, the username and password, API access, and the connection to haddock. It will also check the authentication code. If everything is correct, your configuration will be saved and you will reach the **Connections** screen, where you can follow the sales sync. If there is a problem, the Connector will highlight the field you need to correct or show a message explaining the issue. See the **Errors and solutions** section of this guide. > 💡 The initial check does not verify that the export profile exists or includes the correct terminals. Review its configuration in step **C** of "Before installing - set up BDP". --- ## How do I know it is working? On the **Connections** screen, you will see your linked restaurants, their status, and when each one was **last synced**. During the first import, you will see **"Importing your sales history"** along with its progress. This can take a while if there is a lot of history. ![BDP Connections screen while importing sales history](https://storage.googleapis.com/helpdesk-haddock-images/integrations/point-of-sale/bdp-connector-new-and-recommended/images/10-haddock-connector-app-importing-sales-history.png) When the sync finishes successfully, the restaurant will show **"Up to date"** and its last sync time will be updated. ![BDP restaurant up to date with its last sync time and the Sync Now button](https://storage.googleapis.com/helpdesk-haddock-images/integrations/point-of-sale/bdp-connector-new-and-recommended/images/11-haddock-connector-app-up-to-date.png) Under **Runs automatically**, you can see how often sales are synced. To start a manual sync, click **Sync Now**. This button is hidden while history is being imported and disabled if a sync is already running. --- ## Day-to-day use * The program **runs in the background** - you do not need to keep it open. When you close the window, it minimizes to the notification area (bottom right of the Windows desktop) and keeps working. * To open it again, **click the icon** in the notification area. * It updates and restarts itself if there is any problem - you do not need to worry about anything. --- ## 🔧 Errors and solutions If there is a problem when connecting, the Connector will highlight the field you need to correct or show a message explaining the issue. Look it up here to see what to do: ### 🚨 "API not accessible on localhost:5555. Make sure BDP is running on this machine." ✅ BDP is not open, is on another computer, the port is wrong, or a firewall/antivirus is blocking the port. Check that: * BDP is **open and running** on the correct computer. * The port under *Connection settings* is **5555** (the default). If BDP runs on another machine, enter its IP address in **BDP Server IP** under **Connection settings**. * If opening **http://localhost:5555** in the browser on that machine loads nothing, BDP's API is not listening there: contact your BDP reseller. ### 🚨 "BDP server is reachable but login failed." ✅ The username or password is wrong. Verify them with your BDP reseller or technician. ### 🚨 "BDP license is not activated or login credentials are invalid." ✅ BDP's integration module is not enabled. Ask your BDP reseller to enable it and to confirm your username, password, and export profile number. ### 🚨 "Cannot reach haddock cloud." ✅ The computer has no internet access, or a firewall/proxy/antivirus is blocking the secure (HTTPS) connection to haddock. Check the computer's internet connection and that the firewall or antivirus allows outbound HTTPS traffic to haddock. If the message says the cloud "is reachable but rejected the request", it is a temporary issue: try again in a few minutes. ### 🚨 "Authentication code is invalid" / "Invalid authentication code format." ✅ The code was copied incorrectly or has expired. Go to the haddock web app (**Restaurant settings** > **My integrations** > **BDP Connector**), generate a new one, and paste it in full. Codes expire if they are not used. ### 🚨 I do not have the username, password, or export profile number ✅ They do not come out of the box: they are created in BDP before installing the connector. Ask your BDP reseller or technician for them and share the **"Before installing - set up BDP"** section of this article, which has the exact steps. ### 🚨 The sync finishes, but I do not see sales ✅ Check that you are viewing the correct restaurant and dates in haddock, that BDP has sales for that period, and that those dates are included in the history you imported. Also check **Export Profiles**: go to **Connections**, select the restaurant, and click **Edit configuration**. The numbers must match the **Código** of the profiles created in BDP. An empty field uses profile **0**, not all profiles. In BDP, open **Utilidades > Importación/Exportación de Datos > Parámetros de Exportación** and check that each profile: * Exists and has **Tipo Exportación: WebLink**. * Includes the correct terminals in **Terminal Inicial / Terminal Final**. * Has **Fra. Simpl. Barra** and **Fra. Simpl. Mesa** selected, with all fields in the three columns checked in both tabs. The initial connection check does not validate these profiles: a successful connection does not guarantee you are exporting sales from the right restaurant. After correcting the Connector details, click **Save configuration**. When no history import or sync is running, you can click **Sync Now** under **Connections**. If sales from earlier dates are still missing, contact support to review the import for that period. --- ## The connector was working and now it fails * **I do not see sales right after connecting:** the first import can take a while if there is a lot of history. Check its progress under **Connections** and wait for it to finish. The **Sync Now** button is not shown during the import. * If you see **"Sync is temporarily delayed"**, the Connector will try again automatically. Click **View details** to see the problem and review the **Errors and solutions** section of this guide. * The connector also shows **notifications in the Windows notification area** (bottom right) when it has been unable to reach the POS or haddock for a while. * Check that the POS computer is **powered on** and that BDP is still running. Still not working after checking this? See **[How to fix connection problems with my POS](https://support.haddock.app/en/article/how-to-fix-connection-problems-with-my-pos-oasu2t/)** or contact haddock support chat. --- ## My articles look wrong or are missing in haddock The connector pushes both **sales** and the **article catalog** automatically (catalog every **6 hours** by default). If the catalog still looks broken — wrong names, missing modifiers/combos, or "BARCELO & COCA COLA \| BARCELO & KAS LIMON \| …" style accumulated names on a single article — you can request a refresh from the haddock web app: 1. Go to **Restaurant settings** > **My integrations** > **BDP Connector**. 2. Click **"Refresh"**. This requests both a sales resync and a **catalog resync**. The Connector will pick up the request when it next communicates with haddock; the refresh may take some time and requires the computer to be on, connected to the internet, and running the Connector. The button is rate-limited to once every 12 h per integration. If after the refresh the catalog still looks wrong, contact support — the issue is on the connector / BDP side and needs investigation. *Integrations may include additional costs not covered by haddock.*