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
Read your own data programmatically — items, stock, customers, invoices, vendors, purchase orders — create or update items, customers and vendors, raise stock adjustments, transfers, requisitions, purchase orders, invoices, payments and expenses, and decide approvals — with an API key, from your own scripts, spreadsheets or systems.
Phase 1 asked you to generate a structured invoice. Phase 2 asked you to hand it over before you may issue it. That is not a bigger compliance task — it is a different architecture, and it means your system is no longer the record of its own invoice.
Each person chooses how they hear about the problems that matter to their job: stockouts, margin drops, stuck approvals, failed syncs and ageing receivables, by email, push or SMS. The workspace keeps the ceiling, and nobody is told about records they cannot open.
One page that tells an administrator what is unfinished, what is switched off and what has gone stale, a template that fills the gaps in a new workspace without overwriting anything, and bulk user changes that carry a reason and one audit batch.
One page for the health of every connection: failures, retries and dead letters, a named owner and runbook for each connector, replays that a second person approves, warnings before a sync goes wrong, and a sandbox for checking your webhook receiver.
A till that sells and a stock system updated later will disagree by Friday. The warehouse behind each counter, the batch that leaves with the sale, and why the system should refuse a sale it cannot supply.
You choose which parts of the business forward events, so something has to decide which part each event came from. Where a notification carries a tag that is a fact; where it does not, it is a keyword search over the sentence.
Find practical guides for setup, inventory, procurement, sales, POS, finance, workflows, scanners, integrations, billing, troubleshooting, and support. Start with your role, the task you need to finish, or the problem you need to solve.
WhatsApp will not let a business send a message it has not read first. Every business-initiated notification uses wording approved by Meta in advance — which shapes everything about how the connector works.
Most APIs live at one address for everybody. Infobip gives each account its own hostname, which makes the base URL configuration rather than a constant — and turns a username field into a web address.
Suppliers acknowledge each purchase order with a delivery promise line by line, send shipment notices with their delivery note, and raise or answer disputes on the order’s own thread.
One screen for security events raised across your workspace — boundary violations, suspicious access and risky API calls — with a triage state per incident so nothing is looked at twice or not at all.
Choose which notifications your organization receives and on which channels — in-app, email, push, SMS, Slack, Teams, WhatsApp, Telegram, Discord or Google Chat — and how often reminders repeat.
Larger suppliers connect their own ERP or warehouse system: submit quotations, acknowledgements, shipment notices, invoices and price proposals over the API, and receive signed events by webhook.
Suppliers give each colleague only the access they need, see where their account is signed in, are alerted to new sign-ins, and choose which business emails they receive.
The address of your Salesforce org is not a constant. It is handed to you at connection, it can change on a renewal, and a connector that stopped listening will fail on a day nobody did anything.
Most integrations decide what makes two records the same and tell you afterwards. This one reads the answer out of your own table, which moves the decision somewhere you can see it.
Send every audit event to your SIEM as it happens — Splunk, Datadog or any HTTPS endpoint — with the hash-chain values that let it prove nothing was removed or changed on the way.
Use Finance and Reports to review the general ledger, chart of accounts, journals, payables, bank reconciliation, taxes, statements, month-end close and QBO sync.
File customer invoices and POS sales to KRA's eTIMS automatically as they are issued, and reverse them properly when a document is cancelled, credited or refunded.
Use this glossary to understand the common AWRA terms used across inventory, assets, procurement, sales, POS, finance, workflows, integrations, and support.
This Troubleshooting guide helps users diagnose common issues before opening a support ticket.
Page 6 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.