Set up Glop with ImaCash
The Glop profile reads the Firebird database prepared by the provider. This guide covers connection and transaction reading; the Glop edition, database structure and cash device require confirmation for each installation.
1. Prepare access with the provider
Ask for the edition and active database, compatible Firebird and driver versions, server, port and a private account with read permissions. The Firebird service must be able to open that database. Do not treat values suggested by the form as confirmed settings.
2. Select the integration
Open Settings > Integration and choose POS > Glop. Hospitality and the Save button belong to the historical screen: the current workflow checks the configuration when you close it.
3. Complete the five fields
Server IP receives the confirmed Firebird destination; Server port receives its numeric port. User and Password are private details supplied by the administrator. Sales identifies the active database file as seen by the Firebird server; it is neither an exchange folder nor the security database. No DSN or additional SQL database is configured in a separate field.
4. Close and choose payment methods
Closing attempts to open and close Firebird and read the available payment methods. If Cash type and Card type appear, select the actual, distinct methods used by this installation without guessing identifiers. An empty list, cancelled dialog or successful connection does not prove a valid selection or complete reading.
5. Check tickets and cash movements
Reading starts at the specified date and time, inclusive. Tickets can separate up to three portions according to the selected methods; some cash reconciliation states use the full amount as cash. Cash movements are also read as cash. Check amount, sign, time and reference, and avoid counting the same event twice. Complete history and duplicate-free reading are not guaranteed.
6. Limit terminals and employees
Check terminal identifiers and employee names and identifiers against local filters. A populated list does not prove correct conversion or filtering for tickets and cash movements. There is no separate company selector: validate scope and terminal isolation before use.
7. Distinguish records from confirmation
Accept cards does not authorize or settle a bank payment. Check cash, card and mixed payments separately. Confirming or rejecting in ImaCash does not write a closure or cancellation in Glop. This profile does not establish support for products, stock, shifts or an independent bank total.
8. Review an encryption mismatch
For an encryption or WireCrypt error, the provider must check versions and the client and server authentication and encryption policies. Do not change firebird.conf or restart the service as a general remedy, or weaken protection to bypass the error. Authentication rejection and network failure need different checks.
9. Validate before use
With the provider, check reading, methods, filters and results in both applications and against actual cash. If the result is uncertain, review the transaction before repeating, resynchronizing or restarting. This guide and a successful connection do not establish a supervised physical test.
The logo identifies Glop. It does not establish compatibility of every edition, module or cash device with this profile.