Skip to content
What's New

Releases and build notes

What changed in each version of MartPOS for Windows, newest first, then what was built milestone by milestone before the first release.

No release published yet

Release notes appear here as each version of MartPOS for Windows is published. Until then, the build notes below say what has been built so far.

New items at the till, stock lots by expiry date and batch, charges after a purchase is posted

Latest Works today
  • Adding an item at the till: where the owner allows it (Settings › Products › Adding items at the till: off, owners and managers, or cashiers too), a scanned barcode that matches nothing is added at the till with its name, Urdu name, price, piece or loose kg and category, and goes straight on the bill. A cashier without the right can have a manager approve it with their PIN. Each such item is recorded and marked for review in Catalog and on the dashboard.
  • Stock lots: for items that track expiry dates, each delivery's date and batch number is kept as a lot at its place (a line can be split into several lots), sales and everything else that takes stock out use the earliest date first, returns go back to the lot they came from, moves and transfers between branches carry their lots, and counts can go lot by lot. The near-expiry report, the warning at the till and the alerts use the lots. A store PC from before builds its lots once from its dated deliveries; costing stays weighted average.
  • Later charges: a freight or other bill that comes after a purchase was posted is added to it, on the supplier's bill or paid now, shared by value or quantity. The part for goods still in stock raises their average cost; the part for goods already sold goes to cost of goods sold. It can be voided the same day, and the owner portal shows it on the purchase.

Settings for all branches, from the owner portal

Works today
  • Settings › For all branches in the owner portal: the owner shares a section of settings from one branch's values (the receipt's look and words, the ways of paying, the Sales rules, cash and shifts, khata rules, statements, barcode rules, expiry, suppliers and purchases, sign-in and passwords, and more), and every branch that follows it gets the same values.
  • Each branch's store PC applies a shared change with its own checks, at its next sync, and the portal shows what each branch did with it, with the reason when one refused. What depends on a branch's own printers, accounts, counters or stock stays that branch's own; opening hours, the business day, FBR POS and the money accounts are never shared.
  • A branch can keep its own values: a change made on its store PC to a shared section makes that section the branch's own, and the business's value never overwrites it. Managers can read the page; only owners change it.

Password and PIN rules, which PCs each role may use, backups on a schedule, sync controls

Works today
  • Settings › Sign-in & passwords: a password's least length (8 to 16) and letters with digits, PINs of at least 4, 5 or 6 digits with the obvious ones refused, 3 to 10 wrong tries locking sign-in for 1 to 60 minutes, and passwords that expire after 30 days to a year, with a change asked for at the next sign-in. Passwords and PINs are never logged or sent to the cloud.
  • Settings › PCs & sign-in: each PC is for the till and the back office, the till only, or the back office only, and the owner chooses which roles may sign in there. The store PC checks it at every sign-in and on every request.
  • Settings › Backups: a backup at a daily time (Pakistan time) and after each shift closes, the newest few kept and none older than a set number of days, a second copy to another folder such as a USB drive with a warning when it cannot be written, and each backup read back to check it before it is kept.
  • On the Sync & FBR page: pause and resume sync (billing goes on; records wait on the store PC), and unpair the store PC from MartPOS Cloud by typing UNPAIR, refused while records are still waiting. The data stays on the store PC.
  • Settings search, a box beside the Settings menu that opens the page and the card you typed, and Settings history: who changed which setting, when, from what to what. Urdu names under the English ones can also show on a bill's page and in the stock list.

Products, buying and business settings, and landed cost on purchases

Works today
  • Landed cost: freight, loading and other charges on a purchase, on the supplier's bill or paid now from the drawer, a bank or a wallet, are shared into the items' cost by value or by quantity, so profit counts what the goods really cost the shop.
  • Settings › Products: the SKU prefix and digits, in-store EAN-13 barcodes from the 20 to 29 prefixes with their check digit, duplicate barcodes allowed or refused, a new item's tax rate and reorder level, and what happens when an item with stock past its date is sold: allowed, a warning, a manager's PIN, or refused. Stock past its date is estimated from the dated deliveries.
  • Settings › Stock & buying: a new supplier's credit days, numbers for purchases, returns to suppliers and supplier payments on the same rules as bill numbers, a manager for every return to a supplier and a limit in days, and transfers between branches that need a manager to send.
  • Settings › Business: the business-day cutoff (a shop open past midnight counts the small hours on the day before, in its reports and in the owner portal), the A4 invoice and statements in English, Urdu or both with lakhs and crores, and each branch's opening hours.

Printers on each PC, barcode label layouts, and receipts with a logo and Urdu

Works today
  • Settings › Printers on this PC: each PC's receipt, label and A4 printers, a network receipt printer by its address, a test print for each with the result in plain words, and each PC's paper, copies, margins and label offsets.
  • Settings › Barcode labels: saved label layouts (the size in mm, A4 sheets or a roll, which words and which barcode), the layout the label dialog starts from, and a calibration print for each PC.
  • Receipts: the shop's logo (PNG or JPG, made black and white for thermal paper, and on the A4 invoice), the receipt's words in English, Urdu or both, item names in English, Urdu or both, and normal or large text. Urdu goes to a thermal printer as a picture in the Noto Nastaliq Urdu font.

Khata credit rules, statements, expense categories and cash to the bank

Works today
  • Settings › Payments › Khata: a bill that takes a customer over their credit limit is refused, warned about (the cashier confirms), or needs a manager's PIN; the same choices while a customer's oldest unpaid bill is older than a set number of days. The bill keeps how it was let through and by whom.
  • Choose which bills a payment settles, for customers and suppliers; oldest first stays the default.
  • Statements as the shop wants them: every line or one row per bill, everything or only unpaid bills, each bill's items, a note at the foot, on A4 or the receipt printer.
  • Expense categories the shop adds, renames and switches off, each with its own account in profit and loss; a manager's approval for cash taken to or from the bank above an amount the owner sets; and an opening balance for each bank or wallet account.

Owner portal: managers, orders, stock per place and alerts in Roman Urdu

Works today
  • Managers in the owner portal: an owner invites a manager by email, for every branch or only chosen ones. The manager sets their own password from the link, sees the shop records, reports and alerts, and changes nothing: not the plan, the licence, store PCs, settings, items or the members.
  • Orders in the portal, read-only: customers' orders with what is still to deliver, and purchase orders with what is still to come from the supplier.
  • Khata in the portal shows the advance paid to each supplier beside what the shop owes (never taken off it), and the same customer across branches when both branches have the same mobile number for them. Names alone are never merged, and the mobile number itself is not sent to the cloud.
  • Stock per place (shop floor, godown) in the portal. A store PC says which place each movement used from this update on; stock moved before it shows as "place not reported", so the branch total stays the figure to trust.
  • Alert emails in English or Roman Urdu, each member's own choice, and the MartPOS team can adjust the wording. Alert texts by SMS go out through SendPK with the shop's approved message templates.

Business types, services and charges, expiry dates and missed sales

Works today
  • Business type: Kiryana, General store or Mini mart, chosen at setup and changed in Settings › Business type. It sets what new items start with (a kiryana's start as sold loose), suggests categories, and chooses which screens the menus show; "Show every feature" shows them all. Changing it never deletes or changes a record.
  • Services and charges, such as home delivery or a carry bag: billed and refunded like any item, with no stock and no cost. Purchases, counts and transfers leave them out.
  • Optional expiry dates: tick "Track expiry dates" on an item and every purchase of it needs the date on the goods. Reports › Near expiry lists each date with the quantity likely to be left (the first to expire counted as sold first), and the dashboard warns about stock close to its date or past it.
  • Missed sales: "Asked for" (Ctrl+M) at the till notes what a customer wanted and did not get (out of stock, not kept, or the price). Reports › Missed sales lists it, most asked first.
  • Shelf labels printed with a price that has changed since are listed in Labels and on the dashboard, to print again with "Add all to print".
  • Cashiers see stock quantities but not what stock cost. Urdu item names are shown in the Noto Nastaliq Urdu font on screen, in PDFs and in the owner portal's catalogue. CSV imports take two new columns: item type (goods or service) and track expiry.

Loose goods by amount

Works today
  • Selling by amount: on a loose item the cashier presses F6 (Rs worth) and types the amount. The store PC works out the weight to the gram at that line's price and the line shows it: Rs 50 at Rs 160 a kg is 0.313 kg, billed Rs 50.08.

Retail catalogue: loose goods, packs, Urdu names and barcode checks

Works today
  • Items have a name, a size or variant, an Urdu name, other names customers ask for (cheeni, shakar), a brand, a category and a shelf. Search covers all of them and every barcode.
  • Items sold loose keep their stock in parts of their unit, such as 0.625 kg of sugar. Bags and cartons are packs of the item, each with its own price and barcode.
  • A barcode of 13, 12 or 8 digits is checked as an EAN-13, UPC-A or EAN-8, and a wrong check digit is refused. Any other code is kept as the shop's own label. MartPOS never makes a barcode up.
  • Imports, branch transfers, item changes from the owner portal and the demo data all carry these fields. The demo data is a synthetic general store.
  • Selling by amount, business types, services and charges, and expiry dates followed later the same day (above).

MartPOS for general retail, and items from the owner portal

Works today
  • MartPOS takes the till, store server, cloud sync and owner portal built earlier this month and turns them to kiryana stores, general stores and mini marts. Modules a general store does not need were taken out.
  • The owner adds a new item in the owner portal, for one branch or several: its details, packs with their sizes, a barcode per pack, prices, tax rate and reorder level. Each store PC adds it with its own checks. Stock is never sent: opening stock is entered on the store PC.
  • Existing items: packs, pack sizes, barcodes, tax, reorder level and pricing (quantity breaks, prices in price lists, promotions with dates) changed in the portal. Each store PC applies a change only to what the portal saw; a change made in the shop meanwhile is never overwritten, and refusals come back with the reason.
  • Add-ons in Plan & billing: an extra branch, counter or staff account, charged for the days left in the paid period and paid like a plan. The limit rises in each store PC's licence once the payment is verified.

FBR POS reporting and tax on each item

Works today
  • FBR POS reporting through PRAL, off until the shop switches it on in Settings › FBR POS. It works through FBR's online API or FBR's Fiscal Component on the store PC, with each branch's own FBR POS ID.
  • Each sale is reported to FBR right after it is saved, the receipt prints the FBR invoice number and its QR code, and returns go as credit notes against the original invoice. Bills made while FBR cannot be reached print as offline invoices and are sent automatically later, oldest first.
  • A tax rate on every item, added on top of the price and shown on the till, receipts, the A4 invoice and reports, with a PCT code and a Third Schedule mark per item. The owner or their tax adviser sets them; MartPOS suggests none.

Price lists and promotions, transfers between branches

Works today
  • Price lists for groups of customers, with dates: their own item prices, or a discount off a brand or category. Quantity breaks per pack. Promotions for walk-in customers with a first and last day, ended early only with a reason.
  • One source sets each price and nothing stacks: the till takes the lowest of the price, a quantity break and one promotion, and every bill line says where its price came from. Selling below cost still needs a manager, except in a clearance promotion.
  • A second shop joins the business from the cloud with a pairing code, as a new branch.
  • Stock sent to another branch leaves at its cost at once; the other branch counts it in at the same value, and anything short is written off there with a note. The sender sees what arrived.

Purchase orders, the godown and barcode labels

Works today
  • Purchase orders to a supplier at an agreed cost, delivered in parts. Each delivery is received against the order and never beyond what is still to come; each bill is matched against the agreed cost.
  • A godown or back store beside the shop floor. Stock moves between them at its cost; the till sells what is on the floor, and stock reports show where everything is.
  • Barcode labels on A4 sheets or a 50 × 30 mm roll: EAN-13 for a valid EAN, Code 128 of the item's own code otherwise.

Expenses, closing the books, stock counts and owner reports

Works today
  • Shop expenses by category (rent, wages, electricity, transport, repairs, bank charges, other), paid from a counter's drawer, the bank or a wallet. Cash taken to or from the bank. Both show at the shift close.
  • The owner can close the books through a past date; nothing can then be posted into it. Reopening needs a reason; both are recorded.
  • Stock counts while the shop stays open: each counted line keeps what the records said at that moment, and only real differences are posted.
  • Reports: profit and loss for any period, stock value by category, and ageing of what customers and suppliers are owed.

Orders, supplier returns and the licence check

Works today
  • Orders and reservations: Order (F7) at the till, and a Pending deliveries screen. Stock is held for the customer until a hold date (14 days by default), and walk-in sales cannot take it. Items not in stock are awaited.
  • Hand-over is a normal bill at the agreed order price and can be paid from the customer's advance. Cancelling what is left needs a manager.
  • Supplier returns: goods sent back become a claim at the net price last paid to the supplier (stock leaves at average cost). Their credit note settles the claim; a shortfall can be written off with a reason. Returns past a supplier's return window need a manager and a reason.
  • Advances paid to suppliers, used when their bill is entered. The same supplier bill number cannot be entered twice.
  • The store PC checks the cloud's signed licence grant itself, offline, and shows active, grace, ran out or suspended. Past grace, or when suspended, new sales and purchases stop; records stay readable and money owed can still be received. Turning the clock back does not extend it.

Owner portal, licence grants and this website

Works today
  • MartPOS Cloud accounts for shop owners, with two-step sign-in (authenticator app) and recovery codes.
  • Dashboard of each branch's daily sales as reported, with the time of the last report and a STALE mark after 15 minutes.
  • Paired PCs with last-seen times, revoking a PC, and one-time pairing codes from the portal.
  • Signed offline licence grants issued by the cloud.
  • This website, with guides for features that exist.

Customer advances

Works today
  • Take an advance in cash, bank, card or wallet; it is held for the customer, not counted as a sale.
  • Pay a bill "From advance", alone or with other tenders; refund what is left through the drawer.
  • Advances on the khata, at the till, in the shift close and in an advances report.

Going live from your old lists

Works today
  • Import items (with packs and opening stock), customers and suppliers (with opening balances) from CSV.
  • Every row checked before saving; errors by row number; the import resumes after a power cut.

Tills on other PCs

Works today
  • Other PCs in the shop join the store PC with a one-time code over an encrypted, pinned connection, and can be removed at once.

Pairing with MartPOS Cloud and sync

Works today
  • A store pairs with the cloud using a one-time code and sends its sales and returns in order, each once.
  • Sales made while the cloud was down arrived later, and the cloud's daily totals matched the store's report.
  • The till shows whether it is connected, what is waiting and anything the cloud refused.

The till and the store server

Works today
  • Keyboard-first billing, split payments, returns against the bill, khata, purchases, stock movements, double-entry day book, blind shift close.
  • Packs with sizes per item, several barcodes per item, dated prices.
  • Receipts and A4 invoices.
Get in touch

Want to try MartPOS in your shop?

Tell us about your shop and we will show you the till and the owner portal, and set MartPOS up on your shop PC with you.