Extension Development Guide
The workflow begins with scheme creation, where the logistic services are defined, including their features, regions, and transport types. Next, serviceability areas are configured by uploading a detailed CSV file specifying the regions where the services will operate. Following this, a Turn Around Time (TAT) file is uploaded to define delivery timelines for various locations. Once the scheme is set up, an account creation function when a seller subscribes to a scheme.
To monitor and automate the process, the integration listens to delivery events via webhooks, which trigger actions such as notifications or status updates based on delivery events.
Finally, the extension undergoes a review and submission process to ensure it is fully operational and meets Fynd's standards before being available to sellers.
Follow these development best practices before starting extension development to ensure a smooth, efficient, and maintainable process.
📄️ Boilerplate Overview
Logistics extension boilerplate code explanation for the pre-written FDK codebase. Understand project structure, routes, and components for building Fynd Commerce delivery partner extensions.
📄️ Create Scheme
Create delivery partner scheme UI using FDK methods for logistics extension service plan configuration. Outlines process and methods for building scheme setup interfaces for sellers.
📄️ Create Account
Create delivery partner accounts in Fynd Commerce using FDK methods from your logistics extension. Guide for account creation flow and API integration with Fynd Platform.
📄️ Listening to Delivery Events
Listen to delivery events with webhooks in Fynd Commerce logistics extensions. Learn how webhooks trigger actions after shipment and logistics events from Fynd Platform.
📄️ Update Status and Info
Update shipment status and tracking information in Fynd Commerce using FDK methods from your logistics extension. Keep platform and sellers synchronized with delivery partner tracking data.