Articles on: Integrations

Generic Integration for POS Systems

The Generic Integration for POS Systems lets you connect any POS to haddock through a standard API. With this integration, sales and the product catalog are synchronized automatically, without needing to enter data manually.


It is the ideal solution for POS systems that do not have a native integration with haddock.



For restaurants: how to benefit


If your POS does not appear in haddock's list of native integrations, you can ask your POS provider or distributor to implement the connection through our Generic Integration.


The process is simple:


  1. Contact your POS provider and ask them to integrate haddock.
  2. The provider implements the connection using our API.
  3. You activate the integration from haddock in Settings > Integrations > Generic API for POS Systems. Activating the integration in haddock is free.
  4. Sales and the catalog are synchronized automatically.


Your provider can contact us to receive the technical documentation and a free test environment.



POS systems already integrated with the Generic Integration


Several POS systems already use haddock's Generic Integration to synchronize sales data. These include DSTnet, Ofibarman, Haleteo, Fourvenues, Madisa, and others.


If your POS is already compatible, you only need to activate the integration from haddock.



For POS systems that want to integrate


If you are a POS provider and want to offer haddock integration to your clients, contact us. We provide:


  • A free test account with a configured development environment.
  • API access credentials.
  • Full technical documentation.


Technical details


The API uses Basic HTTP authentication. The credentials (username and password) are generated from haddock's integration settings.


The integration lets you synchronize two types of data:


  1. Catalog: items, categories, menus, and modifier groups. It is recommended to send the catalog before sales.
  2. Sales: orders with their payments and items. Orders are stored by their external ID, so if the same order is sent twice, it is updated instead of duplicated. It is recommended to send them in batches.


The full API documentation, with examples and all available fields, is here:


👉 https://pos-api.haddock.app/docs



Multi-location management


If your POS manages several locations, there are two ways to send data to haddock:


Option 1: Separate credentials


Each location has its own property in haddock with its own API credentials. The POS sends data for each location separately to its corresponding credentials.


This is the simplest option and does not require additional configuration.


Option 2: Routing by venueID


A single authenticated connection can distribute orders to multiple locations. Each order includes a venueID field that indicates which location it belongs to, and haddock automatically routes it to the corresponding property.


This option is useful when the POS manages multiple locations from a single system. Contact us to configure it.



Need help?


If you have questions about how to set up the integration, message us through the support chat and we will help you.


Your POS provider or distributor may charge for their integration services or for additional modules required. These costs are not covered by haddock.

Updated on: 23/04/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!