Give each audience a clear way into the work.

A customer checking an order, a supplier responding to a purchase request and an employee submitting information need different experiences. Start with the person, the records they need and the task they should be able to complete. That gives the application a useful boundary.

We compare the account’s existing centers and configured workflows before proposing a custom experience. A tailored application may be worthwhile when the journey crosses systems or needs a different interaction. The assessment identifies that gap and the integration, access and support work that comes with it.

Choose the experience you need to explore.

Customer portals

Help customers find relevant account information and scope any permitted requests or transactions. Compare a tailored experience with NetSuite Customer Center before deciding what to build.

Vendor and partner portals

Examine supplier collaboration and partner-facing workflows separately. Each relationship needs its own record visibility, commercial boundaries and responsibility for follow-through.

Employee portals

Consider a focused entry point for internal requests, information and approvals. Review existing Employee Center capability, employee privacy and the approval structure.

Mobile apps

Explore tasks performed away from a desk. Device requirements, connectivity, distribution and the handoff into NetSuite belong in the mobile design.

Decide whether users need information or permission to act.

A read-only experience and an application that changes a business record have different requirements. For viewing, define which records, fields and documents are visible and how current they need to be. For actions, also define validation, approval, confirmation and recovery when the result is uncertain.

Make these decisions before expanding the feature list.

  • Access boundaries

    Identify each audience and its relationship to the records. Separate portal sign-in, application authorization and the permissions used to connect with NetSuite.

  • Account and operating fit

    Confirm available interfaces, licensing, hosting responsibilities and support arrangements for the proposed architecture.

  • Evidence of readiness

    Choose representative tasks and permission tests. Agree how the business will recognize correct data, successful actions and recoverable failures.

Custom delivery and product scope

Are these ready-made portal products?

This section describes custom portal and mobile application work. The audience pages explain possible workflows to scope. Specific features, integrations, delivery terms and ongoing responsibilities should be agreed for the project.