Frequentlyaskedquestions

Yes, though the site is written for Kurdistan because that is where the specific knowledge is worth the most. The dual-currency, multi-wallet and Kurdish/Arabic RTL work transfers directly to neighbouring markets, and I take remote work in English for clients elsewhere. Pricing for the Kurdistan market is deliberately lower than Western rates; work for clients abroad is quoted separately.

Four things, and they are all checkable rather than claims. I publish my pricing, where almost every local vendor is quote-on-demand only. I publish technical documentation and integration guides, where effectively no local vendor does. I work natively in Kurdish — both Bahdini and Sorani — as well as Arabic and English, where the largest local competitors ship English and Arabic only. And I work alone with no subcontractors, so the person who scopes your project is the person who builds it. The trade-off is honest: I cannot staff a twenty-person on-site rollout. If that is what you need, you want a larger firm and I will say so.

Yes, and it works far better when the same person builds both — because then the AI reads your live database instead of a stale export. The use cases that reliably pay for themselves are unglamorous: supplier-invoice extraction straight into accounts payable with three-way matching, demand forecasting and reorder planning that accounts for seasonality and Ramadan and Newroz peaks, natural-language reporting so an owner can ask "which branch lost money last month" in Kurdish on their phone, exception detection for duplicate payments and price drift, and settlement reconciliation matching across two currencies. What does *not* pay for itself is a chatbot on your website that cannot see your stock. I will tell you which is which for your business before you spend anything.

Yes — that is one of the things I have been doing longest. WhatsApp assistants that answer customers in their own language, AI receptionists for hotels and clinics, booking and scheduling assistants, sales-lead qualifiers that hand warm leads to a human, and document-processing pipelines that read invoices, IDs and receipts. The difference from a generic chatbot is that these are wired into a real system — live stock, real bookings, actual order status — so the answers are true rather than plausible. Every AI decision is logged and auditable, and there is always a defined fallback to a human when confidence is low.

It depends on scope, and any vendor quoting you a number before understanding your business is guessing. What actually drives the price is knowable, though: the number of branches and tills, whether you need kitchen operations, whether you need batch and expiry control, how many payment wallets you want to accept, whether you need full dual-currency reconciliation, and — usually the biggest hidden factor — how much data has to be migrated and what condition it is in. Packaged local products are typically cheaper up front; custom is worth paying for when you run several branches, when your workflow is genuinely unusual, or when you need an integration nobody else will build. I give a fixed scope and a fixed price in writing after a free scoping call, so the number you see is the number you pay.

Because a POS for one till and a POS for a six-branch group are not the same product, and any number I printed would be wrong for one of you. What I publish instead is exactly what drives the price up and down — branches, modules, integrations, currencies, and above all how much data has to be migrated and what condition it is in — so you can estimate your own scope before we ever speak. Then you get a free scoping call and a written proposal with a fixed scope and a fixed price. Not an hourly estimate that grows. If the scope changes mid-project, we agree the change and its cost in writing first.

Yes. FIB authenticates with OAuth2 client credentials, then a create-payment call returns a payment ID, a base64 QR code, a short readable code and a deep link into the FIB app; you confirm the result either by polling the status endpoint or by receiving a webhook. FIB publishes official SDKs for PHP, Laravel, Python, Flutter, Android and iOS plus a WooCommerce plugin, and there is a sandbox to test against. The part that takes real work is not the API call — it is idempotency, webhook verification, a proper payment state machine, and reconciling FIB's dinar settlement against a ledger denominated in USD. Cost depends on how many rails you want, whether reconciliation is included, and what it plugs into; it is meaningfully cheaper bundled into a POS or ERP build than commissioned standalone.

You need accounting software if your problem is producing financial statements. You need an ERP once your problems are operational — stock counts that do not match the shelf, two branches quoting different prices, payroll taking three days because hours and salaries live in different places. The tell is that the same number exists in more than one system and they disagree. Start with the two modules that are actually on fire, usually inventory and purchasing, and add accounting underneath once they are feeding it. Buying a full ERP suite up front is how most of these projects fail.

Several companies sell point-of-sale software in Kurdistan — Ejaf Technology, MiroTech, Geno, BoMN, Standing and Awrosoft are the established local vendors, mostly in Hawler. I build custom POS systems from Duhok for businesses whose workflow does not fit an off-the-shelf product: multi-branch operations, businesses pricing in USD while their payment gateway settles in IQD, and anyone who needs the interface and receipts to work properly in Kurdish. If a packaged product genuinely fits you, I will tell you so and name it — that is a shorter conversation and it costs you nothing.

The right restaurant POS in Kurdistan has to do four things most imported products do badly: handle IQD and USD on the same bill with a stable exchange rate, keep taking orders when the internet drops, print and display correctly in Kurdish and Arabic RTL, and accept more than one mobile wallet — because ZainCash, AsiaPay and NassWallet are each locked to a different mobile network, so a single-wallet checkout turns paying customers away. Beyond that: table map, table-side ordering, kitchen tickets, course firing and split bills. Note that the 10% tax on restaurants was abolished in July 2024, so you should not be paying for a tax module you no longer need.