Salla Docs
Merchant
Merchant
  • Merchant API
  • Salla OAuth 2.0
  • Merchant Dashboard
Partner APIs
Partner APIs
  • App API
  • Shipments & Fulfillment APIs
  • Salla AWB
  • Recurring Payments API
  • App Functions
  • Billing System Salla partners
  • App Onboarding
Storefront
Storefront
  • Twilight Engine
  • Twilight SDK
  • Web Components
  • Ecommerce Events
  • Component Bundle
  • Change Log
Salla CLI
Merchant
Merchant
  • Merchant API
  • Salla OAuth 2.0
  • Merchant Dashboard
Partner APIs
Partner APIs
  • App API
  • Shipments & Fulfillment APIs
  • Salla AWB
  • Recurring Payments API
  • App Functions
  • Billing System Salla partners
  • App Onboarding
Storefront
Storefront
  • Twilight Engine
  • Twilight SDK
  • Web Components
  • Ecommerce Events
  • Component Bundle
  • Change Log
Salla CLI
Salla - Opensource
Salla - Developers Community
  1. App Onboarding
  • Overview
  • Get Started
  • Interfaces and Responses
  • Real World Scenario
Merchant
Merchant
  • Merchant API
  • Salla OAuth 2.0
  • Merchant Dashboard
Partner APIs
Partner APIs
  • App API
  • Shipments & Fulfillment APIs
  • Salla AWB
  • Recurring Payments API
  • App Functions
  • Billing System Salla partners
  • App Onboarding
Storefront
Storefront
  • Twilight Engine
  • Twilight SDK
  • Web Components
  • Ecommerce Events
  • Component Bundle
  • Change Log
Salla CLI
Merchant
Merchant
  • Merchant API
  • Salla OAuth 2.0
  • Merchant Dashboard
Partner APIs
Partner APIs
  • App API
  • Shipments & Fulfillment APIs
  • Salla AWB
  • Recurring Payments API
  • App Functions
  • Billing System Salla partners
  • App Onboarding
Storefront
Storefront
  • Twilight Engine
  • Twilight SDK
  • Web Components
  • Ecommerce Events
  • Component Bundle
  • Change Log
Salla CLI
Salla - Opensource
Salla - Developers Community
  1. App Onboarding

Real-World Scenario: Store Personalization

In this step, your App asks the Merchant to define their niche so you can pre-configure the App's layout. We will validate two fields: business_category (Dropdown) and primary_goal (Radio/Selection).

The Validation Logic#

1
Selection Requirement
Ensure the merchant has selected a category from the list.
2
Logic Constraint
If they select "Other" as a category, you might require them to provide additional details. (For this minimal example, we will ensure they at least make a primary selection.)

Implementation Example#

Field KeyUX PurposeValidation Focus
business_categoryAllows the app to load industry-specific templates (e.g., Food vs. Fashion).Presence check (Ensures the value is not empty).
primary_goalDetermines which metrics (ROI, Conversion, or Traffic) appear on the home screen.Data integrity (Ensures the value matches your accepted list).
Important
Contextual Feedback
By using .setFields(), the error message appears directly under the Business Category dropdown, ensuring the merchant notices and corrects it.
Immediate Value
The success() block triggers a personalized dashboard. This creates an "Aha!" moment for the merchant and reinforces the value of completing onboarding.
Modified at 2026-02-18 17:37:29
Previous
Interfaces and Responses