Product Mapping

Product mappings tell Kotally how many credits to grant when a customer buys a GoHighLevel product.

Create a mapping

In Admin -> Product Configs, create one mapping for each sellable offer that should grant credits.

Required fields:

• Name: staff-facing label for the offer.
• Type: package or membership.
• GoHighLevel product: selected from GoHighLevel or entered manually by product id.
• Calendar: the booking calendar that can consume the credits.

Package fields:

• credits_total: number of credits granted by the purchase.
• expiry_days: optional number of days before unused credits expire.

Membership fields:

• monthly_credits: number of credits granted in each membership period.
• expiry_days: optional expiry window for each granted balance.

Matching rules

Kotally grants credits only when the payment event resolves to one active product mapping for the same GoHighLevel location.

If multiple products are present on an invoice, each item must resolve clearly. If a payment cannot be matched, Kotally records the event for inspection but does not create credits.

On the standalone API, you skip product matching: a grant names the mapping directly with product_config_id, so each product config is still the source of the credit rules (see the API Quickstart).

Rollout recommendation

1. Start with one test package product.
2. Buy it with a test contact.
3. Confirm the contact shows the correct balance in the Kotally admin or embed.
4. Book a matching calendar appointment and confirm one credit is deducted.
5. Repeat for memberships and any additional calendars.