Start hereCMS 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
- Download the official CMS Pharmacy Billing Pro Setup 5.13.33.exe from the Download page or the secure link provided by CMS Pharma.
- 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.
- Follow the installer prompts and complete installation. Launch CMS Pharmacy Billing Pro from the desktop shortcut or Start menu.
- On first launch, create or sign in to your local application account as shown on the login screen.
- 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.
- Use Verify Subscription while connected to the internet. Confirm that the displayed plan and expiry date are correct.
- Set up firm details, users, print preferences and medicine master data before live billing.
Part B — Backup and first-day checks
- Open Backup & Restore and create an initial backup before importing or entering business data.
- Import products/stock only after reviewing the source file and matching fields.
- Test one sample purchase and one sample sale; verify batch, expiry, GST, discount, stock deduction and print output.
- Check daily closing and reports against the test transactions.
- 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
- Install and activate CMS Pharma Stock Connector on the pharmacy's own WordPress website (not on the central product sales website).
- In WordPress Admin, open CMS Pharma Sync. Copy the HTTPS Stock API URL and generated Site Sync Token. Keep the token private.
- In Billing Pro, open Website Sync. Enter the API URL and token, enable sync, then use Test / Sync Now.
- Create or edit the Weekly Medicine Stock page and add shortcode
[cmspharma_weekly_stock]. - 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.
- 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)
- Install and activate CMS Pharma Subscriptions v1.1.2 on the central CMS Pharma WordPress website.
- Configure the supported payment gateway credentials in the plugin settings. Never put secret keys in page content or share them in screenshots.
- Use the plugin shortcodes
[cmspharma_subscription] and [cmspharma_account] on the subscription/account pages. - Run a sandbox/test payment first, verify webhook delivery and order status, then switch to live only after end-to-end testing.
- 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.