Commerce Catalog and Finance Controls

Commerce controls the rate card, add-ons, charges, payment methods, gateway accounts, terminals, tax groups, coupons, invoices, transactions, disputes, settlements, freezes, transfers, upgrades, refunds, and credit notes.

What this page is for

Who should use it

Owner, finance, manager

Where to find it

/commerce and related finance routes

Before you start

Create plans with duration and base commercial behavior. Do not encode EMI terms as separate plan unless the product itself is different.
Configure GST tax groups before selling taxable plans.
Keep gateway, terminal, and payment mode setup in Admin/Commerce before asking front desk to collect.
Freeze, transfer, upgrade, refund, and void actions must leave audit and ledger evidence.
Only one active online payment integration should be used for live checkout/payment-link actions at a gym, and only one active terminal payment integration should be used for live POS-terminal collection.
Payment modes should be operationally named, for example Cash Drawer 1, Manual UPI QR, Bank Transfer, Razorpay, Razorpay POS, Paytm POS, Pine Labs, or Internal Credit.
Gateway setup must declare provider, account name, merchant reference when used, credentials, webhook secret, test/live mode, and supported capabilities: checkout, payment links, mandates, and refunds.
Terminal setup must declare provider, device name, external device id or serial, linked gym/location, active state, and linked payment method/account where required.
Refund, void, backdate, write-off, and manual adjustment policies should require finance/owner approval based on amount or risk.
Cash drawers and shifts are part of finance control. Open a shift with drawer and opening amount before cash collection, and close it with counted closing amount and notes.

Daily workflow

Before launch: create service categories, tax groups, payment modes, gateway accounts, terminal devices, plans, add-ons, charges, and coupons.
During operations: review transactions, disputes, settlements, refunds, and failed payments.
For lifecycle changes: use freeze, transfer, or upgrade flows instead of manually editing subscription records.
At day end, review Finance Ops for approvals, cash shifts, refund ledger, credit ledger, and freeze/transfer/upgrade history.

Watch out

Amounts in setup screens are often minor units. Validate high-value fields before saving.
Backdated billing and write-offs should be manager/finance-only operations.

Use the left menu to open related pages in Integrations.
Use Ask Docs for questions that are already covered in this public documentation.