Set up Ágora POS in ImaCash
This guide covers the AgoraPOS selector in ImaCash and its SQL Server reader. Ágora API and Ágora Retail are different modes: confirm with the provider which one is prepared for your installation before selecting or changing the link.
Before you start
The provider must confirm the compatible version and structure, the active server and database, and an authorised account with the required read permissions. Check access under the identity that runs ImaCash and preserve a working configuration. Do not copy manual examples or assume every Ágora installation is compatible.
Setup steps
- Open Configuration > Integration and select POS > AgoraPOS. Do not select API or Retail because the names look similar.
- Review these fields with your technician and use only private details supplied by the administrator:
- Server IP and Port identify the SQL Server destination for your installation. The port is used when the destination has no instance or port already included; this guide does not specify a universal port.
- Database Name is the exact name of the compatible sales database, not a file or a list of tills.
- Instance Name identifies the SQL Server instance when applicable. The instance takes priority over the Port field; do not add it twice or combine details from another installation.
- Fill in User and Password with the authorised private SQL account and enter the password only in ImaCash. This mode does not display a Windows authentication checkbox. If an earlier configuration already uses it, preserve its valid Windows identity and request technical review; do not edit files to enable it.
Use Save and check the connection. Change an existing configuration with support and no operations in progress. Saving or opening SQL does not prove that all the correct payments and movements are being read.
Cash, cards and cash movements
This mode uses the cash and card methods expected by the link; it has no payment-method selectors of its own. The provider must confirm the mapping. With Accept cards off, the reader includes cash payments on documents; enabling it also includes the expected card payments. It does not automatically include custom methods, credit or vouchers and does not authorise a bank payment.
Each payment is read as the paid amount minus change. Separate payments on a mixed-payment document can produce separate movements for their components; the full document total is not repeated for each method. Cash/supplier movements are read as cash and retain the POS sign, even with cards enabled: they are not all outflows. Validate their scope and meaning before using them for automatic cash movements.
Tills, operators and filters
Review the actual names and identifiers provided by your installation. Set the filters in ImaCash and check them against known documents. The operator filter can also exclude cash/supplier movements; do not assume both readers use the same origin or selection. A list of centres does not by itself establish equivalence with tills, and this link’s shop reference does not identify a real physical shop.
Check the results
With the provider, compare existing cash, card and mixed payments, paid amounts minus change, negative documents and cash/supplier movements. Review dates, tills, operators, missing records and duplicates. Negative amounts retain their sign but do not prove a refund was made. Delivery notes identified as reopened are omitted from this reading; that does not confirm cancellation or removal of an earlier pending item. Do not run real payments or refunds to test setup.
The link reads data; it does not import items or write confirmations, rejections or cancellations to Ágora. A successful connection does not prove complete reading, document closure, bank payment, reconciliation or physical validation. Confirm the scope of both readers and each installation with the provider.