What are the basic requirements for customer sync?

Read about basic requirements and field definitions for customer sync here, and review the customer sync template attached.

Before testing the integration, provide the following information if you plan on including it in your customer file. All fields are optional unless otherwise noted.

• Currencies and price labels (required)
  • Currency/price label combination must be unique.
• Payment method terms and codes
• Shipping method terms and codes
• Sales representative names, codes, and emails
  • The relationship between sales rep email and code is 1:1. Each sales rep email address can only be associated with one sales rep code.
• Warehouse names and codes
• Customer group names and codes
• Company number names and codes

Once provided, the JOOR team will load this information into your account, and you can begin testing.

Find a list of recommended Customer Sync testing scenarios here. Use this list as a guideline as you test different scenarios that are relevant to your business. Once all tests have been executed successfully, your integration should be ready to activate.

Basic Requirements and Tips
 

1. Files must be generated by the ERP and may not manually altered in any way.
2. File format must be configurable to match integrations requirements.
3. File name must be specified for the integration to be able to pick up new files. We recommend including the word customer along with a timestamp.
4. Files must be automatically sent to JOOR's FTP server, hosted by BrickFTP. More on BrickFTP's security technology can be found here.
5. After receiving a finalized file format, we recommend two weeks of testing by placing files on an FTP and reviewing changes on the JOOR website. This helps ensure all functionality is working properly.
6. Files must be in .txt or .csv format. We recommend using pipe as the delimiter.

 
If modifications need to be made to the integration after it is live, this must be first communicated to your Customer Success Manager, and a test file should be sent containing the updated format. This will be reviewed and an additional round of testing in the Sandbox environment will take place. After the JOOR team approves this modification, the production integration will be updated and the new files may be sent.

• You do not need to send your full customer list each time. You can choose to only send the customers that have changed.
• New customers will take up to 48 hours to be processed by our Customer Data team. Updates to existing customers will be processed automatically.
• We are able to process multiple file formats through Customer Sync. Our standard format features different rows for each billing and shipping address. We use a column, address_type, to indicate whether the row is a shipping or billing address.
  • If you decide to use Customer Sync, please provide a sample file and our team will ensure it is workable.