Introduction

Style Sync is JOOR's flat file style integration. A Style Sync integration adds, updates, drops, and deletes styles in your account. A Style Sync Integration also allows you to manage linesheets, if you are able to pass through linesheet information from your ERP.

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 using the word "style" 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].
• An action code is required for each row as this tells the integration how to read the contained data. Action codes can be client-specific values that are mapped to the following actions:
  • Add - Creates new style
  • Update - Updates style data
  • Drop - Drops style from the specified (non-custom) linesheet
  • Delete - Deletes style entirely from JOOR and all linesheets
• Files must be in either .txt or .csv format.
  • We recommend using pipe ("|") as the delimiter as it is unlikely to appear in the style data.
• Files must not exceed 20MB.
• 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.

If any modifications need to be made to the integration after it is live in the Production environment, this must first be 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.

Prerequisites

Before beginning to test the integration, you will need to provide the following information. All fields are optional unless otherwise noted.

• Currencies and price labels (required)
• Style Tag Names
• Casepack information

Tips

• Each linesheet can only have one set of delivery dates. If there are multiple deliveries, please indicate this in the linesheet name.
• If you wish to use Linesheet Season Name and Linesheet Season Year, you send these in separate columns.
• If you wish to deactivate a style from all linesheets to which it is tied, you should send a Drop record for the style with a blank linesheet name field.
• You do not need to send your whole collection each time. You can choose to only send the style/colors that have changed.
• To change a color name, you must pass through a Drop/Delete for the old color name and then an Add for the new color name.
  • Please see our Testing Scenarios section for further guidance on how to perform this update.
• Sizes are excluded from the updates managed through the Action Codes. There are two ways to remove a size:
  • Send an Update record with all sizes you wish to display. The remaining sizes that are excluded from your file will be marked inactive on JOOR.
  • Include a Size Active column in your Style Sync file. If any value is populated in this column for a specific row, the size will remain active. If left blank, the size will be marked inactive.
• We are able to process file formats with either:
  • One size per row (recommended) OR
  • A list of comma separated sizes in a single row
• To manage size order display you must either:
  • Include a Size Order column in your Style Sync file OR
  • List sizes in the correct display order

Testing Scenarios

A list of recommended Style Sync testing scenarios is also available for your reference. You may download it from the Testing Scenarios section of our Style Sync documentation online. Use this list as a guideline as you test different scenarios that are relevant to your business. Once all relevant tests have been executed successfully, your integration should be just about ready to activate on your Production account.

Reporting

Success and Error report emails are generated every time a file is processed via the integrations. If you and your team wish to receive these report emails, please specify the recipients' email addresses and we will set them up accordingly.

This feature is available on the Production environment. If you wish to receive the email reports during the testing period on Sandbox, please reach out to your dedicated Integrations Manager.

Style Sync Fields