Collections Data Model

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

organization name

The formal name of the organization.

'Massage Spa Express' is the formal name of an organization.

varchar(512)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

organization account name

The domain name of the organization in Zenoti.

If you use this URL to log in to Zenoti 'https://massagespa.zenoti.com', then "massagespa" is your account name. The formal name and domain name may be different.

varchar(256)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

center name

The center where the payment is done.

varchar(128)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

zone name

The zone to which the center belongs.

varchar(800)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

center city

The city in which the center is located.

varchar(128)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

center state name

The state in which the center is located.

varchar(4096)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

country name

The country in which the center is located.

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

center zip

The postal code in which the center is located.

varchar(32)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

center time zone

The time zone in which the center is located.

varchar(128)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

minutes to add

The number of minutes to add to the UTC time to get the current time at the center. If you use filters such as Today or Tomorrow, Tableau generates the timestamps in UTC. We require this field to calculate the center time. It is not required for timestamps that are in the data source directly, these are already aligned to the center’s time zone.

int4

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

operating center

This flag indicates whether the center is operational. - True indicates an operational center. - False indicates a non-operational center.

boolean

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

center company name

The name under which the center is registered.

Businesses, especially in a franchisee model, may register each center as a different company - such details are tracked in the Centers > General tab.

varchar(200)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

is center franchise

This flag indicates whether the center is a franchisee. - True indicates that it is a franchisee. - False indicated it is not a franchisee.

boolean

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

center cstn number

The center's Central Sales Tax (CST) number.

varchar(80)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

center tin number

The center's Taxpayer’s Identification Number (TIN).

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

center tot number

The center's Transient Occupancy Tax (TOT) number.

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

center vat number

The center's Value-Added Tax (VAT number.

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

center luxary tax number

The center's Luxury Tax number.

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

center wid

A unique identifier for the center in analytics. This is generated by Analytics and does not exist in the core system.

bigint

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

center code

Unique code associated with every center.

varchar(512)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

center service tax number

The center's Service Tax number.

varchar(80)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

base center name

The center where the invoice is generated.

varchar(200)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

base center company name

The base center's company name.

Businesses, especially in a franchisee model, may register each center as a different company - such details are tracked in the Centers > General tab.

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

base center zone name

The zone to which the base center belongs.

varchar(800)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

etllastupdatedon

Latest timestamp at which the corresponding record was either inserted or updated in this data source.

timestamp without time zone

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to two types of centers. 1. Center: Center where the payment is done. 2. Base Center: Center where the invoice is generated. In some situations, it is possible that these two centers are different. The fields in this group detail the various attributes of the center and base center.

etllastupdatedby

ETL system admin user who inserted or updated the corresponding record in this data source.

varchar(50)

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

guest first name

First name of the guest.

varchar(160)

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

guest middle name

Middle name of the guest.

varchar(128)

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

guest last name

Last name of the guest.

varchar(256)

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

user wid

A unique identifier for the guest. This is generated by Analytics and does not exist in the core system.

bigint

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

user id

A unique identifier for the guest. This is a non-blank value that gets populated for every guest.

varchar(36)

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

guest code

A unique identifier for the guest. This is a non-mandatory value and it can be blank. This maps to the guest code in the guest's profile in Zenoti.

varchar(128)

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

guest city

The city to which the guest belongs.

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

guest state

The state to which the guest belongs.

varchar(4096)

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

guest country name

The country to which the guest belongs.

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

guest zipcode

The postal code in which the guest belongs.

varchar(128)

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

guest email

The guest's email ID.

varchar(256)

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

guest mobile phone

The guest's mobile number.

varchar(64)

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

guest home phone

The guest's home phone number.

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

guest phone code

The country code of the guest's phone number.

integer

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

guest gender

The guest's gender.

Possible values: Male Female Not Applicable

varchar(14)

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

guest dob

The guest's date of birth.

timestamp

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

guest anniversary date

The guest's marriage anniversary.

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

guest type name

An indicator of whether the guest is indeed a guest or an employee availing a service.

Possible values: Guest Employee Internal Guest/Virtual Guest: Guests who made their first purchase on Webstore.

varchar(128)

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

guest tags

The tags associated with the guest.

Tags can be setup for guests in their profile under the 'General' tab. These will be comma separated values if there are multiple tags.

varchar(65535)

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

is guest inactive

This flag indicates whether the guest is inactive. A guest is considered inactive if their profile has been removed from the system. - True indicates that the guest is inactive. - False indicates that the guest is active.

boolean

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

guest referral source

The source from where the guest got to know about the organization.

Possible values: - Advertisement - Driving By - Friend - Guest - Instagram - Other - Walkin - Yelp - Youtube

varchar(1600)

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

referred by first name

The first name of the person who referred the guest.

varchar(160)

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

referred by last name

The last name of the person who referred the guest.

varchar(256)

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

referred by user code

The user code of the person who referred the guest. If an employee referred them, the employee code is populated here. If another guest referred them, the referring guest code is populated here.

varchar(128)

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

referred by guestid

The user id of the person who referred the guest.

varchar(36)

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

refby userwid

Unique identifier of the person who referred the guest. This is generated in Analytics.

bigint

Guest

These fields detail the attributes of the guest who took the service, product, package, membership, gift card or prepaid card.

guest base center

Base center of the guest. This is where the guest's profile was created.

varchar(256)

Item

Everything sold can be classified as items. In most cases, an item is either a service, product, package, membership, gift card, or prepaid card. This group details out the attributes of the item.

item type code

The type of item sold or refunded. An item can be a service, product, membership, package, gift card or prepaid card.

Possible values: Day Package Day Package Refund Gift Card Membership Membership Freeze Fee Membership Refund Package Package Refund PrePaid Card PrePaid Card Refund Product Product Refund Service Service Refund

varchar(100)

Item

Everything sold can be classified as items. In most cases, an item is either a service, product, package, membership, gift card, or prepaid card. This group details out the attributes of the item.

item name

The name of the item sold. For example, if item type code = Service, then item name is the name of the service. If item type code = Product, then item name is the name the product.

varchar(512)

Item

Everything sold can be classified as items. In most cases, an item is either a service, product, package, membership, gift card, or prepaid card. This group details out the attributes of the item.

item code

The unique code of the item sold. For example, if item type code = Service, then item code is the code associated with that service. If item type code = Product, then item code is the code associated with that product. It is slightly different for a gift card. If item type code = Gift card, then item code is unique for every gift card sold.

varchar(256)

Item

Everything sold can be classified as items. In most cases, an item is either a service, product, package, membership, gift card, or prepaid card. This group details out the attributes of the item.

item tags

The tags associated with the item.

Tags can be created for a service, product, package, or membership in the Organization view. These will be comma separated values if there are multiple tags.

varchar(65535)

Item

Everything sold can be classified as items. In most cases, an item is either a service, product, package, membership, gift card, or prepaid card. This group details out the attributes of the item.

businessunit

The business unit to which the item belongs.

Item

Everything sold can be classified as items. In most cases, an item is either a service, product, package, membership, gift card, or prepaid card. This group details out the attributes of the item.

is item inactive

This flag indicates whether the item is inactive. An item is considered inactive if it has been removed from the system. - True indicates that the item is inactive. - False indicates that the Item is active.

boolean

Service

If the item sold or refunded is a service, these fields get populated. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted since categories in Analytics correspond to sub-categories in the core system while parent categories in Analytics correspond to categories in the core system.

service name

The name of the service.

varchar(512)

Service

If the item sold or refunded is a service, these fields get populated. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted since categories in Analytics correspond to sub-categories in the core system while parent categories in Analytics correspond to categories in the core system.

service category

The category of the service. This is setup as sub-category in core.

For a service 'Brazilian Wax', category could be 'Waxing', and parent category could be 'Hair removal'.

varchar(256)

Service

If the item sold or refunded is a service, these fields get populated. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted since categories in Analytics correspond to sub-categories in the core system while parent categories in Analytics correspond to categories in the core system.

service parent category

The parent category of the service. This is setup as category in core.

Service

If the item sold or refunded is a service, these fields get populated. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted since categories in Analytics correspond to sub-categories in the core system while parent categories in Analytics correspond to categories in the core system.

service length

The ideal time taken to complete a service (in minutes), as setup in Zenoti.

integer

Service

If the item sold or refunded is a service, these fields get populated. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted since categories in Analytics correspond to sub-categories in the core system while parent categories in Analytics correspond to categories in the core system.

service businessunit

The business unit to which the service belongs.

varchar(200)

Service

If the item sold or refunded is a service, these fields get populated. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted since categories in Analytics correspond to sub-categories in the core system while parent categories in Analytics correspond to categories in the core system.

service tags

The tags associated with the service.

Tags can be created for a service in the Organization view. These will be comma separated values if there are multiple tags.

varchar(65535)

Service

If the item sold or refunded is a service, these fields get populated. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted since categories in Analytics correspond to sub-categories in the core system while parent categories in Analytics correspond to categories in the core system.

service has variant

This flag indicates whether the service has a variant. - True indicates that the service does have a variant. - False indicated that the service does not have a variant. - Not applicable.

A center has a service called 'Massage' which has two variants - '30 minute massage' and '60 minute massage'. This flag would be True for the service 'Massage; and it would be False for the services '30 minute massage' and '60 minute massage'.

varchar(14)

Service

If the item sold or refunded is a service, these fields get populated. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted since categories in Analytics correspond to sub-categories in the core system while parent categories in Analytics correspond to categories in the core system.

service is variant

This flag indicates whether the service is a variant. - True indicates that the service is a variant. - False indicates that the service is not a variant. - Not applicable

A center has a service called 'Massage' which has two variants - '30 minute massage' and '60 minute massage'. This flag would be False for the service 'Massage; and it would be True for the services '30 minute massage' and '60minute massage'.

Service

If the item sold or refunded is a service, these fields get populated. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted since categories in Analytics correspond to sub-categories in the core system while parent categories in Analytics correspond to categories in the core system.

is addon

This flag indicates whether the service is an add-on. - True indicates that the service is an add-on. - False indicates that the service is not an add-on.

boolean

Service

If the item sold or refunded is a service, these fields get populated. Services are grouped into categories which are further grouped into parent categories. This is slightly convoluted since categories in Analytics correspond to sub-categories in the core system while parent categories in Analytics correspond to categories in the core system.

is service inactive

This flag indicates whether the service is inactive. A service is considered inactive if it has been removed from the system. - True indicates that the service is inactive. - False indicates that the service is active.

Product

If the item sold or refunded is a product, these fields get populated. Products are grouped into categories which are further grouped into parent categories. This is slightly convoluted since categories in Analytics correspond to sub-categories in the core system and parent categories in Analytics correspond to categories in the core system.

product name

The name of the product.

varchar(256)

Product

If the item sold or refunded is a product, these fields get populated. Products are grouped into categories which are further grouped into parent categories. This is slightly convoluted since categories in Analytics correspond to sub-categories in the core system and parent categories in Analytics correspond to categories in the core system.

product category

The category of the product. This is setup as sub-category in core.

For a product 'Pink Mini Gloss Purse Set', category could be 'Lipstick', and parent category could be 'Cosmetics'.

Product

If the item sold or refunded is a product, these fields get populated. Products are grouped into categories which are further grouped into parent categories. This is slightly convoluted since categories in Analytics correspond to sub-categories in the core system and parent categories in Analytics correspond to categories in the core system.

product parent category

The parent category of the product. This is setup as category in core.

Product

If the item sold or refunded is a product, these fields get populated. Products are grouped into categories which are further grouped into parent categories. This is slightly convoluted since categories in Analytics correspond to sub-categories in the core system and parent categories in Analytics correspond to categories in the core system.

product business unit

The business unit to which the product belongs.

varchar(200)

Product

If the item sold or refunded is a product, these fields get populated. Products are grouped into categories which are further grouped into parent categories. This is slightly convoluted since categories in Analytics correspond to sub-categories in the core system and parent categories in Analytics correspond to categories in the core system.

product tags

The tags associated with the product.

Tags can be created for a product in the Organization view. These will be comma separated values if there are multiple tags.

varchar(65535)

Product

If the item sold or refunded is a product, these fields get populated. Products are grouped into categories which are further grouped into parent categories. This is slightly convoluted since categories in Analytics correspond to sub-categories in the core system and parent categories in Analytics correspond to categories in the core system.

product has variant

This flag indicates whether the product has a variant. - True indicates that the product has a variant. - False indicates that the product does not have a variant. - Not applicable.

A center has a product called 'Lavender shampoo' which has two variants - '150 ML shampoo' and '100 ML shampoo'. This flag would be True for the product 'Lavender shampoo; and it would be False for the products '150 ML shampoo' and '100 ML shampoo'.

boolean

Product

If the item sold or refunded is a product, these fields get populated. Products are grouped into categories which are further grouped into parent categories. This is slightly convoluted since categories in Analytics correspond to sub-categories in the core system and parent categories in Analytics correspond to categories in the core system.

consummable

This flag indicates whether the product can be consumed as part of a service. - True indicates that the product can also be a consumable. - False indicates that the product is not a consumable.

Product

If the item sold or refunded is a product, these fields get populated. Products are grouped into categories which are further grouped into parent categories. This is slightly convoluted since categories in Analytics correspond to sub-categories in the core system and parent categories in Analytics correspond to categories in the core system.

retail

This flag indicates whether the product can be sold as a retail product. - True indicates that the product can be sold as a retail product. - False indicates that the product cannot be sold as a retail product.

Product

If the item sold or refunded is a product, these fields get populated. Products are grouped into categories which are further grouped into parent categories. This is slightly convoluted since categories in Analytics correspond to sub-categories in the core system and parent categories in Analytics correspond to categories in the core system.

is product inactive

This flag indicates whether the product is inactive. A product is considered inactive if it has been removed from the system. - True indicates that the product is inactive. - False indicates that the product is active.

Membership

membership name

The name of the membership.

varchar(512)

Membership

If the item sold or refunded is a membership, these fields get populated.

membership category

The category of the membership.

varchar(200)

Membership

If the item sold or refunded is a membership, these fields get populated.

membership tags

The tags associated with the membership.

Tags can be created for a membership in the Organization view. These will be comma separated values if there are multiple tags.

varchar(65535)

Membership

If the item sold or refunded is a membership, these fields get populated.

membership type

The type of membership sold. This is usually Recurring, Non-Recurring or Set up.

Possible values: Recurring Non-Recurring Set up: This is populated for memberships which have a setup cost involved.

varchar(16)

Membership

If the item sold or refunded is a membership, these fields get populated.

membership recurring

This flag indicates whether the corresponding membership is a recurring membership. This is useful when the membership type is Set up. This field lets you know whether the set up was done for a recurring or non-recurring membership. - True indicates a recurring membership. - False indicates a non-recurring membership.

varchar(5)

Membership

If the item sold or refunded is a membership, these fields get populated.

membership credit amount

Amount credited to the eligible membership for the respective cycle.

This could be blank in some cases. E.g. When membership benefits are discounts on services, rather than actual credits.

float8

Package

If the item sold or refunded is a package or day package, these fields get populated.

package name

The name of the package.

varchar(512)

Package

If the item sold or refunded is a package or day package, these fields get populated.

package type

The type of the package. This is usually a day package, series package, or promo package.

Possible values: Day package: Combination of services that must be consumed in a single day. Series package: Combination of services that a guest can purchase and use over a period of time. Promo Package: Short term promotional packages that need to be consumed on a single day.

varchar(14)

Package

If the item sold or refunded is a package or day package, these fields get populated.

package category

The category to which the package belongs.

varchar(200)

Package

If the item sold or refunded is a package or day package, these fields get populated.

package businessunit

The business unit to which the package belongs.

Package

If the item sold or refunded is a package or day package, these fields get populated.

package tags

The tags associated with the package.

Tags can be created for a package in the Organization view. These will be comma separated values if there are multiple tags.

varchar(65535)

Package

If the item sold or refunded is a package or day package, these fields get populated.

is package inactive

This flag indicates whether the package is inactive. A package is considered inactive if it has been removed from the system. - True indicates that the package is inactive. - False indicates that the package is active.

boolean

Bundle

If the item sold is a bundle.

BundlePackageID

Helps you identify the bundle package (GUID). In case of multiple bundle packages, then ID remains same.

VARCHAR(36)

Bundle

If the item sold is a bundle.

BundlePackageNo

Helps you identify the number of bundle packages in a invoice.

INT

Gift card and prepaid card

If the item sold or refunded is a gift card or prepaid card, these fields get populated.

is giftcard

This flag indicates whether the card is a gift card or a prepaid card. - True indicates that the purchase of a gift card. - False indicates the purchase of a prepaid card.

Gift card and prepaid card

If the item sold or refunded is a gift card or prepaid card, these fields get populated.

giftcard code

The unique code of the gift or prepaid card.

varchar(800)

Gift card and prepaid card

If the item sold or refunded is a gift card or prepaid card, these fields get populated.

giftcard recipient name

The name of the recipient for whom the gift or prepaid card is purchased.

varchar(1024)

Gift card and prepaid card

If the item sold or refunded is a gift card or prepaid card, these fields get populated.

giftcard validity

The number of days for which the gift or prepaid card is valid.

integer

Gift card and prepaid card

If the item sold or refunded is a gift card or prepaid card, these fields get populated.

giftcard purchase price

The price at which the gift or prepaid card is sold.

A gift card/prepaid can be priced at $100 and carry a value of $200.

numeric(19,4)

Gift card and prepaid card

If the item sold or refunded is a gift card or prepaid card, these fields get populated.

giftcard value

The value assigned to the gift or prepaid card at the time of purchase.

Gift card and prepaid card

If the item sold or refunded is a gift card or prepaid card, these fields get populated.

one time use

This flag indicates if the gift or prepaid card can be used once or multiple times. - True indicates that the gift or prepaid card can be used only once. - False indicates that the gift or prepaid card can be used multiple times.

boolean

Gift card and prepaid card

If the item sold or refunded is a gift card or prepaid card, these fields get populated.

is giftcard inactive

This flag indicates whether the gift or prepaid card is inactive. A gift or prepaid card is considered inactive if it has been removed from the system. - True indicates that the gift or prepaid card is inactive. - False indicates that the gift or prepaid card is active.

Gift card and prepaid card

If the item sold or refunded is a gift card or prepaid card, these fields get populated.

is bonus giftcard

This flag indicates whether the gift card is a bonus gift card. - True indicates that it is a bonus gift card. - False indicates that it is not a bonus gift card.

Bonus gift cards are gift cards that are free as part of promotions.

Gift card and prepaid card

If the item sold or refunded is a gift card or prepaid card, these fields get populated.

promotion name

The name of the gift card promotion.

varchar(2048)

Gift card and prepaid card

If the item sold or refunded is a gift card or prepaid card, these fields get populated.

promotion code

The unique code assigned to the gift card promotion.

varchar(512)

Gift card and prepaid card

If the item sold or refunded is a gift card or prepaid card, these fields get populated.

promotion description

The description of the offer for the gift card promotion.

E.g. 'Purchase a 100$ giftcard and recieve a 10$ bonus gift card for free'

varchar(32000)

Gift card and prepaid card

If the item sold or refunded is a gift card or prepaid card, these fields get populated.

prmotion rule criteria

The rule based on which the gift card promotion is applicable. They are usually given based on either the price of the gift cards purchased, or the number of gift cards purchased.

If you have a gift card promotion 'Purchase a giftcard worth atleast $100 and get a giftcard worth $20 for free', the promotion rule criteria would be 'Total Price of Gift Card(s)'

varchar(2000)

Gift card and prepaid card

If the item sold or refunded is a gift card or prepaid card, these fields get populated.

promotion rule minimum value

Minimum purchase price of the gift card to be eligible for the free bonus gift card.

This is the 'Minimum Value' set in the bonus gift card promotion rules when you navigate to Marketing > Gift card promotions. If you have a gift card promotion - 'Purchase a gift card worth $100 and get a gift card worth $20 for free', the promotion rule minimum value would be $100.

numeric

Gift card and prepaid card

If the item sold or refunded is a gift card or prepaid card, these fields get populated.

promotion rule maximum value

Maximum purchase price of the gift card to be eligible for the free bonus gift card.

This is the 'Maximum Value' set in the bonus gift card promotion rules when you navigate to Marketing > Gift card promotions. If you have a gift card promotion - 'Purchase a gift card worth $100-$300 and get a gift card worth $20 for free', the promotion rule maximum value would be $300.

Gift card and prepaid card

If the item sold or refunded is a gift card or prepaid card, these fields get populated.

promotion rule bonus value

This is the value assigned to the bonus gift card.

Class or Workshop

If the sold or refunded item is a class or workshop, these fields are populated. Guests can register for either classes or workshops. An individual occurrence of a class is a session. Workshops can be divided into tracks that can be further divided into events, which are further divided into sessions.

session name

Name of the session for which the guest registered.

varchar(128)

Class or Workshop

If the sold or refunded item is a class or workshop, these fields are populated. Guests can register for either classes or workshops. An individual occurrence of a class is a session. Workshops can be divided into tracks that can be further divided into events, which are further divided into sessions.

session code

Unique code of the session for which the guest registered.

varchar(32)

Class or Workshop

If the sold or refunded item is a class or workshop, these fields are populated. Guests can register for either classes or workshops. An individual occurrence of a class is a session. Workshops can be divided into tracks that can be further divided into events, which are further divided into sessions.

class name

Name of the class corresponding to the session for which the guest registered.

varchar(128)

Class or Workshop

If the sold or refunded item is a class or workshop, these fields are populated. Guests can register for either classes or workshops. An individual occurrence of a class is a session. Workshops can be divided into tracks that can be further divided into events, which are further divided into sessions.

class code

Unique code of the class corresponding to the session for which the guest registered.

varchar(32)

Class or Workshop

If the sold or refunded item is a class or workshop, these fields are populated. Guests can register for either classes or workshops. An individual occurrence of a class is a session. Workshops can be divided into tracks that can be further divided into events, which are further divided into sessions.

workshop name

Name of the workshop for which the guest registered.

varchar(128)

Class or Workshop

If the sold or refunded item is a class or workshop, these fields are populated. Guests can register for either classes or workshops. An individual occurrence of a class is a session. Workshops can be divided into tracks that can be further divided into events, which are further divided into sessions.

workshop code

Unique code of the workshop for which the guest registered.

varchar(32)

Class or Workshop

If the sold or refunded item is a class or workshop, these fields are populated. Guests can register for either classes or workshops. An individual occurrence of a class is a session. Workshops can be divided into tracks that can be further divided into events, which are further divided into sessions.

track name

Name of the workshop track for which the guest registered.

varchar(128)

Class or Workshop

If the sold or refunded item is a class or workshop, these fields are populated. Guests can register for either classes or workshops. An individual occurrence of a class is a session. Workshops can be divided into tracks that can be further divided into events, which are further divided into sessions.

track code

Unique code of the workshop track for which the guest registered.

varchar(32)

Invoice

This group of fields detail out the invoice associated with the items.

invoice no

The unique identifier for the invoice within the center.

varchar(40)

Invoice

This group of fields detail out the invoice associated with the items.

invoice id

The unique identifier for the invoice within the organization.

varchar(36)

Invoice

This group of fields detail out the invoice associated with the items.

invoice item id

The unique identifier for each line item within the invoice.

Invoice

This group of fields detail out the invoice associated with the items.

invoice source

The source from where the invoice was created. 

MMS: Invoices created through the core system (i.e abc.zenoti.com) PoS: Invoices created through PoS screen of the core system Mobile: Invoices created through the CMA (Customer Mobile App) Web: Invoices created through the Webstore Imports: Invoices created through bulk data import Offline: Invoices created through the offline app Dunning: Invoices created through scheduled membership/package payments Auto Collection: Invoices created through the payment mode called 'Auto Pay' Take5: Invoices created through the 'Take5 mobile app' MobilePosAndroid: Invoices created through the Therapist Android App MobilePosiOS: Invoices created through the Therapist iOS App Shopify: Invoices created through 'Shopify' Queue: Appointment booked from the queue-Admin Kiosk: Appointment booked from the Guest-Kiosk: In-store KioskCMA - Appointment booked from the Guest-Kiosk : CMA KioskWeb - Appointment booked from Guest-Kiosk : Webstore

varchar(21)

Invoice

This group of fields detail out the invoice associated with the items.

invoice status

This indicates whether the invoice is open or closed.

varchar(14)

Invoice

This group of fields detail out the invoice associated with the items.

invoice closed date and time

The date and time at which the invoice was closed.

This value is not populated if the invoice is not closed.

timestamp

Invoice

This group of fields detail out the invoice associated with the items.

invoice closed date

The date on which the invoice was closed.

date

Invoice

This group of fields detail out the invoice associated with the items.

invoice item created date

The date on which the invoice item was created.

Invoice

This group of fields detail out the invoice associated with the items.

invoice item created date and time

The date and time at which the invoice item was created.

timestamp

Invoice

This group of fields detail out the invoice associated with the items.

sale date

For Service item type, this is the date and time at which the service was performed. For other item types, this is the date and time at which the item was added to the invoice.

date

Invoice

This group of fields detail out the invoice associated with the items.

sale date and time

For Service item type, this is the date and time at which the service was performed. For other item types, this is the date and time at which the item was added to the invoice.

timestamp

Invoice

This group of fields detail out the invoice associated with the items.

no sale comments

The comments that the front desk staff enters when the sale of an intended service, membership, or package does not take place.

E.g. A guest comes in for a paid consulation for a weight loss program. The consultant may not recommend that the guest undertake the program due to medical conditions. In such a case, the front desk may enter a comment such as: "Guest has a medical condition - the medical consultant advises against taking this program." Such comments appear in the "No Sale Comments" column.

varchar(65535)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

transaction id

A unique non-blank identifier for each transaction. For example, if an invoice is paid by using two swipes of a credit card, then two unique transaction IDs get associated with the invoice. There is an exception in case of group invoices. Even if they are paid through a single transaction, the 'transaction ID' is different against each of the group invoices.

Transaction ID shows up only when a payment is made.

varchar(36)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

payment no

A unique identifier for each transaction. This could be blank in some cases. This maps to the payment number in the invoice in the core system.

varchar(80)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

receipt no

A receipt number generated for an invoice after the invoice is closed. It is associated with the invoice.

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

factcollectionwid

A unique identifier for every collection at the most granular level in this table. This is generated in Analytics, it does not exist in the core system.

bigint

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

factcollectionid

A system-generated unique identifier for each record in the collections data source. This is generated within Analytics.

integer

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

payment date

The date on which the payment was made.

date

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

payment date and time

The date and time at which the payment was made.

timestamp

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

payment type

The mode of payment.

Possible values: - Card: Through a credit card - Cash: Through cash - Check: Through a cheque - Packageusage: Through redemption of a package - Membershipusage: Payment done using benefits of a membership - MembershipCredit: Payment done using the credit value available through a membership - LP: Through redemption of loyalty points - GC: Through redemption of a giftcard - PPC: Through redemption of a prepaid card - Custom: Through a custom payment

varchar(100)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

payment option type

For card payments, the type of card gets populated here. For cheque payments, the name of the cheque gets populated here.

For Card, the following are payment option types: - VISA - DEBIT CARD - DISCOVER - CHECK - CC - DINERS CARD - AMEX - UNIONPAY - DISCOVER CARD For Cheque, the following are payment option types: - RBS - BANK OF AMERICA

varchar(40)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

credit card approval number

For credit card payments, the approval number for the credit card transaction gets populated here.

varchar(256)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

credit card last four digits

For credit card payments, the last four digits of the credit card get populated here.

varchar(32)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

cctransactionfee

For credit card payments, the transaction fee collected gets populated here. This gets duplicated for each transaction in the invoice, it does not get apportioned for each line item in the invoice. In case of group invoices, the transaction fee is duplicated across the group invoices and is not apportioned for each invoice.

varchar(80)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

cc transaction id

A unique identifier for each 'cctransactionfee' collected. In case of group invoices which are paid through a single cc transaction, the 'cc transaction ID' against all the group invoices is the same.

varchar(36)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

cctransactionstatus

Transaction status tells you if the transaction has been successful or not

nvarchar(128)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

custom payment name

For custom payments, the name of the custom payment method gets populated in the custom payment name field. If the appropriate option isn't there, the user can enter the information in the Custom payment additional details field.

ZenotiCustom ZenotiCustomPayment Groupon

varchar(400)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

custom payment additional details

varchar(65535)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

consider in financials

This flag indicates whether the custom payment method should be considered in the sales or collections reports. This is a flag in the core system under Admin > Categories > Custom Payments. - True indicates that the custom payment method should be considered in the financial reports. - False indicates that the custom payment method should not be considered in the financial reports.

varchar(5)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

membership center name

If the payment was made using a membership, the center from where the membership was purchased gets populated here.

This is populated only for payments made using a membership.

varchar(200)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

package center name

If the payment was made using a package, the center from where the package was purchased gets populated here.

This is populated only for payments made using a package.

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

is redeption instrument gc

This flag indicates whether the payment was made using a gift card or a prepaid card. - True indicates that the payment was made using a gift card. - False indicates that the payment was made using a prepaid card. - Null indicates that neither a gift card nor a prepaid card was used.

This is populated only for payments made using a gift card or a prepaid card.

boolean

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

gift card code

The unique code of the gift or prepaid card used to make the payment.

varchar(256)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

giftcard center name

For payments made using a gift or prepaid card, the center from where it was purchased gets populated here.

This is populated only for payments made using a giftcard/ prepaid card.

varchar(200)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

is redemption instrument bonus giftcard

This flag indicates whether the gift card used is a bonus gift card. - True indicates that it is a bonus gift card. - False indicates that it is not a bonus gift card.

Bonus gift card is the card that you get for free as a part of a promotion.

boolean

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

redemption gc promotion name

For the bonus gift card used, this field contains the name of the promotion associated with the bonus gift card at the time of its purchase.

varchar(2048)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

redemption gc promotion code

For the bonus gift card used, this field contains the unique code associated with the bonus gift card at the time of its purchase.

varchar(512)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

redemption gc promotion description

For the bonus gift card used, this field contains the description of the offer associated with the bonus gift card at the time of its purchase.

E.g. 'Purchase a 100$ giftcard and recieve a 10$ bonus gift card for free'

varchar(32000)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

redemption gc prmotion rule criteria

For the bonus gift card used, this is the rule based on which the gift card promotion was applicable at the time of its purchase. They are usually given based on either the price of the gift cards purchased, or the number of gift cards purchased.

If you have a gift card promotion 'Purchase a giftcard worth atleast $100 and get a giftcard worth $20 for free', the promotion rule criteria would be 'Total Price of Gift Card(s)'

varchar(2000)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

redemption gc promotion rule minimum value

For the bonus gift card used, this is the minimum gift card purchase price it was associated to at the time of its purchase.  

This is the 'Minimum Value' set in the bonus gift card promotion rules when you navigate to Marketing > Gift card promotions. If you have a gift card promotion - 'Purchase a gift card worth $100 and get a gift card worth $20 for free', the promotion rule minimum value would be $100.

numeric

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

redemption gc promotion rule maximum value

For the bonus gift card used, this is the maximum gift card purchase price it was associated to at the time of its purchase.  

This is the 'Maximum Value' set in the bonus gift card promotion rules when you navigate to Marketing > Gift card promotions. If you have a gift card promotion - 'Purchase a gift card worth $100-$300 and get a gift card worth $20 for free', the promotion rule maximum value would be $300.

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

redemption gc promotion rule bonus value

For the bonus gift card used, this is the value assigned to the gift card.

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

payment mode number

For gift card or prepaid card payments, this populates the 'giftcarduserid'. For membership payments, this populates 'usermembershipid'. For package payments, this populates 'packageuserid'.

varchar(156)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

amount type

The type of amount. We distinguish between the total amount that was supposed to be collected and the amount that was collected. Possible values: - ToBeCollectedAmount: Total amount to be collected as per invoice. - ToBeCollectedTax: Total tax to be collected as per invoice. - PaymentWithoutTax: Amount received as payment not including tax as per invoice. - TaxCollected: Payment received as tax as per invoice. - RedemptionWithoutTax - MembershipUsage: Amount received as payment using a membership. - PackageUsage: Amount received as payment using a package. - Tips - SSG - EnvironmentalFee Tips, SSG and EnvironmentalFee are recorded at the invoice level. They are not apportioned to every line item in the invoice. Use the amount type and amount fields together to infer how much has been collected, how much is left to be collected, etc.

Say a service worth $100 is sold and the tax for the service is $10. Say, the guest made a partial payment of $55, then four rows would be seen for this invoice in data: ToBeCollectedAmount is 100 ToBeCollectedTax is 10 PaymentWithoutTax is 50 TaxCollected is 5

varchar(100)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

amount

The actual amount against the corresponding amount type. This is a numerical value. Use the amount type and amount fields together to infer how much has been collected, how much is left to be collected, etc.

float8

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

adjusted amount

When the payment is made with a liability instrument whose price is different from the value associated with it, this field shows you the value realized by the business.

If a service worth $100 is paid using $50 cash and $50 gift card whose price is $25 and value is $50, then: Amount: $50 + $50 = $100 Adjusted Amount: $50 + $25 = $75

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

amount by payment

If the payment was made using the benefits available in a membership, this is the invoice value of the service performed. For other types of payments, this is the value from the 'amount' field.

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

dispute date

If a dispute was raised, this is the date on which it was raised.

date

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

dispute date time

If a dispute was raised, this is the date and time at which it was raised.

timestamp

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

dispute reason

The reason for the dispute.

duplicate subscription_canceled credit_not_processed fraudulent general product_not_received product_unacceptable unrecognized

varchar(1028)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

dispute respond by date

The date on which the dispute was actioned upon.

date

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

dispute respond by date time

The date and time at which the dispute was actioned upon.

timestamp

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

dispute status

The status of the dispute.

warning_closed lost under_review won needs_response Evidence_Saved warning_needs_response warning_under_review dispute

varchar(512)

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

dispute amount

The amount that is being disputed by the customer.

float8

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

dispute fee

The processing fee that the customer must pay for raising the dispute.

Payment

This group of fields details out how the item was paid for - amount, type, mode etc.

dispute charge back amount

The amount that is charged to the business after the dispute is resolved.

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

employee first name

The first name of the employee marked as primary 'Sold by' for the corresponding item.

varchar(160)

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

employee middle name

The middle name of the employee marked as primary 'Sold by' for the corresponding item.

varchar(128)

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

employee last name

The last name of the employee marked as primary 'Sold by' for the corresponding item.

varchar(256)

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

employee - code

The unique code of the employee marked as primary 'Sold by'.

varchar(128)

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

employee mobile phone

The mobile number of the employee marked as primary 'Sold by'.

varchar(64)

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

employee last date

The date on which the employee who is marked as the 'primary sold by' stopped working for the organization.

timestamp

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

employee gender

The gender of the employee marked as primary 'Sold by'.

Possible values: - Male - Female - Not applicable

varchar(14)

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

employee job name

The job name associated with the employee marked as primary 'Sold by'.

Therapist, Manager, Aesthetician etc.

varchar(1020)

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

employee job code

The unique code associated with the job of the employee marked as primary 'Sold by'.

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

employee tags

Tags associated with the employee marked as primary 'Sold by'.

varchar(65535)

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

is employee inactive

This flag indicates whether the primary 'Sold by' employee is inactive. An employee is considered inactive if they have been removed from the system. - True indicates that the employee is inactive. - False indicates that the employee is active.

boolean

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

employee additional field 2

The details in 'Additional Field2' for the employee marked as primary 'Sold by'.

Additional Field2' can be entered for an employee when you navigate to 'Employee'>'Manage Employees'>'General' in Zenoti.

varchar(8000)

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

employee additional field 1

The details in 'Additional Field1' for the employee marked as primary 'Sold by'.

Additional Field1' can be entered for an employee when you navigate to 'Employee'>'Manage Employees'>'General' in Zenoti.

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

closed by employee first name

The first name of the employee who closed the invoice.

varchar(160)

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

closed by employee middle name

The middle name of the employee who closed the invoice.

varchar(128)

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

closed by employee last name

The last name of the employee who closed the invoice.

varchar(256)

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

closed by employee - code

The unique code of the employee who closed the invoice.

varchar(128)

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

closed by employee mobile phone

The mobile number of the employee who closed the invoice.

varchar(64)

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

closed by employee gender

The gender of the employee who closed the invoice.

Possible values: - Male - Female - Not applicable

varchar(14)

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

closed by employee job name

The job name associated with the employee who closed the invoice.

Therapist, Manager, Aesthetician etc.

varchar(1020)

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

closed by employee is inactive

This flag indicates whether the employee who closed the invoice is inactive. An employee is considered inactive if they have been removed from the system. - True indicates that the employee is inactive. - False indicates that the employee is active.

boolean

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

closed by employee additional field 1

The details in 'Additional Field1' for the employee who closed the invoice.

Additional Field1' can be entered for an employee when you navigate to 'Employee'>'Manage Employees'>'General' in Zenoti.

varchar(8000)

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

closed by employee additional field 2

The details in 'Additional Field2' for the employee who closed the invoice.

Additional Field2' can be entered for an employee when you navigate to 'Employee'>'Manage Employees'>'General' in Zenoti.

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

closed by start date

The date on which the employee who closed the invoice started working in the organization.

timestamp

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

closed by last date

The date on which the employee who closed the invoice stopped working in the organization.

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

closed by employee last date

The date on which the employee who closed the invoice stopped working in the organization. 

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

relationship manager first name

The first name of the employee who is assigned as the Relationship Manager or Primary Consultant to a guest.

An employee can be set as a 'Relationship Manager' by adding his/ her name as 'Primary Employee' in the Guest profile.

varchar(160)

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

relationship manager last name

The last name of the employee who is assigned as the Relationship Manager or Primary Consultant to a guest.

varchar(256)

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

relationship manager employee - code

The employee code of the employee who is assigned as the Relationship Manager or Primary Consultant to the guest.

varchar(128)

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

relmgr userwid

Unique identifier of the relationship manager to the guest. This is generated in Analytics.

bigint

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

employee code

DO NOT USE- THIS FIELD IS BEING DEPRECATED

varchar(128)

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

closed by employee code

Employee

This group of fields describes the attributes of three types of employees: 1. 'Sold by' employee: Each item in an invoice is associated to an employee who primarily sold the item. For products, packages, memberships, gift cards it is usually the employee who creates the invoice who is marked as the 'sold by' employee. For services, it is usually the service provider who is marked as the 'sold by' employee (for appointments booked by front desk). For bookings made on the Webstore, the guest is marked as the 'sold by' employee. This is editable in the invoice. 2. 'Closed by' employee: The employee who closes the invoice. 3. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

relationship manager user code