Configuration Settings
All customer settings are located under the Customers subtab within the Data Orchestration tab. In this subtab, the Customer Settings field group contains all configuration fields required for managing the Customer flow.
Note: Click any field label in the Customer Settings field groups to see a description of its purpose and usage.
Field Descriptions
Enable Customer Flow: Check/mark to enable importing Stripe customers into NetSuite. Uncheck to stop all customer imports.
Update Stripe Customer Metadata: Check/mark to automatically write the NetSuite Customer record's Internal ID back to the corresponding Stripe customer after it is created.
Last Exported Date - Unix format: Shows the last time customers were imported from Stripe (in Unix timestamp). This value is used in the next import to fetch only charges created after this time using the created[gte] parameter.
Note: The system updates this field after every flow execution, and it is read-only.
Last Exported Date - Date/Time: Shows the last time customers were imported from Stripe (in Date/Time format).
Note: The system updates this field after every flow execution, and it is read-only.
Criteria to find existing customer record: This field is used to define how NetSuite identifies an existing customer before creating a new record. It allows users to set up specific conditions (filters) based on incoming Stripe invoice data, such as email, Stripe customer ID, or other mapped fields. These conditions are executed at runtime to search for a matching customer record in NetSuite.
If a record satisfying the defined criteria is found, that customer is used for further processing; otherwise, the script proceeds based on the configured fallback behavior.
Note:The criteria are defined as a set of filters, which can include one or more conditions combined using AND/OR logic.
If no criteria are provided, the script falls back to default matching (typically using email and/or Stripe customer ID).
A default customer can be specified in the configuration to be used when no matching record is found.
Refer to the Field Mapping Documentation for examples and detailed instructions on setting up the criteria.
Customer Field Mappings:
Controls how Stripe Customer fields are mapped to NetSuite Customer fields
Note: Only fields from the Stripe customer object can be used.Sample Field Mappings
{ "fields": [ { "generate": "subsidiary", "hardCodedValue": "1" }, { "generate": "companyname", "extract": "name" }, { "generate": "email", "extract": "email" }, { "generate": "custentity_nm_stripecharge_customer_id", "extract": "id" } ], "sublist": { "addressbook": [ [ { "generate": "defaultshipping", "hardCodedValue": true }, { "generate": "defaultbilling", "hardCodedValue": false }, { "generate": "addr1", "extract": "shipping.address.line1" }, { "generate": "addressee", "extract": "name" }, { "generate": "city", "extract": "shipping.address.city" }, { "generate": "country", "extract": "shipping.address.country" }, { "generate": "state", "extract": "shipping.address.state" }, { "generate": "zip", "extract": "shipping.address.postal_code" } ], [ { "generate": "defaultshipping", "hardCodedValue": false }, { "generate": "defaultbilling", "hardCodedValue": true }, { "generate": "addr1", "extract": "address.line1" }, { "generate": "addressee", "extract": "name" }, { "generate": "city", "extract": "address.city" }, { "generate": "country", "extract": "address.country" }, { "generate": "state", "extract": "address.state" }, { "generate": "zip", "extract": "address.postal_code" } ] ] } }