Administration / Configuration

Platform Settings: Tab-by-Tab Guide

Configure SigmaCart’s storefront, applications, integrations, payments, communications, analytics, tax, and system preferences from one central settings workspace.

Open Platform Settings

Sign in to the Admin Panel and navigate to Settings. Select a tab, update its options, and use Save Settings to store your changes.

Admin Console Dashboard → Settings → General Settings → Select Tab → Update Fields → Save Settings

Settings tab map

01General02Design03Customer Application 04Delivery Application05Store Dashboard06Android Apps 07SEO08Push Notifications09Social Login 10Google Maps11Payment Gateways12SMS Settings 13Email Settings14Google Analytics15Tax Settings 16Translations17Custom CSS

Tab 01General Settings

Configure the platform identity, locale, currency, operational timing, image handling, payment behavior, and administrative targets.

Setting	Purpose
Website URL	Public storefront URL. Use the complete production HTTPS address.
Store Name	Primary platform or marketplace name.
Application Time Zone	Controls order, expiry, notification, and reporting timestamps.
Store Currency / Symbol / Alignment	Defines the transaction currency and how its symbol appears.
Wallet Name	Customer-facing label for the wallet feature.
Minimum Store Payout	Minimum amount required before a store payout can be processed.
Order Acceptance Threshold	Maximum store-response time before the administrator is alerted.
Delivery Acceptance Threshold	Maximum delivery-agent response time before the administrator is alerted.
Upload Image Quality	Controls quality for images uploaded through supported dashboards.
Awaiting Payment Threshold	Defines how long an order may remain awaiting payment; cron processing is required.
Store Payment-Gateway Selection	Allows store owners to select supported payment methods when enabled.
Daily Revenue Target	Sets the administrative revenue goal displayed by supported dashboards.
Development Mode	Enables development-specific behavior. Keep disabled on production unless instructed.

Currency changes affect commerce

Do not change the currency on an active store without reviewing product prices, payment gateways, taxes, delivery fees, wallets, commissions, reports, and existing orders.

Tab 02Design Settings

Setting	Guidance
Logo	Upload the primary brand logo in a supported format and test it on desktop and mobile.
Favicon	Upload a square, recognizable browser icon.
Store Color	Defines the main storefront brand color.
Store App Primary Color	Sets the primary color used by supported store-application interfaces.
Cart Background / Text	Choose colors with sufficient contrast for clear cart information.
New / Popular / Recommended Badge	Configure distinct but accessible colors for product-status badges.

Accessibility first

Verify text contrast, focus states, buttons, cart content, and badges in both light and dark environments before publishing new colors.

Tab 03Customer Application

This tab controls storefront checkout, discovery, address, PWA, cart, promotion, dietary, privacy, and loading behavior.

CheckoutCOD, tips and pickupConfigure COD for self pickup, cash-change prompts, tip amounts or percentages, and self-pickup availability.

DiscoverySearch and store orderSort stores by distance, randomize stores, show inactive items, and configure homepage search.

ExperienceCart and interfaceControl addon prices, item counts, promo sliders, badges, date formatting, layouts, menus, and loading spinners.

Group	Available controls from the Blade resource
Payments and checkout	COD on self pickup, cash-change prompt, delivery tips by amount or percentage, coupon-description success message, dynamic-delivery rounding.
Store discovery	Sort delivery/self-pickup stores by distance, Google Distance Matrix, randomize stores, homepage search.
Address	Automatic full address, mandatory flat/apartment, delivery PIN, default phone-country code.
Cart and products	Addon prices, total quantity, inactive items, veg/non-veg badge, hide zero price, discount percentage.
Promotions and layout	Promo slider, Recommended Layout V2, expand all item menus, footer navigation style.
PWA and privacy	PWA installation footer, iOS add-to-home popup, GDPR checkbox, tax/VAT number.
Presentation	Try on Phone, relative date/time, simple loading spinner.

Test checkout after changes

Any change involving COD, self pickup, tips, address, distance, delivery charge, coupons, or product pricing should be tested through a complete customer checkout.

Tab 04Delivery Application

Setting	Purpose
Enable Delivery Guy Earnings	Turns on earning calculations and related views for delivery agents.
Earning Source	Defines the value or basis from which the agent’s commission is calculated.
Full Address on Order List	Shows delivery addresses directly in supported order listings.
Customer Information Before Pickup	Controls whether customer address or information is visible before package pickup.
Order Add-ons	Shows selected product add-ons to the delivery agent.
Price, Total and Comments	Shows commercial details and customer comments in the delivery workflow.
COD Collection	Displays the delivery agent’s cash-on-delivery collection information.

Balance privacy and operations

Expose only the customer and commercial data an agent requires at each stage of fulfillment.

Tab 05Store Dashboard

Setting	Recommendation
Hide Customer Details	Enable when store owners should not receive customer contact or address information beyond operational need.
New Order Fetch Rate	Choose a reasonable refresh interval that balances timely orders with server load.
Notification Tone	Select the audio used for supported new-order alerts and test browser autoplay permissions.

Tab 06Android Apps

Enable only the applications and services you have installed and configured.

SigmaCart Customer Android App
SigmaCart Delivery Android App
SigmaCart Store Android App
SigmaCart SocketPush Service
Firebase Realtime Database URL
Matching mobile-app environment

Do not enable unavailable apps

Turning on an app integration without its matching build, credentials, database, or push service can create broken links and missing notifications.

Tab 07SEO Settings

Field	Purpose
Meta Title	Main search-result title for supported pages.
Meta Description	Concise search-result summary.
Open Graph Title / Description / Image	Controls previews on supported social and messaging platforms.
Twitter Card Title / Description / Image	Controls supported X/Twitter link previews.

Use production URLs

After saving SEO settings, inspect the rendered page source and test public share previews. Cached social previews may take time to refresh.

Tab 08Push Notifications

Enable push notifications. Turn on the master option only after credentials are ready.
Enable order notifications. Choose whether supported order events generate pushes.
Configure Firebase Web Push. Enter the Sender ID, public key, and server key expected by the installed integration.
Configure OneSignal if used. Enter the App ID and REST API key.
Write the new-order message. Keep the store notification concise and useful.
Test browser and app delivery. Confirm permission prompts, background delivery, and order links.

Protect server credentials

Never place secret or server keys in public documentation, screenshots, frontend code, or support messages.

Tab 09Social Login

Provider	Settings	Verification
Facebook	Enable Facebook Login, App ID, login-button text.	Configure the exact production domain and callback URL in the provider console.
Google	Enable Google Login, Google App ID, login-button text.	Add approved JavaScript origins and redirect URIs, then test new and existing accounts.

Tab 10Google Maps

Setting	Use
Show Map on Order Tracking	Displays supported map tracking to customers.
HTTP-Restricted API Key	Used for browser-facing map requests where referrer restrictions are supported.
IP-Restricted API Key	Used for server-side requests where server IP restrictions are supported.
No-Restriction Key	Used by features that explicitly require it, such as the referenced store-location picker. Handle with exceptional care.

Restrict every key whenever possible

Enable only required Google APIs, apply the restriction type expected by each integration, set usage quotas, and monitor billing. Never reuse unrestricted keys in public frontend code.

Tab 11Payment Gateways

The Blade resource supports gateway enablement and configuration for Stripe, PayPal, Paystack, Razorpay, PayMongo, Mercado Pago, Paytm, Flutterwave, and Khalti.

Gateway	Configuration fields shown
Stripe	Public key, secret key, locale, postal code, iDEAL, and FPX options.
PayPal	Environment, sandbox key, and production key.
Paystack	Public key and private key.
Razorpay	Merchant ID, Key ID, Key Secret, and Webhook Secret.
PayMongo	Public key and secret key.
Mercado Pago	Access token.
Paytm	Environment, Merchant ID, Merchant Key, Website, Industry Type, and Channel ID.
Flutterwave	Public key.
Khalti	Public key and secret key.

Select the correct environment. Use sandbox or test mode before production.
Enter credentials exactly. Remove accidental spaces and never expose secret values.
Configure callbacks and webhooks. Use HTTPS production URLs and verify webhook signatures.
Test success, failure and cancellation. Confirm the order and transaction states remain consistent.
Enable production only after reconciliation. Verify captured amounts, refunds, fees, and currency.

Tab 12SMS Settings

Area	Configuration
Default Gateway	Select MSG91 or Twilio.
MSG91	Auth Key, Sender ID, and DLT template IDs for OTP, store orders, and delivery-agent orders.
Twilio	Account SID, access token, and sending phone number.
Authentication	Login/registration type, OTP verification, and OTP message.
Store Notifications	Enable new-order SMS, define the message, and optionally include order value.
Delivery Notifications	Enable delivery-agent new-order SMS and define the message.
Customer Order Status	Enable supported status SMS notifications.

Regulatory templates may be mandatory

For MSG91 in India, align Sender ID and every message with approved DLT registrations. Twilio trial accounts may send only to verified recipients.

Tab 13Email Settings

Area	Settings
Default Gateway	Select SendGrid or SMTP.
SendGrid	API key.
SMTP	Host, port, username, password, and encryption.
Sender Identity	From email address and From name.
Password Reset	Enable reset email and configure its subject.
Order Invoice	Enable invoice email and configure its subject.

Verify deliverability

Use a domain-authorized sender and configure SPF, DKIM, and DMARC. Test password-reset and order-invoice emails before relying on them in production.

Tab 14Google Analytics

Enable analytics and enter the Analytics ID expected by the installed SigmaCart integration. The Blade label references a UA ID, so confirm whether your release supports GA4 before entering a G-... Measurement ID.

Consent may be required

Implement the cookie and consent behavior required in the countries where you operate, and avoid collecting sensitive personal or payment data in analytics events.

Tab 15Tax Settings

Confirm the applicable tax rule. Consult a qualified tax professional for your products and operating region.
Enable tax. Turn it on only after product pricing and invoice behavior are understood.
Enter the tax percentage. Use the correct numeric rate.
Test calculations. Verify subtotal, discount, delivery fee, rounding, and final total.
Review invoices and refunds. Ensure tax is represented correctly throughout the order lifecycle.

Tab 16Translations

The Translations entry opens a dedicated management page rather than an inline settings tab. Use it to maintain supported interface strings and languages.

Preserve placeholders and variables
Use consistent terminology
Review text length on mobile
Test fallback language
Check checkout and error messages
Clear translation cache if required

Tab 17Custom CSS

The Blade resource provides separate editors for storefront custom CSS and admin-dashboard custom CSS.

Editor	Scope
Custom CSS	Overrides supported customer-facing storefront styles.
Admin Custom CSS	Overrides supported administration-panel styles.

/* Keep selectors narrow and document every override. */
.storefront-banner {
  border-radius: 16px;
}

Back up CSS before editing

Invalid or overly broad selectors can hide controls, break responsive layouts, or reduce accessibility. Test storefront and admin CSS independently on desktop and mobile.

Recommended configuration order

General and Design. Establish URLs, locale, currency, brand identity, and core behavior.
Customer, Delivery, and Store applications. Configure operational and user-experience features.
Maps and Social Login. Register domains, callbacks, APIs, and restrictions.
Payment Gateways. Complete sandbox testing before production credentials.
SMS, Email, and Push. Configure providers and test every important notification.
SEO, Analytics, and Tax. Validate public metadata, tracking consent, and financial calculations.
Translations and Custom CSS. Apply content and presentation refinements last.

Final verification checklist

Production URL uses HTTPS
Time zone and currency are correct
Logo, favicon, and colors are tested
Customer checkout completes
Store and delivery workflows work
Maps and social callbacks work
Payment success and failure are tested
SMS, email, and push are delivered
SEO metadata renders correctly
Tax totals and invoices are verified
Secrets are not publicly exposed
Development mode is disabled

Platform configuration complete

After saving and testing every enabled integration and workflow, clear relevant caches and perform one final end-to-end order using production-like settings.

Troubleshooting

Problem	What to check
Saved value does not appear	Confirm Save Settings succeeded, reload the correct tab, and clear configuration, application, and frontend caches.
Integration fails	Check environment, exact credentials, enabled provider, callback URL, API permissions, restrictions, and server logs.
Checkout breaks	Review currency, tax, gateway selection, delivery settings, store configuration, and recent custom CSS or scripts.
Notifications are missing	Verify provider credentials, templates, contact data, queues or cron, app permissions, and notification toggles.
Map does not load	Check API key type, enabled Google APIs, billing, domain or IP restrictions, quotas, and browser errors.
Mobile layout changed	Review custom CSS, colors, footer style, layout toggles, cache, and responsive testing.

Settings #