MediStock
Pharmacy POS and inventory management for Android and Windows 11, with shared LAN checkout and offline-capable desktop operations.
About MediStock
MediStock is a pharmacy point-of-sale and inventory management system for store owners, managers and cashiers. It helps organize medicine and product catalogs, barcode/SKU lookup, supplier purchases, batches and expiry dates, sales, returns, customer and supplier balances, cash movements, reports and receipt printing. On Windows 11, one computer can run Branch Server + POS and host the shared local branch database for paired POS Client computers on the same shop network. After the branch is configured and initialized, local checkout is designed to continue through internet interruptions; cloud synchronization resumes when internet and the configured MediStock backend are available. First-time branch setup and cloud synchronization require a working connection to the configured backend.
Designed with everyday use in mind
We focus on clear interfaces, practical features and a straightforward experience. Check the app's official listing for the latest availability and requirements.
Organize medicine and product records, SKU/barcode identifiers, current quantities and stock locations.
Track received stock batches and expiry dates, with expiry visibility and stock rotation support.
Record supplier purchases and invoices, supplier balances and related inventory movements.
Record sales and payment methods, create receipts and review sales history.
Manage supported customer returns, purchase returns, damaged/expired write-offs and stock adjustments.
Choose Branch Server + POS for the main branch computer or POS Client for an additional checkout computer on the same shop network.
After initial branch setup, the desktop branch server and paired LAN POS clients are designed to keep local checkout working during internet interruptions. Cloud sync requires a configured backend and internet access.
Owner, manager and cashier workflows provide role-based access to supported business operations.
Install MediStock and configure offline checkout
MediStock Desktop uses one Branch Server + POS computer as the local authority for that branch and lets additional POS Client computers share the same branch database over your shop network. This avoids each checkout computer independently changing its own stock copy.
1. Set up the main branch computer
- Download the Windows installer from this page and install MediStock on the computer that will be the main branch server.
- Open MediStock and select Branch Server + POS.
- While internet access is available, enter the URL of your configured MediStock cloud/backend and sign in with an approved owner or manager account.
- Complete the initial registration and branch setup. The application registers the computer and obtains the selected branch's starting data from the configured backend.
- Keep this computer running when other POS Client computers need to use the local branch database. You can also use the branch-server computer as a normal checkout terminal.
2. Add another checkout computer on the shop LAN
- Connect the main branch computer and the additional Windows computers to the same trusted local shop network. Avoid guest Wi-Fi or network settings that isolate devices from one another.
- Install the same MediStock Windows version on each additional computer and select POS Client.
- On the Branch Server computer, open Sync & Devices and generate a six-digit pairing code.
- On the POS Client, discover the Branch Server and enter the pairing code. After pairing, the client receives its own device token and uses the shared branch database through the authenticated local-network gateway.
- Do not set up every checkout computer as a separate Branch Server for the same branch. Use one Branch Server and pair the other POS computers to it.
3. What happens when the internet stops working?
- After the branch has been initialized, the Branch Server keeps the local branch database and is designed to continue local checkout when cloud internet access is interrupted.
- Paired POS Client computers can continue using that shared local branch database while the Branch Server and shop LAN remain running.
- Cloud synchronization cannot complete while the internet/backend is unreachable. Pending cloud-bound operations are retained for synchronization by the Branch Server when a compatible connection returns.
- Offline local checkout is not the same as internet access: cloud-dependent functions and remote/mobile access may be unavailable during an outage.
4. Network and firewall checklist
- The Branch Server must be running and all POS Client computers must be able to communicate across the same shop LAN.
- If Windows Firewall asks, allow MediStock for your trusted Private network only, according to your store's IT/security policy.
- The desktop architecture uses TCP port 32191 for its authenticated LAN gateway. Allow local-network access only when needed for paired POS Client computers.
- Port 32190 is the Branch Server's internal localhost-only API. Do not expose it to the LAN or the public internet.
- The configured MediStock backend and internet connection are required for initial online setup and later cloud synchronization.
Quick troubleshooting
A POS Client cannot find the Branch Server
Check that both computers are on the same shop LAN, the Branch Server application is running, and the network does not isolate clients. Check Windows' Private/Public network profile and any firewall prompt. Do not solve discovery issues by exposing the internal port 32190 to the network.
Local checkout works, but cloud data is not updating
Check the branch computer's internet connection and configured MediStock backend URL, then review the application's sync/device status. Cloud updates are expected to resume only after the backend can be reached. If the connection stays unavailable, contact support with the app version and a description of the sync status—never send passwords or pairing tokens.
What should I test before using it in a live pharmacy?
Test the actual shop network with at least two computers, make a test sale while internet is available, temporarily disconnect the internet and confirm local checkout, then reconnect and verify that the sale synchronizes exactly once. Also test receipt printers, backup and restore, simultaneous checkout and your normal branch reconciliation process. Start with test data and keep a separate verified backup.
Important: Offline checkout depends on successful initial setup, a functioning Branch Server, the local network and compatible backend configuration. These are setup instructions, not a substitute for testing the installer and synchronization in your own shop before production use. This installer is unsigned, so Windows may show an unknown-publisher/security warning.