Close
logo

Custom fulfillment flows

Git RepositoryEdit on Github
Last update: a year ago by JettiReading time: 2 min

Custom fulfillment flows

Jetti will out the box send fulfillment details to your channel. For example, when an order is shipped from a dropship provider, Jetti will automatically send the tracking details back to your channel (e.g. your Shopify or custom channel). From there, typically a notification is sent to the customer.

However, there may be additional use cases you need to support alongside this. In this example, we'll look at how we can use Zapier to poll for a list of new shipments, to then send pick-up information to a carrier.

Polling for shipment information

To poll for new shipments, you can query the dropshipments.json resource. The dropshipments resource contains a list of shipped dropship purchase orders. You can filter this list if needed. However, by default it will show all shipments order with the most recent first.

The list on its own may not be useful. So, you may want to include additional data, such as the dropship provider, customer and details of the line items. You can use the include mechanism for this. However, in the API, we provide pre-defined API scopes to avoid overly complex query building. An example of this is the feed scope.

curl --request GET \
--url 'https://api.jetti.io/api/dropshipments.json?scope=feed' \
--header 'Authorization: Bearer {{token}}'

With the above data, you can access all of the required data to automate external tasks. For example, look for new entries in the list and trigger an external pick up notification through Zapier to a last mile delivery partner. You'll look for any new id entries when polling (as that's the unique identifier for new shipments). Then triggering the corresponding action (e.g. sending a notification through an email delivery service).

๐Ÿ  In-house inventory โ€” Previous
Updating inventory
Next โ€” ๐Ÿ“ฆ Shipping
Custom tracking integrations