This article shares some possible use cases you could support, as well as a sample flow that supports each use case. This can be a helpful jumping off point as you plan your implementation.
You can set up staff member-based service variants. This allows the business to offer customers different service prices depending on which staff member is providing the service.
To create staff member-based variants:
staffMemberIds
array.serviceId
, STAFF_MEMBER
as options.values.type
,
as well as all staff member IDs in variants.values.choices.staffMemberId
.
Make sure to also specify the only supported option ID in every
variants.values.choices.optionId
field.variants.values.choices.price
.You can set up service variants based on the booked equipment. This lets the business offer different service prices depending on which equipment the customer has booked.
To create equipment-based variants:
serviceId
, CUSTOM
as options.values.type
,
Equipment
as options.customData.name
, and all supported equipment
choices in the options.customData.choices
array. Additionally, make sure
to repeat all supported choices in variants.values.choices.custom
and to specify the only supported option ID in every
variants.values.choices.optionId
field.variants.values.choices.price
.