Customer, vendor and partner portals: let people outside the company help themselves

What a portal replaces

Most portals are built to stop the same five phone calls. Where is my order. Send me the invoice again. What is my outstanding balance. Has my payment been received. Which documents are still pending from me.

Each of those calls takes a staff member a few minutes and an interruption. A portal answers them from the same data your team looks at, and it gives the outside party a record they can check without asking. The same logic applies in the other direction: a supplier portal lets vendors see purchase orders, upload invoices and check payment status, which removes the follow-up emails from your accounts team.

WavX builds vendor, supplier, employee and customer portals as part of its custom software work. The three common kinds:

If the main job is placing repeat orders against a catalogue and price list, read the B2B ordering portal page. That is a portal with an ordering engine at its centre, and it is scoped differently.

Check what you already pay for

Several accounting and CRM products include a portal. Zoho Books, for example, documents a customer portal where customers can accept or decline quotes, view and pay invoices online, and generate a statement of accounts, and a separate vendor portal where suppliers can accept purchase orders, upload invoices for you to verify, and track payments. Those descriptions are from Zoho's help documentation, read on 2 October 2026.

If your data already lives in one such product, and its portal shows what your customers need, use it. It costs little or nothing extra and is maintained by someone else.

A custom portal is worth building when:

• The data is spread across systems. Orders in one place, dispatch in another, invoices in Tally, documents in email. The portal is where they finally meet.
• The rules are yours. A distributor sees prices that depend on volume, region and scheme; a contractor can only upload an invoice against an approved work order.
• Different people in one account need different access. The customer's purchase manager can place orders, their accounts person can only see invoices.
• The portal is part of the product. Customers judge you by it, so it carries your brand and works the way your service works.

Modules in a typical build

Payment collection uses a gateway such as Razorpay. Accounting sync for most Indian small and mid-sized businesses means Tally. Status messages often go out over the WhatsApp Business API.

Data protection is part of the scope

A portal is the most exposed thing most companies run: it is on the public internet, and its whole purpose is to show private records to outsiders. Two things follow.

First, the access rules have to be right. The classic portal fault is changing a number in the address bar and seeing another customer's invoice. WavX scopes every query to the logged-in account on the server, not in the browser, and tests that rule on every screen.

Second, Indian law now sets duties for personal data. The Digital Personal Data Protection Rules, 2025 were notified on 14 November 2025, with an eighteen-month period for phased compliance, according to the government's explainer. For a portal that holds individuals' data, the parts that shape the build are:

• a clear consent notice explaining what is collected and why;
• reasonable security safeguards, where the Act's highest penalty, up to ₹250 crore, applies to failing to maintain them;
• informing affected individuals without delay if there is a breach, in plain language;
• handling requests to access, correct or erase personal data, which must be answered within ninety days.

A portal is a natural place to let people see and correct their own details. This is general guidance, not legal advice; your lawyer should confirm what applies to your business.

What it costs: a planning range

Worked from the model behind the software cost estimator. These are planning ranges for budgeting, not quotes.

Assumptions: standard design and small scale (up to about 1,000 users). The model multiplies by 1.3 for a growing user base and by 1.25 for custom UI design. A companion mobile app adds ₹2,00,000 to the subtotal. The spread is 15% below to 25% above.

The figure that moves most between projects is the sync. A clean ERP with an API is straightforward; a Tally install on one office computer, or data kept partly in spreadsheets, takes longer. That is why the quote follows a look at your systems.

Timeline

The cost model puts subtotals under ₹6,00,000 in a 6 to 10 week band and larger ones in 10 to 16 weeks. A typical sequence:

1. Scoping (1 to 2 weeks). Who logs in, what each role sees, which system owns which data. Sample exports from each source.
2. Sync first. Build and test the connection to your systems of record before the screens, because every screen depends on it.
3. Core screens. Orders, documents, statement. Then payment and tickets.
4. Pilot. Ten or twenty friendly customers or vendors use it for two weeks. Their questions show what is unclear.
5. Roll-out. Invite the rest in batches, with a short message explaining what they can now do themselves.

The customer portal guide has a planning checklist for the first step.

When not to build one

• Your accounting or CRM product's portal already covers it. Use it.
• Fewer than a few dozen active accounts. A well-run email or WhatsApp routine may cost less than a portal's upkeep.
• Your own data is not reliable yet. A portal shows customers exactly what your system says. If balances are wrong internally, fix that first, or the portal will create more calls than it removes.

If the people who need the screens are your own staff rather than outsiders, the job is an internal tool or a dashboard, which costs less because the access rules are simpler.