STYLEFORCE HELP / SELLER

Seller guide

Updated 23 October 2026. For store owners and authorized seller staff. The current example stores are demo/Test environments, not a promise of real payment, courier or statutory invoicing services.

Your store and subscription

StyleForce provides subscription-based storefront software. Your business manages its products, accepted prices, stock, fulfillment, customer support, policies, payment connection and delivery arrangements.

Specific subscription prices, billing frequency, inclusions and renewal terms still need agreement. Automated subscription collection is not available. Seller checkout payments remain separate from future StyleForce subscription billing.

Sign in securely

Open your store's seller login, or use the seller sign-in launcher. Use seller credentials, not a customer account. Owners and staff complete authenticator verification after their password. During enrollment, confirm a current code and keep the recovery codes privately.

Invite individual staff members and grant appropriate permissions. Do not share the owner password. Some settings and sensitive actions require owner access, a current password check or additional verification.

Set up the storefront

1. Complete the approved owner invitation and sign-in setup, including required authenticator enrollment.
2. In Settings → Store presentation, enter approved store, contact, support and policy content.
3. Add products, variants and eligible images. Review the public product pages.
4. Add the actual available inventory. Publishing a product does not add stock.
5. Configure supported delivery areas, charges, estimates and pickup options.
6. Review applicable business/tax inputs and the approved payment environment with the platform before any real trading.

Custom domains use an assisted verification workflow. Get the actual domain guidance from the platform; a requested hostname is not yet an active, verified storefront address.

Products, images and stock

Create products in the relevant category. Enter accurate names, descriptions, prices and variant attributes. Follow the media controls' file and publication limits. Do not invent measurements, package contents, warranties, discounts or tax inputs.

Use the supported dedicated logo/favicon library for brand assets. Where enabled, reusable size charts can be selected or inherited from the product category. Populate charts with your actual measurements.

Review the exact variant in Inventory before adjusting stock. Record a meaningful reason and inspect the result. If an operation times out, check the existing record before repeating an adjustment. Availability can change while customers browse.

Where import tools are available, review the preview and reported issues before applying it. Reuse the existing saved operation after an uncertain response rather than starting duplicate imports.

Store presentation and merchandising

Use approved store/contact information, product imagery and policy text. Review public pages after saving.

• Select eligible products for collections and homepage rows where offered.
• Set banners and announcements with valid destinations and realistic expiry dates.
• Review category links, search/share information and image descriptions.
• Keep policy content consistent with your operational cancellation, return and delivery settings.

A marketing banner alone does not configure a checkout discount. Use the supported offer controls and verify the accepted checkout amount.

Orders, fulfillment and delivery

Open Orders, inspect the accepted items, variants, payment and delivery details, and follow the offered fulfillment actions. Payment confirmation, packing, dispatch and delivery are distinct events. Record only work that actually happened.

Seller delivery settings define supported PIN codes, charges, estimates, free-delivery thresholds and pickup options where enabled. Test the intended address and basket before publishing a delivery claim.

Where a shipping integration is enabled, provide the actual pickup and packed-parcel details. An unknown booking result is not a definite failure: inspect or reconcile the original booking before starting another. Manual tracking should accurately identify its source. Demo courier events do not arrange real collection.

Payment and shipping connections

Use only the designated owner connection screen and the approved environment. Do not paste provider credentials into tickets or free-text settings. The current hosted preview supports a seller-owned Razorpay merchant Test connection; this does not permit Live keys or establish completed Live acceptance. Shipping-provider availability also depends on approved seller configuration.

A configured connection that fails must be investigated; it must not be treated as a successful mock payment or courier booking. Preserve the original order/operation reference after a timeout. Disconnection does not necessarily cancel an external operation already in progress.

Returns, refunds, billing and reports

Review the after-sale request, accepted policy and fulfillment facts. Record receipt and inspection accurately before the offered decision or restock action. A customer conversation or returned parcel does not automatically approve a refund.

Track refunds until a verified outcome is recorded. Do not issue another refund merely because a response timed out.

Billing provides available TEST documents and formatted invoice/credit copies with browser Print/Save as PDF. These preserve accepted seller, tax and order snapshots. They are not evidence of live statutory issuance or StyleForce subscription renewal invoices. Reports summarize application records; recorded payment capture is not proof of bank settlement. Access depends on your role and permissions.

Enable StyleForce customer sign-in

As the owner, open Settings → StyleForce sign-in and complete the required verification to enable or disable participation. Each seller's choice is independent.

Customers keep separate store accounts, carts and orders. Matching email addresses do not import older purchases automatically; customers must prove ownership of the older account and select it. Read Accounts and sign-in. Customer entry never grants seller access.

Staff, support and exports

Use Customer support for your customers' purchase questions and Platform technical support for software issues. Include the action, time and safe reference ID. Omit passwords, provider keys and unrelated customer records. A technical ticket does not authorize someone else to make your fulfillment or refund decisions.

External email/SMS delivery is not implied by an in-app notice. Email/OTP recovery delivery is not enabled in the current demo preview.

Where available, the owner can use Export and offboarding to review scope and create a private export. Refresh its status and download through the authorized control before expiry. Keep downloaded business data private. Exports exclude some records and binaries; they are not a complete backup. The offboarding preview does not delete the store, and export expiry is not physical erasure.

Daily review and troubleshooting

Review new orders, unresolved refunds/support cases, stock shortages, missing content and failed actions. Before any real launch, confirm seller identity, policies, tax inputs, payment acceptance and delivery arrangements with the platform.

If a save reports a conflict, reload and compare the current values before resubmitting. If access is denied, confirm the store, role, permissions and session. For an unresolved payment or courier operation, preserve its reference and use its supported review path.

Return to the help centre or read the customer guide.