Price it the way you price anywhere, then adjust for three things Gulf law decides for you: who bears withholding tax, the currency and exchange rate your invoice must carry, and what you may not do with your reseller's price. For Saudi public buyers you do not have to guess what competitors charge, because the government publishes it.

Most advice on Gulf pricing starts from the premise that the region is opaque and you have to guess. For the largest single block of buyers in the region that is simply false, and the correction is the most useful thing in this article.

Figures and rules in this piece are current as at 28 October 2026. Where a statutory provision is quoted from an Arabic original with no official English text, or from an official translation that the issuing body itself labels unofficial, that is stated at the point of quotation. Almost every Gulf tax instrument quoted below carries its publisher's own disclaimer that the Arabic prevails.

Saudi Arabia publishes every bidder's price, and almost nobody looks

Etimad, the Saudi national procurement platform, exposes each tender's award results through a public endpoint that requires no login, no account and no credentials. The human readable tender page is less dependable: of fifteen tenders checked on 28 October 2026, six redirected to a login and nine served without credentials. The results endpoint returned the full table for all fifteen.

What it returns, for a tender whose results have been announced, is two tables. The first is the list of submitting suppliers, with the name of the supplier, the value of its financial offer and the result of the examination of its technical offer, marked compliant or non compliant. The second is the awarded supplier, repeating its own financial offer next to the final award value. Where results are not yet out, the endpoint returns a single Arabic sentence saying the awarding results have not been announced yet.

That is not a survey, an estimate or a vendor claim. It is the actual money every competitor put on the table, published by the buyer. The visitor index reported more than 290,000 tenders when queried on 28 October 2026, of which more than 241,000 had award results announced. The index begins in late 2019 and counts direct purchases as well as open competitions, and it cannot be browsed through: the listing serves only a shallow window at either end of whatever sort you choose, so you get at it by searching and filtering rather than by paging.

Four worked examples, all retrieved and checked on 28 October 2026, with public tender pages a reader can open.

A direct purchase by National Guard Health Affairs, tender HR421415, for a three year Photoshop subscription licence for the public relations department of King Abdulaziz Hospital in Al-Ahsa, offers closing 14 October 2026, drew four offers and all four passed the technical examination: SAR 5,451.00, SAR 6,641.25, SAR 16,531.25 and SAR 39,215.00. The highest compliant offer was more than seven times the lowest. The award went to the cheapest at SAR 5,178.45, exactly five percent below its own offer.

An open competition by the Saudi Export-Import Bank, tender 10000653, for renewal of licence subscriptions and technical support for its information technology infrastructure systems for 2026, offers closing 10 September 2026, drew three offers, all compliant: SAR 4,334,551.25, SAR 4,796,523.06 and SAR 7,217,286.19. The highest was about 66.5 percent above the lowest. The award went to the cheapest at exactly its own offer. That one matters because it is the same pattern at seven figure scale, which kills the objection that wide dispersion is an artefact of trivial contracts.

A direct purchase by King Fahd Hospital in Jeddah, tender ORN0000019693, for renewal of attendance system licences, offers closing 15 September 2026, drew two compliant offers, SAR 98,325.00 and SAR 166,750.00, about 69.6 percent apart, and was awarded at the lower figure unchanged.

An open competition by the Saudi Irrigation Organization, tender number 751/20, for securing and supplying Microsoft software licences, offers closing 6 May 2020, drew four offers from three bidders, one of which submitted twice. Both of that bidder's offers, SAR 956,649.36 and SAR 988,149.36, were marked technically non compliant, and the cheaper of the two was the cheapest number on the table. The award went to the cheapest compliant bidder at SAR 981,132.14, about 2.6 percent above that cheapest number, and at exactly its own offer.

Three things in that record are worth more than the numbers themselves, and none of them ages.

The spread is enormous and it is not confined to small contracts. Compliant resellers quoting against one published specification for the same product came in anywhere from 66 percent to more than seven times apart. If you have been told that Gulf buyers are simply price driven, that record says something more precise: wide dispersion survives the evaluation, because bidders are not all pricing the same thing and the evaluation is not only about price.

The cheapest bid is not a safe bid. In the Microsoft tender the cheapest offer on the table failed the technical examination and the money went to a dearer compliant one. Pricing to be lowest is wasted if the technical submission does not clear, and the published record lets you see how often that happens.

Most awards land on the bidder's own number. Across the awards checked for this piece the award value equalled the winning offer exactly in most cases, competed or not, and the only reductions seen were five percent on the Photoshop licence, about 1.4 percent on a 2020 video conferencing licence award and five halalas on a 2020 subscription. The negotiation happens before the envelope, not after it.

Two honest limits. First, this is Saudi public sector procurement. It is an outstanding guide to selling to Saudi government and government linked buyers and a weak proxy for Gulf private sector enterprise pricing. Second, nothing else in the region publishes every bidder's price. Bahrain comes closest and is worth knowing about: the Tender Board publishes a monthly awarding report as a public PDF, current to August 2026, giving for each award the tender number, the buying entity, the subject, the winning bidder and the award value in dinars to three decimals, including software lines such as an SAP support award at BHD 88,697.495 and an Oracle managed services award at BHD 600,000.000. What it does not give you is the losing bidders' numbers, which is the whole value of the Saudi record. The UAE federal Digital Procurement Platform resolves to a login page, and the Ministry of Finance's current business opportunities page lists open tenders with their reference, title and dates and no award values.

Set against that, the best commercially available thing is thin. The one benchmark report with a stated Gulf sample, Avasant's Middle East composite benchmarks chapter for 2026 and 2027, describes its own sample in these words: "Chapter 6 provides composite metrics for organizations across the Middle East, including Bahrain, Kuwait, Oman, Qatar, Saudi Arabia, and the United Arab Emirates. The 25 respondents in this sample range in size from a minimum of about $70 million to over $445 billion in annual revenue." Twenty five respondents, six countries, a revenue range spanning four orders of magnitude, behind a login, and it is an IT spending and staffing benchmark rather than a source of software prices. A Saudi government platform publishing every bidder's exact figure beats it comfortably, and it is free.

Withholding tax is not yours to move, and one state has legislated on what happens if you try

The rates differ sharply across the six states and that spread is set out in which GCC country you should enter first. How the same software attracts a different rate depending on which copyright rights pass is in Saudi market entry for technology companies. What follows is only the question those two pieces do not answer: can you put the tax on the customer?

As a matter of private contract, yes, and nothing in the Gulf instruments reviewed for this piece voids an agreement that the customer bears the tax. As a matter of tax law, no, because every statute fixes the duty to withhold and remit on the Gulf payer, and the payer cannot contract that away.

Saudi Arabia, Article 68 of the Income Tax Law, as the tax authority quotes it in its own withholding guideline: "Every resident, whether a taxpayer or not under this Law, and every Permanent Establishment of a non-resident in the Kingdom that makes a payment to a non-resident from a source in the Kingdom, must withhold tax from the amount paid". The same guideline adds that government departments, ministries and other authorities are caught "by virtue of being residents, notwithstanding that they do not acquire the status of a 'taxpayer'". The base is "the entire amount paid by the resident to the non-resident", so a gross up, which contractually increases the amount paid, increases the base with it. The guideline also reads "payments" broadly enough to cover any means "that results in the discharge of liability between the transacting parties and have the same economic effect", though that passage is about what counts as a payment to the non-resident rather than about a payer bearing the tax, so it corroborates the arithmetic rather than establishing it. The authority has not published that arithmetic anywhere this piece could find, in English or Arabic, and it is not attributed to them here.

The penalties land on the payer. Paragraph A of Article 77 of the Law imposes a delay penalty of one percent of the unpaid tax for every thirty days of delay on the person obliged to withhold, and Article 68(1)(E) of the Implementing Regulations adds the same one percent for every thirty days where the tax is paid late after the tenth day of the month following the payment to the beneficiary. Article 69 of the Implementing Regulations then extends the fraud penalty in Paragraph B of Article 77, twenty five percent of the tax difference, to the person obliged to withhold where information is concealed or incorrect information is given with intent to evade tax, and the guideline states that "the responsibility for its payment lies with the entity obligated to withhold". That is why a Saudi buyer resists a gross up: it is signing up to a liability it already carries personally, on a larger number.

Qatar is the one state that has legislated the consequence, and it did so without prohibiting anything. Article 11 of the Executive Regulations of the Income Tax Law, issued by Cabinet Decision No. 39 of 2019, lists the expenses that are not deductible, and the second item is: "Income tax borne by the taxpayer on behalf of a non-resident." So the Qatari customer may agree to bear your tax, and then loses the deduction for it against its own corporate tax. Article 24 of the same Regulations requires the withheld tax to be remitted "before the sixteenth day of the month following the month in which the withholding occurred", and Article 24(7) of Law No. 24 of 2018, as amended in 2022, penalises a failure to withhold with "a financial penalty equal to the amount of tax not withheld, in addition to paying the due tax amount". A Qatari buyer asked for a gross up is being asked to take a non deductible cost on top of a doubled downside. Note that the Law has its own Article 11, about tax returns, which is a different provision.

Oman puts the liability on the payer in the same way. Article 53 of the Income Tax Law, Royal Decree 28/2009, in the Tax Authority's own English, which that authority labels a translation under which the Arabic prevails: a taxpayer paying any of the Article 52 amounts "shall be liable to deduct tax from the gross amount paid or credited" and remit "not later than fourteen days from the end of the month in which that amount has been paid or credited, whichever is earlier". Article 53 bis, added in 2017, extends the same duty to ministries, bodies and public authorities. Article 144 then provides that where the tax is not paid in time, "The assessment shall be made in the name of the person who has paid the amount". Note that Article 52 lists "Consideration for the use of or right to use computer software" as its own head of charge, so a software vendor is squarely inside it.

Kuwait is the exception, and it is narrower than it is usually described. The Ministry of Finance's Budget Executive Regulations for FY 2026/2027, which KPMG dates to 29 March 2026, are reported to bar Kuwaiti government contracts from containing clauses under which the state bears a contractor's income tax or grants it an exemption. This piece cannot quote the instrument: mof.gov.kw refused every connection attempt from the research environment, on repeated tries, and no secondary source gives an article number. KPMG's Kuwait member firm says the ministry "has reiterated" that "Government contracts must not include clauses, whereby Government: Bears income tax on behalf of companies, or Exempts companies from income tax", and that such clauses "are prohibited in government dealings and may be deemed invalid", which is hedged and implies the rule predates these regulations. Deloitte describes it as prohibiting "contractual provisions that require government entities to bear or assume the income tax liabilities of contractors, or to grant tax exemptions on their behalf". Two further points matter commercially. The prohibition is reported only for government contracts, so it says nothing about a Kuwaiti private buyer. And "the state bears the tax" is not quite the same proposition as "a gross up clause"; gross up is the firms' own label for it, used in both firms' headings.

Separately, Kuwait runs a retention rather than a withholding tax. RSM Kuwait's November 2015 tax flash reports that all ministries, authorities, public institutions, companies, private entities and natural persons contracted with a foreign corporate body "shall retain 5% of the contract, agreement or transaction value or from each payment to the corporate body", and that amounts withheld "shall be considered in trust for the interest of the State Public Treasury until settlement of tax due". Its 2024 income tax newsletter puts the obligation more broadly still, as a mandatory retention of five percent "from each payment made to any company, irrespective of the recipient's location", released to recipients who have obtained an annual tax clearance certificate, and adds that where a foreign company closes its operations and leaves Kuwait without settling, the tax authority can collect the foreign company's due payment from the Kuwaiti contract owner that engaged it. Note that RSM cites the governing articles inconsistently across those two publications: the 2015 flash gives Articles 37 and 39 of Law No. 2 of 2008, the 2024 newsletter Articles 37 and 38 of its Executive Bylaw. The Bylaw attribution is the coherent one, and the numbers should be treated as reported rather than verified. KPMG adds that where a government entity has held a retention for five years without the contractor claiming it with a tax clearance certificate, the entity must transfer those funds directly to the ministry.

The practical consequence for a price list is simple. In Saudi Arabia, Qatar and Oman, assume the tax leaves your invoice and that recovering it is a procedure, not a certificate. In Kuwait, assume five percent of every payment is parked until you have produced a clearance certificate, and do not price a government deal on the assumption that the state will absorb the tax. In the UAE the question does not arise: Article 45 of Federal Decree-Law No. 47 of 2022 sets withholding tax on the listed categories of state sourced income derived by a non resident "at the rate of 0% (zero percent)", subject to a Cabinet decision that could change it.

Your pricing page probably does not have to show Gulf tax, and the Saudi regulator says so in terms

Four of the six states require advertised prices to include VAT, and the instinct of a European vendor with a public price page in euro is to assume it is caught. On the published rules it usually is not, and the clearest statement of why comes from the Saudi tax authority's own electronic commerce guideline, second edition, May 2026: "if non-resident Suppliers make supplies to Customers registered for VAT, and those Customers are required to account for the VAT themselves on the received supplies using the Reverse Charge Mechanism, the non-resident Supplier shall have no tax obligations".

That sentence generalises, but not through the words of the display duty. Only Oman addresses that duty to the person: Article 37 obliges "The Taxable Person" to display tax inclusive prices. The UAE frames it on the supply and reaches the person only through the penalty at Article 76(1). Saudi Arabia has no domestic display article at all, and Bahrain's is drafted impersonally. What does generalise is the step behind it: in all four states a taxable person is someone registered or obliged to register, and a non resident's duty to register turns on being liable to pay the tax, which reverse charge moves to the business customer. The UAE says it plainly at Article 13(2) of Federal Decree-Law No. 8 of 2017, which obliges a person with no place of residence in the State to register where he makes supplies "and where no other Person is obligated to pay the Due Tax on these supplies in the State". Bahrain's Article 29(C) requires a non-resident to register regardless of the value of his supplies "as long as he is obliged to pay the Tax in the Kingdom", Oman's Article 57 requires registration from the date on which he is obliged to pay the tax, and the Saudi Implementing Regulations impose mandatory registration on a non-resident obligated to pay tax on supplies made or received by that person in the Kingdom.

The mechanics of that shift for the UAE specifically are in whether you need a local entity to sell software in the UAE, and this piece does not repeat them. Where the states diverge is in the exceptions, and a vendor that does become registered somewhere faces four different pricing page obligations.

The UAE is the most accommodating. Article 38 of Federal Decree-Law No. 8 of 2017, in the version the tax authority serves from its legislation archive and marks "This is not an official Translation", reads: "In the case of a Taxable Supply, the advertised price shall include the Tax. Instances where prices do not include the Tax shall be determined by the Executive Regulation of this Decree-Law." The exceptions are at Article 27 of Cabinet Decision No. 52 of 2017, headed "Price Excluding Tax", under which the taxable person may declare prices exclusive of tax for exports and "Where the customer is a Registrant", and shall declare them exclusive of tax for reverse charge supplies. So in the UAE business to business exclusive pricing is not merely permitted, it is required.

Saudi Arabia has no price display provision in its VAT Implementing Regulations, which were read in full for this piece, and the authority's own guidance points elsewhere for the rule. The only binding source is Article 25(2) of the GCC Common VAT Agreement: "published prices in the local market for Goods and Services must include VAT." The authority's retail guideline footnotes the display rule twice to exactly that treaty provision rather than to any Saudi instrument, and its electronic commerce guideline confines the duty to end consumers: "Final prices announced to end consumers on websites, electronic platforms, social media stores, or applications must include VAT."

Bahrain is the trap. The duty is in Article 3 of Decree-Law No. 48 of 2018, whose official Arabic requires the announced price for goods and services in the local market to include the amount of tax due, a phrase both of the National Bureau for Revenue's own renderings shorten. The only exception, at Article 2 of the Executive Regulations, is export, with no carve out for a registered customer. The penalty at Article 60(B)(3) is addressed in the Arabic, which prevails, to everyone who commits the listed acts rather than to a taxable person. And Article 4(4) obliges "Every Person who includes an amount of Tax on an invoice issued in the Kingdom" to pay it, so a vendor that helpfully adds a VAT line to look compliant can manufacture a liability it did not have. Note also that Bahrain's official legislation portal still prints the original five percent rate, because it serves original enactments rather than consolidations; the National Bureau for Revenue's own current page states that the standard rate was amended to ten percent as of 1 January 2022.

Oman is the bluntest. Article 37 of the VAT Law, Royal Decree 121/2020, is one unqualified sentence, and in the Tax Authority's own English it reads: "The Taxable Person shall present the prices of Goods and Services inclusive of the Tax." There is no export exception and no business to business exception. The penalty sits at Article 203 of the Executive Regulations, under which the Chairman may impose an administrative fine of not less than one thousand and not more than ten thousand Omani rials for, among the listed cases, a taxable person's failure to display prices inclusive of tax. The English of the Law is the Tax Authority's own and it labels it a translation for general guidance under which the Arabic prevails. The Authority serves the Executive Regulations only as the Arabic Official Gazette text, so the Article 203 wording here is read from the Arabic, and none of the three amending decisions issued since, 456 of 2022, 521 of 2023 and 81 of 2025, touches it.

For the gross number a buyer pays, the current standard rates are fifteen percent in Saudi Arabia, ten percent in Bahrain since 1 January 2022, five percent in the UAE and five percent in Oman. Qatar and Kuwait have not enacted VAT. Qatar publishes the GCC Agreement among its laws while its tax authority's own list of taxes in Qatar does not include VAT at all, and the International Monetary Fund's 2024 Article IV report records that the authorities "continued to assess the appropriate timing for VAT introduction". For Kuwait the Fund's February 2026 Article IV report states that measures to "introduce a VAT and excise tax, have not been implemented" and that "The authorities are developing plans to implement these tax reforms", and its own illustrative scenario models zero VAT revenue for the first three projection years. So the gross price of identical software varies by fifteen points across one customs union, even though for a registered business buyer the tax is recoverable and economically neutral.

One thing that is not in the price at all: customs duty. The Saudi imports and exports guideline defines goods for VAT purposes as "All types of tangible property (physical assets)" and notes that the term import "in the GCC and in the Saudi law relates only to the import of goods", adding that "There are no specific procedures for the import of services, and VAT is not collected upon the import of services by the Authority, as is the case for the import of goods." The UAE reaches the same place from Article 3(1)(e) of its Executive Regulation, which treats "The transfer or licensing of intangible rights" as a supply of services. Software on a disc is goods and meets the tariff. The same software downloaded or consumed as a service is not an import of goods in either state, so no customs duty arises on it, and the only indirect tax is destination state VAT that a registered buyer self assesses.

The exchange rate on your invoice is not yours to choose

This is the rule most often missed, and it is where a euro price list actually breaks. Four regulators, four different definitions of the rate, and three different trigger dates.

The UAE is the strictest. Article 69 of Federal Decree-Law No. 8 of 2017, headed Currency Used on Tax Invoices, provides that where "the supply is in a currency other than the UAE Dirham, then for the purposes of the Tax Invoice, the amount stated in the Tax Invoice shall be converted into the UAE Dirham according to the exchange rate approved by the Central Bank of the State at the date of supply". Article 59(1) of the Executive Regulation goes further than converting the tax: it requires the gross amount payable and the tax amount to be expressed in dirhams, and the per line amount payable with them, plus "the rate of exchange applied where the currency is converted from a currency other than the UAE dirham". A euro price list cannot itself be a UAE tax invoice.

The central bank publishes the rate for this purpose on a table headed "Exchange rates against UAE Dirham for VAT related obligations", and the tax authority's public clarification VATP004 removes the discretion a vendor might think it has: "Businesses must use the exact exchange rate as published by the UAE Central Bank, which includes using the same number of decimal places as published", with the worked example that where the dollar rate is published as 3.672500 it "is not permitted to round the exchange rate to fewer decimal places e.g. 3.7". For a European vendor that rule bites harder than the example suggests, because the central bank publishes the dollar to four decimals and most of the rest of the table to six: on 27 October 2026 the euro was published at 4.092378 dirhams. VATP004 also fixes the timing: "The UAE Central Bank updates the exchange rates on its website each day on or after 6pm, to cover the rate applicable for that day", and "Where a tax invoice is issued prior to 6pm on any given day, it will be acceptable to use the exchange rate published on the UAE Central Bank website at the time the tax invoice is raised, i.e. the rate for the day before." For the case that actually applies to a remote vendor, the clarification says the buyer accounting under reverse charge "should use the UAE Central Bank exchange rate applicable on the date of supply", and that where a foreign supplier issues something that is not a UAE tax invoice "It is acceptable to use the date of the invoice as the date of supply".

Saudi Arabia is Article 61 of the VAT Implementing Regulations, headed Currency Conversion, and it is not limited to invoices: "Where any relevant amount to which these Regulations apply is expressed in a currency other than riyal, the amount must be converted to riyal using the daily rate prescribed by the Saudi Central Bank on the date that the relevant Tax becomes due in accordance with the Agreement and the Law". Note the trigger is the tax due date, not the date of supply. The English is the authority's own, is labelled an unofficial translation whose Arabic version supersedes, and is an earlier edition than the current Arabic; the current Arabic still names the regulator by its former name, the Saudi Arabian Monetary Agency. Article 53(5) separately requires a tax invoice to carry its details in Arabic and to show "the amount of Tax payable, shown in SAR", and that is the only amount Saudi Arabia requires in riyals.

Oman uses an average rather than a rate, and here the Tax Authority publishes its own English text. Article 68 of the VAT Law reads: "The Tax Invoice is to be issued in Omani Rials or any other currency. In case it is issued in a foreign currency, the Tax value is to be calculated in Omani Rial per the average purchase and sale price of the currency published by the Central Bank of Oman at the Tax due date." Article 69 adds that "The Taxable Person cannot maintain any accounting records or books in a foreign currency expect after receiving written approval from the Authority", the misspelling being the Authority's own. That English is the Tax Authority's, and it states that where the English and Arabic differ the Arabic prevails.

Bahrain is Article 40 of Decree-Law No. 48 of 2018. The Ministry of Finance's bilingual text reads in English: "The amount of the Tax Invoice must be converted to Bahraini Dinars if the Supply was made in another currency, and the conversion should be based on the exchange rate approved by the Central Bank of Bahrain." The Arabic column adds the words on the date of supply, which the English omits, and the Arabic prevails. Article 52 of the Executive Regulations then requires the value of the supply, the unit price exclusive of tax and the total amount due inclusive of tax all in dinars, plus the exchange rate applied.

Five pegs and one basket

Five of the six Gulf currencies are fixed to the US dollar, and in three cases the practice is older than the formal arrangement. The Saudi riyal at 3.75, with the formal dollar peg dating only from January 2003: the Fund's 2016 Article IV report records that the riyal was officially pegged to the SDR before then, "even though in practice it has been pegged to the U.S. dollar since 1986, with a middle rate of SAR 3.7450=$1". The UAE dirham at a mid point between the official buying and selling rates of 3.6725, which the Fund says "has been AED 3.6725 = $1 since November 1997", though the de jure dollar peg dates only from February 2002 because before that the dirham was formally pegged to the SDR. The Qatari riyal at 3.64, which the Fund records as pegged at that rate "since July 2001, following an unofficial peg since June 1980". The Bahraini dinar at 0.376, which the Central Bank of Bahrain's own monetary policy page says "has been effectively unchanged since 1980". The Omani rial, which the Fund quotes the other way round at "RO 1 = $2.6008", with the central bank maintaining fixed buying and selling rates.

Kuwait is the one that is different, and it is different by design. The Central Bank of Kuwait's exchange rate policy page states: "Effective 20 May 2007 by virtue of the Decree No. 147/2007, the KD exchange rate was repegged to an undisclosed weighted basket of international currencies of Kuwait's major trade and financial partner countries." The Fund's February 2026 Article IV report puts it precisely: "Kuwait's de facto exchange rate arrangement is classified as other managed. Since May 2007, Kuwait's de jure exchange rate arrangement has been a conventional peg against an undisclosed currency basket."

The cleanest way to see what that means is a single published table from the one Gulf central bank whose currency is not dollar pegged. On 28 October 2026 the Central Bank of Kuwait's foreign currency page listed, against the dinar, a daily percentage change of 0.06 for the US dollar and 0.06 for each of the Saudi riyal, the Emirati dirham, the Qatari riyal, the Bahraini dinar and the Omani rial, while the euro moved minus 0.39, sterling minus 0.29, the yen minus 0.16 and the Swiss franc minus 0.22. The 0.06 is not a coincidence between six currencies: it is the dinar's move against the dollar, and on that day every dollar pegged currency in the table printed it, the Bahamian dollar included. The same table also reproduces all five pegs arithmetically: dividing the dollar's 308.350 fils by each Gulf rate returns SAR 3.74998, AED 3.67302, QAR 3.63998, BHD 0.37608 and one Omani rial to 2.60078 dollars.

So for a euro price list sold into Saudi Arabia, the UAE, Qatar, Bahrain and Oman, there is effectively no local currency risk to manage. The customer's currency is a fixed multiple of the dollar. What moves is your price as that customer experiences it, because their budget is dollar referenced and your number is not, and so are the numbers of any dollar pricing competitor you are set against. That is a competitiveness and renegotiation exposure rather than a treasury position: if you invoice in euro and are paid in euro you carry no transactional currency risk at all, the buyer carries the conversion, and what you carry is the risk that a euro strengthening quietly prices you out of a renewal. Decide which of those two you are actually managing before you hedge anything.

Kuwait is the exception again, and the honest version of it is narrower than the usual one. Kuwaiti dinar forwards exist, so the exposure is not unhedgeable. It is unmodellable: the basket weights are undisclosed, so you cannot replicate the reference rate or decompose the exposure, and a dollar hedge will not neutralise it the way it does for the other five. On the evidence of that same table the basket behaves in a dollar dominated way, which is why the Fund classifies the de facto regime as other managed while the de jure peg is to the basket. The residual is small and irreducible rather than large and alarming.

One correction to the obvious conclusion. The rate you must use on the invoice is not the peg cross and not your bank's rate. It is the rate the relevant central bank published on the relevant date, under the four different definitions set out above. That, not the peg, is the number that will not reconcile.

What you may not do with your partner's price

Appoint a Gulf reseller and the instinct is to control the resale price, or at least to set a floor. The published rules make that the riskiest pricing decision in this article, and the risk is not where most vendors expect.

Saudi Arabia starts broad. Article 5 of the Competition Law, Royal Decree M/75, prohibits practices that prejudice competition "particularly the following: 1. Determining or proposing prices of goods, fees of service, and terms of sale or purchase, and the like." It does not say between competitors, and an entity is "Any natural or legal person engaged in an economic activity", so a supplier and its distributor are within the words. But the Implementing Regulations issued by Board Resolution No. 337 of 1441H narrow the automatic case considerably. Article 8(1) prohibits such agreements "if the purpose or effect of which is to undermine competition", while Article 8(2) makes practices a violation in themselves only "among competing - or potentially competing - firms". A foreign vendor and its Saudi reseller are not competitors, so a resale price clause between them is judged on purpose or effect rather than condemned outright. Resale pricing is named explicitly only at Article 6(2) of the Law, as an abuse of a dominant position, and dominance under Article 10 of the Regulations means a market share of forty percent or more, or the ability to influence the market. Even against a dominant vendor it is not automatic: Article 9(2) of the Regulations makes only two dominance abuses violations in themselves, refusal to deal and tying, and resale price maintenance is not among them.

The law reaches a Polish company with no Saudi presence. Article 3(1) of the Law applies it to "practices taking place outside the Kingdom which have an adverse effect on fair competition within the Kingdom", and the Regulations add that the authority may assess the impact "whether the impact is existent or potential". There is no turnover filter and no presence filter. Penalties under Article 19 run to ten percent of the annual sales that are the subject of the violation, or ten million riyals where sales cannot be estimated, or up to three times the gains, with publication at the violator's expense.

The UAE is where the real exposure sits, and it is not the dominance article. Article 5(1)(a) of Federal Decree-Law No. 36 of 2023 catches price setting only where it is "contrary to the market price, in a manner that negatively affects competition", which is a double qualifier and no automatic prohibition. Article 6(1)(a) names "directly or indirectly imposing prices or conditions of reselling of goods or services" as an abuse of dominance, and Cabinet Decision No. 3 of 2025 puts dominance where a market share exceeds forty percent "of the total transactions in the Relevant Market". But Article 7 prohibits the identical conduct with no dominance requirement at all, as an abuse of economic dependence, "in which a costumer has no alternative solutions for marketing or supply", the spelling being the statute's own. A reseller whose business is built on one vendor's product is the paradigm case, and the vendor's own size is irrelevant. Article 3 applies the law to "the exploitation of intellectual property rights inside and outside the State", with no effects qualifier attached to that limb, and to economic activity outside the State affecting UAE competition.

There is also no small company safe harbour in the UAE any more. Cabinet Decision No. 3 of 2025 contains only the dominance and merger thresholds, and its Article 5 repeals Cabinet Decision No. 13 of 2016, the instrument that commentary credits with exempting small undertakings below a combined market share. Nothing in the 2025 decision carries that forward. The Executive Regulations issued by Cabinet Decision No. 59 of 2026 contain no resale price provision, no vertical block exemption and no threshold either; the Ministry publishes them in Arabic only, and that reading is of the Arabic original, in which the only market share reference runs the other way, allowing dominance to be found on an ability to influence even where the forty percent is not exceeded. Only two category exemptions have been issued, one a twelve month block exemption for exclusive dealing in food promotion and delivery through digital platforms and one a two month emergency measure for essential goods, and neither touches software distribution. The routes left are an individual exemption, on which silence counts as rejection, or nothing. Penalties under Article 24 are a fine of "not less than (AED 100,000) one hundred thousand dirhams and not more than (10%) ten percent of the annual total sales realized by the violating undertaking in the State".

Bahrain has the most precise drafting in the region for this purpose, because Law No. 31 of 2018 defines "Price" to include "any cost, discount or margin-profit or any other element of a price". A clause forbidding your reseller from discounting, or dictating its margin, is a clause about price as a matter of statutory definition. Article 3 prohibits arrangements with the object or effect of hindering competition, including influencing selling prices, and Article 3(2) makes a prohibited arrangement "null and void", though it does so "Without prejudice to the rights of third party, acting in good faith", which is what stops a void clause unwinding your distributor's downstream sales. Article 9 names "Directly or indirectly imposing selling or purchase prices, or any other trade conditions" as an abuse of dominance, which catches a resale price clause without ever using the word resale, and Article 8 presumes dominance above a forty percent market share, with sixty percent for two or more undertakings acting together. Article 2 applies the law "even if one or more of the parties, is not established in the kingdom". Bahrain is also the one state with a small company route, because Article 5 lets the Authority exempt categories of arrangement including those "in which all parties are all small undertakings", though that requires the Authority to have issued the resolution.

Oman's prohibitions are in Royal Decree 67/2014, not in the 2018 decree that created its competition centre. Article 9 catches agreements made "either inside or outside the Sultanate of Oman" for the purpose of undermining competition, "particularly with regard to the following: A/ Pricing, discounts, sale or purchase terms and conditions or provisions of the services." Article 10(F) names "Pricing or directly or indirectly determining the conditions for the resale of the products" as a dominance abuse. Article 7 is the one that undercuts territorial price control from a different direction: any person may import a product licensed for trade in Oman for sale, distribution, marketing or promotion "regardless whether such imported product was previously monopolized", whether or not there is an exclusive agent.

Qatar places vertical distribution restraints inside its dominance article rather than its agreements article, and is the only Gulf instrument reviewed here that uses the phrase "vertical relationship", at Article 4(5) of Law No. 19 of 2006. Its agreements article, Article 3(1), prohibits "Manipulating the prices of the products being handled". There is no resale price provision and no extraterritoriality clause anywhere in the law. The penalty under Article 17 is a fine of "not less than 100,000 riyals and not more than 5,000,000 riyals", and the courts also "undertake to confiscate the profits resulting from the contravention". Kuwait has a competition law, Law No. 72 of 2020, which the research for this piece could not obtain in primary form, so no proposition about it is advanced here.

Finally, the UAE commercial agencies regime adds nothing helpful. Federal Decree-Law No. 3 of 2022 contains no provision about the price at which the agent sells; the word price does not appear in it, and nor do cost, margin or discount. Its wider effects are covered in whether you need a local entity to sell software in the UAE. What matters here is the shape of the carve out in the competition law: Article 5(2) of Federal Decree-Law No. 36 of 2023 is expressly "Subject to the provisions of Federal-Decree Law No. (3) of 2022 Regulating Commercial Agencies", and Article 5(2) is the market sharing and customer segmentation limb. The price setting limb is Article 5(1)(a), and the agency carve out is not attached to it. A registered commercial agency gives you territorial shelter and no price shelter at all.

Charging a Saudi customer more than a UAE customer for the same software, by contrast, is the thing vendors worry about and should worry about least. Every Gulf prohibition on differential pricing sits inside the abuse of dominance article: Article 6(4) in Saudi Arabia, Article 6(1)(c) in the UAE, Article 9 in Bahrain and Article 10(J) in Oman. Saudi Arabia and Oman both require the compared contracts to be "similar contracts" and the UAE requires "identical contracts", so different country enterprise deals with different scopes, support terms, currencies and payment terms are not the comparison those provisions describe. Bahrain is drafted the other way round and is the one to watch, because Article 9 catches dissimilar conditions "in any type of contracts and agreements concluded with consumers or suppliers of equivalent legal positions", putting the likeness test on the counterparty rather than on the contract. Qatar has no differential pricing provision at all: its nearest limb, Article 4(7), prohibits "Relinquishing the principle of equality of opportunity among competitors, differentiating some competitors from others in the conditions of sale or purchase agreements", which is about competitors and conditions rather than about what you charge two customers. Each law's relevant market is bounded by the state in any event, with Bahrain's definition the bluntest: the geographical scope means "the international geographical borders of the Kingdom of Bahrain". There is no Gulf wide single market rule comparable to European law. The one qualification is the UAE's Article 7(2), which applies the discrimination prohibition with no dominance requirement where a customer has no alternatives, and that bites on differential treatment between resellers who depend on you, not on what you charge end customers in different countries.

What this means in practice

Build the price in this order, and the Gulf stops being a guess.

Start with the published record, not with a benchmark report. If you are selling to Saudi government or government linked buyers, read the award results in your category before you quote. Search the visitor listing by product name, filter to the telecoms and information technology activity and to tenders whose award has been announced, and sort newest first; the listing will not page through the whole archive, so the search terms do the work. What you are looking for is not an average, it is three things: the dispersion, how often the cheapest bid loses on technical compliance, and whether renewals in your space attract one bidder or several. That last question is worth most, because a category where renewals draw a single bid is a category where incumbency rather than price is the whole game. No comparable per bidder source exists for the private sector or for the other five states, though Bahrain's Tender Board publishes monthly award values for the winner alone. For those markets, price from your own economics, and treat anyone offering you a Gulf benchmark with a sample you cannot inspect as offering you nothing.

Quote net of withholding and say so in the quotation. Assume the tax leaves your invoice in Saudi Arabia, Qatar and Oman, and that five percent is retained in Kuwait until you produce a clearance certificate. Ask for a gross up if you want, but price as though you will not get it, and know that in Qatar you are asking the customer to accept a non deductible cost and in Kuwaiti government contracts you may be asking for something the buyer is barred from giving. Build the recovery lag into working capital rather than into the headline number.

Decide which currency exposure you are actually running before you hedge. If you invoice in euro and are paid in euro, you have no transactional position and the customer bears the conversion: what you have is the risk that a stronger euro prices you out of a renewal against dollar referenced budgets and dollar priced competitors, which is handled in the commercial terms, with a review mechanic or a multi year price in the customer's reference currency, not by a treasury. If you invoice or accept payment in a Gulf currency, you are running euro against dollar in all five pegged markets and something unmodellable in Kuwait. Then handle the invoice separately from either: name the central bank rate and the trigger date your customer's jurisdiction requires, in the contract, so the reconciliation argument happens once at signature rather than every month. For the UAE that means the central bank's published VAT rate table at the date of supply, at the full published precision, which for the euro is six decimal places.

Put the tax treatment in the commercial terms rather than in the price. State that prices are exclusive of VAT and that the customer accounts for it under the reverse charge where the law so provides, and do not add a VAT line to an invoice for a jurisdiction where you are not registered, which in Bahrain can create a liability out of nothing. If you sell a single subscription to an unregistered Gulf buyer or a consumer, the registration cliff is immediate and there is no threshold, so decide deliberately whether your checkout accepts one.

Give your reseller a recommended price and a margin, never a floor and never a discounting ban. Set the price you charge the reseller, which is yours to set, and let the resale price be its own. If the relationship is one where the reseller genuinely has no alternative to your product, treat the UAE's economic dependence article as the binding constraint whatever your market share, and get local advice before any clause that touches the resale number. The extraterritorial reach is written into the Saudi, UAE, Bahraini and Omani statutes, and outside Bahrain's small undertakings route there is no de minimis to hide behind.

Last, price for the collection reality rather than the stated terms. A late payment percentage is unenforceable in Saudi Arabia and has to be priced in rather than drafted in, UAE delay interest runs from maturity by operation of law so a UAE price can assume it, and invoicing a Bahraini customer in euro rather than dinars removes the statutory cap on interest. Those mechanics, and the VAT you fund before you collect it, are set out in what happens if a Gulf customer does not pay. If you are bidding for Saudi public work, the local content apparatus is worth roughly ten percent of contract value in pricing headroom, which is explained in how Gulf enterprise procurement actually works.

If you want a second pair of eyes on a Gulf price before it goes into a proposal, get in touch.

Sources

This article is general information about published rules and is not legal, tax or financial advice. Gulf tax, competition and VAT rules change frequently and several of the instruments quoted here are unofficial translations whose Arabic originals prevail. Figures, rates and statutory references are current as at 28 October 2026. Take professional advice on your own facts before pricing or contracting.