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
Stock control — item master and locations, counts and adjustments, transfers and approvals, traceability and quality holds, replenishment, and warehouse operations.
Every morning AWRA emails and posts a bell notice about assets due back within your reminder lead time (three days by default) or already overdue: admins get the full list and each custodian with an email or a login gets their own items. Warranties ending within the warranty lead time (thirty days by default) are sent to admins. Both can be switched on or off per channel in Notification Preferences.
The gap between recording stock and being told what to buy, when, and from whom is the difference between digital and intelligent. What smart inventory and intelligent procurement mean in 2026 — and how to choose a system that delivers both for a Kenyan operation.
Our ABC report bands the catalogue on cumulative consumption value, which is the correct definition and not the common one. Our counting module can hold a class against a plan. Nothing carries the first into the second, so at catalogue scale the classification is never refreshed.
You type a minimum you are never willing to go below. Whether a nightly job may write over it is a question about who decides; here a typed figure is kept, till sales count as usage, and each warehouse can hold its own level. What a par level is, and where it should live.
Aggregating cocoa, sesame, cashew or grain means buying from hundreds of smallholders in cash, in the field, on weight and grade — then proving every kilogram to a buyer or a lender. The records that make that provable and financeable.
Serial-number tracking for stock has a table, a model, three screens, two routes and a count on the dashboard. It has no code path that can create a row. The screens work perfectly and will always be empty — and the test that would have found it takes ninety seconds.
A vendor-honest guide to choosing operations software in Ethiopia — what an ERP must do for an Addis-and-regions business, how forex and multi-currency reorder the checklist, what to budget, and the straight answer on VAT and e-invoicing.
Cocoa runs on one of the most structured supply chains in African agriculture — and everything around it does not. What operational records both ends of that spectrum need, and where a general operations system honestly stops.
Every item carries a unit of measure, and tonnes, kilograms and litres take a quantity to three decimals. The next piece is conversion — buying maize by the tonne and selling it by the bag as one item — and for a bulk business that is where the margin lives.
An asset is tracked as one identified record or as a quantity in buckets, and the choice is free until the first unit moves. The bucket turns out to be a six-part key, which is why a pool of four hundred can become eleven rows nobody asked for.
eTIMS on every receipt, shrinkage visibility, multi-branch control, and a straight answer on what happens when the line drops — what to demand from a retail system, with an evaluation checklist.
Every item has a type, Stock or Service. A service sits in the same catalogue, carries its own price and income account, is sold and bought like any other item, and never touches stock.
One reorder point per item treats a Nairobi depot and a Kisumu shop as the same building. Each warehouse can carry its own minimum and maximum, and the reorder screen fills each one to its own ceiling.
Advancing seed and fertiliser on credit grows farmers — and quietly loses money when it is tracked as neither stock nor debt. How to run check-off without the leak.
A free-text field with validation is not a smaller version of a coded one. Where a jurisdiction wants a value from a published list, the field either holds it or your document is not the document.
A stockout is a clinical event and expired stock is money in the disposal drum — batch tracking, FEFO, consumables par levels, and the weekly hour that runs it all.
Most stock counts produce a new number and throw away the evidence of how the old one went wrong. Blind, valued, placed and dated — miss any one and you get a correction instead of a reason.
The long chain — landed costs at the port, regional depots, in-transit as a location, van routes, and agent consignment — with the leak at every link named.
FIFO issues the oldest stock first; FEFO issues whatever expires soonest — they sound interchangeable and are not. Where FIFO quietly fails, and what FEFO requires.
How much to order at once — the EOQ equation, the two costs it balances, a worked example, and the tidy assumptions that make it lie in the real world.
The annual count finds a year of errors at once and explains none of them — how cycle counting works, ABC scheduling, blind counts, and replacing the shutdown weekend.
A register tells you a certificate expired last month. A control stops the order. Almost every organisation has the first and believes it has the second.
Page 1 of 9 · 209 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.