Integration modes
Choose the mode that matches your installation. Confirm the connector and its requirements with the provider before changing the setup.
Configure BitFARMA through Access
Select this mode only if the provider confirms Access file access. Sales and Auxiliary take files, rather than an exchange folder or SQL server.
The connector uses 32-bit Microsoft Jet OLE DB 4.0. The provider must prepare the files and compatible component for the actual Windows user running ImaCash. Do not convert files or change their password to test the connection.
Configuration steps
- Open Configuration > Integration > POS and select Bitfarma.
- In Sales select the sales file confirmed by BitFARMA. Earlier documentation mentions diario.mdb; verify the actual installation file rather than relying only on its name.
- In Auxiliary select the auxiliary file confirmed by the provider. The historical reference is genera32.mdb; both files must belong to the same installation and be accessible to the actual user.
- In Password enter the private file password supplied by the administrator. This is not the password used to sign in to BitFARMA; do not use example values.
- When closing the configuration with changes, choose to save and review the result. If a restart is offered, confirm it explicitly when appropriate. Saving without changes does not guarantee a fresh reading of options.
- Before live use, validate references, amounts including cents, signs, dates, workstations and operators with the provider, as well as cash actually accepted or returned. Opening a connection does not replace these checks.
Scope and checks
It reads net sales presented as cash, including the rounding and customer adjustments received from the source. It provides no card or mixed-payment breakdown. Check the resulting amount; the synchronisation date applies by day and does not prove complete historical retrieval.
The source supplies workstations and sales staff. Review ImaCash capture filters with representative data; do not assume store separation or use Workstations as a payment method.
Confirming or cancelling in ImaCash does not write a confirmation or cancellation to BitFARMA. It is not a bank payment or a fiscal close. If the outcome is uncertain, review the source and actual cash with support before repeating or restarting.
These modes do not import products or shifts. This guide does not certify physical validation or compatibility with every version or machine; the provider must confirm the installation and its operations.
View the BitFARMA SQL Server mode
Historical visual reference in Spanish: the screenshot keeps the fields empty and shows Pharmacy and the former Save button. In the current interface, use POS and the save-on-close procedure described above.
Configure BitFARMA through SQL Server
Select this mode for the SQL Server installation confirmed by the provider. Use a private account with query permissions; it does not need Access files or an account for writing confirmations.
The administrator supplies the SQL destination, main catalogue and authorised account. This profile offers no separate port or instance fields or Windows authentication; do not add fields or use an administrator account for convenience.
Configuration steps
- Open Configuration > Integration > POS and select BitfarmaSQL.
- Complete Server IP, Database name, User and Password with the confirmed private details. Database name is the main catalogue, rather than the username.
- Service name takes the optional history catalogue in the same SQL environment. It is not a Windows service or instance. Leave it empty unless the provider confirms that catalogue and its query permissions; do not invent a name.
- In payment methods select the actual, distinct cash and card codes. Review Accept cards where applicable. Workstations is not the payment method identifier and does not replace these selectors; saving without changes may retain the previous list.
- When closing the configuration with changes, choose to save and review the result. If a restart is offered, confirm it explicitly when appropriate. Saving without changes does not guarantee a fresh reading of options.
- Before live use, validate references, amounts including cents, signs, dates, workstations and operators with the provider, as well as cash actually accepted or returned. Opening a connection does not replace these checks.
Scope and checks
It reads sales, amounts received and grouped operations according to source data; it adds history when its catalogue is configured. Cash/card classification depends on the selected methods: it does not guarantee a universal breakdown of mixed payments, change or a reconciled bank total.
Workstations and sales staff come from the source, but filters do not cover sales, amounts received, groups and history uniformly. Validate each scope with support; do not rely on them for global exclusion or store separation.
Confirming or cancelling in ImaCash does not write a confirmation or cancellation to BitFARMA. It is not a bank payment or a fiscal close. If the outcome is uncertain, review the source and actual cash with support before repeating or restarting.
These modes do not import products or shifts. This guide does not certify physical validation or compatibility with every version or machine; the provider must confirm the installation and its operations.
View the BitFARMA Access file mode
Historical visual reference in Spanish: the screenshot keeps the fields empty and shows Pharmacy and the former Save button. In the current interface, use POS and the save-on-close procedure described above.
