Kapta · 15/09/2026
Start by distinguishing a booking, attendance and sale. Attending a class may consume a previously purchased pack; invoicing every attendance again could duplicate the document for the same service.
Which processes should be separated?
List memberships, drop-in classes, packs, services and products. Identify which are prepaid and which are charged on use. Use actual operational examples to choose the event that should prepare a document.
What information does the connection need?
Kapta's Mindbody catalog entry covers customers, bookings and sales, subject to account permissions and available data. Identify the studios, locations and services included. Kapta Mindbody integration.
What if a customer attends two studios?
Decide whether the locations share an invoicing entity and how the customer is identified across systems. Names and emails can change; retain the identifiers associated with the record. Different companies require an explicit destination rule.
What should be tested?
Include a pack purchase, class attendance, membership renewal and cancellation. Verify that attendance does not repeat the purchase invoice. Kapta can assess the workflow from these examples and confirm what can be automated for your account.
