Customer Matching
When order sync runs, the customer is synced first so that the order can post against that customer. FarApp matches customers on orders to existing customer records in NetSuite by company name or name and email. This ensures that FarApp doesn’t match to the incorrect customer record. If FarApp finds multiple customers that match by both company name or name, and email FarApp will match to the oldest (by created date) customer record. It’s important to make sure that you don’t have duplicate customer records in NetSuite to avoid confusion regarding which customer FarApp will post against. Before you proceed with your integration you’ll want to find and merge your duplicate customer records in NetSuite.
To Find Your Duplicate Customer Records
- In NetSuite, navigate to Lists > Mass Update > Entity Duplicate Resolution.
- From here, you can search matching records and resolve many duplicates in a single operation.
Merge Customer Records, If You Have Duplicates
- Click Edit next to the name of the customer whose record will serve as the source customer.
- This is the customer record that will be merged into the target customer record. This customer record will be deleted during the merge process.
- On the Customer page, click Merge.
- On the Merge Customer page, select the target customer into which you want to merge this source customer record.
- Both the source and target customer records must have the same primary subsidiary to merge the records.
- Click Merge.
- At the prompt to confirm the action, click OK.
- On the Duplicate Resolution Status page, the merge is queued for process.
- Click Refresh to process the merge or the Cancel link to halt the merge process.
- The Status column provides the results of the merge.
- Navigate to the target customer record and verify that it contains the data from the source customer record.
- If you use the Standard Customer Form, the System Notes subtab of the System Information subtab displays a line entry for the customer merge.
- Go to Lists > Relationships > Customers and verify that the source customer does not appear in the customer list.
Customer Mapping
Customer Mappings are used for fields that apply to the customer of an order. Please note that these mappings only apply when the customer is created. FarApp treats NetSuite as the master of record for customer data so as a leading practice, the only data that it will update on a customer once the record is created is the address book entries to add new addresses.*
*Note: Mappings will only apply when a customer record is created. However, if you have fields on your customer form that you would like updated upon order sync, please submit a request to FarApp support
Map Customer Fields used for Customer Creation
- Navigate to your Customer Mappings.
- If you have multiple channels/accounts make sure the proper channel and account is selected in the FarApp menu on the left.
- You should now see all the mappings for your channel/account. If you see any mappings marked “Read Only” those are default mappings that FarApp sets up for you.
- Click the button labeled Reload NetSuite List (this can take a few minutes to run). You’ll need to do this whenever you want to map list values that were added in NetSuite since the last time this was run. The button is available in a few mapping screens but it’s the same button so you only need to click it once.
- To add a mapping to this list click Add Mapping in the upper right of the screen. This will bring up a window of the NetSuite customer fields to choose from.
- Select the customer field from the drop down list. If you are using a custom field, select Custom Field and then enter the field ID of the field you want to use. The ID should start with “custentity”. If you do not know how to get the field ID of a field in NetSuite follow the instructions here: https://support.farapp.com/hc/en-us/articles/216635418-NetSuite-Internal-IDs-and-Field-IDs
- Once you’ve selected your field click Add Mapping and then click the Close button on the popup screen.
- Your new mapping should show up at the bottom of the mapping list. Now you’ll want to select the Mapping Type. The types to choose from are:
- Fixed: set a constant value in the “Value” field that will always post to NetSuite.
- Order Header Mapping: Select from the fields FarApp has pulled in on an order.
- Order Header Mapping with Translation: Behaves like an if/then condition for the value you select. Once you select which field to base the translation off of, click the Click to view/edit link that appears. In this screen you’ll want to click Add Row for each possible value the field you’ve selected could have. For example: if you use Location ID, place 1 in the value column of the first row and 3 in the value column of the second row, then whenever the Location ID shows up as 1, FarApp will post 3 to the NetSuite field you’ve selected to map to.
- Logic: If you require more complex mappings, please see the following article for instructions: https://support.farapp.com/hc/en-us/articles/360001396847-Setting-Up-Custom-Order-Mappings.
- Once you have selected your Mapping Type select your Mapping Value ([Storefront] Field/Fixed Value column). Please see the previous step about “Mapping Type” to help you figure out what the value should be.
- Click Save your new mapping should now show up in all future customers under the channel/account you specified.
Next Steps
If you are doing Fulfillment Sync, please proceed with Step 6: Fulfillment Sync. Otherwise, please proceed to Step 7: Testing Order Sync and Fulfillment Sync.
Comments
0 comments
Please sign in to leave a comment.