How to choose a JoFotara-ready POS system in Jordan: a buyer's checklist
What to check before you buy a cashier system in Jordan: how it handles JoFotara on every sale, what happens offline, which hardware it supports, how shifts, stock, branches and returns work, and the questions to ask every vendor.
Choosing a cashier program in Jordan used to be about speed at the till and a tidy receipt. Since the national e-invoicing system arrived, a register also has to issue a compliant e-invoice for every sale, print its QR code, survive internet cuts and handle returns as credit notes. A demo rarely shows those parts. This checklist covers what to test before you sign, with questions you can put to any vendor. If you want to see how one system handles it, our POS system for Jordan page walks through shifts, returns and JoFotara in Aspirations, as one option among several.
1. JoFotara on every sale
In Jordan a counter sale is a cash invoice. If your business is covered by the national e-invoicing system, each sale has to reach JoFotara. ISTD's technical integration guide says the QR code returned by the national system must be shown on the seller's invoice, so a register that cannot print it is not ready, whatever the brochure says. Check that:
- Each sale is sent to JoFotara automatically through integration, not typed again on the portal.
- The QR code JoFotara returns is printed on the receipt and stored with the sale.
- The system stores the invoice ID, UUID, QR code and JoFotara status, as ISTD's guide recommends, so any sale can be traced later.
- Rejected sales are visible to someone the same day, with JoFotara's error message.
- Each item carries the right tax category (16% general rate, zero-rated or exempt). To check prices with and without tax, use our sales tax calculator.
The setup itself, from credentials to the first accepted invoice, is in our JoFotara step-by-step guide.
2. What happens when the internet drops
Internet cuts happen, and the queue doesn't wait. Ask the vendor to unplug the network during the demo and keep selling. Then check what happened:
- Can the register keep selling, and are offline sales kept on the device in order?
- When the connection returns, are sales uploaded once, with duplicates recognised?
- For JoFotara, ISTD's guide says that after a timeout or connection failure the invoice must be resent without generating a new UUID. Ask how the system does this.
- What does the receipt show for a sale made offline, and how is the e-invoice completed afterwards?
- What doesn't work offline (loyalty redemption, credit limits, live stock in other branches)?
3. Hardware: test with your own devices
List what you have and what you plan to buy, then test those exact models:
- Computer or tablet: does it run in a browser, a Windows program or an app? Browser-based systems are easier to replace if a PC fails.
- Receipt printer: 80mm or 58mm, Arabic text and the QR code printed clearly.
- Barcode scanner: most USB scanners type like a keyboard, but test your labels, including variants by size or colour.
- Scales: if you sell by weight (vegetables, meat, nuts), ask whether the system reads the scale directly or reads weight-embedded barcodes printed by a label scale. Many systems do one but not the other.
- Customer display, cash drawer and card terminal: is the card terminal integrated, or does the cashier record the card amount?
4. Shifts and cash closing
The drawer is where money goes missing. A good register makes the shortage visible the same night:
- Opening float, X report at any time and Z report on closing with a sequential number.
- Expected cash calculated by the system, not typed by the cashier.
- The variance posted automatically to a cash over/short account.
- Split payments (cash and card), with change given from cash only.
- A cashier role that sees only its own shift.
5. Stock and accounts in sync
A standalone cashier program that sends a daily total to accounting leaves stock and the ledger to be rebuilt by hand. Ask whether a sale reduces stock and posts revenue, tax and cost of sales at the moment it is saved, and whether purchases, transfers and stocktakes live in the same system. Batch and expiry tracking matters for groceries and pharmacies, and serial numbers matter for phones and electronics.
6. Branches
- Each register belongs to a branch and sells from that branch's warehouse.
- Reports per branch and consolidated.
- Transfers between branches with stock in transit.
- A branch registered under its own tax number has its own JoFotara credentials and issues invoices under its own identity.
7. Returns and exchanges
A return must become a credit note that references the original sale, with a reason. JoFotara accepts returns on quantities only and won't accept more than was sold, so the register should find the receipt by number, let you pick lines and refuse over-returns. The JoFotara portal user guide says the portal can only return invoices issued on the portal, so sales your register sent by integration must be returned from the register itself. Our guide to JoFotara credit notes and returns explains the rules.
8. Controls that protect you
Article 67(b) of the Income Tax Law makes it an offence to deliberately design an accounting program intended to produce records that materially do not match reality. Be wary of any cashier program that offers to delete receipts, hide sales or keep a "second drawer". Look instead for gap-free numbering, locked issued invoices, a full audit trail of voids and refunds, and permissions for discounts and price changes.
Before you sign: run one branch for a week
A demo shows the best case; a pilot shows the rest. Run the system for a week on one register in one branch, sell your real items, do a partial return and a full shift close, and cut the internet at least once. Then compare the week's sales on the JoFotara portal with the POS report and with the drawer. If all three agree, you are on the right track.
Questions to ask every vendor
- Is your JoFotara integration live with customers today, or ready and waiting for credentials? Can I see a real receipt with a QR code that scans in Sanad?
- What happens to a sale, its e-invoice and its QR code when the internet drops?
- Which printers, scanners, scales and card terminals have you tested? Can we test mine?
- How does a return reference the original sale, and can I return part of a receipt?
- Does a sale post to stock and the ledger immediately, or as a daily summary?
- How are prices charged: per register, per branch or per user? What do updates and support cost?
- Can I export my sales, items and customers if I leave?
- Who supports us in Arabic, and during which hours?
Where Aspirations fits
Aspirations POS runs in a web browser on a PC or tablet and works as a PWA. Each sale is a cash invoice from the same engine as the rest of the ERP: it issues stock, posts to the ledger and is sent to JoFotara after it is saved, with the returned QR code printed on 80mm receipts. It has X and Z reports with the variance posted to cash over/short, barcode lookup, held sales, split payments, promotions and loyalty, offline selling with an ordered upload queue, branches with their own warehouses, and returns by receipt as credit notes. Its limits: no scale integration, no customer display, card terminals stay separate, and there are no restaurant tables or kitchen orders; the POS runs in the browser. The JoFotara integration is ready (UBL 2.1) and requires your own credentials; a sale JoFotara couldn't receive is resubmitted manually. Plans are being finalised, and a free trial is available. For shops, see also our retail and supermarket software page.
This checklist is general information. E-invoicing requirements can change, so confirm your obligations with the Income and Sales Tax Department.
