Find answers, support paths, and rollout guidance fast
Search the same approved public knowledge source used by AwraIQ. Results stay grounded in published AWRA resources, so buyers, customers, and support teams work from one source of truth.
Product helpImplementationSecurity reviewsBilling & support
An operations layer for Saudi distributors and contractors: stock across Riyadh, Jeddah and Dammam, procurement with approvals that block, landed cost on the consignment, plant and tools under named custody, and project cost attribution — designed to sit alongside your ZATCA e-invoicing provider rather than pretend to replace it. No Fatoora integration, no Arabic interface, no Mudad or GOSI: all stated up front.
These Developer & Marketplace Policies (the "Developer Policies" govern your access to and use of the application programming interfaces, developer tools, documentation, and sandbox environments made available by AWRA OpsHub ("AWRA", "we", "us", or "our") (collectively, the "APIs" ), and the listing or distribution of any application or integration through the AWRA OpsHub Marketplace .
The Connectors directory is the single integration layer for AWRA OpsHub, with 30+ connectors across communication, payments, accounting, tax, storage, CRM, e-signature, identity/SSO, productivity and developer webhooks — most of them live today. Connections use secure OAuth or your own provider keys, encrypted credentials, and signed webhooks with retries and delivery monitoring.
Push alerts, approvals and operational events to where your team already works. Slack, Microsoft Teams, WhatsApp, Telegram and Discord are live for channel notifications, and SMS is live via Africa's Talking, Twilio or Infobip for order confirmations, OTPs, vendor comms and payment reminders. Per-module toggles control which events post to each channel.
Archive invoices, purchase orders, receipts, exported reports and vendor documents to cloud storage you control. Google Drive, Dropbox and OneDrive/SharePoint are live, filing documents into per-type folders automatically as they are generated, with a Sync-now backfill. Least-privilege access means AWRA only touches the files it creates.
Point AWRA at an HTTPS endpoint and every audit event your organization records is sent there in sequence: as signed JSON, to a Splunk HTTP Event Collector, or to Datadog Logs. Each event carries its place in the hash chain, so your security team can see a missing or reordered entry from their own side.
Read items and stock, customers and invoices, vendors and purchase orders. Create and update items, customers and vendors. Raise stock adjustments and transfers, requisitions and purchase orders, invoices, payments and expenses, and decide approvals as a named person.
AWRA submits your customer invoices and POS sales to KRA's eTIMS system live over the OSCU API — under your own PIN, in sandbox or production. Every filed document comes back with a KRA receipt number, signature and QR code, printed right on it.
Sync vendors, items, purchase orders, customers, invoices and payments received with your books. QuickBooks Online is live — connect, disconnect and run syncs with accounts auto-mapped. Broader ERP and accounting bridges are scoped per rollout.
AWRA QuickBooks Sync Health gives finance and operations teams a clear way to monitor QBO readiness, required mappings, provider messages, retry queues, and exception resolution so external accounting sync does not become a mystery during close.
AWRA Procurement is the procurement module of AWRA OpsHub — run purchase requests, RFQs, quotations, approvals, purchase orders, receiving, budget checks, vendor collaboration, and integrations from one controlled buyer workflow.
AWRA API & Webhook Automation gives technical buyers a governed event layer for outbound webhooks, API access, signed payloads, retries, logs, idempotency, and integration observability across operational workflows.
AWRA Accounting Automation links procurement, inventory, POS, payments, journals, bank reconciliation, petty cash, depreciation, period close, reports, and QuickBooks sync into one controlled finance workflow.
We do not treat demos as generic product calls. Our AWRA demo is a guided walkthrough shaped around your operating model: inventory, procurement, sales/POS, finance, reporting, integrations, approvals, and rollout readiness.
AWRA OpsHub supports schools, NGOs, SMEs, retailers, warehouses, finance teams, and governance leaders with one disciplined operating layer for stock, spend, assets, approvals, reports, integrations, and field execution.
AWRA Integrations & Sync Hub centralizes connector management, sync operations, webhook governance, and integration health tracking so teams can trust cross-system data flow at scale.
Find payment, rollout, integration, audit, and advisory partners that help organizations implement AWRA OpsHub with less friction and stronger operating discipline.
Api Docs guidance for AWRA public page workflows, setup, troubleshooting, and support.
Page 7 of 10 · 224 articles
Still need a human answer?
For rollout planning, enterprise procurement, billing, security review, or customer support, share the context and we will route it to the right owner.
We use necessary cookies for secure sessions. With your permission, we also use cookies and browser storage for preferences, analytics, and demo engagement. Privacy Policy
AWRA OpsHub
Cookie settings
Cookie Consent Manager
Necessary cookies stay on for login, CSRF protection, and security. You can choose the optional categories below.
Overview
General Information
AWRA uses cookies and browser storage to keep public pages secure, remember selected preferences, measure website performance, and manage demo engagement prompts.
You can choose whether functional and marketing engagement storage apply. Analytics measurement is always active in this AWRA setup.
These settings apply to AWRA public website experiences such as the homepage, feature pages, pricing calculator, blog, help center, and request-demo page. Authenticated dashboard and vendor portal sessions still rely on required security cookies.
Required
Always active
Functional
Optional
Analytics
Always active
Marketing
Optional
For more context on privacy handling, open the Privacy Policy.
Required Cookies
Required Cookies
Always Active
Required cookies and storage support basic website delivery, secure sessions, request protection, and remembering the consent choice itself.
These cannot be switched off from this manager because disabling them would break login/session behavior, form protection, or the ability to remember the privacy choice you save.
Cookie details
Session security: keeps secure server sessions working while browsing AWRA.
CSRF protection: helps verify form submissions and protect requests.
Consent record: stores the preference decision so the banner does not keep asking after a choice is saved.
Examples: Laravel session cookies, CSRF tokens, and the AWRA consent preference record.
Duration: session security can expire with the browser/session; saved consent can last longer so the same browser remembers the choice.
Functional Cookies
Functional Cookies
Functional storage improves the public website experience by remembering interface choices, helper states, dismissed notices, and short-lived interaction preferences.
Turning this off does not stop secure required cookies or analytics. It only limits optional convenience memory.
If disabled, AWRA may show some helper prompts again or forget non-essential display choices. Core public pages, contact forms, and request-demo forms still work.
Cookie details
UI preferences: remembered display choices and helper states where available.
Dismissed notices: session-level or preference-level memory for notices the visitor has closed.
Frequency helpers: optional browser storage that prevents repeated prompts when allowed.
Examples: localStorage or sessionStorage values for dismissed banners, guide/helper states, and lightweight public-page preferences.
Effect when off: AWRA avoids optional convenience memory unless it is also allowed through marketing and engagement preferences.
Analytics Cookies
Analytics Cookies
Always Active
Analytics helps AWRA understand public page performance, traffic patterns, and content usefulness so we can improve the marketing website.
This category does not by itself enable demo popups, exit-intent prompts, or advertising pixels. Those are controlled by Marketing & engagement.
In this AWRA setup, Google Analytics and Google Tag Manager measurement are treated as mandatory website measurement and remain active.
Cookie details
Google Analytics / GTM: measures aggregate traffic and page activity.
Performance insight: helps identify which public pages, docs, and demo paths visitors use.
Operational signal: supports website quality decisions without enabling demo popups by itself.
Examples: Google measurement identifiers such as GA/GTM tags and related browser identifiers set by Google scripts.
Use: page views, source/referrer trends, public content performance, and product education page effectiveness.
Marketing & engagement
Marketing & engagement
Marketing and engagement storage supports demo prompts, exit-intent prompts, campaign attribution, and future advertising pixels.
When disabled, AWRA will not auto-open demo or exit-intent popups. CTA buttons can still open a form because that is a direct visitor action.
When enabled, AWRA can remember that a visitor already saw, dismissed, or submitted a demo prompt so the same popup is not repeated aggressively.
Cookie details
Demo prompt memory: tracks whether an auto prompt or exit prompt was recently dismissed.
Demo submission memory: avoids asking again after a visitor submits a demo request.
Campaign context: keeps source page, referrer, and UTM context available for demo requests.
Examples: popup frequency caps, demo-submitted flags, engagement source fields, and UTM/referrer context.
Effect when off: auto demo prompts and exit-intent prompts stay blocked; normal navigation and manually clicked CTA buttons still work.