Customer | End consumer who purchases products and services offered through sales channels of a company. | User |
Merchant | Either owner of a Fynd Platform account or its authorized staff members who can use the feature being described. | Seller |
Selling Location | Physical Store, warehouse, storage facility, or fulfillment center where merchants keep their inventory stock. | Store, Location |
Application | Sales channel through which customers explore merchant offerings and make purchase. | Sales Channel, Storefront |
Application API | Gives access to customer facing data of an application to power storefront user experience. | Storefront API |
Application ID | Unique identifier of a sales channel of a company. | |
Company | A merchant account on Fynd Platform. | Fynd Platform Account, Merchant or Seller Account, Account. |
Company ID | Unique identifier of a company. | |
Extensions | Plugins that extend the functionality of a merchant's company on the Fynd Platform by offering additional features beyond the basic capabilities. | |
Fynd Development Kit (FDK) | Suite of resources and tools designed to expedite extension and theme development and improve developer productivity. | SDK |
FDK Client | SDK library that abstracts away the underlying complexities of making API requests to Fynd Platform and handling responses. | SDK libraries, FDK Client libraries, fdk-client-javascript, fdk-client-java |
Platform API | Gives access to merchant facing data of a company like creating products, updating inventory, creating promotions, and so on. | |
Company level platform API | Gives access to merchant facing data that isn't related to a specific sales channel and generally affects all the sales channel. You don't require to specify Application ID in these APIs. | |
Application level platform API | Gives access to merchant facing data related to a specific sales channel. You need to pass Application ID in these APIs to specify which sales channel the API is requested for. | |
Partner API | Gives access to partner account data and helps in extension and theme management. | |
Theme Editor | Allows merchant to customize the appearance and functionality of their online store by modifying layout, and design elements. | |
Partner Organization | A partner account created on Fynd Partners required for accessing Fynd Platform as a partner. | Partner Account |
FDK CLI | Streamlines development tasks, enabling developers to create starter code template, build, and test extensions and themes efficiently from the command line. | |
Environment | Cluster in which the extension or theme is being built. Can be derived from the domain where your partner account is created. If your partner account is created on https://parters.fynd.com then environment (or cluster) URL would be https://api.fynd.com | Cluster |
Themes Marketplace | Themes store where merchants can explore and install ready to use themes for their online storefront. | Themes Store |
Live Account | Represents an access of a partner organization to a merchant operated company on Fynd Platform. Live account id is same as company id. | Company |
Development Account | Test company on Fynd Platform used by developers for testing extensions or themes before they are made available to merchants. | |
Partner Panel | User interface provided to Fynd partners enabling developing and publishing extensions and themes, managing development and live accounts, accessing resources, and tracking performance metrics. | |
Extension URL | Hosting URL of the extension server | Base URL, Launch URL, Hosting URL |
Action Component | Vue components that expose functions for theme developer to call Application API. | |
Sections | Sections are re-usable UI elements which can be configured from Theme Editor. | |
Blocks | Blocks are used as multi-entry props for a section. These are configurable from Theme Editor. | |
Theme Components | UI Components exported from a theme. | |
System Pages | Pre-defined pages for a theme. | Theme Pages |
Global Components | Components defined in theme engine which can be used by theme developers. | |
Fynd Platform Interface (FPI) | Class that helps manage extension theme bindings and listen to events triggered by theme engine in online storefront during customer sessions. | |
Theme Binding | Enables extension UI components to be dynamically rendered in the online storefront. | |
Extension Type | Represents the way in which extension interacts with Fynd Platform and type of use case solved. Following type of extension can be created: General, Payments, Sales Channel & Logistics. | |
Company-level Extension | Provide features that are not related to sales channels and are accessible to merchants from the Extensions tab under Company area on Fynd Platform. | Company Launch Type |
Application-level Extension | Add features in sales channels and are accessible to merchants from Extensions tab under Sales channels. | Application Launch Type, Sales Channel-level Extension |
Marketplace Extension | Connect merchant stores to marketplaces like Amazon, Flipkart, AJIO, and so on. | Sales Channel Extension |
Payments Extension | Integrate Fynd Platform with Payment Gateway or Payment aggregator to provide payment processing services to merchants. | |
Logistics Extension | Integrate Fynd Platform with Delivery Partners to provide delivery services to merchants. | |
Extension Distribution | Refers to the way extension is published to be accessible to intended merchants. | |
Private Extension | Distributed to and installable by specific companies | |
Public Extension | Published on extensions marketplace and can be installed by any merchant on Fynd Platform. | |
Partner Access Token | Authentication token generated from partner panel that is required to create extension and theme through FDK CLI. | |
FDK Extension Library | Streamlines extension development by auto handling extension OAuth implementation and providing methods to generate API Clients, subscribe to webhooks, and implement extension’s session and access token storage. | Extension Helper Library, fdk-extension-javascript, fdk-extension-java |
Access Scope | Represents a permission given to API client to access required data of merchant's company. | Scopes, Permissions, API scopes |
Extension Proxy URL | Enables extension to make API calls to its server from online storefronts using Fynd Platform as a proxy so as to avoid CORS error by browser. | |
Extension ID | Unique identifier of an extension. | Extension Client ID, extension-api-key |
Extension Secret | Secret key used for authenticating interaction between Fynd Platform and extension. | Extension Client Secret, extension-api-secret |
Access Mode | Determines the way access token can be used to call Fynd Platform APIs. It can be Online or Offline. | |
Online Access Mode | Generates temporary access token to be used for calling Fynd Platform APIs while merchant is actively interacting with extension in iframe on Fynd Platform's merchant panel. | |
Online Access Token | Token generated using Online Access mode. Can only be used for calling Fynd Platform APIs when the extension is opened in iframe by merchant on Fynd Platform.. | |
Offline Access Mode | Used for calling Fynd Platform APIs in background tasks that don't require active merchant session like handling payments, updating inventory. | |
Offline Access Token | Token generated using offline access mode and can be used to call Fynd Platform APIs in background tasks. | |
Extension Launch type | Determines where in the merchant panel the extension is accessible to merchants to open it in an iframe. | Launch location |
Extension Bridge Library | Helps to set up contextual UI components as part of the header when extensions are launched in iframe. | |
Public Theme | Themes that can be used and customized by multiple merchants as per their requirements. These themes are listed on themes marketplace. | |
Custom Theme | Theme developed for a specific storefront and is not easily customizable for other storefronts. | |
Partner Access Token | Authentication token generated from partner panel that is required to create extension and theme through FDK CLI. | |
Turn Around Time (TAT) | It indicates the time to deliver a shipment in regions/pin codes. This TAT data will be used to provide an indicative delivery date when customers go through the storefront journey across PDP, Cart, and check-out pages. TAT data needs to be provided to the platform system. Therefore, it is up to the extension’s owner to choose whether to update the data and the frequency of the data. | |