Customer Overview

in the nue self service api, a customer represents an organization that purchases your products or services this concept is equivalent to an account in salesforce, and the terms are often used interchangeably when discussing nue's integration with salesforce core customer concepts a customer record serves as the foundation for all commercial relationships in nue, storing essential information such as basic identification (name, account number) contact information (addresses, phone, email) billing details (payment methods, terms) classification data (industry, type, size) financial metrics (arr, revenue, contract values) the customer object is designed to support both b2b and b2c business models, with flexible record types that can be configured to match your specific business needs customer id management and external system integration nue uuids vs external system ids nue uses uuids (universally unique identifiers) as the primary identifier for all customer records these uuids ensure global uniqueness and are the primary key used throughout the nue platform example nue customer id 20aa111d b3e6 446b 8e94 1d9b3d39e9dd the externalid field the externalid field is a critical component for integration with external systems, particularly salesforce this field stores the corresponding identifier from the external system, creating a mapping between nue's internal uuid and the external system's id format key characteristics of externalid initially null when customers are created through the self service api populated automatically when the customer synchronizes with salesforce contains the salesforce account id (typically 15 or 18 characters) enables bidirectional synchronization between nue and salesforce used for data consistency and integration workflows example salesforce account id 001ot00000mx5kziai id lifecycle example // 1 customer created in nue self service { "id" "20aa111d b3e6 446b 8e94 1d9b3d39e9dd", "name" "digital innovations llc", "externalid" null, // no salesforce sync yet "type" "prospect" } // 2 after first order activation and salesforce sync { "id" "20aa111d b3e6 446b 8e94 1d9b3d39e9dd", "name" "digital innovations llc", "externalid" "001ot00000mx5kziai", // now contains salesforce account id "type" "direct customer" } integration benefits this dual id system provides several advantages system independence nue can operate independently while maintaining external system relationships data migration enables smooth migration between systems without losing relationships api flexibility both nue uuids and external ids can be used for lookups and operations audit trail clear tracking of which records have been synchronized across systems conflict resolution helps resolve data discrepancies between integrated systems customer lifecycle stages understanding the customer lifecycle in nue helps you implement the right workflows 1\ prospect stage customer record exists in nue only externalid field is null (no salesforce synchronization yet) limited billing/payment information customer type typically set to "prospect" 2\ active customer stage first order has been activated automatic synchronization to salesforce occurs externalid field populated with salesforce account id full billing and subscription management available complete customer relationship established 3\ customer management stage ongoing updates and maintenance order modifications and renewals full integration with external systems comprehensive reporting and analytics customer salesforce account relationship for organizations using nue with salesforce integration, understanding how customer records in nue relate to account records in salesforce is crucial for maintaining data integrity and optimizing your sales operations data source and authority when your nue instance is connected to salesforce, customer records are designed to work seamlessly with your existing salesforce infrastructure synchronization strategies nue supports two distinct synchronization approaches, allowing you to choose the strategy that best fits your business model selective synchronization (default behavior) by default, customer records created through the self service api don't immediately sync to salesforce instead, synchronization is triggered only when meaningful business activity occurs—specifically when the first order is activated for that customer this selective approach provides several strategic advantages prevents salesforce data pollution by avoiding the creation of account records for prospects who haven't yet made a purchase commitment maintains a clear distinction between marketing leads/prospects and actual paying customers in your salesforce org optimizes your salesforce environment by ensuring that only customers with real business value appear in your sales and customer management workflows reduces crm clutter and helps your sales teams focus on genuine customer relationships continuous bidirectional sync (optional configuration) organizations requiring real time data synchronization can enable immediate bidirectional synchronization through a specialized configuration setting when this option is activated customer records created via the self service api instantly synchronize with salesforce, automatically generating corresponding account records account modifications in salesforce immediately sync back to the nue customer record, ensuring both systems remain perfectly aligned real time data consistency is maintained across both platforms, ideal for organizations with complex sales processes or multiple customer touchpoints this approach is particularly valuable for businesses that need immediate visibility into self service customer creation within their existing salesforce workflows and reporting structures more details can be found https //docs nue io/salesforce account vs nue customer customer data architecture core relationships customers in nue connect to several other key objects contacts individual people associated with the customer organization orders purchase transactions and configurations invoices generated based on selected billing cycle subscriptions ongoing service agreements physica assets physical or virtual products delivered entitlements access rights and usage permissions data integration points customer data flows through multiple systems salesforce master customer relationship management payment systems payment processing analytics platforms business intelligence and reporting understanding these relationships helps you design effective customer management workflows and troubleshoot integration issues next steps now that you understand the core customer concepts, you can move on to getting started with customer management learn basic crud operations advanced customer workflows implement complex business scenarios customer data reference understand all available fields and validation rules