Introduction

Customer Sync is JOOR's flat file customer integration. A Customer Sync integration adds and updates customer connections in your account. The integration can run up to once per hour and pulls files from an FTP server, the credentials for which will be provided by JOOR.

Basic Requirements

• Files must be entirely generated by the ERP and may not be manually altered in any way.
• File format must be configurable in order to match the requirements of the integration.
• 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.
• Files must be automatically sent to JOOR's FTP server, hosted by BrickFTP.
  • More on BrickFTP's security technology can be found [here].
• 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 to ensure all integration functionality is working properly.
• Files must be in either .txt or .csv format.
  • We recommend using pipe ("|") as the delimiter as it is unlikely to appear in the customer data.

If any modifications need to be made to the integration after it is live in the Production environment, this must be first communicated to your Customer Success Manager. 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 has approved this modification, the Production integration will be updated and the new files may be sent.

Tips

• You do not need to send your full list each time. You can choose to only send the customers that have changed.
• All new customers will take up to 48 hours to be processed by our Customer Data team. Any 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 then use a column, address_type, to indicate whether the row is a shipping or billing address.
  • If you decide to use Customer Sync, you will need to provide a sample file and our team will ensure that it is workable.

Prerequisites

Before beginning to test the integration, you will need to 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 to 1. Each sales rep email address can only be associated with one unique sales rep code.
• Warehouse names and codes
• Customer group names and codes
• Company number names and codes

Testing Scenarios

Basics

• Add a new connection

Connection Specific Data

• Add a payment method
• Update a payment method
• Add a shipping method
• Update a shipping method
• Add a new address (billing & shipping)
• Update an existing address (billing & shipping)
• Add an alias
• Add additional address to existing connection
• Add a discount
• Update a discount
• Add a company number
• Update a company number
• Add a door
• Update a door
• Add a buyer
• Update a buyer

Customer Sync Fields