The Supplier List Has a Ceiling
How many suppliers you can keep active is governed by your plan, and switching one on when you are at the limit is refused outright. That is an ordinary commercial arrangement and an unusual thing to write a post about — which is exactly why it is worth writing before you meet it in the middle of a migration.
Most software limits are invisible until they are not. You load your data, you get to the last hundred rows, and a screen tells you something nobody mentioned during the evaluation.
Ours meters active suppliers. We would rather you read that here than find it on a Tuesday afternoon with a spreadsheet half loaded.
What is actually metered
The number of active vendors, not the number of vendor records. Switching a vendor from inactive to active is the moment capacity is consumed, and if you are already at your plan's limit the activation is refused with a message that says so and tells you the two ways forward: upgrade, or deactivate somebody else.
That distinction between records and active records is the useful part, and it is not accidental. A supplier you dealt with three years ago can stay in the system, with their history, their documents and every order you ever placed, without costing you a slot — as long as they are switched off.
History is free. Availability is what is metered. That is the right way round, and it is worth knowing which side of the line each of your suppliers belongs on.
Why this interacts with two other behaviours
Both of them deactivate suppliers, which means both of them quietly return capacity to you.
| What happens | Effect on the supplier | Effect on your capacity |
|---|---|---|
| You blacklist a supplier | Deactivated, with a reason and an actor recorded | A slot is returned |
| A qualification lapses | Deactivated automatically at six each morning | A slot is returned, silently |
| You remove a blacklist | Stays inactive until somebody activates them | No slot is consumed until then |
| You reactivate anybody | Available for quotation again | A slot is consumed, and may be refused |
The second row is the one to watch. A qualification expiring frees a slot without anybody deciding to free it — and when the supplier renews and somebody tries to switch them back on, the activation can be refused because the slot has since been used by somebody else. The refusal is clear, and it will arrive at an inconvenient moment.
Why a small-island supply base makes the arithmetic tighter
Not because there are more suppliers — because of the shape of the list.
A Barbadian business of any size tends to buy from a long tail of local suppliers for small, frequent, low-value things, and from a small set of overseas suppliers for the things that matter. The long tail is where the count lives, and it is precisely the part nobody curates, because each individual entry is too small to be worth an argument.
So the limit is reached by a hundred suppliers you buy from twice a year, and the one you need activated urgently is the one that is refused.
How to stay ahead of it
Four habits, all of which are good practice anyway
- Deactivate on a schedule, not on a crisis. Once a quarter, list suppliers with no order in eighteen months and switch them off. Their history stays. Reactivating one takes seconds and is a deliberate act, which is a better default than everybody being permanently available.
- Do the count before the migration, not during it. Take your supplier list, strip out the ones you have not used in two years, and load the rest as active with the remainder inactive. Loading everybody as active is the mistake that produces the refusal.
- Watch for the silent returns. Qualifications lapsing free slots without anybody noticing, so your headroom moves on its own. If you are close to the limit, that headroom is not stable.
- Treat the limit as a curation prompt. An unbounded supplier list is not a benefit. Most organisations discover, when forced to look, that a third of their active suppliers should not be.
Three questions to ask any vendor about their limits
What is metered on my plan, exactly?
A good answer sounds like
A named list — users, records, storage, transactions.
What it actually means
Ask before the migration. A limit found during a data load is a limit found at the worst possible moment.
Is it records, or active records?
A good answer sounds like
A precise answer.
What it actually means
The difference decides whether you can keep your history. Ours meters active vendors and keeps every record.
What happens at the limit — a refusal, a warning, or a charge?
A good answer sounds like
One of the three, plainly.
What it actually means
A silent overage charge is the worst of the three and the most common in this category.
Our position
Count your active suppliers before you migrate, not after. Load your long tail inactive and activate on demand — it takes seconds, it is a deliberate act, and it produces a supplier list that reflects who you actually buy from. Check the current limits against your plan on the pricing page rather than against any number quoted in an article, because those change and this page will not.
What AWRA OpsHub does today
- Active vendors metered against the plan, with activation refused at the limit and an explicit message naming both remedies.
- Inactive vendors retained in full — history, documents, orders, contacts — at no capacity cost.
- Blacklisting deactivating a vendor and returning the slot, with the reason and actor recorded.
- Automatic deactivation of a vendor whose qualification has lapsed, on a daily job.
- A refusal to reactivate a blacklisted vendor, checked before the capacity check.
What it does not do
- Any warning as you approach the limit. The refusal is the first notification you get.
- A view of how many slots you have used and how many remain.
- Automatic deactivation of dormant suppliers — the quarterly cull is yours to run.
- Any notification when a lapsed qualification returns a slot.
Not ours, by choice
- We are not publishing plan numbers here on purpose. Limits and prices change; an article does not. Check the pricing page.
- Metering activity rather than records is the right side of this trade and we would defend it — nobody should have to delete their purchasing history to fit a plan.
- Nothing here is Barbadian. It is what a long tail of small suppliers does to a metered list; a small-island supply base is where that tail is longest relative to the business.
What is not built for your market today can still be built for you
Anything described above as not built is a statement about what ships in the standard product today — not a limit on what AWRA OpsHub can do in your market. Kenya's eTIMS integration and its maintained payroll engine exist because Kenyan clients needed them and commissioned them; neither appeared by itself. The same door is open here. If tax on the purchase side, a rate that follows the class of supply, a bank or mobile money feed, a statutory return format, a rule your own operation needs that the standard one does not have, or a link to a system you already run is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.
The unit a rate is measured in, and the direction it travels
Two builds cover most of what this region exposes. A rate that follows the class of supply rather than only the jurisdiction, for markets where one tax has several rates and a country-keyed default is correct and useless at the same time. And tax recorded on the purchase side — a rate and an amount held out of cost, attributable to a supplier and a period — for businesses whose returns are claims rather than payments. Both are data-model changes rather than settings, and we would quote them as such.
Banks, payments and supplier obligations with dates on them
Statement feeds and local payment rails wired into the Payments Register, alongside supplier qualification that carries a per-supplier expiry and acts when it passes — the latter already runs, and reporting against a local content or preference regime is the buildable part on top of it.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
Payroll and statutory returns
A local payroll engine with income tax tables and social security contributions computed on live employee records, producing returns in the layout your authority expects rather than rebuilt each month.
Systems you already run
The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. No roadmap slide, and no pretending in a demo that something exists when it does not.
Tell us what you need integratedCount your active suppliers before you migrate
It takes twenty minutes and it is the difference between a clean data load and a Tuesday afternoon spent deactivating people. We will do it with you as part of any migration conversation.
Plan the migrationFrequently asked questions
Do I lose anything by deactivating a supplier?
No. The record stays, with every order, document and contact attached to it, and reporting on their history is unaffected. What changes is that they cannot be selected for a new quotation until somebody switches them back on.
What is the limit on my plan?
Check the pricing page rather than any figure quoted in an article — limits and prices change and a blog post does not. What is stable is the mechanism: active vendors are metered, records are not.
Can I be warned before I hit the limit?
Not today. The refusal at the point of activation is the first signal, which is why the quarterly cull is worth doing as a habit rather than as a reaction. If you are consistently near the limit, that is a conversation about your plan rather than about your process.
