Browse help articles Turn on your storefront after completing the profile Resolve Almost ready to go live without guessing the missing details Understand locked website-management options Hide your storefront deliberately Check and copy your own storefront address Preview a template without applying it Apply an available storefront template Save the three supported brand colours Understand automatic homepage wording Stop future automatic homepage-text updates Why the automatic-text card may be missing or disabled Prepare a safe edit to template-driven homepage content Set a standard flat delivery charge Set or remove the free-shipping threshold Configure the optional fast delivery tier Write realistic delivery-window settings Limit delivery using serviceable pincodes Exclude delivery destinations with blocked pincodes Show or hide the requested-delivery-date field Add an accurate delivery-step checkout note Turn off the delivery offer without confusing existing orders Recover safely from a delivery-settings load or save error Update an order tracking ID carefully Find a shipping label when a shipment exists Distinguish shipment cancellation from order cancellation Read the ship-by estimate without promising a delivery date Add a UPI ID for direct payment Add bank details for customer transfers Change payout details without accidentally removing another method Why saved payout details are masked Enable or pause the direct-payment offer Remove stored direct-payment details What to do when payout saving is switched off Confirm a direct transfer using your own payment record Investigate missing direct-payment instructions Correct a payout-details validation error Distinguish Payment Gateway from Direct Pay settings Check whether a payout change actually saved Sign in with the email registered to your merchant account Resolve a sign-in email error Handle a sign-in connection failure safely Sign out of the merchant app Find the app version before reporting a problem Open an official help link when the app cannot launch a browser Prepare a useful support report without exposing private data What to do when a visible setting has no action Prepare and save a first physical product Correct a product-name validation error Complete the required product description Enter a non-variant product price Resolve the missing-product-image message Handle an interrupted product-image upload Choose the correct category while adding a product Create a product category with a useful description Edit an existing category instead of duplicating it Find a category when the category list looks empty Complete product option names and values Review every variant combination price Do not confuse blank variant stock with zero stock Resolve Variant Errors without deleting the product Enter bulk-pricing tiers without overlapping ranges Use product tax fields only with verified tax information Check whether a product save completed before retrying Understand optional service-product details without assuming a booking guarantee Start inventory tracking with a counted opening balance Correct a stock count with a reason attached Understand the consequence before disabling stock tracking Find a product without mistaking a partial list for the whole catalogue Read stock history before making another correction Review low-stock alerts without treating them as purchase orders Recover from an uncertain stock-adjustment response Keep variant stock separate from a product-wide count Find items, money and delivery in the order details screen Interpret Total, Paid and Due without assuming a bank confirmation Record a received balance using Clear due amount Check what Delete order removes before confirming Copy the right order reference for a support conversation Keep an operational note on the correct order Generate an order bill from the order record Download an already generated bill Find customer bills separately from platform invoices Inspect a bill before choosing Save or Share Investigate an empty bill list before assuming records were deleted Find the billing GST settings without relying on an old profile field Understand the confirmation before saving GST settings Distinguish the billing default from a product-specific tax setting Recover from a failed PDF save without duplicating the bill Change quantities and remove an item from your cart Understand an empty cart after changing browser or store Complete the fields your merchant requires at checkout Resolve a pincode validation or serviceability message Choose a delivery date the checkout actually permits Request a service time without assuming the slot is confirmed Handle an item that becomes unavailable at submission Understand Pay the store directly at checkout Look up one order with its reference and checkout contact Open My Orders using your checkout email Troubleshoot an order-history OTP that does not arrive Sign out of customer order history on a shared device Send a useful support report without exposing customer or payment secrets
oBizee Help Correct a payout-details validation error Direct payment
Correct a payout-details validation error The app can place an error beside UPI ID, account holder name, account number or IFSC. Correct the named field using your own verified information.
Source checked · 26 September 2026 Source-checked guidance Checked against the current local V1 app or storefront source. These instructions have not been independently executed in a live account. If your screen differs, confirm the app version before changing business data.
What to do Read the error beside the input and the Check the details message. Compare the value privately with a trusted bank record. Correct the full replacement payload, including other methods you intend to retain. Save once and inspect the masked result after reopening. What you should see The field error clears and the stored methods match the intended configuration.
If it does not work An uppercase IFSC presentation does not prove the branch or account is correct. Do not guess missing characters. If the error persists for a verified value, send the error wording and field label to support, not the complete sensitive value.
For support, include the screen name, time, app version and a redacted error. Never share passwords, OTPs, payment PINs or secret keys.