These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Aerospace Components CPQ
- Features
- Customers and organizations
Customers and organizations
Customer accounts, operating organizations and team membership.
OverviewCustomer accounts×
Aerospace Components CPQ · Customers and organizations
New
Customer accounts
Customers
| Name | Code | Contact name | Address | Eligibility note | Organization | |
|---|---|---|---|---|---|---|
| Customer 618 | CDE-267 | Contact 334 | Z-7 | EN-356 | ORG-5432 | |
| Customer 153 | CDE-781 | Contact 420 | N-8 | EN-844 | ORG-8359 | |
| Customer 351 | CDE-998 | Contact 442 | F-9 | EN-615 | ORG-7794 | |
| Customer 310 | CDE-993 | Contact 825 | V-9 | EN-643 | ORG-4590 | |
| Customer 360 | CDE-192 | Contact 180 | T-22 | EN-823 | ORG-3246 |
6 of 6 records
Customer 618Customers · CST-68089
CodeCDE-267
Contact nameContact 334
AddressZ-7
Eligibility noteEN-356
OrganizationORG-5432
What you can do
Set the scope every quote depends on
Every quote, requirement and customer in the app belongs to an Organization. An Organization has a Name, a Code, an Active flag, a time zone and a Currency chosen from USD, EUR, GBP, CAD, JPY and CHF. Customers belong to an Organization and carry the Name, Code, contact name, Address and an eligibility note that tells the quoting team what to check before quoting that account. Team members connect a person’s Users account to an Organization, with their role name, time zone and an Active flag.
Getting this scope right is what lets pricing refuse a request from outside the organization it names. It also decides who can own a quote and who can review one, because both Owner and Reviewer point at team members.
How the work is organized
- Administrators maintain the scope. The App Administrator manages Organizations, Customers and team members. Quote Specialists read customer records but do not change them.
- Eligibility is written down. eligibility note is required on every customer, so a specialist sees any condition on that account before preparing a quote.
- Inactive stays on file. Setting Active to No on a customer or team member keeps their earlier quotes and decisions intact while stopping new work.
What to agree during setup
Agree which legal or operating units become Organizations and the Code each one uses. Agree the customer Code format and what belongs in eligibility note, such as an approved-supplier condition or a payment hold. Agree the role name values you record on team members so they line up with the roles in the app. Decide who in your business may ask the App Administrator to deactivate a customer or a team member and how that request is recorded.
Check the handoff on an actual case
Load two organizations, a handful of customers for each and the team members who quote and review for them. Create a quote for a customer of the first organization and try to price it under the second; confirm the request is refused. Deactivate a team member who owns an approved quote and confirm the quote and its decision history are unchanged. Add an eligibility note to a customer and confirm the Quote Specialist can read it from the customer record while preparing a draft.
Ask the App Administrator to list every active reviewer for each organization. Ask the Auditor to confirm that list matches the people who recorded review decisions last month.
What your team sees
- Customer accounts — active customers with code, contact, address, eligibility note and organization.
- Team membership — active team members with role name, organization, time zone and platform user.
Follow the work through
- Draft to priced quote: Build a draft quote for an active customer, then price it within the right organization.
- Correction and reconciliation: Cancel or correct authorized scope and check what each operation receipt claims.
Check roles and permissions and the data model before loading organizations and customers.
What it keeps track of
Data model- Organizations
- Operating organizations that own quotes, customers and team membership.
- Customers
- Customer accounts that receive aerospace component quotes.
- Team members
- Internal team members with organization membership, platform identity and role scope.
- Users
- Users
Who uses it
Permissions- App Administrator
- , Admin, Auditor.
- The App Administrator maintains organizations, customers and team membership.
- The Admin maintains the platform Users accounts behind each team member.
- The Auditor reads all of them.
Set up Aerospace Components CPQ your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.