Home / Product / Registration and Login

Phoenix P21 Customer Registration & Login

How Phoenix Connects Web Users to Prophet 21

Phoenix is built to ensure that customers who log into your website receive the same pricing, availability, and product access they would if a customer service representative were working with them directly inside Prophet 21 (P21). To accomplish this, all registered Phoenix users are explicitly linked to a valid P21 customer record.

This tight integration ensures that the website is not operating as a separate system, but rather as another secure interface into the same ERP data used by your internal teams.

P21 Customer-Based Pricing, Availability, and Restrictions

Every logged-in Phoenix user is attached to a specific P21 customer code. That customer code determines exactly what the user can see and do on the website, including:

  • Customer-specific pricing
  • Inventory availability by location
  • Product visibility and purchasing restrictions
  • Terms, credit rules, and ordering permissions

Because the website uses the same customer context as P21, the online experience mirrors the ERP experience with no discrepancies between systems.

Unified Order, Invoice, and Quote History

Once logged in, customers can view their complete transactional history directly on the website. This includes:

  • Orders placed through the Phoenix eCommerce site
  • Orders entered directly into Prophet 21 by customer service
  • Invoices, statements, and quotes generated in P21

There is no separation between “web” activity and “ERP” activity. Everything is consolidated under the same P21 customer account, providing a single, consistent source of truth.

P21 Ship-To Address Integration

Phoenix also pulls all ship-to records directly from Prophet 21. During checkout, customers can select from their existing P21 ship-to addresses rather than manually re-entering shipping information.

This ensures accurate delivery information, consistent tax and freight calculations, and full alignment with your existing P21 shipping rules.

Why Customer Registration Requires Approval

Because Phoenix users must be tied to a valid P21 customer record, registration is intentionally controlled and requires administrative approval. Users cannot be automatically activated without review.

This approval process ensures that customers are properly linked in P21 and prevents incorrect pricing, data exposure, or ordering permissions.

Depending on the situation, approval may involve:

  • Linking the user to an existing P21 customer
  • Creating a new P21 customer record
  • Assigning the user to a shared or “front counter” customer ID

The Phoenix Registration Workflow

The registration and approval process follows a clear, controlled workflow:

  • The shopper submits a registration request with basic information such as name, email, phone number, and an existing P21 customer ID if available
  • An administrator receives an email notification to review the request
  • The administrator logs into Phoenix and assigns the required P21 linkage details, including customer ID, company ID, ship-to ID, and contact ID (if required)
  • Optional roles and permissions are configured for the user
  • The registration is approved and the customer receives a confirmation email

Flexible User Roles and Permissions

Phoenix supports a wide range of role-based options that can be configured during approval, including:

  • Ability to make accounts receivable (A/R) payments
  • Master customer access to manage additional users or emulate other customer codes
  • Restriction to quote-only functionality instead of direct order placement
  • Additional customer-specific permissions based on business rules

A Seamless ERP-Driven Web Experience

Once approved, customers can log in and immediately access trusted P21 pricing, real-time availability, complete order and invoice history, and ERP-driven checkout options.

The result is a secure, controlled, and fully integrated web experience where Phoenix acts as an extension of Prophet 21—maintaining accuracy, consistency, and control across both systems.