Commerce Workspace

Commerce Workspace is the control plane for the sellable catalog and money operations: plans, add-ons, charges, coupons, payment modes, gateway accounts, terminal devices, tax groups, invoices, payment processing, subscriptions, refunds, disputes, settlements, freezes, transfers, and upgrades.

What this page is for

Who should use it

Owner, finance, manager, platform admin

Where to find it

/commerce

Before you start

Use Commerce Workspace for setup and review. Use POS for a live customer sale.
Plan duration belongs in the plan/rate card; paid-in-full, recurring, EMI, billing cycle, and proration are sale-time choices.
Payment modes should reflect real collection paths such as cash, manual UPI, bank transfer, Razorpay, terminal, and internal credit.
Gateway accounts and terminal devices must be configured and healthy before online checkout, payment links, hosted checkout, or terminal collection buttons are enabled.
Tax/GST groups, invoice sequence, GL codes, refund/void rules, and settlement exports should be changed only with owner/finance approval.
Overview is for current commerce health. Checkout / POS is for catalog-driven sale. Payment Operations is for invoice collection and provider handoff. Transactions is for ledger review. Subscriptions is for freeze/transfer/upgrade workflows. Finance Ops is for approvals, cash control, refunds, credits, and workflow history.
Payment Operations includes Generate payment link, Send payment link, Create payment mandate, Pay here, Terminal collection, and Terminal status reconciliation.
Generate payment link fields are Invoice, Integration used, and Expiry. The selected invoice must have an outstanding balance.
Send payment link fields are Payment link, Channel, and Recipient. Channels are Email, SMS, and WhatsApp, and each depends on communication-provider readiness.
Create payment mandate fields are Member and Integration used. Use it only for customers who consent to recurring collection.
Pay here fields are Invoice and Amount (minor); the Open Razorpay button is disabled when checkout readiness is missing.
Terminal collection fields are active terminal integration, Invoice, and Amount (minor); provider reference is captured after POS-terminal confirmation.
Terminal status reconciliation fields are Pending terminal payment, Status, Provider transaction id, Provider order id, Provider method, and Provider payload JSON. Use Sync from payload when the terminal provider returns a raw response body.
Terminal reconciliation statuses are Succeeded, Failed, Canceled, and Pending.
Finance Ops approvals cover refunds, voids, backdates, and write-offs. Each row shows request type, invoice, amount, threshold/policy, status, and approval count.
Cash control forms are Open shift with Cash drawer and Opening amount (minor), and Close shift with Open cash shift, Closing amount (minor), and Notes.
Refund ledger shows processed refunds. Credit ledger shows non-cash member credit. Workflow history shows freeze, transfer, and upgrade records.

Daily workflow

Before launch, create tax groups, invoice sequence, payment modes, gateway accounts, terminal devices, plans, add-ons, joining fee, coupons, and lifecycle policies.
During operations, review payment processing, transactions, settlements, disputes, refunds, failed payments, and subscription lifecycle requests.
When setup changes, run a small test sale or preview before asking front desk to use the new setting.
Use terminal reconciliation only for payments that are still pending and where the terminal/provider response has been checked.
Close cash shifts daily so cash, manual UPI, bank-transfer notes, and offline references can be matched before the next day starts.

Watch out

Do not make live catalog or tax changes while staff are actively selling unless the team knows exactly when the change takes effect.

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