
Warehouse
One warehouse. Every branch in sync.
e-Inventory is the hub of a pharmacy group. It owns the product, vendor and price master, buys for everyone, and moves stock to and from each EzPOS branch electronically, with nobody re-keying a line. For a standalone drug store it runs purchasing, sales and inventory end to end.
45
capabilities in the release
1 day
per site to onboard*
0
lines re-keyed between warehouse and branch
* Hardware and network ready on the day. Authority connections and data migration are scoped separately.
Approved and connected
The lists and gateways this product is live on.
LOGO
Tatmeen
LOGO
RSD
LOGO
DoH drug list
LOGO
MOHAP drug list
LOGO
UPP fields
LOGO
Daman formulary
What it does
From procurement to every shelf.
e-Inventory sits at the centre of the group: it buys from vendors, holds the master data, and moves stock to and from every branch. Requests and transfers travel electronically and land in EzPOS without anyone typing them again.
Central master data
One source of truth for products, vendors, pricing, discount policy, promotions and cashback vouchers, published to every EzPOS branch automatically.
Procurement and purchasing
LPO and direct purchasing, free-of-cost receiving, purchase returns for expiring stock, and barcode printing at goods-in.
Replenishment that reads history
Reorder quantities calculated from past sales, plus threshold-based suggestions when a product falls below its level.
Inter-branch stock flows
Branch stock requests, warehouse requests to branches, transfers, internal and external returns, and indirect purchase orders a branch raises for warehouse approval.
Sales and salesman operations
Assign pharmacy customers to salesmen, capture orders for internal and external pharmacies on the road, and steer selling with target items and staff incentives.
Reporting across the group
Purchases, sales, stock, expiry, transfers, promotions, cashback vouchers and incentives for the warehouse and every branch, in one place.
A day on the floor
How the week actually goes.
STEP 01
The branch asks
A pharmacy drops below its threshold and raises an electronic stock request. It lands in the warehouse queue, not in somebody's messages.
STEP 02
The warehouse buys
Sales history and threshold levels generate the LPO. Goods-in records batch, expiry and free-of-cost lines, and prints the barcode that the branch will scan at the till.
STEP 03
Stock moves
The approved request becomes a transfer, and it is received in EzPOS at the branch automatically. No line is typed twice and nothing is counted twice.
STEP 04
Returns and money follow
Near-expiry stock goes back to the supplier, or to a branch that will sell it. Purchase orders and returns arrive in AMS as bills and debit notes, ready for approval.
Inside the product
Modules, in the order you'd meet them.
Three screens run the group. Each one removes a spreadsheet.
Master data and pricing
Where the group's rules are set: products, vendors, departments and categories, discount policy, privilege-card discounts, promotions and staff incentives. Change a price or a promotion once and every branch dispenses on the new one.
Product & vendor master Promotions & CBV
Procurement and replenishment
Where buying gets cheaper: LPO and direct purchase, free-of-cost tracking, sales-driven and threshold replenishment, and purchase returns. Reorder quantities come from what actually sold, not from memory.
LPO & direct Replenishment
Transfers and returns
Where the group stops losing stock: branch requests, warehouse requests, transfers out and in, internal and external returns. Every movement is received electronically at the other end.
Zero re-keying EzPOS sync
Proof
One customer, one number, one quote.
[Customer quote to come — two sentences from a named operator at a named site.]
[Name Surname]
[Role · Organisation]
[00%]
Outcome measured
[00m]
Outcome measured
Deployment
One day per site. The warehouse goes in on day one — installed, configured, master data loaded — and each branch is a day of its own after that, so a group comes on in as many days as it has sites rather than in a quarter. Pricing and promotion policy are set once at the warehouse. Authority connections and migration of purchase and stock history run alongside, not in the critical path.
Works with
Pairs with the rest of the suite.
Each of these does its own job. Most customers add the next one once the first has paid for itself.
EzPOS
Every branch's till runs on the master data e-Inventory publishes, and receives its transfers automatically.
AMS
Purchase orders become bills, returns become debit notes, and the group's ledgers, VAT files and year-end come out of the same data.
CCMS
The claims side of the same group: e-Inventory keeps the shelves right, CCMS keeps the insurer payments right.
EzRx
Payer approvals and remittances for the branches e-Inventory supplies.
Questions
The four things buyers ask first.
Standalone or group, what the branches need, how prices travel, and recall traceability.
We're a standalone drug store, not a group. Is this over-specified?
No. For a standalone store e-Inventory runs purchasing, sales, returns and stock on its own, without the branch-transfer side switched on. The group features are there when you open the second site.
Do our branches need e-Inventory too, or just EzPOS?
Just EzPOS. e-Inventory is the warehouse system; branches run EzPOS and receive master data, prices, promotions and transfers from it.
How do a price change and a promotion actually reach the till?
You set them once in e-Inventory. EzPOS at every branch syncs and applies them — including discount policy, privilege-card rates and incentives — so no branch is dispensing on last month's price list.
If a batch is recalled, can we trace where it went?
Yes. Goods-in records batch and expiry, transfers record which branch received them, and EzPOS records the sale against the scanned batch — so the trail runs from supplier to the till that sold it.
See it on your own workflow.
Tell us which authority licenses you and what you run today. We'll configure the walkthrough for your market — thirty minutes, no slide deck.
A specialist replies within one working day
Onboarded in one day once you are ready
We review your data migration before you commit
