Ask any purchase executive in an Indian SME factory to describe their morning and you will hear a version of the same thing. Three vendors have not replied to yesterday’s enquiry, so they get called. One vendor has sent a rate but on WhatsApp, so it gets copied into an Excel comparison sheet. A supplier wants to know whether last month’s invoice has been passed, so the call gets transferred to accounts, who ask for the invoice number, which the supplier does not have to hand. Somewhere in the middle of this, an actual purchase decision is supposed to happen.
None of this is anyone’s fault. It is what happens when the interface between two companies is a phone number. The information exists on both sides, but it lives in two different systems that only connect through a human retyping things. Every retyping is a chance for a rate to land in the wrong row.
A vendor portal is the standard fix, and it is no longer enterprise-only technology. But it is also frequently oversold, and a portal that suppliers refuse to log into is worse than no portal at all — you end up running email and a system nobody uses. This piece covers what a portal genuinely does, the parts that matter for Indian procurement specifically, and how to roll one out so it does not die in month two.
What a vendor portal actually is
Strictly, it is a second front door into your system. Your staff log into the ERP with full access to everything they are permitted to see. Your suppliers log into a separate, tightly-scoped area where the only records visible are the ones belonging to them: their RFQs, their purchase orders, their shipments, their invoices. A supplier can never see another supplier’s rates — which sounds obvious, but is exactly the property an emailed comparison sheet cannot guarantee once it has been forwarded twice.
The useful mental model is a bank’s net-banking site. The bank has a core system; you get a constrained window into your own records within it. Nobody thinks of net banking as “a website the bank built”. They think of it as the reason they stopped visiting the branch to check a balance. A vendor portal is aiming at the same outcome for the supplier phone call.
A vendor portal connects your suppliers to your system. A supplier marketplace or B2B network is a shared platform where buyers discover new sellers. They solve different problems. If your goal is finding new vendors, a portal will not help. If your goal is running the vendors you already have with less friction, a portal is the right tool and a marketplace is not.
The six jobs a portal takes off your team
When people evaluate portal software they tend to look at the feature list. It is more useful to look at which recurring human tasks disappear. There are six.
1. Supplier onboarding and KYC collection
Today onboarding a new vendor means emailing them a form, receiving a partially-filled scan, chasing the GST certificate, chasing the cancelled cheque, and then someone in accounts typing all of it into the vendor master. In a portal, you send an invitation, the supplier fills the form themselves, and the documents arrive attached to a registration request rather than scattered across an inbox.
The part that matters more than the form is the review workflow. A registration should not go straight into your vendor master. It should move through states — submitted, under review, revision requested, and finally approved or rejected — so that a half-complete registration can be sent back to the supplier with a note instead of being silently fixed by your team or, worse, approved with a wrong IFSC that surfaces when a payment bounces three weeks later.
Whether a supplier is MSME-registered, and under which category, changes your legal payment obligation under Section 43B(h) — the 45-day rule. Most factories discover a supplier’s MSME status at year end, when the disallowance is already baked in. Ask for the Udyam number and category on the registration form itself. See our explainer on the 45-day payment rule for why this is the single most expensive field on the whole form.
2. RFQ quoting
This is where the transcription errors live. The vendor enters their own quotation number, quotation date, validity date, rate and available quantity, plus their terms and conditions. Nobody on your side reads a PDF and types a number into a comparison sheet, which means nobody transposes 4,850 into 4,580.
One detail that separates portals built for manufacturing from generic ones: unit-of-measure conversion per vendor, per item. Your item master may carry a bracket in pieces while the supplier quotes and invoices in kilograms. If the portal validates the vendor’s entered quantity against a limit expressed in the item’s unit, the vendor’s perfectly correct kilogram figure gets rejected or capped at a nonsensical number, and you get a phone call — which is precisely the phone call the portal was supposed to eliminate. The conversion factor has to be stored against the vendor-item pair and applied before any quantity check.
3. Purchase order visibility and acknowledgement
Suppliers should be able to see their open orders without asking, including quantities already despatched against each line. The recurring failure this fixes is the partial-delivery argument: you believe 400 of 1,000 pieces are outstanding, the vendor believes 300, and neither of you can prove it because the deliveries were tracked on two separate sheets.
4. Rate contracts
If you buy repeat items, you almost certainly have negotiated annual rates — and they almost certainly live in a spreadsheet that one person maintains. Putting an annual rate contract (ARC) in the portal means both sides are looking at the same agreed rate per unit, minimum and maximum order quantities, and validity window.
Two things are worth insisting on here. First, price revisions should be a workflow, not an edit — a revised rate with an effective-from date, a reason, and an approval, so that a mid-year steel price change is a recorded event rather than an overwritten cell. Second, the contract should warn you before it lapses, both on approaching expiry and on approaching the estimated annual quantity. Rate contracts expiring unnoticed is how factories end up buying at spot rates for two months without realising.
5. Shipment and despatch entry
Let the supplier record what they have actually despatched, with the transport documents attached. When the material reaches your gate, your stores team is checking an expected consignment against an existing record rather than creating one from a delivery challan under time pressure while the truck waits.
6. Invoice submission and payment status
The vendor submits the invoice, and — the part that drives adoption more than anything else — the vendor can see which of their invoices have been paid, and against which payment. Not a vague status, but the actual payments allocated to a specific invoice.
It is worth being blunt about why this feature matters. Every other item on this list is something you want. Payment visibility is something the supplier wants. It is the reason they will log in at all. A portal that gives suppliers only work and no benefit gets used for a month and then abandoned.
Running procurement out of an inbox?
OEMup is a manufacturing ERP built for Indian SMEs, with a full vendor portal included — supplier registration and KYC review, RFQ quoting, purchase order and rate-contract visibility, vendor-entered shipments, invoice submission and payment status. Plus BOM, MRP, production planning, inventory, HRMS and GST in the same system.
Book a Demo →Email vs. portal, task by task
| Task | Email / WhatsApp today | With a vendor portal |
|---|---|---|
| Onboarding a new supplier | Form emailed, scans chased, data typed into vendor master by your staff | Supplier fills their own record; you review, request revisions, then approve |
| Collecting quotations | Replies in mixed formats; someone builds a comparison sheet by hand | Rates entered by the vendor into fixed fields; comparison is automatic |
| Purchase order acknowledgement | Thumbs-up emoji, no record | Acknowledgement recorded against the order, with a timestamp |
| Negotiated annual rates | Spreadsheet one person maintains; revisions overwrite history | Rate contract visible to both sides; revisions dated, reasoned, approved |
| Despatch information | Photo of the LR sent on WhatsApp | Shipment recorded by the vendor with documents attached |
| “Has my invoice been paid?” | Phone call to purchase, transferred to accounts | Supplier checks their own invoice and payment list |
| Audit trail | Reconstructed from an inbox, if at all | By-product of the workflow |
The India-specific parts most generic portals miss
A vendor portal designed for a US or European buyer will get several things wrong for an Indian factory. These are the ones worth checking on any demo.
Miss 1 — No MSME field
Without MSME registration status and category captured at onboarding, you cannot apply the 45-day payment rule correctly, and the exposure only becomes visible at year-end assessment.
Ask for: Udyam number and micro / small / medium category on the registration form, flowing into the vendor master.Miss 2 — GSTIN treated as a text field
If the portal accepts any string as a GSTIN, you will onboard duplicates of the same legal entity under three spellings of its name, and your purchase register will never reconcile against GST data.
Ask for: a duplicate check on GSTIN at registration, before the request reaches your review queue.Miss 3 — One unit of measure per item
Covered above, and worth repeating because it is the most common cause of a factory quietly abandoning portal quoting: vendors who trade in kilograms cannot quote against an item master that thinks in pieces.
Ask for: vendor-specific UoM with a conversion factor, applied to quantity validation.Miss 4 — Registration is all-or-nothing
A meaningful share of Indian SME suppliers will not create a login, especially for a one-off enquiry. If quoting requires registration, you lose those quotes and your comparison gets thinner.
Ask for: a public, tokenised link that lets a vendor respond to a single RFQ without an account — with registration offered, not forced.Miss 5 — No document re-request loop
KYC documents expire. GST certificates get amended, bank accounts change. Without a way to request a fresh document against an existing vendor, your KYC file is accurate only on the day the vendor was onboarded.
Ask for: the ability to raise a document request to an existing vendor and approve or reject what comes back.Give the vendor’s own staff different access
A supplier is a company, not a person. Their accounts clerk should be able to see invoices and payments; their despatch clerk should be able to record shipments; you may not want either to see negotiated rate contracts. A portal that issues one shared login per supplier company forces the supplier to hand the same credentials to everyone, which is how your rate contract ends up on a WhatsApp group.
Look for per-user permission switches on the vendor side — view purchase orders, view rate contracts, add shipments, manage the item catalogue, view invoices — so the supplier can delegate internally without over-sharing.
A five-step rollout that actually gets used
The failure mode for vendor portals is not technical. It is a portal that launches to 200 suppliers at once, gets 11 logins, and is quietly abandoned. Stage it instead.
Clean the vendor master first
Deduplicate, fix GSTINs, mark who is genuinely active. Most factories find that a third of their vendor master has not been transacted with in two years. A portal built on a dirty master multiplies the mess rather than fixing it, and this step is unglamorous enough that it gets skipped — which is exactly why it is step one.
Pilot with your top twenty suppliers
The twenty suppliers who account for most of your purchase value are also the ones with the most to gain and the most incentive to cooperate. Run full KYC on this group so the review workflow gets exercised on real documents before you scale it.
Switch on payment visibility first
Before RFQs, before shipments. It is the feature suppliers want, and it converts a portal from an obligation into something they check voluntarily. First logins are the whole battle.
Move quoting and orders across
Once suppliers are logging in of their own accord, shift RFQ responses and purchase order acknowledgement into the portal. Keep the public no-login link available for the suppliers who will never register — there will be some, and that is fine.
Set a date and retire the parallel process
Announce that from a fixed date, quotations are accepted only through the portal or its public link. Running both channels indefinitely is the single most reliable way to guarantee the portal stays empty, because your own team will keep taking the easier path.
When you do not need one
Worth saying plainly, because the honest answer is not always yes. If you buy from fewer than about ten suppliers, if each purchase is bespoke rather than repeat, or if your purchasing is concentrated in one or two long-standing relationships where a phone call genuinely is faster — a portal is overhead. The economics turn on supplier count multiplied by transaction frequency, not on your turnover.
The signal to watch for is a specific one: when a member of your team spends more time chasing suppliers for information than evaluating what the suppliers have sent, the chasing has become the job. That is the point at which a portal pays for itself, and it usually arrives somewhere north of thirty active suppliers.
The bottom line
A vendor portal is not really about giving suppliers software. It is about changing where the boundary between two companies sits — moving it from a phone number to a shared, structured record. The quotation your vendor types is the quotation your system compares. The invoice they submit is the invoice your accounts team sees. The payment you make is the payment they can verify without calling.
The factories that get value from this treat it as a procurement process change with a software component, not a software rollout. Clean the vendor master, pilot small, lead with the feature suppliers actually want, and set a date to stop accepting the old way.
If procurement is the area you are trying to fix, the companion read is Procurement Management for Indian Manufacturers: The Indent-to-Payment Flow, which covers the internal half of the same journey. For the payment-terms exposure a portal helps you track, see MSME 43B(h) and the 45-Day Payment Rule. And if you are weighing whether your current setup has run out of road, 5 Things Tally Cannot Do That a Manufacturing ERP Can is the operational case.
FAQ
What is a vendor portal?
A separate, password-protected login for your suppliers alongside your ERP. The supplier enters their own quotations, sees their own purchase orders and rate contracts, records shipments, submits invoices and checks payment status. Each supplier sees only their own records.
Is a vendor portal worth it for a small factory?
It depends on supplier count and repeat frequency rather than company size. Under about ten suppliers with bespoke orders, email is fine. Above roughly thirty active suppliers with repeat items and negotiated rates, the time your team spends chasing information usually exceeds the cost of the portal.
Will my vendors actually use it?
Some will not, and the design has to assume that. Adoption improves sharply when the portal offers something the supplier wants — payment visibility above all — and when there is a public no-login route for suppliers who refuse to register for a one-off enquiry.
Can different people at the same supplier have different access?
They should be able to. Look for per-user switches on the vendor side covering purchase orders, rate contracts, shipments, item catalogue and invoices, so a supplier’s despatch clerk is not automatically shown negotiated pricing.
How does a vendor portal handle KYC documents expiring?
Through a document request loop: you raise a request against an existing vendor for a specific document, the vendor uploads it through their login, and your team approves or rejects it with a reason. Without this, your KYC file is only accurate as of the onboarding date.
Does a vendor portal replace an ERP?
No. It is a front door onto one. The portal is only useful because the RFQ, purchase order, shipment and invoice records already exist in a system behind it — a standalone portal with no ERP behind it just moves the re-keying problem to a different screen.
Related reading
- Procurement Management for Indian Manufacturers: The Indent-to-Payment Flow — the internal half of the same journey
- MSME 43B(h) Explained: The 45-Day Payment Rule — why MSME status belongs on the registration form
- 5 Things Tally Cannot Do That a Manufacturing ERP Can
- OEMup vs Tally — side-by-side comparison
- All OEMup features