Overview#
Welcome to the App Functions documentation for third-party developers. This comprehensive guide will help you build powerful, event-driven applications on Salla platform.
What are App Functions?#
App Functions allow you to embed custom logic directly into the lifecycle of merchant and customer activities on Salla. Write serverless functions that execute automatically when specific events occur in a store - no infrastructure to manage, automatic scaling, and seamless integration with Salla APIs.
📚 Documentation Structure#
Core Documentation#
🚀 Get Started — Get started with your first App Function in minutes 📋 Supported Events — Complete list of all available merchant and customer events Event Reference#
The event directories contain detailed schemas and examples for all available events:🏷️ Brand Events — Brand creation, updates, and deletion
📦 Order Events — Order lifecycle events
🛍️ Product Events — Product management events
👤 Customer Events — Customer account events
🚚 Shipment Events — Shipping and fulfillment events
Quick Links#
Getting Started#
Key Concepts#
Execution Types#
Synchronous Actions — Execute immediately, block the user, must respond in milliseconds (e.g., shipment.creating)Asynchronous Events — Process in the background after the operation completes (e.g., order.created)Customer Events — Triggered by storefront interactions, always asynchronousContext Object#
Every function receives a context object:Pricing#
App Functions are currently in beta and free of charge. When generally available, pricing will be based on:Common Use Cases#
Merchant Events#
Order Management — Send confirmations, sync with fulfillment systemsInventory Sync — Update external inventory systems when products changeShipping Integration — Calculate rates, generate labels, track shipmentsCustomer Sync — Update CRM systems with customer dataAnalytics — Track business metrics and generate reportsCustomer Events#
Behavior Tracking — Monitor product views, searches, and interactionsCart Recovery — Send reminders for abandoned cartsPersonalization — Customize user experience based on behaviorMarketing — Trigger campaigns based on customer actionsAnalytics — Track conversion funnels and user journeysExample Function#
Here's a simple example that sends order data to a webhook:Best Practices#
Keep Functions Focused#
Each function should have a single, clear purpose. Break complex logic into multiple functions.Use Settings for Configuration#
Store API keys, URLs, and feature flags in app settings, not in code.Return Consistent Responses#
Always return an object with a success boolean and relevant data or error information.Test Thoroughly#
Test with various scenarios including success cases, failures, and edge cases.Check that required data exists before using it to prevent runtime errors.Keep Responses Small#
Return only necessary data. Large responses can slow down execution and make debugging difficult.Available Events#
Merchant Events (50+ events)#
Orders — created, updated, cancelled, refunded, etc.Products — added, updated, deleted, quantity low, etc.Shipments — creating (sync), created, cancelled, updatedCustomers — created, updated, login, OTP requestBrands — created, updated, deletedCategories — created, updatedStore — branch management, tax configurationSpecial Offers — created, updatedCheckout — started, step completedCustomer E-commerce Events (25+ events)#
Product Interactions — viewed, clicked, searched, shared, reviewedCart & Checkout — product added/removed, cart viewed/updated, checkout flowPromotions — viewed, clicked, coupon entered/applied/denied/removedWishlist — product added/removed, added to cartUser Account — signed in/up/out, profile updatedResources#
Documentation#
Support#
Community — Join our developer communityPartner Portal — Access support through the portalDocumentation — Comprehensive guides and referencesTypeScript Support#
All events have TypeScript interfaces for better development experience:
Next Steps#
Ready to get started? Follow these steps:Modified at 2025-11-17 11:41:06
