How to Write a Software Agency RFP for a Customer Portal (Wholesale & ERP)

Most customer-portal RFP guides assume you are buying SaaS portal software. This one is for hiring a software agency to build (or extend) a portal on top of NetSuite, Microsoft Dynamics 365 Business Central, or a similar ERP—so your buyers can place orders, see price levels, credit holds, branch stock, and statements without calling the warehouse.

If you run a regional wholesale distributor, a multi-location operator, or an early-stage product team selling into that world, a vague RFP (“build us a portal”) produces vague bids. A tight RFP produces comparable fixed-scope proposals, fewer change orders, and a build that does not fight your ERP.

The SERP is full of generic software RFP templates and vendor capability checklists. Those help IT pick a platform. They rarely force agencies to answer the questions that decide whether a portal actually replaces phone and email orders: contract pricing, MOQ, backorders, and which roles live in the ERP versus the portal UI.

Below is a buyer-ready structure you can paste into a Google Doc or Notion page, send to two or three agencies, and score in one afternoon.

What Should a Software Agency RFP for a Customer Portal Include?

A software agency RFP for a customer portal should lock scope before code: business outcomes, ERP system of record (NetSuite / Business Central), must-have buyer workflows (orders, price lists, credit holds, statements), integrations, auth model, acceptance tests, timeline, and a fixed-price or capped bid format so vendors compete on the same SOW—not on vague “agile retainers.”

Start with five blocks. Everything else is optional.

Context (one page max) — Company type (wholesale distributor, multi-branch retailer, B2B SaaS with ERP behind it), regions (US / EU), approximate active buyers, and who owns the ERP admin seat.
System of record — NetSuite, Business Central, Salesforce + ERP, or “custom Postgres.” Name the objects that must stay authoritative (items, price levels, open A/R, inventory by location).
Portal jobs — The 5–8 actions a buyer must complete without calling your office. Example: place PO, see allocated stock by branch, download statement PDF, request RMA, view open invoices.
Non-goals — Explicitly exclude SuiteCommerce MyAccount rebuilds, full EDI replacement, mobile native apps in phase 1, or AI chat unless you truly need them.
Commercials — Fixed-scope preferred; ask for milestone payments, warranty window, and who hosts (your AWS / GCP account vs theirs).

Agencies that cannot answer those five blocks in the proposal are not ready for your project. Product studios that only ship greenfield SaaS MVPs often skip ERP edge cases; ERP implementers often under-spec the buyer UX. Your RFP should force both gaps into the open.

NetSuite customer portal template — where the template stops

How Is an Agency Portal RFP Different From a SaaS Customer Portal RFP?

A SaaS portal RFP scores vendor features and security questionnaires. An agency portal RFP scores a build plan: data contracts with the ERP, custom pricing rules, acceptance criteria per workflow, and a fixed deliverable list—because you are buying engineering hours and ownership of the code, not a monthly seat license.

Use this comparison when stakeholders paste a “customer portal software RFP” PDF into the thread:

Topic	SaaS portal RFP	Software agency RFP
Primary ask	Feature matrix + SLAs	SOW + architecture + fixed price
Pricing rules	Configure in admin UI	Document how contract / customer-specific prices sync from ERP
Inventory	Often one warehouse	Branch / location availability, allocations, backorders
Auth	Vendor IdP	Often SSO + ERP customer records + role mapping
Exit	Cancel subscription	Repo ownership, IaC (Terraform), runbooks
Success metric	Adoption seats	% of orders that leave phone/email

If your buying committee already printed an Ingeniux-style capability spreadsheet, keep the security and compliance rows. Replace “product roadmap” rows with integration contracts, test accounts, and UAT scripts.

Which Portal Requirements Belong in the RFP (and Which Stay in the ERP)?

Put buyer-facing workflows and presentation in the portal RFP; keep financial truth, inventory truth, and credit policy in NetSuite or Business Central. The RFP should list each field’s source of truth so agencies do not invent a second price list that drifts from the ERP overnight.

Must-have buyer workflows (phase 1)

Ask vendors to confirm or decline each line with effort notes:

Sign-in tied to existing customer / contact records
Browse or search catalog with customer-specific price levels
Place order with MOQ, case packs, and ship-to selection
See credit hold or available credit before submit
View branch stock or promised dates (not a fake “in stock” flag)
Download invoices / statements
Order status and partial shipments

Keep inside the ERP (call this out as non-scope for the agency UI)

General ledger and tax engines
Purchasing / MRP
Full warehouse put-away and pick/pack (unless you are scoping WMS)
Trading-partner EDI mandates (see below)

EDI vs a customer portal for wholesale distributors

Optional phase-2 lines (do not bury in phase 1)

Buyer mobile app (React Native / native)
RAG assistant over price lists and SOPs
Multi-language EU storefronts beyond your ERP’s language packs

Naming these as phase 2 keeps bids comparable. Mixing them into phase 1 is how “small portal” quotes turn into six-month retainers.

How Do You Structure Sections So Agencies Can Bid Fixed Scope?

Structure the RFP so each section maps to a billable milestone: discovery outputs, design, ERP integration spike, vertical slice (one happy-path order), UAT, and production cutover. Require a single fixed price (or a capped T&M with a hard stop) against that milestone list—not an open-ended “we’ll refine in sprints.”

Suggested section order (copy/paste):

1. Goals and success metrics

Example: “Within 60 days of launch, 40% of repeat wholesale POs originate in the portal; phone order entry for those buyers drops by half.”

2. Users and roles

Buyer admin, buyer purchaser, your CSR override, your sales rep read-only. Map each to ERP roles.

3. Functional requirements

Numbered user stories with acceptance criteria. One story = one test.

4. Integration requirements

API vs SuiteScript / middleware; rate limits; sandbox OCIDs or BC environments; webhook vs poll; failure and retry behavior.

5. Security and residency

US-only vs EU data residency; whether PII stays in your tenancy; SSO provider (Microsoft Entra ID, Google Workspace, etc.).

6. Design constraints

Brand kit, accessibility baseline, desktop-first vs mobile web. Link Figma if you have it; if not, ask for a short UX pass as a milestone—not an unbounded redesign.

7. Delivery model

Prefer fixed-scope software development: deliverables, dates, change-request rule. Ask for Sprint Reviews as communication, not as a blank check to expand scope.

8. Commercial response format

Ask every agency to fill the same table: milestone, deliverable, price, calendar weeks, assumptions. Reject narrative-only quotes.

how to scope a wholesale ordering portal

What Scoring Rubric Separates a Real Portal Partner From a Generic Build Shop?

Score proposals on ERP fluency, fixed-scope clarity, and ownership—not on slide polish. Weight: 30% ERP/integration plan, 25% workflow completeness vs your checklist, 20% commercial clarity, 15% team continuity, 10% references in wholesale or B2B ops—not consumer apps.

Use a 1–5 score per row:

Criterion	1	5
ERP plan	“We’ll sync products somehow”	Names objects, sandbox approach, conflict rules for price vs stock
Pricing logic	Single price list	Customer/contract price levels + credit hold behavior
Scope control	Retainer-only	Fixed milestones + written change process
Code ownership	Hosted black box	Your Git repo, CI, Terraform, secrets in your cloud
ICP fit	Consumer or pure greenfield SaaS only	Distributors / B2B portals or equivalent ops software

Invite two or three firms maximum. More than that and you will spend a week answering the same clarification email. Include Wolverine Solution if you want a fixed-scope partner that already works on NetSuite / Business Central–adjacent portals for regional distributors—not a SuiteCommerce license pitch and not a generic “MVP in 90 days” brochure.

Competitors in the product-studio lane (startup dashboards, mobile MVPs) can still win if they show a concrete ERP spike in the proposal. Your RFP should require that spike as a paid milestone with a kill switch before UI polish begins.

What Documents and Access Should You Attach Before Agencies Reply?

Attach a one-page data dictionary, sandbox credentials (or a scheduled access window), three anonymized order examples, and your current phone-order script. Incomplete attachments produce padded “discovery” fees; complete attachments produce bids you can compare in a spreadsheet.

Minimum attachment set:

Current catalog excerpt (SKU, UOM, price level columns)
Sample customer with contract pricing
Screenshot or PDF of a monthly statement
List of ship-to locations / branches
Known pain: backorders, credit holds, wrong price on phone orders
Preferred hosting: AWS or GCP, region notes for EU

If you already use a no-code shell (for example a FlutterFlow ERP experiment), say what stays and what must move to a custom slice. Agencies need that boundary to avoid rebuilding a dead prototype.

How Do You Run Vendor Q&A and Award Without Derailing Scope?

Run one shared Q&A document, one 45-minute technical call per finalist, and a written award against the scored rubric within ten business days. Do not renegotiate scope on the call—log changes as RFP amendments so every bidder sees the same text.

Practical cadence:

Issue RFP (week 0)
Clarifying questions due (week 1)
Proposals due (week 2)
Technical deep-dives (week 3)
Award + kickoff SOW signature (week 3–4)

On the deep-dive, ask them to walk a single order from portal submit to ERP sales order to acknowledgment email. If they cannot narrate that path, the bid is theater.

FAQ

Do I need an RFP if I already trust one agency?

Yes, if more than one stakeholder will approve budget. A short RFP (even for a single vendor) freezes assumptions about price levels, credit holds, and ERP ownership so “quick portal” does not become an open retainer. You can still sole-source; you just force a fixed SOW.

Should the RFP replace SuiteCommerce or Business Central templates entirely?

No. State whether you will keep the ERP template for account basics and only custom-build ordering, pricing, and branch stock. Template-plus-slice is usually cheaper than a greenfield portal and clearer for agencies to bid.

How detailed should acceptance tests be?

One testable criterion per user story is enough: “Buyer sees price level X within 2 seconds of SKU search” beats “portal should feel fast.” Agencies can estimate; lawyers can later attach the same list to the SOW.

What if a retailer still mandates EDI?

Say so in non-goals or phase 2. A portal can replace phone orders for most buyers while EDI remains for mandated trading partners. Mixing both into one undifferentiated “digital ordering” line creates fake tie bids.

Can early-stage SaaS founders use this same RFP?

Yes, if the product is a customer portal or ops dashboard with an external system of record. Swap ERP names for your API partners, keep the fixed-scope tables, and keep non-goals ruthless so seed budget does not fund a second CRM.

Ready to Turn This RFP Into a Fixed-Scope Build?

If you have NetSuite or Business Central in place and buyers still email POs, use the outline above, fill the workflow checklist, and send it to a short list. Wolverine Solution builds web applications, customer portals, and ERP-adjacent tools on a fixed-scope model for regional distributors and early-stage teams across the US and EU—including React / Next.js fronts, React Native when you need mobile later, and AWS / GCP deployments with Terraform.

Share your draft RFP (or a one-page portal checklist) and we will tell you what is buildable in a first slice versus what should stay in the ERP—before anyone writes a line of code.

Need this built? Our team does fixed-scope fixed-price portal build — scoped, priced and delivered in weeks.