Automatically importing branches

Branches can be uploaded automatically to Enable via SFTP data feeds to calculate special pricing agreement (SPA) support. Branches selected on a SPA rely on branch data imported into the Enable channel in order for support to be accurately calculated.

This article will guide you through:

1. How to download the branches template
2. How to populate the branches template
3. How to save the branches file
4. How to upload the branches file

Looking for something else?

• Looking to import branches for SPAs via the Enable user interface? Learn about manually importing branches for SPAs here.
• Importing branch data for rebate agreements rather than special pricing agreements? Learn about automatically importing branches for trading programs here.
• Looking to add branches to a special pricing agreement? Learn how to add branches to a new SPA here.
• Alternatively, see our Help Center for more on SPAs.

Branch data for SPAs are located within the Config area of the Trading programs app.

Channel admin users have access to the Config area and branches template within Enable.

To download the branches template:

Step 3: Click on Config in the green banner at the top of the page.

Step 4: Click on Structure in the drop-down menu.

Step 5: In the Dimensions tab, click Branches.‍

Step 6: On the right of the page, click Download template and set the checkbox for Populated with existing to download a template containing all existing branch data within your Enable channel. Alternatively, leave the checkbox blank to download an empty template.

Step 7: Click Download to save the template to your computer’s downloads folder.

If you are importing branches via SFTP, you may navigate away from the config area within Enable, and continue with the steps in the next section.

Once the branches template has been downloaded, you will need to populate each row with the following column data for your SPA branches. Column headers must not be changed or renamed in the file.

• Branch Name: Must be unique across all branches within the Enable channel.
• Customer Reference: Only displayed if your organization is the manufacturer. Must match the reference of a customer within the Enable trading partner data. If your organization is the distributor, this column won’t exist and should not be used.
• Branch Reference: Must be unique across all branches within the Enable channel.
• Start Date: Leave blank as branch dates are not applicable for SPAs.
• End Date: Leave blank as branch dates are not applicable for SPAs.
• Region: Enter the region or group the branch is in. This column be named differently depending on your channel’s configuration. Tip: Regions can be used to group branches for easy creation of a new SPA, as well as to accurately calculate support based on the movement of inventory if your channel is using the quantity and price/cost ledger.

If required by your implementation team:

• (Optional) Add the row count in the final row in the form “ROWCOUNT IS X”, where X is the total number of branches you are uploading. In the CSV file, this will be the total row count - 2.

If you have a singular collection for branches, save your CSV file and rename the file to the format “{DIMENSION NAME}-TIMESTAMP.csv”, where:

• {DIMENSION NAME} is replaced by the pluralized label given to the branches dimension in your channel, e.g. BRANCHES.
• TIMESTAMP is replaced by a 14-digit number in the form yyyyMMddhhmmss made up of the creation date, e.g. BRANCHES-20240417030422.csv.

If you have multiple collections for branches, save your CSV file and rename the file to the format “{DIMENSION NAME}-{COLLECTION NAME}-TIMESTAMP.csv”, where:

• {COLLECTION NAME} is replaced by the name of the branches collection you want to update, e.g. Branches 2024.
• {DIMENSION NAME} is replaced by the pluralized label given to the branches dimension in your channel, e.g. BRANCHES.
• TIMESTAMP is replaced by a 14-digit number in the form yyyyMMddhhmmss made up of the creation date, e.g. BRANCHES-Branches 2024-20240417030422.csv.

Step 1: Connect to your SFTP location using the SFTP credentials provided by your implementation team.

Step 2: Navigate to the Imports folder.

Step 3: Upload the Branches CSV file into the Imports folder.

Step 4: Create an empty file with the same name as the Branches CSV file with an additional appended “.ok” (e.g. BRANCHES-20240417030422.csv.ok). This will begin the import process into your channel.

Step 5: Check to see if the file was received by Enable once the file has finished processing. If the Branches CSV file is in the Succeeded folder, this indicates that the branch data is now in the Enable platform. If the Branches CSV file is in the Failed folder, this indicates that the file has failed and a corresponding Error.txt file will be generated describing the error.

What’s next?

Need help resolving SFTP errors? Learn how to understand SFTP errors here.

Looking to import product data into Enable via SFTP? Learn how to automatically import products for SPAs here.