Zoho Analytics Consultant, Saudi Arabia

Arabic-first dashboards and Hijri dates

In much of the Kingdom, the people who make the final decisions read most comfortably in Arabic. A dashboard designed in English and translated later usually shows it: labels truncated, charts reading in the wrong direction, numbers and names mixed awkwardly. I plan the Arabic version first and treat English as the second audience.

What I test in Zoho Analytics before committing to a design:

• Right-to-left behavior. How each chart type, table, filter and exported PDF handles Arabic text. Support can vary by component and by mobile app, so I check every view leadership will open.
• Source data. Branch, product and customer names appear in Arabic only if they were captured that way. Where they were not, we decide whether to translate master data in the source system.
• Terms. A short Arabic and English glossary approved by finance, so net sales or collections always use the same wording.

Calendars need thought too. Most financial reporting follows the Gregorian year, yet trading in retail, food and hospitality moves with Ramadan and the Eid holidays, which shift each Gregorian year. A date table that carries both calendars lets the owner compare this Ramadan with the last one rather than with the same Gregorian month. If any of your contracts, approvals or zakat discussions use Hijri periods, I confirm that with finance during discovery.

Blending accounting, POS and storefront data

Saudi businesses I meet rarely run a single system. Accounting may sit in Zoho Books, Odoo, ERPNext or a regional package. Each retail branch or café has a POS. Online sales come through storefront platforms such as Salla or Zid, or marketplaces such as Noon and Amazon, and B2B companies keep pipeline in a CRM.

For each source I establish three things:

1. How data leaves the system. A Zoho Analytics connector, an API, a database link or a scheduled file. Connector coverage changes, so I check what is currently available rather than assuming, and design a file route where nothing better exists.
2. Which figure is authoritative. Under ZATCA's e-invoicing rules, issued tax invoices are the formal sales record. POS and storefront totals are reconciled to them, not the other way around.
3. Who resolves differences. When a branch's POS total and its invoiced sales disagree, a named person investigates before the dashboard is published.

Storefront and marketplace payouts arrive net of commission, shipping charges, cash on delivery fees and returns. I separate those components so gross sales, fees and settlements can each be traced. This is the same discipline I apply in system integration work: agree the data contract before connecting anything.

Family groups, branches and the reports leadership requests

Many Saudi businesses are part of a family group: a holding company, several operating companies, branches in Riyadh, Jeddah and the Eastern Province, and sometimes affiliates elsewhere in the GCC. Owners want the group picture; banks reviewing facilities and partners in joint ventures want their own slices.

Requests I commonly design for, described generally:

• Sales, gross margin and collections by company, branch and city, against budget and the prior year.
• Receivables aging with government and semi-government customers shown separately, since their payment cycles often differ from private clients.
• Stock holding and slow-moving items for trading companies, which banks reviewing working capital lines tend to ask about.
• Project or contract profitability for contractors and service companies.

The riyal is pegged to the US dollar, but groups trading in euros, yuan or dirhams still need a rate table owned by finance. Intercompany sales, shared service charges and shareholder balances are tagged and removed from group totals. Every KPI is agreed with the finance manager before it appears, and statutory consolidation stays with your accountants. If group reporting keeps breaking because the ledgers themselves are inconsistent, my ERP consulting in Saudi Arabia addresses that root cause.

Snapchat, Google and storefront sales in one margin view

Saudi consumer brands often put a large share of their ad budget into Snapchat, TikTok, Instagram and Google, while B2B companies rely more on Google and LinkedIn. Each platform claims its own conversions, and none of them knows about returns, cash on delivery refusals or marketplace commission.

The reporting chain I build:

• Spend by campaign from each ad account, through a connector if your plan supports that platform, otherwise a scheduled import. Check current connector availability for Snapchat and TikTok in particular.
• Orders and leads from the storefront or CRM, with campaign parameters captured on every order.
• Settled sales after refusals, returns and fees, linked to the tax invoice.
• Product cost, so each channel is judged on contribution rather than order value.

Seasonality matters here. Comparing campaign performance across Ramadan, White Friday and summer periods without adjusting for the calendar leads to poor budget decisions, which is another reason the date design above comes first. This connects to my paid marketing work, where spend decisions are made from settled revenue.

Hosting, HR data and when Power BI or a warehouse fits better

Government-facing companies and regulated sectors in the Kingdom often ask whether data stays in the country. Zoho has been expanding regional hosting, but availability can differ by product and account, so confirm with Zoho where Zoho Analytics data would be held for you, and ask your legal advisor whether your sector or contracts impose a requirement.

Workforce reporting needs particular care. Leadership may want to track headcount by nationality against Saudization targets and labor cost by branch. That data is sensitive. I keep it in restricted workspaces with named access and aggregate it wherever individual detail is not needed.

Zoho Analytics is not always the right choice. I recommend alternatives when:

• The group runs on Microsoft or SAP. Larger organizations with Dynamics 365 or SAP and an internal team already skilled in Power BI should usually stay there.
• Volumes are large. Item-level POS data from many branches over several years, or many systems needing heavy transformation, may call for a warehouse with BI on top.
• Arabic requirements exceed what testing shows. If the Arabic output is not good enough for your board, I will say so.

I am independent of every vendor. For the broader platform picture, see my Zoho consultant page for Saudi Arabia or the Saudi Arabia overview.