Planning SuiteCommerce MyAccount Features for B2B Buyers
A useful B2B portal reflects the way customers already buy. Interview buyers and account staff before adding a long feature list. A distributor that receives repeat orders by SKU needs a different portal from a business that negotiates every quote.
Start with jobs, not widgets
Collect a small set of real tasks:
- find an order by purchase order number;
- repeat a past order with current price and availability;
- download an invoice;
- pay an eligible balance;
- create and approve a quote;
- let a colleague order within an account policy;
- upload a list of SKUs and quantities;
- request a return.
For each task, record who may perform it, which NetSuite record is authoritative, and what should happen when data is stale or incomplete.
Features worth evaluating
Better order search
Let users search by identifiers they know, such as PO number, order number, date, or status. Apply authorization on the server. Hiding another account's row in the browser is not access control.
Reorder
A reorder action should build a new cart, not copy an old transaction blindly. Recheck item status, minimum quantities, current pricing, inventory, shipping restrictions, and substitutions. Show the customer what changed before adding lines.
Quotes
Define the quote lifecycle first: draft, submitted, reviewed, accepted, expired, or rejected. Name the NetSuite transaction or custom record behind each state. Decide whether accepting a quote creates a cart, sales order, or another approval step.
Account users and permissions
Avoid inventing a second authorization system in frontend code. Map contacts, customer records, roles, and any approval records deliberately. Test access with multiple subsidiaries and customer accounts if the business uses them.
Pricing and invoices
Display the result returned for the signed-in customer rather than reproducing pricing logic in JavaScript. Invoice visibility and payment eligibility also need server-side checks. Account balance alone does not prove that a user may view or pay every invoice.
Lists and bulk order entry
Saved lists are useful when customers buy a stable set of items. CSV entry needs strict limits and clear row-level errors. Parse and validate uploads on the server, protect against formula injection in exported files, and never trust a customer-supplied price.
Returns
Show only orders and lines eligible under the merchant's return policy. A request is not necessarily an approved return. Keep status names aligned with the operational process so customers and staff see the same state.
Use supported extension points
Oracle recommends using the Extensibility API where it provides the required component. Its general best practices advise against changing source files and importing unsupported core modules. Start with Oracle's anatomy of an extension and generated project structure for the site's release.
An extension can reduce upgrade friction, but it does not guarantee compatibility forever. Managed SuiteCommerce applications update automatically, so test active extensions against release preview and release notes. SCA has a manual migration path. Oracle describes both in Commerce Patches and Upgrades.
Prioritize with evidence
Score each candidate on:
- task frequency;
- customer and staff time saved;
- authorization and accounting risk;
- data readiness;
- implementation and support effort.
A specific example: if support receives many “where is my invoice?” requests, first verify that contacts can be mapped safely to invoice access. A polished invoice screen built before that rule is settled creates risk, not self-service.
Release one bounded task, instrument its use, and ask customers whether it worked. Expand from observed demand instead of promising a universal adoption percentage.
