Skip to main content

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 turnaround 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.

Best Practices

Follow these development best practices before starting extension development to ensure a smooth, efficient, and maintainable process.


Was this section helpful?