Start here

CMS Pharmacy Billing Pro Installation Guide

Follow these steps to install the Windows application and connect your optional CMS Pharma website services.

Part A — Install the Windows application

  1. Download the official CMS Pharmacy Billing Pro Setup 5.13.33.exe from the Download page or the secure link provided by CMS Pharma.
  2. On Windows, open the downloaded setup file. If Windows displays a security prompt, verify that the installer came from the official CMS Pharma source before continuing.
  3. Follow the installer prompts and complete installation. Launch CMS Pharmacy Billing Pro from the desktop shortcut or Start menu.
  4. On first launch, create or sign in to your local application account as shown on the login screen.
  5. Open Subscription. Start the eligible trial or connect an existing CMS Pharma account using the website URL and account license key provided for that account.
  6. Use Verify Subscription while connected to the internet. Confirm that the displayed plan and expiry date are correct.
  7. Set up firm details, users, print preferences and medicine master data before live billing.

Part B — Backup and first-day checks

  1. Open Backup & Restore and create an initial backup before importing or entering business data.
  2. Import products/stock only after reviewing the source file and matching fields.
  3. Test one sample purchase and one sample sale; verify batch, expiry, GST, discount, stock deduction and print output.
  4. Check daily closing and reports against the test transactions.
  5. Keep the backup on a separate secure drive or approved cloud location. Do not rely on the same PC alone.

Part C — Optional WordPress stock website connection

  1. Install and activate CMS Pharma Stock Connector on the pharmacy's own WordPress website (not on the central product sales website).
  2. In WordPress Admin, open CMS Pharma Sync. Copy the HTTPS Stock API URL and generated Site Sync Token. Keep the token private.
  3. In Billing Pro, open Website Sync. Enter the API URL and token, enable sync, then use Test / Sync Now.
  4. Create or edit the Weekly Medicine Stock page and add shortcode [cmspharma_weekly_stock].
  5. If WooCommerce is installed, only pre-existing products individually enabled for stock updates and in allowed categories are updated. The connector does not create products.
  6. Check the public stock page after sync. Public prices are off by default; do not publish confidential or patient-identifiable data.

Part D — Subscription website setup (administrator)

  1. Install and activate CMS Pharma Subscriptions v1.1.2 on the central CMS Pharma WordPress website.
  2. Configure the supported payment gateway credentials in the plugin settings. Never put secret keys in page content or share them in screenshots.
  3. Use the plugin shortcodes [cmspharma_subscription] and [cmspharma_account] on the subscription/account pages.
  4. Run a sandbox/test payment first, verify webhook delivery and order status, then switch to live only after end-to-end testing.
  5. Test renewal, failed payment, expiry, duplicate webhook and desktop license verification before accepting customer payments.

Troubleshooting

  • Subscription not active: confirm the correct website URL, account/license key, internet connection, payment status and expiry; then use Verify Subscription.
  • License disappears after restart: update to the latest approved app build, verify online, restart once and confirm the plan remains active. Do not delete local application data.
  • Website sync fails: verify HTTPS API URL, current token, REST API access and connector plugin status. Regenerating the token invalidates the old token.
  • Stock page empty: confirm a successful sync, published page and shortcode spelling. Clear WordPress/Hostinger cache.
  • Old desktop icon remains: remove the old shortcut and create a new shortcut after installing the updated build; Windows may cache shortcut icons.
Important: Back up your existing pharmacy database before upgrading or reinstalling. Never uninstall or clear application data until a verified backup is available. The exact installer requirements and supported Windows versions should be confirmed against the release notes supplied with your build.