Understand subscription and order-limit blocks
Billing state and order-limit controls can suspend checkout or direct an authorized owner to Admin billing without hiding existing operational context. Read the full-screen billing or order-limit message, do not attempt repeated checkout, and ask the Business Account owner to review billing in Admin. Submit the payment once, then verify Orders and Payments before retrying any uncertain result.
Before you start
- An authenticated POS session on the intended branch.
- A reviewed cart with the correct customer, service mode, item prices, tax context, and amount due.
Steps
- Read the full-screen billing or order-limit message.
- Do not attempt repeated checkout.
- Ask the Business Account owner to review billing in Admin.
- Refresh POS only after the account state is corrected.
Expected result
Checkout remains blocked until the Business Account owner corrects the stated billing or order-limit condition. Never submit an uncertain tender again until Orders and Payments show whether it succeeded, failed, or queued.
Permissions
- The staff member needs POS checkout access for the active branch; discounts, overrides, Khata, and some tenders may require the specific manager or configured payment permission.
Troubleshooting
POS does not let staff read the full-screen billing or order-limit message; they cannot continue to do not attempt repeated checkout.
Check the required state before trying again: An authenticated POS session on the intended branch. A reviewed cart with the correct customer, service mode, item prices, tax context, and amount due. Keep the same branch and record, reopen /billing, and try the blocked action once. If it still fails, stop and send Support the safe order/payment references, tender, amount, branch, status, and time; omit card data, CVV, wallet secrets, and PINs. Note whether POS changes as staff read the full-screen billing or order-limit message.
The total, tender, receipt, server record, and local queue do not show one payment outcome after the final checkpoint: Refresh POS only after the account state is corrected.
Compare the final total, Orders entry, Payments entry, receipt, external-terminal result, and local queue. Never repeat an uncertain tender. Retry only when both server records and the local queue prove no payment exists. Do not repeat the action if the records conflict; ask Support to review the safe order/payment references, tender, amount, branch, status, and time; omit card data, CVV, wallet secrets, and PINs. The final evidence must establish whether staff could refresh POS only after the account state is corrected.
Related articles
Cart totals show subtotal, discount lines, VAT or tax, service charge, tip, and final amount using current branch pricing.Apply or remove a promotion code
Promotion validation returns the eligible saving or explains why the code did not change the cart.Use an authorized discount or price override
Discounts and overrides appear only when configured and may require manager approval before checkout can continue.Choose a payment method
The checkout shows only payment methods enabled for the branch, including cash, card, wallet, UPI, or Khata where configured.
Open in TajerGo
Sign in with the appropriate role and confirm your Business Account and branch before continuing.
Read as Markdown · Guidance for support agents
Last reviewed 2026-09-06 · Send documentation feedback