Operations ERP Suite
The full ERP spine: orders, CRM, production, stock, purchasing, projects, finance, approvals, reporting, people and automation.
Next.js · TypeScript · PostgreSQL · Recharts
Explore
From $899
OverviewProcurement1 / 8
Business Operations
ProcurementLive
Vendor Hub
Most vendor problems are really visibility problems. Give the vendor a login and the chasing stops: they see the order, they acknowledge it, they invoice against it, and they keep their own paperwork current.
- From
- $629
- Function
- 27
- Roles
- 2
- Users
- Unlimited
Next.js · TypeScript · PostgreSQL · Auth.js
Inside the app
What it does out of the box
27 connected functions on one schema, spanning two sides of the same relationship. Everything below is in the template before a line of customisation.
Procurement dashboard
What needs a decision today, what is committed, and a twelve-week payables outlook. The Friday run is the only one you can still change.
Vendors
Filtered by status and category, with year-to-date spend, your risk rating and whether the compliance file is complete enough to raise an order.
Purchase orders
Raised, acknowledged, in production, delivered, late. Unacknowledged is the earliest warning you get that a date is not going to hold.
Invoices and matching
Three-way, two-way or mismatched, stated plainly. Nothing is approved quietly because the numbers were close enough.
Payment runs
The run, what is in it, what is held and what settled. The money moves through your own banking; this records what was scheduled and what happened.
Documents
Contracts, insurance, tax and certifications per vendor. A lapsed blocking document stops the next order issuing, which is the point of holding it.
Messages
Conversations attached to the vendor and, where it matters, to the order. A decision agreed by email that nobody can find later is what this replaces.
Settings
Approval thresholds, which documents block and which only warn, integrations and the reminder ladder. Ours are a starting point, not a recommendation.
Vendor home
The supplier opens on their onboarding progress, their next payment and their open orders. Four of six complete, and the two outstanding ones are named.
Vendor orders
They acknowledge the date or they say now that it will not hold, rather than on the delivery date.
Vendor invoices
Submitted against a purchase order and matched the same day. A rejected invoice says which line disagreed instead of just failing.
Vendor documents and payments
They see what is expiring before you have to chase it, and they can hold you to your own payment terms.
Permissions
Two sides, one build
A vendor portal only works if the vendor uses it, so the supplier side is a real application rather than a read-only page. Both sides run on one schema, and the rules are enforced on the server rather than by hiding buttons.
Procurement20 functions
The buying side, end to end
- Vendors with spend, risk and compliance state
- Purchase orders, including who has not acknowledged
- Invoice queue with the match result stated plainly
- Payment runs, held items and settlement history
- Thresholds, blocking documents and reminder rules
Vendor7 functions
The supplier side, on their own login
- Onboarding progress, with the outstanding items named
- Orders to acknowledge, and orders in production
- Invoices submitted against a purchase order
- Documents, with expiry flagged before it lapses
- Payments due, paid, and how quickly you actually pay
The build
Every function in the box
27 functions, all of them live in the preview. Nothing on this list is a mockup or a roadmap item.
Access
- Sign in
Procurement
- Dashboard
- Vendors
- Purchase orders
- Invoices
Records
- Documents
- Payments
- Messages
- Settings
Vendor side
- Home
- Your orders
- Your invoices
- Your documents
- Your payments
- Messages
- Company profile
What you get
Delivered as a repository, not a login.
Finance and operations teams whose purchasing runs on email approvals and a shared drive.
- 15 production functions spanning the buying side and the vendor side
- Full source code and PostgreSQL schema in your repository
- Role-based access control, enforced server-side
- Immutable audit log written on every change
- Responsive layouts, usable on a phone, not just resized
- CSV import and export on every core record
- Deployment configuration for your cloud account
- Twelve months of updates, and no per-seat charge ever
Access and evidence
Built to survive an audit
Giving an outside company a login is the part that needs care. What a vendor can see, what they can change and what blocks an order are structural here, not a checklist someone signs at year end.
- Row-level permissions, enforced server-side on every query
- A vendor sees their own orders, invoices and documents and nothing else
- Vendors with an expired blocking document cannot receive a new order
- Match result recorded per invoice, not inferred at approval time
- Bank detail changes retained in history rather than overwritten
- Messages attached to the vendor and to the order they concern
- Immutable audit log with seven-year retention and export
Related
Apps that pair with this one
Inventory Control
Catalogue, stock, warehouses, purchase orders, suppliers, sales, cycle counts and valuation, on one append-only movement ledger.
Next.js · TypeScript · PostgreSQL · Tailwind
Explore
From $649
Order Management
A full order management system: orders, customers, catalogue, stock, warehouses, shipping, returns, automation rules and integrations.
Next.js · TypeScript · PostgreSQL · Tailwind
Explore
From $699
Questions
Vendor Hub, in practical terms
Do I get the source code for Vendor Hub?
Yes. The repository, application code, database schema, migrations, seed data and deployment configuration, is transferred to your organisation on delivery. There is no licence key and nothing that calls home.
How many people can use it?
As many as you like, on both sides. Pricing is per application, not per user, so every buyer and every vendor you work with can have an account at no extra cost.
How are approval thresholds configured?
In settings, by the procurement side, without a developer. A threshold pairs a value band with the person who clears it, and the same screen decides which documents block an order and which only warn. Changes apply to new orders, so anything in flight keeps the rules it started under.
What can a vendor see?
Their own record and nothing else. A vendor signs in to the orders raised to them, the invoices they submitted, their own documents and their own payments. They cannot see other vendors, your category spend, or what you pay anyone else. Bank detail changes are kept in history rather than overwritten.
Can Vendor Hub be changed to match our process?
That is the usual route. A fitted build adjusts categories, thresholds, which documents block an order, the vendor onboarding steps, branding and up to two integrations, and typically takes one to three weeks from a signed scope.
What does it cost to run?
Hosting only, paid to your own cloud provider, roughly $50 to $200 a month depending on order volume and document storage. There is no recurring fee to us unless you choose managed hosting.
Want Vendor Hub shaped around your process?
A fitted build adjusts fields, stages, roles and integrations to how your team already works. One scoping call, a fixed price, one to three weeks.
