ImaCash integration

Pharmagest

Prepare Pharmagest in ImaCash using its exchange folder: POS selection, file permissions, requests and responses, and saving the configuration.

ImaCash icon used for the Pharmagest profile
Pharmacy

Configure the Pharmagest exchange folder

This profile exchanges amount requests through files. Confirm the Pharmagest edition and exchange method prepared for your installation with the provider; the profile name does not establish support for all its products or versions.

The installer must confirm a dedicated folder accessible to both programs. The Windows account running ImaCash needs permission to read, write and delete files there. Do not choose a documents or backup folder or publish its private path.

  1. From Main, open Configuration, identify yourself if requested and enter Integration. Choose POS > Pharmagest. You need access to Configuration; the installation may lock some controls.
  2. In Transactions, use the button beside the field to select the confirmed folder. This is a folder, not an individual file. This profile does not request an SQL server, port, database username or password.
  3. Close with X. If changes are pending, Save checks and saves in phases; Continue editing returns to the form and Exit without saving discards pending changes. Read each result: exiting does not undo phases already saved. Continue startup or restart only when the application offers it and the workstation is ready.
Native demonstration of Configuration > Integration > POS > Pharmagest with Transactions empty, without selecting a folder or saving.
Isolated demonstration of the real, localized form. The private field is empty; the example does not open the selector, start the connector, read or delete requests, or save configuration.

What happens to requests

During operation, ImaCash reads V*.txt and P*.txt requests from that folder and removes the files after reading them. This reading is not filtered by the resynchronization date. A received row does not establish payment; do not copy historical requests or restore consumed files for testing.

Responses and checking the result

When the workflow reports the result, the connector attempts to write an .OK response or, if it receives that result marked as canceled, .KO. Rejecting a request does not itself generate that response. Also check that Pharmagest has processed it; the file alone does not establish the physical cash result.

The connection indicator does not check whether the folder exists, is accessible or uses the correct format. During commissioning, the installer must compare the request, response and result in both programs. For an uncertain operation, check the POS and machine before repeating, restarting or reintroducing files.

This profile handles cash amount requests. It does not provide an item catalog, stock, shifts or a bank total here, or establish card or mixed payments. Define the operating scope through the prepared folder; do not assume automatic separation by user or checkout. Saved configuration does not physically validate the installation.

Configuration: choose the profile and review exit options

Official Pharmagest website

Integration ready to move forward

If this integration matches your software, the next step is moving into real operation

We can help you validate the scope, confirm compatible hardware and prepare the next implementation step.