How to Choose FBR-Ready POS Software in Pakistan: A 12-Point Buyer Checklist
Many POS products now say “FBR ready”. The phrase can mean anything from a full integration to a receipt that merely looks right. Before you commit your counters to a system, use this checklist. It is written from what actually goes wrong in shops, not from a brochure.
Key takeaways
- “FBR ready” should mean the software sends invoices to FBR, saves the fiscal number and prints the SRO 1006 layout, not just a lookalike receipt.
- Ask about returns (credit notes), duplicate protection, multi-shop PoS IDs and what happens when FBR is down.
- Be careful with claims of “FBR approved” or “certified”. Ask what exactly that means and for proof.
- Test on the sandbox before you pay for a year.
The 12-point checklist
| # | Ask the vendor | Why it matters |
|---|---|---|
| 1 | Does it print every SRO 1006 field in the standard layout? | A missing field makes the receipt non-compliant. See SRO 1006 explained. |
| 2 | Does it send each invoice to FBR and store the fiscal number? | The stored number is your proof and feeds the QR code. |
| 3 | Is the sale ever blocked if FBR or the internet is down? | It must not be. The invoice should be saved first and sent later. |
| 4 | How are sales returns reported? | Returns should go as credit notes against the original invoice, with stock and ledger updated. See how to post a sales return to FBR. |
| 5 | What stops one sale getting two FBR numbers? | The FBR software does not check for repeats. The POS must guard against double sends and lost answers. |
| 6 | Do item lines add up to the total to the paisa? | Rounding drift means what you print differs from what FBR holds. |
| 7 | Can I use a separate PoS ID for each shop? | Reporting under the wrong shop is a real risk for multi-shop businesses. |
| 8 | Is there a sandbox mode with a clear TEST marker? | You need to practise without creating real invoices. |
| 9 | Is there a register of sent, pending and failed invoices? | You must be able to see what is still unreported, with the reason. |
| 10 | Are stock, customer ledger and accounts in the same system? | Otherwise every sale is typed twice and the numbers drift. |
| 11 | Does it print on 80 mm and 58 mm thermal rolls and A4? | A QR that is cut off or too small will not scan. |
| 12 | What setup help and support do you give, in Urdu and English? | The first week is where most problems appear. |
Red flags
- “FBR approved” with nothing to show. Ask exactly what was approved, by whom, and when.
- A receipt template with no real FBR connection. The fiscal number must come from FBR, not from the software itself.
- Returns “handled manually”. You will end up with unreported credit notes.
- No answer on duplicates. If the vendor has not thought about double sends, you will meet them in production.
- Per-invoice pricing surprises. Ask for the full monthly cost, including setup and support.
How to test a vendor in one afternoon
- Ask for a sandbox demoWatch a sale go to the FBR sandbox, come back with a number, and print.
- Try to break itStop the FBR service and send an invoice. The sale must stay saved with a clear message.
- Press send twiceThe second press must show the saved number, not create another.
- Do a returnMake a sales return and see the credit note, the stock change and the ledger change.
- Open the registerCheck that everything is listed with its status and can be exported.
Follow the same flow in our setup and sandbox checklist.
How PaakiShop answers the 12 points
PaakiShop prints the SRO 1006 layout, sends each invoice through FBR's fiscalization service, stores the number and QR, never blocks a sale, reports returns as credit notes, guards against duplicate sends, keeps lines exact to the paisa, supports a PoS ID per shop, marks sandbox invoices as TEST, lists everything in an FBR register with CSV export, and keeps stock, ledgers and accounts in the same system. It prints on 80 mm, 58 mm and A4, and we help with setup in Urdu and English.
We say it plainly: PaakiShop integrates with FBR's fiscalization service and has been tested against the FBR sandbox. It is not an official FBR product. See it all on the FBR digital invoice page.
Frequently asked questions
What does FBR-ready POS software mean?
It should send each sale to FBR, store the fiscal number, print the SRO 1006 layout with QR and FBR logo, and handle returns and failures properly.
Is any POS software officially approved by FBR?
Ask any vendor who claims approval to show exactly what was approved and by whom. PaakiShop does not claim certification; it integrates with FBR's service and is tested on the FBR sandbox.
Do I need new hardware?
Not necessarily. PaakiShop runs in the browser, uses FBR's small local service on the counter PC, and prints on common thermal printers.
Can I use one POS for several shops?
Yes, if the software supports a separate PoS ID per shop and refuses to report under the wrong one. PaakiShop does.
How much does it cost?
See the current pricing on our POS software price page. There is a free 3-day trial.
Test PaakiShop against this checklist
Try the sandbox flow, a return and the register yourself. Free for 3 days.
See FBR invoicing in PaakiShopStart free 3-day trialPlease note: this guide explains how FBR POS invoicing and PaakiShop work, in plain language. It is general information, not tax or legal advice. Tax rules and FBR procedures can change, so confirm anything specific to your business with your tax consultant or FBR. PaakiShop integrates with FBR's fiscalization service; it is not an official FBR product.
