Sales data model

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center in which the invoice is created.

organization name

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 the center in which the invoice is created.

organization account name

Domain name of the organization in Zenoti.

If you use the https://massagespa.zenoti.com URL to log in to Zenoti, 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 the center in which the invoice is created.

center name

Center in which the invoice is created.

varchar(128)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center in which the invoice is created.

zone name

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 the center in which the invoice is created.

center time zone

Time zone of the center.

varchar(4096)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center in which the invoice is created.

center city

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 the center in which the invoice is created.

center state name

State in which the center is located.

varchar(1024)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center in which the invoice is created.

country name

Country in which the center is located.

varchar(1024)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center in which the invoice is created.

center zip

Zip code of the center's location.

varchar(32)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center in which the invoice is created.

operating center

Flag that indicates whether the center is operational: - True: Operational - False: Not operational

boolean

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center in which the invoice is created.

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 the center in which the invoice is created.

center wid

Unique identifier of the center. This is generated in Analytics; it 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 the center in which the invoice is created.

minutes to add

Number of minutes that need to be added to UTC time to calculate the current time at the center. Timestamps that are generated by Tableau (for example, if you use filters such as Today and Tomorrow) are in UTC. As a result, you need this field to find out the current center time. Note: You do not need this field for timestamps that are directly in the data source - these timestamps are already in 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 the center in which the invoice is created.

center company name

Name with which the center is registered.

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

varchar(200)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center in which the invoice is created.

is center franchise

Flag that indicates whether the center is a franchisee. - True: Franchisee -False: 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 the center in which the invoice is created.

center cstn number

Central Sales Tax (CST) number of the center.

varchar(80)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center in which the invoice is created.

center tin number

Taxpayer’s Identification (TIN) number of the center.

varchar(80)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center in which the invoice is created.

center tot number

Transient Occupancy Tax (TOT) number of the center.

varchar(80)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center in which the invoice is created.

center service tax number

Service Tax number of the center.

varchar(80)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center in which the invoice is created.

center vat number

Value Added Tax Identification (VAT) number of the center.

varchar(80)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center in which the invoice is created.

center luxary tax number

Luxury Tax number of the center.

varchar(80)

Center, Zone, Organization

An organization can be divided into zones, which can be further divided into centers. Here, we refer to the center in which the invoice is created.

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 the center in which the invoice is created.

etllastupdatedby

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

varchar(50)

Item

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

item type code

Type of item sold or refunded. An item is usually a service, product, membership, package, gift card, prepaid card, or class.

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

varchar(100)

Item

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

item name

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

This is not populated for Class item types. Refer to the fields in the Class and Workshop section.

varchar(512)

Item

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

item code

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

This is not populated for Class item types. Refer to the fields in the Class and Workshop section.

varchar(256)

Item

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

item tags

Tags associated with the item.

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

varchar(65535)

Item

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

businessunit

Business unit to which the item belongs.

varchar(65535)

Item

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

is item inactive

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

boolean

Service

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

service name

Name of the service.

varchar(512)

Service

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

service category

Category of the service. This is set up as Sub-category in core.

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

varchar(256)

Service

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

service parent category

Parent category of the service. This is set up as Category in core.

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

varchar(256)

Service

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

service length

Ideal time taken to complete a service (in minutes), as set up in Zenoti

integer

Service

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

service businessunit

Business unit to which the service belongs.

varchar(200)

Service

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

service tags

Tags associated with the service.

Tags can be created for a service in Organization view. If there are multiple tags, they will be comma-separated values.

varchar(65535)

Service

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

service has variant

Flag that indicates whether the service has a variant. - True: Service has a variant - False: Service does not have a variant - Not Applicable

A center has a service called Massage that has 2 variants: 30 minute massage and 60 minute massage. This flag would be True for the Massage service; it would be False for the 30 minute massage and 60 minute massage services.

varchar(14)

Service

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

service is variant

Flag that indicates whether the service is a variant. - True: Service is a variant - False: Service is not a variant - Not Applicable

A center has a service called Massage that has 2 variants: 30 minute massage and 60 minute massage. This flag would be False for the Massage service; it would be True for the 30 minute massage and 60 minute massage services.

varchar(14)

Service

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

is addon

Flag that indicates whether the service is an add-on. - True: Service is an add-ont - False: Service is not an add-on

boolean

Service

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

is service inactive

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

boolean

Service

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

service internal cost

Internal cost that a center incurs for a service.

This is the value that is entered as Cost to Center when a service is created in Zenoti.

numeric(19,4)

Service

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

equipment name

Name of the equipment that is associated with a service.

Hot Stone Warmer, Tanning machine, Blow Dryer, etc.

varchar(1024)

Service

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

equipment capacity

Capacity of the equipment that is associated with a service.

integer

Service

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

is equipment active

Flag that indicates whether the equipment is active. An equipment is considered inactive if it has been removed from the system. - True: Equipment is active - False: Equipment is inactive

boolean

Service

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

resource name

Name of the resource associated with the service.

Room 1, Room 2, etc.

varchar(128)

Service

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

resource code

Unique code of the resource associated with the service.

varchar(128)

Service

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

resource type name

Type of the resource associated with the service.

varchar(128)

Service

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

resource capacity

Capacity of the resource associated with the service.

integer

Service

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

room category name

Category of the room associated with the service.

varchar(1000)

Product

If the item sold or refunded is a product, these fields get populated. Products are grouped into categories that are further grouped into parent categories. This is slightly convoluted because 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

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 that are further grouped into parent categories. This is slightly convoluted because categories in Analytics correspond to sub-categories in the core system and parent categories in Analytics correspond to categories in the core system.

product code

Unique code associated with the product.

varchar(512)

Product

If the item sold or refunded is a product, these fields get populated. Products are grouped into categories that are further grouped into parent categories. This is slightly convoluted because 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

Category of the product. This is set up as sub-category in core.

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

varchar(256)

Product

If the item sold or refunded is a product, these fields get populated. Products are grouped into categories that are further grouped into parent categories. This is slightly convoluted because 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

Parent category of the product. This is set up as category in core.

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

varchar(256)

Product

If the item sold or refunded is a product, these fields get populated. Products are grouped into categories that are further grouped into parent categories. This is slightly convoluted because 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

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 that are further grouped into parent categories. This is slightly convoluted because 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

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 that are further grouped into parent categories. This is slightly convoluted because 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

Flag that indicates whether the product has a variant. - True: Product has a variant - False: Product does not have a variant - Not Applicable

A center has a product called 'Lavender shampoo' that has 2 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 that are further grouped into parent categories. This is slightly convoluted because categories in Analytics correspond to sub-categories in the core system and parent categories in Analytics correspond to categories in the core system.

consummable

Flag that indicates whether the sold product sold can be consumed as part of a service. - True: Product can also be a consumable - False: Product is not a consumable

boolean

Product

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

retail

Flag that indicates whether the sold product can be sold as a retail product. - True: Product can be sold as retail - False: Product cannot be sold as retail

boolean

Product

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

product volume per item

Per item volume of the sold product. For example, if the sold product is a 150 ml shampoo, this field would display '150'. The unit of the volume is recorded in the 'product volume type name' field.

float(8)

Product

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

product volume type name

Unit of the volume populated in the 'product volume per item' field. For example, if the product sold is a 150 ml shampoo, this field would display 'ml'.

varchar(36)

Product

If the item sold or refunded is a product, these fields get populated. Products are grouped into categories that are further grouped into parent categories. This is slightly convoluted because 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

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

boolean

Membership

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

membership name

Name of the membership.

varchar(512)

Membership

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

membership category

Category of the membership.

varchar(200)

Membership

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

membership type

Type of the membership. Possible values: - Recurring - Non-Recurring - Setup Membership: This is populated for memberships that have setup involved.

varchar(200)

Membership

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

membership recurring

Flag that indicates whether the corresponding membership is a recurring membership. This is useful when the membership type is Setup. This field lets you know whether the set up was done for a recurring or non-recurring membership. - True: Recurring membership - False: Non-recurring membership

varchar(5)

Membership

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

membership tags

Tags associated with the membership.

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

varchar(65535)

Membership

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

membership credit amount

Amount credited to the eligible membership for the respective cycle.

This could be blank in some cases.For example, when membership benefits are discounts on services, rather than actual credits.

float(8)

Membership

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

is downgrade membership

If a membership is cancelled and a new membership is purchased on the same day and the payment made to the new membership is lower than that of the old membership, it is considered as a downgrade membership.

Note: Do not use this field. It is relevant for very specific scenarios only.

varchar(100)

Membership

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

is upgrade membership

If a membership is cancelled and a new membership is purchased on the same day and the payment made to the new membership is higher than that of the old membership, it is considered as an upgrade membership.

Note: Do not use this field. It is relevant for very specific scenarios only.

varchar(100)

Package

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

package name

Name of the package.

varchar(512)

Package

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

package code

Unique code associated with the package.

varchar(512)

Package

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

template package versionid

Unique identifier associated to each template version of the package.

varchar(70)

Package

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

package type

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

varchar(14)

Package

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

package category

Category to which the package belongs.

varchar(200)

Package

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

package businessunit

Business unit to which the package belongs.

varchar(200)

Package

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

package tags

Tags associated with the package.

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

varchar(65535)

Package

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

is package inactive

Flag that indicates if the package is inactive. A package is considered inactive if it has been removed from the system. - True: Package is inactive - False: Package is active

boolean

Bundle

If the sold item 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 sold item is a bundle

BundlePackageNo

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

INT

Gift card and Prepaid card

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

is giftcard

Flag that indicates whether the card is a gift card or a prepaid card. - True: Purchase of a gift card. - False: Purchase of a prepaid card.

boolean

Gift card and Prepaid card

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

giftcard code

Unique code of the gift card or prepaid card.

varchar(256)

Gift card and Prepaid card

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

giftcard recipient name

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

varchar(1024)

Gift card and Prepaid card

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

giftcard validity

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

integer

Gift card and Prepaid card

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

giftcard purchase price

Price at which the gift card or prepaid card is sold.

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

numeric(19,4)

Gift card and Prepaid card

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

giftcard value

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

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

numeric(19,4)

Gift card and Prepaid card

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

one time use

Flag that indicates whether the gift card or prepaid card can be used once or multiple times. - True: Gift card or prepaid card can be used only once. - False: Gift card or prepaid card can be used multiple times.

boolean

Gift card and Prepaid card

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

is giftcard inactive

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

boolean

Gift card and Prepaid card

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

gift card template name

Name of the gift card template used to create the corresponding gift card.

varchar(1024)

Gift card and Prepaid card

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

gift card template description

Description of the gift card template used to create the corresponding gift card.

varchar(8192)

Gift card and Prepaid card

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

is bonus giftcard

Flag that indicates whether the gift card is a bonus gift card. - True: Bonus card - False: Not Bonus card

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

boolean

Gift card and Prepaid card

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

promotion name

Name of the gift card promotion. This is populated if applicable.

varchar(2048)

Gift card and Prepaid card

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

promotion code

Unique code assigned to the gift card promotion.

varchar(512)

Gift card and Prepaid card

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

promotion description

Description of the offer for the gift card promotion.

For example, 'Purchase a 100$ giftcard and recieve a 10$ bonus gift card for free.'

varchar(32000)

Gift card and Prepaid card

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

prmotion rule criteria

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 sold or refunded item is a gift card or prepaid card, these fields are 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 go 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(19,4)

Gift card and Prepaid card

If the sold or refunded item is a gift card or prepaid card, these fields are 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 go 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.

numeric(19,4)

Gift card and Prepaid card

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

promotion rule bonus value

Value assigned to the bonus gift card.

numeric(19,4)

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)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest first name

First name of the guest.

varchar(160)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest middle name

Middle name of the guest.

varchar(128)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest last name

Last name of the guest.

varchar(256)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

user wid

Unique identifier for the guest. This is generated in analytics, it does not exist in the core system.

bigint

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

user id

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 bought the item in the invoice.

guest code

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

varchar(128)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest city

City to which the guest belongs.

varchar(128)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest state

State to which the guest belongs.

varchar(4096)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest country name

Country to which the guest belongs.

varchar(4096)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest zipcode

Zipcode of the guest's address.

varchar(128)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest address 1

Guest's address 1 details.

varchar(2048)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest address 2

Guest's address 2 details.

varchar(2048)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest email

Guest's email ID.

varchar(256)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest mobile phone

Guest's mobile number.

varchar(64)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest home phone

Guest's home phone number.

varchar(64)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest phone code

Country code of the guest's phone number.

integer

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest gender

Guest's gender.

varchar(14)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest dob

Guest's date of birth.

timestamp without time zone

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest anniversary date

Guest's marriage anniversary.

timestamp without time zone

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest type name

Indicator of whether the guest is indeed a guest or an employee.

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 bought the item in the invoice.

guest tags

Tags associated with the guest.

Tags can be set up 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 bought the item in the invoice.

is guest inactive

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

boolean

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest email state

Staus of the guest email based on email delivery status.

Possible values: - 1: notifications will go. - 2: notifications will not go. - 3: Transient. - 0: This is to ensure that emails are not sent to addresses that might bounce.

integer

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest base center

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

varchar(256)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

user creation date

Date on which the guest's profile was created.

timestamp without time zone

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest referral source

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 bought the item in the invoice.

referred by first name

First name of the person who referred the guest.

varchar(160)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

referred by last name

Last name of the person who referred the guest.

varchar(256)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

referred by user code

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 bought the item in the invoice.

referred by guestid

User ID of the person who referred the guest.

varchar(36)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

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 bought the item in the invoice.

guest receive marketing email

A flag that indicates whether the guest opted for marketing emails. - True: Opted. - False: Not opted.

boolean

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest receive marketing sms

A flag that indicates whether the guest opted for marketing SMSs. - True: Opted. - False: Not opted.

boolean

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest receive transactional email

A flag that indicates whether the guest opted for transactional emails. - True: Opted. - False: Not opted.

boolean

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest receive transactional sms

A flag that indicates whether the guest opted for transactional SMSs. - True: Opted. - False: Not opted.

boolean

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest purchased service before

Flag that indicates whether the guest purchased a service with 'appointment status' as 'Closed' on any date prior to the current invoice sale date or not. - True: Purchased service before. - False: Did not purchase service before.

This field is populated as 'False' by default if the current invoice is invalid.

varchar(5)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest purchased product before

Flag that indicates whether the guest purchased a product with 'invoice status' as 'Closed Invoice' on any date prior to the current invoice sale date or not. - True: Purchased product before. - False: Did not purchase product before.

This field is populated as 'False' by default if the current invoice is invalid.

varchar(5)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest purchased package before

Flag that indicates whether the guest purchased a package with 'invoice status' as 'Closed Invoice' on any date prior to the current invoice sale date or not. - True: Purchased package before. - False: Did not purchase package before.

This field is populated as 'False' by default if the current invoice is invalid.

varchar(5)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest purchased membership before

Flag that indicates whether the guest purchased a membership with 'invoice status' as 'Closed Invoice' on any 'invoice date in center' prior to the current invoice sale date or not. - True: Purchased membership before. - False: Did not purchase membership before.

This field is populated as 'False' by default if the current invoice is invalid.

varchar(5)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest purchased day package before

Flag that indicates whether the guest purchased a day package with 'invoice status' as 'Closed Invoice' on any date prior to the current invoice sale date or not. - True: Purchased day package before. - False: Did not purchase day package before.

This field is populated as 'False' by default if the current invoice is invalid.

varchar(5)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest purchased prepaid/gift card before

Flag that indicates whether the guest purchased a prepaid card or gift card with 'invoice status' as 'Closed Invoice' on any date prior to the current invoice sale date or not. - True: Purchased prepaid card or gift card before. - False: Did not purchase prepaid card or gift card before.

This field is populated as 'False' by default if the current invoice is invalid.

varchar(5)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest purchased class before

Flag that indicates whether the guest purchased a class with 'invoice status' as 'Closed Invoice' on any date prior to the current invoice sale date or not. - True: Purchased class before. - False: Did not purchase class before.

This field is populated as 'False' by default if the current invoice is invalid.

varchar(5)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest paid membership freeze fee before

Flag that indicates whether the guest paid membership freeze fee with 'invoice status' as 'Closed Invoice' on any date prior to the current invoice sale date or not. - True: Paid membership freeze fee before. - False: Did not pay membership freeze fee before.

For invalid invoices, this is populated as 'False' by default.

varchar(5)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest paid room charges before

Flag that indicates whether the guest paid room charges with 'invoice status' as 'Closed Invoice' on any date prior to the current invoice sale date or not. - True: Paid room charges before. - False: Did not pay room charges before.

For invalid invoices, this is populated as 'False' by default.

varchar(5)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

guest member status

Membership status of the guest as a primary member. If the guest is associated with a membership as a primary member, the status of the membership is populated here. If the guest is associated with multiple memberships as a primary member, the status is populated as per a precedence order. - If a membership is actually sold on the corresponding sale date (when 'membership sold in invoice' is marked as True), the membership status as of the corresponding sale date is considered. Otherwise, the membership status as of the day prior to the corresponding sale date is considered. If the guest was never associated with any membership as a primary member, this field populates 'Never a member before'. The following list describes the precedence order from highest priority on top to lowest priority at the bottom: Possible values: - Active - Frozen - Suspended - Prior Member with service credits - Prior Member without service credits - Never a member before - Not applicable

varchar(100)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

Add On Guest Membership Status

Membership status of the guest as an add-on member. If the guest is associated with a membership as an add-on member, the status of the membership is populated here. If the guest is associated with multiple memberships as an add-on member, the status is populated as per a precedence order. - If a membership is actually sold on the corresponding sale date (when 'membership sold in invoice' is marked as True), the membership status as of the corresponding sale date is considered. Otherwise, the membership status as of the day prior to the corresponding sale date is considered. If the guest was associated with a membership as an add-on member in the past but was then removed from the membership, this field populates 'Add-on member before but not currently'. In this case, the status of the membership does not matter. If the guest was never associated with any membership as an add-on member, this field populates 'Never been an add-on member'. The following list describes the precendence order from highest priority on top to lowest priority at the bottom: Possible values: - Active - Frozen - Suspended - Prior Member with service credits - Prior Member without service credits - Add-on member before but not currently - Never been an add-on member - Not applicable

varchar(100)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

last sale date

Sale date of the previous visit of the guest. Recurring invoices, refund invoices, voided invoices, cancelled, and no-show appointments are not considered for the previous visit. The invoice status can be either open or closed for the previous visit. This field does not get populated if the current invoice item is a refund, recurring, or invalid invoice item.

date

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

last service sale date

Sale date of the previous appointment with 'appointment status' = 'Closed' or 'Confirmed' or 'Checkin' or 'Open'. The invoice status of the previous appointment does not matter. This field only gets populated if the current invoice item is of service item type.

date

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

next sale date

Sale date of the next visit of the guest. Recurring invoices, refund invoices, voided invoices, cancelled, and no-show appointments are not considered for the next visit. The invoice status can be either open or closed for the next visit. This field does not get populated if the current invoice item is a refund, recurring, or invalid invoice item.

date

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

next service sale date

Sale date of the next appointment with 'appointment status' = 'Closed' or 'Confirmed' or 'Checkin' or 'Open'. The invoice status of the next appointment does not matter. This field only gets populated if the current invoice item is of service item type.

date

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

days from last visit

Difference in days between the current visit and last visit. It is the difference between 'sale date' and 'last sale date'.

bigint

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

days to next visit

Difference in days between the current visit and next visit. It is the difference between 'sale date' and 'next sale date'.

bigint

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

follow up

Note: Do not use this field. It is relevant for very specific scenarios only.

Note: Do not use this field. It is relevant for very specific scenarios only.

integer

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

no sale comments

Comments that the front desk staff enters in the guest's profile when the sale of an intended service, membership, or package does not take place.

Note: Do not use this field. It is relevant for very specific scenarios only.

varchar(65535)

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

is tax exempted

Flag that indicates whether tax is exempted for the guest. - True: Tax is exempted. - False: Tax is not exempted.

smallint

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

first guest status

Note: Do not use this field. It is being deprecated.

Note: Do not use this field. It is being deprecated.

smallint

Guest

These fields detail the attributes of the guest who bought the item in the invoice.

loyalty tier name

Loyalty tier to which the guest belongs as of the 'etllastupdatedon' timestamp.

varchar(2014)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

employee first name

First name of the employee marked as primary 'Sold by' for the corresponding invoice item.

varchar(160)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

employee middle name

Middle name of the employee marked as primary 'Sold by' for the corresponding invoice item.

varchar(128)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

employee last name

Last name of the employee marked as primary 'Sold by' for the corresponding invoice item.

varchar(256)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

employee - code

Unique code of the employee marked as primary 'Sold by'. This is the code taken from the employee's profile in Zenoti.

varchar(128)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

employee code

Unique code of the employee marked as primary 'Sold by'. This is the code from the employee's guest profile. When an employee's profile is created, Zenoti automatically creates their guest profile. Note: The 'employee code' is usually the same as 'employee - code' unless someone manually changes it in the employee's guest profile.

DO NOT USE- THIS FIELD IS BEING DEPRECATED

varchar(128)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

employee mobile phone

Mobile number of the employee marked as primary 'Sold by'.

varchar(64)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

employee gender

Gender of the employee marked as primary 'Sold by'.

varchar(14)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

employee job name

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 the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

employee job code

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

varchar(8000)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

employee start date

Date on which the employee who is marked as the primary 'Sold by' started working for the organization.

timestamp without time zone

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

employee last date

Date on which the employee who is marked as the primary 'Sold by' stopped working for the organization.

timestamp without time zone

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

employee tags

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

varchar(65535)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

employee additional field 1

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

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

varchar(8000)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

employee additional field 2

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

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

varchar(8000)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

is employee inactive

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

boolean

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

close by employee first name

First name of the employee who closed the invoice.

varchar(160)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

close by employee middle name

Middle name of the employee who closed the invoice.

varchar(128)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

close by employee last name

Last name of the employee who closed the invoice.

varchar(256)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

close by employee - code

Unique code of the employee who closed the invoice. This is the code taken from the employee's profile in Zenoti.

varchar(128)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

close by employee code

Unique code of the employee who closed the invoice. This is code from the employee's guest profile. When an employee's profile is created, Zenoti automatically creates their guest profile. Note: The 'employee code' is usually the same as 'employee - code' unless someone manually changes it in the database.

DO NOT USE- THIS FIELD IS BEING DEPRECATED

varchar(128)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

close by employee mobile phone

Mobile number of the employee who closed the invoice.

varchar(64)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

close by employee gender

Gender of the employee who closed the invoice.

varchar(14)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

close by employee job name

Job name associated with the employee who closed the invoice.

varchar(1020)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

close by employee job code

Unique code associated with the job of the employee who closed the invoice.

varchar(8000)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

closeby employee last date

Date on which the employee who closed the invoice stopped working for the organization.

timestamp without time zone

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

close by employee tags

Tags associated with the employee who closed the invoice.

varchar(65535)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

closeby additional field 1

Details in 'Additional Field1' for the employee who closed the invoice.

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

varchar(8000)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

closeby additional field 2

Details in 'Additional Field2' for the employee who closed the invoice.

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

varchar(8000)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

is close by employee inactive

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

boolean

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

createdby employee first name

First name of the employee who added the invoice item into the invoice.

varchar(160)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

createdby employee middle name

Middle name of the employee who added the invoice item into the invoice.

varchar(128)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

createdby employee last name

Last name of the employee who added the invoice item into the invoice.

varchar(256)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

createdby employee - code

Unique code of the employee who added the invoice item into the invoice. This is the code taken from the employee's profile in Zenoti.

varchar(128)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

createdby employee code

Unique code of the employee who added the invoice item into the invoice. This is code from the employee's guest profile. When an employee's profile is created, Zenoti automatically creates their guest profile. Note: The 'employee code' is usually the same as 'employee - code' unless someone manually changes it in the database.

DO NOT USE- THIS FIELD IS BEING DEPRECATED

varchar(128)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

createdby employee mobile phone

Mobile number of the employee who added the invoice item into the invoice.

varchar(64)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

createdby employee gender

Gender of the employee who added the invoice item into the invoice.

varchar(14)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

createdby employee job name

Job name associated with the employee who added the invoice item into the invoice.

varchar(1020)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

createdby employee job code

Unique code associated with the job of the employee who added the invoice item into the invoice.

varchar(8000)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

createdby employee last date

Date on which the employee who added the invoice item into the invoice stopped working for the organization.

timestamp without time zone

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

createdby employee tags

Tags associated with the employee who added the invoice item into the invoice.

varchar(65535)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

createdby additional field 1

Details in 'Additional Field1' for the employee who added the invoice item into the invoice.

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

varchar(8000)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

createdby additional field 2

Details in 'Additional Field2' for the employee who added the invoice item into the invoice.

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

varchar(8000)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

is createdby employee inactive

Flag that indicates whether the employee who added the invoice item into the invoice is inactive. An employee is considered inactive if they have been removed from the system. - True: Employee is inactive. - False: Employee is active.

boolean

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

relationship manager first name

First name of the employee assigned as the relationship manager to the 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 the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

relationship manager last name

Last name of the employee assigned as the relationship manager to the guest.

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

varchar(256)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

relationship manager employee - code

Unique code of the employee assigned as the relationship manager to the guest.

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

varchar(128)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

relationship manager user code

Unique code of the employee assigned as the relationship manager to the guest. This is the code from the employee's guest profile. When an employee's profile is created, Zenoti automatically creates their guest profile. Note: The 'code' is usually the same as 'employee - code' unless someone manually changes it in the employee's guest profile.

DO NOT USE- THIS FIELD IS BEING DEPRECATED

varchar(128)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

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 the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

therapist first name

First name of the employee who is scheduled to perform the service for the guest.

This is only populated for service item types.

varchar(160)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

therapist middle name

Middle name of the employee who is scheduled to perform the service for the guest.

This is only populated for service item types.

varchar(128)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

therapist last name

Last name of the employee who is scheduled to perform the service for the guest.

This is only populated for service item types.

varchar(256)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

therapist employee - code

Unique code of the employee who is scheduled to perform the service for the guest. This is the code taken from the employee's profile in Zenoti.

This is only populated for service item types.

varchar(128)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

therapist code

Unique code of the employee who is scheduled to perform the service for the guest. This is code from the employee's guest profile. When an employee's profile is created, Zenoti automatically creates their guest profile. Note: The 'code' is usually the same as 'employee - code' unless someone manually changes it in the database.

DO NOT USE- THIS FIELD IS BEING DEPRECATED

varchar(128)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

therapist request type

Therapist request type made by a guest.

Note: This is only populated for service item types. Possible values: - Any - Female - Male - Specific: This is populated when the guest requests for a specific employee.

varchar(100)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

therapist gender

Gender of the employee who is scheduled to perform the service for the guest.

This is only populated for service item types.

varchar(14)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

therapist job name

Job name associated with the employee who is scheduled to perform the service for the guest.

This is only populated for service item types.

varchar(1020)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

therapist job code

Unique code associated with the job of the therapist who is scheduled to perform the service for the guest.

This is only populated for service item types.

varchar(8000)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

therapist last date

Date on which the employee who is scheduled to perform the service for the guest stopped working for the organization.

This is only populated for service item types.

timestamp without time zone

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

therapist additional field 1

Details in 'Additional Field1' for the employee who is scheduled to perform the service for the guest.

Additional Field1' can be entered for an employee when you go to 'Employee' > 'Manage Employees' > 'General' in Zenoti. Note: This is only populated for service item types.

varchar(8000)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

therapist additional field 2

Details in 'Additional Field2' for the employee who is scheduled to perform the service for the guest.

Additional Field2' can be entered for an employee when you go to 'Employee' > 'Manage Employees' > 'General' in Zenoti. Note: This is only populated for service item types.

varchar(8000)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

is therapist inactive

Flag that indicates if the employee who is scheduled to perform the service for is inactive. An employee is considered inactive if they have been removed from the system. - True: Employee is inactive. - False: Employee is active.

This is only populated for service item types.

boolean

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

redo therapist first name

First name of the therapist who is scheduled to redo the service.

This gets populated against the initial service that needs to get re-done. This is blank if the initial service does not need to be re-done.

varchar(160)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

redo therapist middle name

Middle name of the therapist who is scheduled to redo the service.

This gets populated against the initial service that needs to get re-done. This is blank if the initial service does not need to be re-done.

varchar(128)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

redo therapist last name

Last name of the therapist who is scheduled to redo the service.

This gets populated against the initial service that needs to get re-done. This is blank if the initial service does not need to be re-done.

varchar(256)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

redo therapist employee - code

Unique code of the therapist who is scheduled to redo the service. This is the code taken from the employee's profile in Zenoti.

This gets populated against the initial service that needs to get re-done. This is blank if the initial service does not need to be re-done.

varchar(128)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

redo therapist code

Unique code of the therapist who is scheduled to redo the service. This is the code from the employee's guest profile. When an employee's profile is created, Zenoti automatically creates their guest profile. Note: The 'code' is usually the same as 'employee - code' unless someone manually changes it in the employee's guest profile.

DO NOT USE- THIS FIELD IS BEING DEPRECATED

varchar(128)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

redo therapist mobile phone

Mobile number of the therapist who is scheduled to redo the service.

This gets populated against the initial service that needs to get re-done. This is blank if the initial service does not need to be re-done.

varchar(64)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

redo therapist gender

Gender of the therapist who is scheduled to redo the service.

This gets populated against the initial service that needs to get re-done. This is blank if the initial service does not need to be re-done.

varchar(14)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

redo therapist job name

Job name associated with the therapist who is scheduled to redo the service.

This gets populated against the initial service that needs to get re-done. This is blank if the initial service does not need to be re-done.

varchar(1020)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

redo therapist job code

Unique code associated with the job of the therapist who is scheduled to redo the service.

This gets populated against the initial service that needs to get re-done. This is blank if the initial service does not need to be re-done.

varchar(8000)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

redo therapist start date

Date on which the redo therapist started working for the organization.

This gets populated against the initial service that needs to get re-done. This is blank if the initial service does not need to be re-done.

timestamp without time zone

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

redo therapist last date

Date on which the redo therapist stopped working for the organization.

This gets populated against the initial service that needs to get re-done. This is blank if the initial service does not need to be re-done.

timestamp without time zone

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

redo therapist tags

Tags associated with the redo therapist.

This gets populated against the initial service that needs to get re-done. This is blank if the initial service does not need to be re-done.

varchar(65535)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

redotherapist additional field 1

Details in 'Additional Field1' for the redo therapist.

Additional Field1' can be entered for an employee when you go to 'Employee' > 'Manage Employees' > 'General' in Zenoti. Note: This gets populated against the initial service that needs to get re-done. This is blank if the initial service does not need to be re-done.

varchar(8000)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

redotherapist additional field 2

Details in 'Additional Field2' for the redo therapist.

Additional Field2' can be entered for an employee when you go to 'Employee' > 'Manage Employees' > 'General' in Zenoti. Note: This gets populated against the initial service that needs to get re-done. This is blank if the initial service does not need to be re-done.

varchar(8000)

Employee

This group of fields describes the attributes of the following six 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, and 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 the front desk staff). 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 closed the invoice.

3. 'Created by' employee: The employee who created the invoice item.

4. 'Relationship manager': The employee who is added as the 'Primary Employee' in the guest profile.

5. 'Therapist': The employee who performed the service.

6. 'Redo Therapist': The employee who performed the redo service.

is redo therapist inactive

Flag that indicates whether the redo therapist is inactive. An employee is considered inactive if they have been removed from the system. - True: Employee is inactive. - False: Employee is active.

This gets populated against the initial service that needs to get re-done. This is blank if the initial service does not need to be re-done.

boolean

Appointment

These fields detail the attributes of the appointment for the corresponding invoice item. These fields are populated for service item type.

appointment pk

Unique identifier for each appointment.

integer

Appointment

These fields detail the attributes of the appointment for the corresponding invoice item. These fields are populated for service item type.

appointment group pk

Unique identifier for each appointment group. Appointment group refers to a set of appointments that are booked together for a guest.

integer

Appointment

These fields detail the attributes of the appointment for the corresponding invoice item. These fields are populated for service item type.

appointment category name

Name of the appointment category.

Appointment categories can be created when you go to Categories > Appointments.

varchar(1024)

Appointment

These fields detail the attributes of the appointment for the corresponding invoice item. These fields are populated for service item type.

appointment category code

Unique code for the appointment category.

Appointment categories can be created when you go to Categories > Appointments.

varchar(1024)

Appointment

These fields detail the attributes of the appointment for the corresponding invoice item. These fields are populated for service item type.

is appointment category active

Flag that indicates whether the appointment category is active.

An appointment category is inactive if the Active checkbox is unselected when you go to Categories > Appointments.

boolean

Appointment

These fields detail the attributes of the appointment for the corresponding invoice item. These fields are populated for service item type.

appointment status

Current status of the appointment. Possible values: - Cancel - Checkin - Closed - Confirmed - Noshow - Open

varchar(100)

Appointment

These fields detail the attributes of the appointment for the corresponding invoice item. These fields are populated for service item type.

appointment cancel or no show status

Flag that indicates whether the appointments with status as 'Cancel' or 'Noshow' have a cancellation or no-show fee associated with them. Possible values: - Cancelled Appointment: Appointment has a cancellation fee. - No Show: Appointment has a no-show fee. - Fulfilled Appointment: Appointment does not have a cancellation or no-show fee.

varchar(21)

Appointment

These fields detail the attributes of the appointment for the corresponding invoice item. These fields are populated for service item type.

is appointment rescheduled

Flag that indicates whether the appointment start time was changed from the initial start time that was set at the time of creation of the appointment. - 1: Appointment was rescheduled. - 0: Appointment was not rescheduled.

smallint

Appointment

These fields detail the attributes of the appointment for the corresponding invoice item. These fields are populated for service item type.

initial appointment start time

If the appointment is rescheduled, this field populates the initial start time of the appointment. If the appointment is not rescheduled, this field is blank.

timestamp without time zone

Appointment

These fields detail the attributes of the appointment for the corresponding invoice item. These fields are populated for service item type.

action performed date time

Latest timestamp at which any change was made to the appointment.

timestamp without time zone

Appointment

These fields detail the attributes of the appointment for the corresponding invoice item. These fields are populated for service item type.

is rebooked

Flag that indicates whether the appointment is the source for a rebooked appointment. Possible values: - True: The appointment is the source for a rebooked appointment. - False: The appointment is not the source for a rebooked appointment.

varchar(100)

Appointment

These fields detail the attributes of the appointment for the corresponding invoice item. These fields are populated for service item type.

rebooked appointment count

Number of appointments or appointment groups that got rebooked from the source. This is populated only for source appointments. If the entire appointment group is rebooked, this field populates the number of times the appointment group is rebooked. If a few appointments within a group are rebooked, this field populates the number of times the appointment is rebooked.

integer

Appointment

These fields detail the attributes of the appointment for the corresponding invoice item. These fields are populated for service item type.

is redo

Flag that indicates whether the corresponding appointment is a redo appointment (initial appointment). - True: Appointment is a redo appointment. - False: Appointment is not a redo appointment.

boolean

Appointment

These fields detail the attributes of the appointment for the corresponding invoice item. These fields are populated for service item type.

is redone

Flag that indicates whether the corresponding appointment is a re-done appointment (subsequent appointment). - True: Appointment is a re-done appointment. - False: Appointment is not a re-done appointment.

boolean

Invoice

These fields detail the attributes of the invoice item.

invoice id

Unique identifier for the invoice (unique within the organization).

varchar(36)

Invoice

These fields detail the attributes of the invoice item.

invoice no

Unique identifier for the invoice (unique within the center).

varchar(40)

Invoice

These fields detail the attributes of the invoice item.

invoice item id

Unique identifier for each invoice item within the invoice.

varchar(36)

Invoice

These fields detail the attributes of the invoice item.

fact invoiceitem wid

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

bigint

Invoice

These fields detail the attributes of the invoice item.

factinvoiceitemid

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

integer

Invoice

These fields detail the attributes of the invoice item.

invoice source

Source from where the invoice was created.

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

varchar(128)

Invoice

These fields detail the attributes of the invoice item.

invoice status

Indicates whether the invoice is open or closed.

varchar(14)

Invoice

These fields detail the attributes of the invoice item.

invoice closed date and time

Date and time at which the invoice was closed.

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

timestamp without time zone

Invoice

These fields detail the attributes of the invoice item.

invoice closed date

Date on which the invoice was closed.

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

date

Invoice

These fields detail the attributes of the invoice item.

invoice item created date and time

Date and time at which the invoice item was added into the invoice.

timestamp without time zone

Invoice

These fields detail the attributes of the invoice item.

invoice item created date

Date on which the invoice item was added into the invoice.

date

Invoice

These fields detail the attributes of the invoice item.

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 without time zone

Invoice

These fields detail the attributes of the invoice item.

sale date

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

date

Invoice

These fields detail the attributes of the invoice item.

invoice item last updated date and time

Date and time at which the invoice was last updated.

timestamp without time zone

Invoice

These fields detail the attributes of the invoice item.

invoice item last updated date

Date on which the invoice was last updated.

date

Invoice

These fields detail the attributes of the invoice item.

invoice date in center

This is the same as the sale date for all records except for records which contain the initial sale of the membership. For these, it is populated as the membership start date.

date

Invoice

These fields detail the attributes of the invoice item.

comments

Comments entered for the corresponding invoice.

varchar(65535)

Invoice

These fields detail the attributes of the invoice item.

invoice includes service

Flag that indicates whether the invoice includes a service (that is not a refund or no-show fee or cancellation fee). - True: Includes service. - False: Does not include service.

varchar(5)

Invoice

These fields detail the attributes of the invoice item.

invoice includes product

Flag that indicates whether the invoice includes a product (that is not a refund). - True: Includes product. - False: Does not include product.

varchar(5)

Invoice

These fields detail the attributes of the invoice item.

invoice includes package

Flag that indicates whether the invoice includes a package (that is not a refund). - True: Includes package. - False: Does not include package.

varchar(5)

Invoice

These fields detail the attributes of the invoice item.

invoice includes day package

Flag that indicates whether the invoice includes a day package (that is not a refund). - True: Includes day package. - False: Does not include day package.

varchar(5)

Invoice

These fields detail the attributes of the invoice item.

invoice includes membership

Flag that indicates whether the invoice includes a membership (that is not a refund). - True: Includes membership. - False: Does not include membership.

varchar(5)

Invoice

These fields detail the attributes of the invoice item.

membership sold in invoice

Invoice that contains the actual sale of the membership (either setup or regular) gets marked as true. For example, if a setup membership is sold as part of invoice 1 and subsequent recurring cycles are part of invoices 2,3,4,..., this flag is marked as true for invoice 1. This flag helps distinguish the initial sale of a membership from its subsequent recurring invoices. If a membership does not have a setup associated with it, the invoice with the first recurring cycle gets marked as true.

varchar(5)

Invoice

These fields detail the attributes of the invoice item.

group invoice id

Invoice ID of the actual sale of the membership. This gets populated against all the subsequent recurring cycles and helps identify the original membership sale.

varchar(36)

Invoice

These fields detail the attributes of the invoice item.

group invoice order

Number order that indicates the order of the recurring membership invoice. For set up membership, this will be 0 and for the subsequent recurring cycles, this will be 1,2,3,…

integer

Invoice

These fields detail the attributes of the invoice item.

is membership discounted

Flag that indicates whether the membership corresponding to the invoice item is discounted. - True: Membership is discounted. - False: Membership is not discounted.

varchar(100)

Invoice

These fields detail the attributes of the invoice item.

invoice includes prepaid/gift card

Flag that indicates whether the invoice includes a prepaid card or gift card (that is not a refund). - True: Includes prepaid card or gift card. - False: Does not include prepaid card or gift card.

varchar(5)

Invoice

These fields detail the attributes of the invoice item.

invoice includes class

Flag that indicates whether the invoice includes a class (that is not a refund). - True: Includes class. - False: Does not include class.

varchar(5)

Invoice

These fields detail the attributes of the invoice item.

invoice includes membership freeze fee

Flag that indicates whether the invoice includes a membership freeze fee. - True: Includes membership freeze fee. - False: Does not include membership freeze fee.

varchar(5)

Invoice

These fields detail the attributes of the invoice item.

invoice includes room charges

Flag that indicates whether the invoice includes room charges. - True: Includes room charges. - False: Does not include room charges.

varchar(5)

Invoice

These fields detail the attributes of the invoice item.

is invoice invalid

Flag that indicates whether the invoice item is valid. - True: Invalid invoice. - False: Valid invoice.

boolean

Invoice

These fields detail the attributes of the invoice item.

is recurring invoice

Flag that indicates whether the invoice is a recurring invoice. - True: Recurring invoice. - False: Not recurring invoice.

varchar(100)

Invoice

These fields detail the attributes of the invoice item.

is upsell

If the guest buys two packages within 365 days within the same business unit, this flag is marked as True for the second package.

boolean

Invoice

These fields detail the attributes of the invoice item.

quantity sold

Quantity sold of the corresponding invoice item.

integer

Invoice

These fields detail the attributes of the invoice item.

restock quantity

This is populated for 'item type code' = 'product refund'. This is the quantity restocked out of the refunded quantity.

float(8)

Invoice

These fields detail the attributes of the invoice item.

list price

List price of the corresponding invoice item.

float(8)

Invoice

These fields detail the attributes of the invoice item.

sale price

Sale price is derived as follows: sale price = 'list price' - 'discount applied' - 'loyalty point redemption amount' - 'membership redemption amount' - 'gift card redemption amount' - 'cashback redemption amount' + 'tax.'

float(8)

Invoice

These fields detail the attributes of the invoice item.

is sale price adjusted

Flag that indicates whether the sale price is adjusted. - True: Adjusted. - False: Not adjusted.

boolean

Invoice

These fields detail the attributes of the invoice item.

original sale price

Original sale price of the invoice item. If the sale price is not adjusted, 'sale price' and 'original sale price' will be the same.

float(8)

Invoice

These fields detail the attributes of the invoice item.

discount applied

Total discount applied on the corresponding invoice item.

float(8)

Invoice

These fields detail the attributes of the invoice item.

discount with tax

Total discount applied on the corresponding invoice item inclusive of apportioned tax.

float(8)

Invoice

These fields detail the attributes of the invoice item.

custom discount

Custom discount applied on the corresponding invoice item. This is already included in 'discount applied'.

float(8)

Invoice

These fields detail the attributes of the invoice item.

tax

Final tax applied on the invoice item.

float(8)

Invoice

These fields detail the attributes of the invoice item.

sale tax

Tax applicable on the invoice item before discount.

float(8)

Invoice

These fields detail the attributes of the invoice item.

rounding adjustment

Rounding adjustments done for the particular invoice.

float(8)

Refund

When refunds are generated, they are created as separate invoices. The fields in this group help provide the link between the refund invoice item and the source invoice item.

is refunded

Flag that indicates whether the invoice item is refunded (whether the corresponding invoice item is the source for a refund). The actual refund invoice is separate. - True: Corresponding invoice is refunded (it is the source for a refund invoice). - False: Corresponding invoice is not refunded (it is not the source for a refund invoice).

varchar(100)

Refund

When refunds are generated, they are created as separate invoices. The fields in this group help provide the link between the refund invoice item and the source invoice item.

refund source invoice item id

This field establishes the link between the source invoice item and the refund invoice item. It is only populated for refund invoice items. This field populates the invoice item ID of the source invoice item.

varchar(65535)

Refund

When refunds are generated, they are created as separate invoices. The fields in this group help provide the link between the refund invoice item and the source invoice item.

refund date and time

Date and time at which the invoice item is refunded. This is the 'sale date and time' of the refund invoice item associated with this source invoice item.

This field is only populated for invoice items that are the source for a refund - where is refunded is True.

timestamp without time zone

Refund

When refunds are generated, they are created as separate invoices. The fields in this group help provide the link between the refund invoice item and the source invoice item.

refund date

Date on which the invoice item is refunded. This is the 'sale date' of the refund invoice item associated with this source invoice item.

This field is only populated for invoice items that are the source for a refund - where is refunded is True.

date

Refund

When refunds are generated, they are created as separate invoices. The fields in this group help provide the link between the refund invoice item and the source invoice item.

refund quantity

Quantity refunded for the invoice item. This is the 'quantity sold' of the refund invoice item associated with this source invoice item. This is populated only for products.

This field is only populated for invoice items that are the source for a refund - where is refunded is True.

integer

Refund

When refunds are generated, they are created as separate invoices. The fields in this group help provide the link between the refund invoice item and the source invoice item.

refund amount

Amount refunded for the invoice item. This is the 'sale price' of the refund invoice item associated with this source invoice item.

This field is only populated for invoice items that are the source for a refund - where is refunded is True.

float(8)

Refund

When refunds are generated, they are created as separate invoices. The fields in this group help provide the link between the refund invoice item and the source invoice item.

refund tax

Tax refunded for the invoice item. This is the 'tax' of the refund invoice item associated with this source invoice item.

This field is only populated for invoice items that are the source for a refund - where is refunded is True.

float(8)

Campaign and Discount

These fields detail the attributes of the discount that are applied to the corresponding invoice item.

campaign name

Name of the campaign applied on the corresponding invoice item. Note: If there are multiple campaigns applied on the invoice item, only one campaign name is populated here.

varchar(512)

Campaign and Discount

These fields detail the attributes of the discount that are applied to the corresponding invoice item.

campaign type

Type of campaign applied on the corresponding invoice item. - 1: Email/SMS - 2: Media -3: Opportunity

varchar(11)

Campaign and Discount

These fields detail the attributes of the discount that are applied to the corresponding invoice item.

campaign code

Unique code of the campaign applied on the corresponding invoice item. Note: If there are multiple campaigns applied on the invoice item, only one campaign code is populated here.

varchar(4096)

Campaign and Discount

These fields detail the attributes of the discount that are applied to the corresponding invoice item.

discount name

Name of the discount applied on the corresponding invoice item.

varchar(256)

Campaign and Discount

These fields detail the attributes of the discount that are applied to the corresponding invoice item.

discount code

Unique code of the discount applied on the corresponding invoice item.

varchar(32)

Campaign and Discount

These fields detail the attributes of the discount that are applied to the corresponding invoice item.

manual discount

Flag that indicates whether the corresponding invoice item contains ONLY a manual discount. - True: Discount applied is ONLY a manual discount.

integer

Campaign and Discount

These fields detail the attributes of the discount that are applied to the corresponding invoice item.

custom discount type

This field displays 'Membership Discount' when a membership discount is applied on the invoice item. Otherwise, it is blank.

varchar(512)

Campaign and Discount

These fields detail the attributes of the discount that are applied to the corresponding invoice item.

custom discount id

A system-generated unique identifier that is populated when a membership discount is applied on the invoice item.

varchar(36)

Campaign and Discount

These fields detail the attributes of the discount that are applied to the corresponding invoice item.

campaign applied date and time

Date and time at which the campaign was applied to the corresponding invoice item. Note: This will be populated only if a campaign is applied on the invoice.

timestamp without time zone

Campaign and Discount

These fields detail the attributes of the discount that are applied to the corresponding invoice item.

campaign applied date

Date on which the campaign was applied to the corresponding invoice item. Note: This will be populated only if a campaign is applied on the invoice.

date

Campaign and Discount

These fields detail the attributes of the discount that are applied to the corresponding invoice item.

campaign auto apply

Flag that indicates whether the campaign has to be auto-applied to the customer. - True: Auto-applied. - False: Not to be auto-applied.

boolean

Campaign and Discount

These fields detail the attributes of the discount that are applied to the corresponding invoice item.

campaign combine offers

Flag that indicates whether the corresponding campaign can be combined with other offers. - True: Can be combined. - False: Cannot be combined.

boolean

Campaign and Discount

These fields detail the attributes of the discount that are applied to the corresponding invoice item.

is campaign active

Flag that indicates whether the applied campaign is active. - True: Active campaign. - False: Inactive campaign. - Null: No campaign is applied.

boolean

Campaign and Discount

These fields detail the attributes of the discount that are applied to the corresponding invoice item.

free service revenue eligible

Flag that indicates whether the discount applied through the corresponding campaign is eligible for free service revenue and commission for employees.

boolean

Redemption and Payment

When an invoice item is paid for, it can be done either through a left-side transaction (redemption) or a right-side transaction (payment) on the invoice screen in core. These fields bring in the values of both the redemptions and payments associated with each invoice item.

cashback redemption amount

Amount redeemed from cashback for the corresponding invoice item. This is a left-side transaction.

float(8)

Redemption and Payment

When an invoice item is paid for, it can be done either through a left-side transaction (redemption) or a right-side transaction (payment) on the invoice screen in core. These fields bring in the values of both the redemptions and payments associated with each invoice item.

gift card redemption amount

Amount redeemed from gift cards for the corresponding invoice item. This is a left-side transaction.

float(8)

Redemption and Payment

When an invoice item is paid for, it can be done either through a left-side transaction (redemption) or a right-side transaction (payment) on the invoice screen in core. These fields bring in the values of both the redemptions and payments associated with each invoice item.

loyalty point redemption amount

Amount redeemed from loyalty points for the corresponding invoice item. This is a left-side transaction.

float(8)

Redemption and Payment

When an invoice item is paid for, it can be done either through a left-side transaction (redemption) or a right-side transaction (payment) on the invoice screen in core. These fields bring in the values of both the redemptions and payments associated with each invoice item.

membership redemption amount

Amount redeemed from memberships for the corresponding invoice item. This is a left-side transaction.

float(8)

Redemption and Payment

When an invoice item is paid for, it can be done either through a left-side transaction (redemption) or a right-side transaction (payment) on the invoice screen in core. These fields bring in the values of both the redemptions and payments associated with each invoice item.

redemption (cashback)

Amount redeemed from cashback for the corresponding invoice item. This is the same as the 'cashback redemption amount' field.

float(8)

Redemption and Payment

When an invoice item is paid for, it can be done either through a left-side transaction (redemption) or a right-side transaction (payment) on the invoice screen in core. These fields bring in the values of both the redemptions and payments associated with each invoice item.

redemption (gift card)

Amount redeemed from gift cards for the corresponding invoice item. This is the same as the 'gift card redemption amount' field.

float(8)

Redemption and Payment

When an invoice item is paid for, it can be done either through a left-side transaction (redemption) or a right-side transaction (payment) on the invoice screen in core. These fields bring in the values of both the redemptions and payments associated with each invoice item.

redemption (loyalty points)

Amount redeemed from loyalty points for the corresponding invoice item. This is the same as the 'loyalty point redemption amount' field.

float(8)

Redemption and Payment

When an invoice item is paid for, it can be done either through a left-side transaction (redemption) or a right-side transaction (payment) on the invoice screen in core. These fields bring in the values of both the redemptions and payments associated with each invoice item.

redemption (membership)

Amount redeemed from memberships for the corresponding invoice item. This is the same as the 'membership redemption amount' field.

float(8)

Redemption and Payment

When an invoice item is paid for, it can be done either through a left-side transaction (redemption) or a right-side transaction (payment) on the invoice screen in core. These fields bring in the values of both the redemptions and payments associated with each invoice item.

is payment received

This flag indicates whether any payment (right-side transaction) is received for the corresponding invoice item.

varchar(100)

Redemption and Payment

When an invoice item is paid for, it can be done either through a left-side transaction (redemption) or a right-side transaction (payment) on the invoice screen in core. These fields bring in the values of both the redemptions and payments associated with each invoice item.

payment (cash)

Payment received through cash for the corresponding invoice item. This is a right-side transaction.

float(8)

Redemption and Payment

When an invoice item is paid for, it can be done either through a left-side transaction (redemption) or a right-side transaction (payment) on the invoice screen in core. These fields bring in the values of both the redemptions and payments associated with each invoice item.

payment (card)

Payment received through card for the corresponding invoice item. This is a right-side transaction.

float(8)

Redemption and Payment

When an invoice item is paid for, it can be done either through a left-side transaction (redemption) or a right-side transaction (payment) on the invoice screen in core. These fields bring in the values of both the redemptions and payments associated with each invoice item.

card payment names

Comma-separated list of card types used while making the payment.

For example, Amex and Visa.

varchar(65535)

Redemption and Payment

When an invoice item is paid for, it can be done either through a left-side transaction (redemption) or a right-side transaction (payment) on the invoice screen in core. These fields bring in the values of both the redemptions and payments associated with each invoice item.

payment (cheque)

Payment received via cheque for the corresponding invoice item. This is a right-side transaction.

float(8)

Redemption and Payment

When an invoice item is paid for, it can be done either through a left-side transaction (redemption) or a right-side transaction (payment) on the invoice screen in core. These fields bring in the values of both the redemptions and payments associated with each invoice item.

payment (custom)

Payment received via monetary- financial custom payments for the corresponding invoice item. This is a right-side transaction.

float(8)

Redemption and Payment

When an invoice item is paid for, it can be done either through a left-side transaction (redemption) or a right-side transaction (payment) on the invoice screen in core. These fields bring in the values of both the redemptions and payments associated with each invoice item.

non-financial custom payment discount

Payment received via custom payments that are not considered in financials for the corresponding invoice item. This is a right-side transaction.

float(8)

Redemption and Payment

When an invoice item is paid for, it can be done either through a left-side transaction (redemption) or a right-side transaction (payment) on the invoice screen in core. These fields bring in the values of both the redemptions and payments associated with each invoice item.

custom payment names

Comma-separated list of custom payment types used while making the payment.

varchar(65535)

Redemption and Payment

When an invoice item is paid for, it can be done either through a left-side transaction (redemption) or a right-side transaction (payment) on the invoice screen in core. These fields bring in the values of both the redemptions and payments associated with each invoice item.

payment (membership)

Payment received via memberships for the corresponding invoice item. This is a right-side transaction.

float(8)

Redemption and Payment

When an invoice item is paid for, it can be done either through a left-side transaction (redemption) or a right-side transaction (payment) on the invoice screen in core. These fields bring in the values of both the redemptions and payments associated with each invoice item.

payment (loyalty points)

Payment received via loyalty points for the corresponding invoice item. This is a right-side transaction.

float(8)

Redemption and Payment

When an invoice item is paid for, it can be done either through a left-side transaction (redemption) or a right-side transaction (payment) on the invoice screen in core. These fields bring in the values of both the redemptions and payments associated with each invoice item.

payment (gift card)

Payment received via gift cards for the corresponding invoice item. This is a right-side transaction.

float(8)

Redemption and Payment

When an invoice item is paid for, it can be done either through a left-side transaction (redemption) or a right-side transaction (payment) on the invoice screen in core. These fields bring in the values of both the redemptions and payments associated with each invoice item.

payment (prepaid card)

Payment received via prepaid cards for the corresponding invoice item. This is a right-side transaction.

float(8)

Redemption and Payment

When an invoice item is paid for, it can be done either through a left-side transaction (redemption) or a right-side transaction (payment) on the invoice screen in core. These fields bring in the values of both the redemptions and payments associated with each invoice item.

total payment value

Note: Do not use this field. It is relevant for very specific scenarios only.

Note: Do not use this field. It is relevant for very specific scenarios only.

float(8)

Redemption and Payment

When an invoice item is paid for, it can be done either through a left-side transaction (redemption) or a right-side transaction (payment) on the invoice screen in core. These fields bring in the values of both the redemptions and payments associated with each invoice item.

total payments (cash, card, cheque and custom)

Payment received via cash, card, cheque, and monetary-financial custom payments for the corresponding invoice item. This does not include tips.

float(8)

Revenue

These fields detail the attributes of the recognized revenue associated with each invoice item.

revenue (cash)

Revenue recognized via cash-based instruments, excluding tax. These are cash, card, cheque, and monetary-financial custom payments.

float(8)

Revenue

These fields detail the attributes of the recognized revenue associated with each invoice item.

prepaid revenue

Revenue recognized via liability instruments, excluding tax.

float(8)

Revenue

These fields detail the attributes of the recognized revenue associated with each invoice item.

revenue (gift card redemption)

Revenue recognized via gift cards, excluding tax.

float(8)

Revenue

These fields detail the attributes of the recognized revenue associated with each invoice item.

revenue (pre paid card redemption)

Revenue recognized via prepaid cards, excluding tax.

float(8)

Revenue

These fields detail the attributes of the recognized revenue associated with each invoice item.

revenue (membership initial recognized)

Initial revenue recognized via memberships, excluding tax.

float(8)

Revenue

These fields detail the attributes of the recognized revenue associated with each invoice item.

revenue (membership credit redemption)

Revenue recognized via membership credit redemptions, excluding tax.

float(8)

Revenue

These fields detail the attributes of the recognized revenue associated with each invoice item.

revenue (membership service redemptions)

Revenue recognized via membership service redemptions, excluding tax.

float(8)

Revenue

These fields detail the attributes of the recognized revenue associated with each invoice item.

revenue (package initial recognized)

Initial revenue recognized via packages, excluding tax.

float(8)

Revenue

These fields detail the attributes of the recognized revenue associated with each invoice item.

revenue (package redemption)

Revenue recognized via packages, excluding tax.

float(8)

Revenue

These fields detail the attributes of the recognized revenue associated with each invoice item.

usage type

This shows whether package usage or membership usage is applied on the invoice item. Membership credit redemptions are not populated as 'membership usage'. Only membership service redemptions are populated as 'membership usage'.

varchar(80)

Revenue

These fields detail the attributes of the recognized revenue associated with each invoice item.

total revenue

Note: Do not use this field. It is relevant for very specific scenarios only.

Note: Do not use this field. It is relevant for very specific scenarios only.

float(8)

Revenue

These fields detail the attributes of the recognized revenue associated with each invoice item.

total adjusted revenue

Note: Do not use this field. It is relevant for very specific scenarios only.

Note: Do not use this field. It is relevant for very specific scenarios only.

float(8)

Revenue

These fields detail the attributes of the recognized revenue associated with each invoice item.

daily recurring revenue(drr)

Daily recurring revenue of the membership calculated based on the membership payment frequency and amount. This is calculated assuming that the 'discount or order setting' is disabled.

float(8)

Revenue

These fields detail the attributes of the recognized revenue associated with each invoice item.

drr with discount or order setting

Daily recurring revenue of the membership calculated based on the membership payment frequency and amount. This is calculated assuming that the 'discount or order setting' is enabled.

float(8)

memberships

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

"discount membership category name"

Category of membership used to get discount

varchar(512)

memberships

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

"discount membership code"

membership code of membership redeemed to get discount

varchar(100)

memberships

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

"discount membership name"

membership name of membership redeemed to get discount

varchar(512)

memberships

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

"discount membership sale center name"

center where redeemed membership is sold

varchar(300)

memberships

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

"discount user membership id"

user membership id of membership redeemed to get discount

varchar(36)

memberships

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

"is membership discount"

Indicates if discount is provided or not using the membership

boolean

invoice

These fields detail the attributes of the invoice item.

factinvoiceitemwid

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

bigint