Set up Ágora Retail in ImaCash
This guide covers POS > AgoraRetail and its SQL Server reader. Ágora POS and Ágora API are different modes. Earlier names AgoraRetail V2 and V3 refer to the same connector; they do not establish commercial versions or additional compatibility.
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 > AgoraRetail. Confirm the prepared mode with the supplier before changing an existing installation.
- 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.
Save the connection and choose the installation’s actual payment methods when the lists appear. Preserve the working configuration and check what was saved before use. If no methods appear, do not assume the connection has validated payments. Complete a normal new ImaCash start with no operations in progress to apply and verify the saved methods.
Cash, cards and cash movements
Select the cash method by its actual name. For cards, choose a different method and enable Accept cards in Settings. With that option off, only the cash method is queried; enabling it adds the selected card method. Do not use example identifiers or assume an empty list or cancelled selection leaves the classification correct. Credit, vouchers and other methods are not automatically included.
Each payment is read as paid amount minus change, retaining its sign. A mixed document may produce separate movements for the selected components; its total is not repeated for each method. A negative amount does not prove an executed refund or bank authorisation. This mode does not include a separate cash/supplier movement reader.
Tills, operators and filters
Check tills and operators against known documents before applying filters. The till list may provide identifiers while movements show names; verify their correspondence. In some schemas the till is the ticket’s opening till rather than the payment location. The operator is the document’s opening operator. Local ImaCash filters may exclude payments already read by SQL; a generic shop reference does not identify a physical shop.
Check the results
Compare existing cash, card and mixed payments, change, negative amounts, dates and document links. Review payments without an associated document, duplicates, omissions and filters with the supplier. Do not make real payments or refunds to test setup. A successful SQL connection does not prove complete reading or document closure. Payments without an associated document may lack a till or operator; do not fill in those details by assumption.
The link reads payments; it neither imports products nor writes confirmations, refusals or cancellations to Ágora. Method lists, a connection and supported schema variants do not establish compatibility with every version or physical validation. Confirm the installation’s scope before automatic use.