Using the Bulk Importer allows studios to set up hundreds of sessions by uploading a CSV data file into the system.
The Bulk Importer template file has specific fields which must be completed with very strict formatting rules.
- Click Clients & Sessions from the left hand menu panel and select Imports.
- To import the file, either drag and drop into the specified area, or click the section and select a file to import. The import file template can be downloaded from both the Imports page in Commerce, or at the bottom of this article.
- If your file has an invalid row you can review why it failed by clicking on the cog and choosing View.
Errors are listed by Line (row) and it also will show you the column header where the error occurred and why.
Headers
Using the correct headers on the csv data file is critical. Some fields are mandatory but others are optional. Some headers must be used together, for example, if you are using any of the columns for Date/Time then you must also use the column for Timezone or the system won't know what time/day to use.
Mandatory Headers
These three columns are the minimum requirement for a CSV bulk session import.
- Template UID: This is the UID for the session template you want to use.
Note: All session template information will be used: tax, season etc.
- Session Label: The name of the Session, this appears in the sessions list and also appears visibly to the people using the shopping cart.
- Client Name: The client is the School or league etc. If a client name has not been created, the client will be created upon import. If you use a slightly different version or spelling of an existing client, a new one will also be created.
- If you wish to use an existing Client then type the name exactly as it appears in your Clients area.
- If you are wanting to create a new client upon import you can also include additional client information that we support.
Optional Headers
Client Reference, Territory Code and Client Access Code are optional identifiers.
- Client Reference is typically an abbreviated identifier for internal use.
- Territory Code is commonly area-based.
- Client Access Code is used when searching for all relevant and active sessions using a unique code for the specific client.
Columns for specific use cases
- Session Access Code: For pre-order stages that require an access code.
- Session Reference: Often used for FTP uploads.
Setting specific dates/time
- Session Timezone: This must be used to include any date/time information during import. The list of timezones supported are limited and listed further below.
- Shoot Date: If you require photo day in the session information. This must be expressed in the following format: yyyy-mm-dd hh:mm:ss.
Only one of the below can be used at a time. However, if these are managed by the Session Template they can be left out.
- First Stage Duration: A set time frame for the first stage to stay active.
- First Stage End At: A set time/day for the first stage to complete.
Session Template controlled settings
Session Category and Season Reference can remain blank if they are in place in the session template you are using. If not you can add them but they must match existing category or season in your account.
Tax fields can also remain empty if setup in the Session Template. They can be overridden by completing the columns.
- Tax Enabled - (0, 1 or empty) 0= NO, 1=YES
- Tax Rate - (0-100 or empty) eg: 8.75 (for 8.75% tax rate)
- Tax Forced - Tax Forced (0, 1 or empty) 0= NO, 1=YES
- Publish - (0, 1 or empty) 0= NO, 1=YES
Timezone format
Timezones need to be in the exact spelling as below:
- America/Chicago
- America/Dawson_Creek
- America/Denver
- America/Detroit
- America/Edmonton
- America/Indiana/Indianapolis
- America/Los_Angeles
- America/Mexico_City
- America/New_York
- America/Phoenix
- America/Toronto
- Asia/Bangkok
- Asia/Ho_Chi_Minh
- Australia/Adelaide
- Australia/Brisbane
- Australia/Darwin
- Australia/Melbourne
- Australia/Perth
- Australia/Sydney
- Europe/Paris
- Pacific/Auckland
Columns with these headers require specific formatting rules:
- First Stage Duration Formatting
- First Stage End At
- First Stage End At Formatting
|
|
|
|
|
Example:
Specific date must be expressed in the following format: yyyy-mm-dd hh:mm:ss |