Every part of this POS system was built for one kind of shop — a Pakistani agri-input dealer selling pesticide, khaad and seed on cash and udhaar. Nothing here is a general retail feature with an agriculture label on it.
Bring what you already have. AgroPOS reads an .xlsx file for products, for customers and for suppliers, so a shop with its catalogue in Excel — or a list an accountant keeps — does not type it in twice. Download the template, paste your rows in, and open it.
Nothing is saved until you have seen what it will do. AgroPOS reads the file first and shows you the list: how many rows are new, which ones you already have, and which cannot be used and why, naming the row so you can find it in Excel. For every record that already exists you decide, row by row, whether to leave it alone or update it — there is no hidden setting that silently overwrites your shop.
Updating changes the details, never the money. An import will not move a customer’s udhaar balance, a supplier’s payable, or a product’s stock: those belong to your bills and purchases. Opening stock on a new product becomes real, sellable stock with its own batch and expiry, and a customer’s old balance goes in once as a single opening figure.
Column order does not matter and spare columns are ignored, so a stock report exported out of AgroPOS can be edited in Excel and fed straight back in.
A sale is three actions: find the product, set the quantity, confirm. The receipt prints on its own if you want it to. Everything runs on your own PC against a local database, so no screen waits on a connection — on a mandi morning with five farmers at the counter, that is the whole difference.
Finding the product is the part most software gets slow. AgroPOS searches on brand name, company, barcode or the technical name of the chemical at the same time, so typing chlorpyrifos lists every brand of it you stock. The farmer names the chemical; the shelf carries brand names; you should not have to translate between them.
Getting started is quick too. Installing takes a couple of minutes on any Windows 10 or 11 PC and most shops bill on the same day. The part that takes real time is entering your product list and opening balances, and that is included — we do it with you, in Urdu, rather than handing you an empty screen.
Search a product by name, Urdu name or barcode, set the quantity and take payment as cash, credit or partial. Discounts can be entered in rupees or as a percentage, and a percentage is converted before it is saved — so every receipt and report shows a settled cash figure.
Stock is held per batch, not per product. Each batch keeps its own batch number, expiry date, pack size, purchase rate and supplier. Sales take from the earliest-expiring batch first, so older goods move before they become a write-off.
Type an opening quantity when you create a product and the figure is recorded — but the till sells from batches, and an opening quantity creates none. So the product reads “25 in stock” and every attempt to bill it answers “out of stock”.
Pending Stock lists exactly those products and walks you through the ordinary purchase that makes them sellable — your supplier, your rate, your choice of cash or udhaar. Nothing is guessed on your behalf, because only you know who you bought from.
The dashboard shows what is expiring within a window you choose, and what has fallen below its reorder level. Expired batches are blocked at the till — a cashier cannot sell them by mistake.
A customer says "add two bags of urea, I'll be back" and walks off to the godown. Hold the bill, serve the next customer, and bring it back with one click — as many held bills at a time as the counter needs, each named so you can find it ("Kashif", "red pickup", "gate par").
A held bill is not a sale. No invoice number is issued and no stock is reserved, so a cart forgotten overnight costs nothing and leaves no gap in your invoice numbering. When you resume it, every line is re-priced against live stock: anything that sold out in the meantime is removed and anything short is reduced to what is actually on the shelf, and the till tells you which lines changed rather than letting you find out in front of the customer.
A customer who is not on your list can be billed without being added first — but on cash only. Credit always needs a named customer, because udhaar owed by nobody is udhaar you will not collect. The receipt prints without a customer block.
Every sale is searchable by invoice number, customer or date. Filter by a single day, not just a range, with Today and Yesterday shortcuts. A sale can also be entered with an earlier date, so a shop starting mid-season can put its existing sales in on the days they actually happened.
80 mm thermal receipts and full A4 invoices, both printed through the normal Windows printer system. Save as PDF or send straight to WhatsApp. On a credit sale the receipt prints the customer's previous balance, this bill's udhaar and the new total.
Set your thermal printer once and every sale prints itself the moment it is confirmed — no dialog to click through at a busy counter.
Every customer carries a running balance and an optional credit limit. The till warns before a sale would push someone past their limit. Customers are stored with father's name and village, because that is how a rural counter actually identifies people.
A single list of everyone who owes you, with their full history. Recording a payment settles it against the oldest unpaid invoices first, so the ledger stays honest rather than becoming a pile of part-paid bills.
A customer owes Rs 51,000 and says he will give 50,000 to close the account. Zeroing the balance by hand would lose the 1,000 entirely: the sale already counted it as earnings, so your books would report money you never received.
Take the payment and tick Settle the account. The khata closes at zero and the forgiven amount is recorded as a write-off expense with that customer’s name on it, so it comes out of profit and you can see at season’s end exactly how much was forgiven and to whom. Admin only — a cashier taking payments all day cannot forgive a balance.
Purchases are entered against batches, and the Supplier Ledger shows total business done with each supplier, what you have paid and what is still payable — with a printable statement. Purchases paid on delivery appear there too, so the account is complete.
Plenty of agri-input dealers sell to farmers and to smaller shops in the villages around them. Those are two different rate cards, and running both out of one price list means either the shop gets the retail rate or the farmer gets the trade rate. AgroPOS keeps them apart.
Mark a customer as a Shop and give the business its own name — that name is what prints on the bill, not the person who came to collect. Set one wholesale rate on each product, and the shop pays it whether they hand over cash or take udhaar, because a trade price is about who is buying, not how they settle.
At the till, Wholesale is a fourth tab beside Cash, Credit and Partial. It lists only your shop customers; the other three list only farmers. Neither can be billed off the wrong rate card by picking from the wrong list. Enter what the shop actually paid and the rest goes to their khata, exactly like a partial sale.
There is more on how the two rate cards stay apart, and what happens when a party buys and sells, on the wholesale and distribution page. A product with no wholesale rate set falls back to your normal price rather than billing nothing. And the whole thing is off until you switch it on — a shop that only sells to farmers never sees a customer type, a second rate box or a fourth tab.
Some parties go both ways. You sell surplus stock back to a distributor; you buy a pallet off the shop down the road when you run short. Kept as a customer account and a supplier account, that is two balances for one person and a reconciliation you do in your head every time they walk in.
Link them and AgroPOS keeps one netted khata. Sell them Rs. 50,000 and buy Rs. 200,000 from them, and the account reads what it should: Rs. 150,000 you owe — one figure, counted once. It shows in your payables and not at all in recovery, so the dashboard does not double it.
Their statement shows both sides: what you sold, what you bought from them, and the net. Sale returns, purchase returns, payments and recovery all land on the same account, each in the right direction. Also off by default.
Returns adjust stock and the ledger together, so a refund never leaves the two disagreeing.
Seven registers print for any date range: stock, batch-wise stock, expiry, sales, purchase, company-wise stock and daily sales. Each carries your shop letterhead and dealer licence number. Purchase prices and stock valuation are deliberately left off — the inspector needs the record, not your margins.
Read what each register must show →
Track a single product's full history — what came in, from which supplier and batch, and where it went.
Each product carries its registration number, technical (active ingredient) name and formulation code — EC, WP, SC, SG, OD and the rest of the CropLife list. An Urdu product name can be stored alongside the English one.
The figures an owner opens the software to see, on one screen: today's cash and credit sales with the invoice count, stock value on hand, pending recovery, supplier payable, and a twelve-month sales chart for the year. Beside them sit the two lists that cost money when nobody looks — batches expiring within the window you choose, and products that have fallen below their reorder level.
One tap for Today, This Month, Last Month or This Year, or pick any range. Sales, less returns, less what the goods actually cost, less shop expenses by category, and the net profit with its margin as a percentage of sales.
The cost used is the rate each batch was bought at, so a figure from last season does not change when a new delivery arrives dearer. Profit by product ranks lines by what they earn rather than by turnover — usually a different order than dealers expect. And if any sold item has no purchase rate recorded, the statement says so and warns that the real profit is lower, rather than quietly counting that whole sale as profit.
A working profit and loss for any period you choose — a week, a month, a whole season. Sales, less returns, less what the goods actually cost you, less your shop expenses broken down by category, and the net profit at the bottom with its margin as a percentage of sales.
The cost used is the rate each batch was bought at, not today's rate for that product, so last season's profit stays what it was when a new delivery arrives at a different price. If any sold item has no purchase rate recorded, the statement says so and warns that the real profit is lower — rather than quietly counting that whole sale as profit. A loss is shown as a loss.
Which lines actually earn, ranked by profit rather than turnover. The product that sells most often is frequently not the one that earns most, because the fast lines are the ones every shop stocks and the rate is squeezed.
Add as many bank accounts as the shop uses — bank name, account title, account number and the balance it holds today. Record money in and money out, with every entry showing the balance the account stood at after it, so the list reads like a bank statement. Entries can be dated back, and the balances above and below correct themselves. Any account prints a PDF statement for a period or for its whole history. Kept separate from sales and purchases: nothing else in AgroPOS writes here, so these figures stay yours to match against the bank.
Day-to-day spending recorded by category and date, and included in the profit and loss statement. A shop coming onto AgroPOS mid-season can enter everything it spent beforehand as one dated opening total, rather than typing months of entries one at a time.
Sales, purchases, stock, expenses and recovery, each over a date range you choose, exportable to Excel when you want to work on the numbers yourself.
Your shop name, address, phone, NTN and dealer licence appear on printed documents. You can upload your own logo, and the invoice footer is yours to write — the paperwork should read as the shop's, not ours.
Staff can be trusted and still make mistakes. A rate that looks wrong three months later, a credit limit nobody remembers raising, a tax percent that changed at some point — these used to leave no trace at all, because an edit simply overwrote what was there.
Change History records edits to the things that move money: product rates, credit limits, tax percent, invoice numbering, and user roles and accounts. Each entry shows what the value was, what it became, who changed it and when. Passwords are never recorded — only that one was changed. Admin only.
Separate accounts with Admin, Cashier and Store Manager roles, so each person signs in as themselves instead of sharing one login. Discounts and price edits need the right authority.
Every evening the same question: is the money in the drawer the money that should be in it? Until you can answer that, a shortage is something you notice weeks later as a gap you cannot explain.
The Day Book takes the float you started with, adds the cash that came in from sales and recovery, subtracts cash expenses, cash purchases, supplier payments and anything you took to the bank — and tells you what should be in the drawer right now.
At closing time you count the notes and enter the total. The software says whether it matches, and by how much it is short or over. Short usually means a payment taken without a bill, or cash that left without an expense entry. Over usually means a sale billed as udhaar that was actually paid. Either way you find out the same day, while somebody still remembers.
The expected figure stays hidden until you have typed what you counted. Seeing the answer first turns counting into copying, and then a real shortage is never noticed. It is shown after you enter your total, and only if you ask for it.
Credit sales sit on the khata, not in the till, so they are left out of the cash figure — the day’s full takings are shown separately. And nothing is frozen when a day closes: enter a back-dated bill next week and that day’s figures correct themselves, instead of quietly disagreeing with your ledger.
When money changes hands the till asks how it arrived. This is what makes the day close worth trusting: only cash goes into the drawer, so a customer who pays Rs 40,000 by Easypaisa is income but not drawer cash. Counted as cash, every evening would show Rs 40,000 missing.
The question is only asked when something is actually being paid — a full udhaar sale is not asked, because nothing has been paid yet. Recovery payments record the method too.
A Store Manager or Admin. A cashier hands over the notes; the person who signs the day off is the one answerable for a shortfall.
Billing, stock, ledgers and reports all run on your own PC. Internet is used three times only: to activate the licence once, to upload cloud backups, and to download updates. When the line drops mid-season, the shop keeps trading.
Nobody has to remember to back up. Every 10 minutes AgroPOS checks whether anything has changed, and when it has, it writes a backup file on your own PC first and then uploads an encrypted copy to the cloud — both, never one without the other. Closing the software backs up again whatever the timer says, so the day's work is off the machine before you lock the shop.
If the internet is down when a backup is due, the local copy is still written and the cloud copy goes up when the line returns. Old local copies are pruned automatically so the drive does not fill. A stolen PC or a dead hard disk costs you the machine, not the season.
Cloud backup is included with every licence — free for the first year, then Rs 5,000 a year if you want to keep uploading. Local backup is unconditional: it never stops and costs nothing, and if you ever choose not to renew the cloud half, your existing cloud backups stay downloadable.
AgroPOS checks for a new version on its own and installs it in the background. You keep billing; it asks you to restart when it is ready. There is nothing to download, no setup file to hunt for and nobody to call.
Updates are free for the life of the licence. New features and fixes are not sold to you again as a new version, and there is no maintenance contract. If the shop is offline the update simply waits until the next time you have a connection — it never blocks the counter.
Backups are tied to your licence key rather than the machine. Install on a new PC, activate with the same key, and your earlier backups are listed there ready to restore. Local ZIP backups in your Documents folder restore directly.
A dealer’s real question in the morning is not “who owes me” — it is “who said they would pay today”. When a customer names a date, record it. Recovery Dates then lists everyone due today alongside every date that has already slipped, oldest first, because the slipped ones are the ones that get forgotten.
Green when the date is still good, red once it has passed. The colour is readable across a counter without reading a word.
Every customer carries a credit score out of 10. It starts at 10, and a date that passes with nothing paid costs one point — nothing else does. Not the size of the balance, not how long they have owed. A farmer carrying 300,000 who pays on every date he names is a good customer; one carrying 20,000 who has broken four dates is not.
Part payment on the day keeps the promise. Somebody who owed 50,000, said the 12th and brought 20,000 on the 12th turned up and paid — that costs nothing.
Below 5, the till warns before a credit sale, in English and Urdu, with what they promised and how late it is. It does not block the sale: you often know something the software does not. The owner can reset any score back to 10, and the promise history is kept either way.
A farmer wanting ten kilos out of a fifty-kilo bag is an ordinary sale in a zarai markaz, and one most tills cannot bill: they count bags, so ten kilos is “0.2”.
With parchoon switched on, picking a bag of khaad asks Full Bag or by the Kg. The loose sale is charged at that product’s own per-kilo parchoon rate — higher than the bag divided down, which is the whole point — and the receipt, the khata and the sale history all say 10 Kg.
When the open kilos run short the next bag is opened automatically, and the till says so first: “1 more bag will be opened for this sale.” Stock always reads 19 bags + 30 Kg — never a fraction of a bag.
Nothing to set up beyond one switch and a per-kilo rate: the software works out which products can be split from the pack size you already entered on the purchase. Spray and seed never show the option.
AgroPOS Mobile is a free Android app that comes with your licence. It shows your customers and their khata, your recovery list, suppliers, shops and stock — so a customer who stops you in the field gets a straight answer instead of “I will check at the shop”.
You can generate any customer’s account statement as a PDF and send it over WhatsApp while you are standing there: what they purchased, what they paid, the balance, and a signature line.
It is read-only. Nothing on the phone can change your books, so a lost handset is an inconvenience and not an accident. Connecting is one QR scan from Settings → Mobile App on the PC — no account, no password. Up to three phones per licence.
The 14-day trial is the complete software with nothing switched off. Enter a real day of purchases and sales, then print an inspection register and decide.
