Priced on your operation, not on a slide.
Wholara is scoped to the catalogue you carry, the locations you ship from and the order volume you process. We do not publish invented list prices for a product we have not yet fitted to your business — instead, here is exactly what drives the number and what every plan includes.
Why we do not show a price table
Two distributors with identical revenue can have wildly different implementations. One runs a 4,000-SKU catalogue from a single warehouse with one order channel; another runs 40,000 SKUs across six branches with EDI, a portal and a legacy ERP that needs a bespoke integration. Pricing the same for both would mean overcharging one of them.
So the process is deliberately short and specific: a scoping call, a written proposal with the assumptions stated, and a fixed implementation plan. No per-seat surprises, no charges for modules you will never switch on.
Three plans, one platform.
Every plan is the same product. What changes is scale, the depth of automation you enable, and the level of implementation and support you need.
For a single-location distributor replacing spreadsheet-led purchasing and manual order entry.
- Inventory, purchasing, pricing, orders and fulfillment modules
- Replenishment suggestions with review and approval
- Order validation: price, stock and credit checks at entry
- Standard integrations and scheduled imports
- Role-based access and full audit trail
- Onboarding and configuration for one location
- Business-hours support
Most often chosen by distributors under roughly 10,000 SKUs shipping from one site.
For multi-location distributors who want the agent acting on routine work, not just recommending it.
- Everything in Core, plus:
- Commit-within-limits automation and approval thresholds
- Multi-location stock, transfers and allocation rules
- Contract pricing, margin floors and freight recovery
- Supplier scorecards and rebate tracking
- EDI, e-commerce and accounting integrations
- Named implementation lead and quarterly review
Most often chosen by distributors running two to ten locations with mixed order channels.
For larger networks with bespoke integration, security review and contractual requirements.
- Everything in Growth, plus:
- Complex or bespoke integrations and data engineering
- Single-tenant or region-specific hosting options
- Single sign-on (SAML or OIDC) and advanced access controls
- Security review, data processing terms and custom retention
- Agreed service levels and escalation path
- Sandbox, staging and controlled release process
For distributors above roughly twenty locations, or with unusual regulatory or contractual constraints.
No published prices, no hidden ones either. Every proposal states the licence basis, what is included, what is metered (if anything), the implementation fee and the assumptions behind the scope. If your volumes move outside those assumptions later, we tell you before anything changes — not on the next invoice.
What actually drives the number.
If you understand these six variables, you can predict your own proposal before we send it.
Catalogue depth and complexity
Number of active SKUs, variants, kits and supersessions. Deeper catalogues need more data work at onboarding and carry more decisions to manage day to day.
Locations and stocking points
Warehouses, branches, will-call counters and van stock. Multi-location adds transfers, allocation rules and branch-level policy — the features that make the network behave like one business.
Order volume and channel mix
Lines processed per month, and whether they arrive by EDI, e-commerce, email or phone. Channel mix affects integration effort more than raw volume does.
Integration surface
How many systems we connect to, and how modern they are. One platform with an API is straightforward; three legacy systems exchanging files need more engineering on both sides.
Automation depth
How much the agent is authorised to do without a review — and how custom your rules are. Observe-only starts lower; commit-within-limits across many workflows requires more configuration and governance.
Implementation and support level
Self-guided vs. led rollout, number of branches to train, and whether you need named support, guaranteed response times or a scheduled review cadence.
Capability by plan.
Capabilities rather than feature counts. A tick means the workflow is available and configured for your operation.
| Capability | Core | Growth | Enterprise |
|---|---|---|---|
| Platform modules | |||
| Inventory, purchasing, pricing, orders, fulfillment | Included | Included | Included |
| Suppliers, customers and reporting | Included | Included | Included |
| Multi-location stock and transfers | — | Included | Included |
| Contract pricing and margin floors | Matrix pricing | Full | Full |
| Batch, serial and expiry tracking | Optional | Included | Included |
| Automation | |||
| Replenishment recommendations | Included | Included | Included |
| Commit within approved limits | — | Included | Included |
| Exception workflows and escalations | Core set | Full | Full |
| Custom approval chains | — | Standard | Bespoke |
| Observe-only mode | Included | Included | Included |
| Integration and data | |||
| Scheduled file import and export | Included | Included | Included |
| Managed ERP and accounting connectors | Standard set | Extended | Extended + bespoke |
| EDI document handling | — | Included | Included |
| E-commerce and portal feeds | One channel | Multiple | Multiple |
| REST API and webhooks | Included | Included | Included |
| Sandbox environment | Included | Included | Included + staging |
| Governance and security | |||
| Role-based access control | Included | Included | Advanced |
| Audit trail and change history | Included | Included | Extended retention |
| Multi-factor authentication | Included | Included | Included |
| Single sign-on (SAML / OIDC) | — | — | Included |
| Single-tenant or regional hosting | — | — | Available |
| Service | |||
| Onboarding and configuration | Guided | Led | Programme |
| Training | Remote sessions | Role-based, per site | Onsite option |
| Support | Business hours | Extended hours | Agreed service levels |
| Review cadence | On request | Quarterly | Agreed schedule |
Where a capability is marked as an option or a range, the exact position is confirmed in your proposal rather than assumed from this table.
Included in every plan, without exception.
These are not upsells. They are the conditions for the product to be worth using at all.
Your data, exported
Full export of your operational records on request and at the end of a contract, in documented formats. No exit fee, no hostage data.
Unlimited users, by role
Wholara is not priced per seat. Warehouse staff, counter staff and occasional users all get appropriate access without a headcount tax.
The audit trail
Every price change, approval, override and agent action recorded with user, timestamp and before-and-after values.
Configuration you control
Operational rules — targets, thresholds, floors and substitution policy — editable by your team without a change request.
Sandbox environment
A mirrored environment for testing rules, integrations and training before anything reaches live data.
Product updates
Continuous improvement without a version upgrade project. Changes are communicated before they affect your workflows.
Documented integration logs
Sync runs with record counts, conflicts and rejections — so "did it post?" is a lookup, not an investigation.
A named contact
Someone who knows your configuration and your business, rather than a rotating queue. Introduced at kick-off and present at every review.
How to decide, and how to build the case.
A distribution software decision usually needs two things: an operational case and a financial one. These are the inputs for both.
Numbers to gather before you talk to us
You probably have most of these already. They are also the measures we will review against later, so collecting them now makes the decision easier and the outcome provable.
Stock value at cost, split by age band
The working capital you are trying to release, and how much of it is already stale.
Service level by category
Where you are losing orders, and what a point of improvement is worth in revenue terms.
Gross margin by account
The accounts where margin is thinner than the invoice suggests.
Hours spent on order entry and purchasing admin
A simple estimate is enough: people, hours per week, fully loaded cost.
Emergency freight and expedited purchase spend
Often the fastest, most visible saving, and the easiest to prove.
Building the financial case
A credible case has three parts, and none of them requires optimistic assumptions:
1. Cash released from stock
Improving how stock is distributed between fast and slow movers frees working capital without lowering service. The value of that cash is your cost of capital, not a hypothetical saving.
2. Margin retained
Applying pricing rules consistently and catching below-floor lines converts directly into gross profit. Even a small number of corrected lines a month is measurable in the accounts you already keep.
3. Capacity without headcount
Hours removed from repetitive work are not automatically a cash saving — they are capacity. The financial case is usually about the growth you can absorb without adding staff, or the role you do not need to hire.
Ask us to model it with you. Bring these numbers to a scoping call and we will work through the arithmetic with your figures. If the case does not stand up, we will say so — a customer who bought on a weak case is worse for both of us than one who waited.
The questions that come up every time.
Direct answers, including the ones that do not favour us.
Because a starting price is a marketing device, not information. It tells you nothing about what your implementation would cost, and it usually excludes the things that matter — integration effort, data work, training and the number of locations.
The alternative is a scoping call and a written proposal. It takes less time than comparing three vendors' tiers and trying to work out which one is comparable.
No. Per-seat pricing penalises exactly the behaviour you want — warehouse staff, counter staff and managers all having access to the information they need. Plans are scoped on catalogue, locations, order volume and integration surface instead.
Implementation is a separate, fixed-scope fee stated in your proposal, covering data work, configuration, integration, training and the parallel run. It is not optional for a first workflow, because an unconfigured system does not produce reliable recommendations.
Additional workflows added later may need little or no further implementation fee, depending on how much new configuration and integration they require. That is stated per phase rather than bundled into a vague services number.
Your proposal states the assumptions behind the scope — catalogue size, locations, order volume and channels. If you grow beyond them, we will tell you what changes and why, in advance, with the option to stay where you are while you decide. There are no automatic overage charges.
Yes, and it is how most rollouts work. Starting with one workflow reduces risk for both sides: your team learns the platform on a process they already understand, and the value is proven against a baseline before you commit to the next phase.
Rolling monthly terms are available, and annual agreements are the common choice because they align with an implementation programme. Enterprise terms — including service levels, retention, data processing and exit provisions — are agreed in writing during procurement.
The parallel-run stage exists precisely so that you find out before cutover rather than after. If the first workflow does not deliver, you have not committed to the rest, your data exports cleanly, and we will tell you what we think went wrong.
We would rather end a rollout honestly at phase one than sell three more phases that will not land.
What your proposal contains
- Plan recommendation and the reasoning behind it
- Scope assumptions: SKUs, locations, order lines, channels
- Integrations included and any bespoke work quoted separately
- Implementation phases with deliverables per phase
- Licence basis and term options
- What is metered, if anything, and the thresholds
- Support level and response expectations
- Exit and data export terms
Get a number you can take to your board.
One scoping call, one written proposal, assumptions stated. No obligation and no follow-up sequence.
wholara.net