In this article, you will learn about the Blaze and Onfleet integration.
BLAZE™ is an enterprise resource planning platform for the legal cannabis industry and with Onfleet's integration, it allows Blaze users to consolidate their operations into one dashboard, stay proactive with real-time ETA's and reduce costs by identifying/eliminating bottlenecks, and much more. With this integration, your team is also able to track time, distance, and performance data of drivers to accurately compensate them.
This integration supports Onfleet task creation, Status updates via Onfleet webhooks, Driver tracking, custom metadata, and driver management. Meaning this integration allow you to:
- Assign in Onfleet will assign in Blaze if inventory is available.
- Delete in Onfleet which removes the connection in Blaze. (You still have to close it in BLAZE).
- Update the scheduled time in Onfleet and it will update the scheduled time in Blaze.
- Complete an order in Onfleet and while it still needs to be completed in Blaze, an indicator in our
- The dispatch section will show the order was completed in Onfleet.
The workflow for your Blaze + Onfleet integration will be as follows:
- An order is placed either online or via phone to a Blaze user.
- Online orders - Your dispatcher will review the order and accept it.
Phone orders - Your dispatcher adds the user, creates the order, views available drivers/inventory.
- The order is then assigned to an Onfleet team.
- The task is created in Onfleet with order details within the task notes.
- Driver will use Onfleet to start tasks, view order details, and navigate to task location.
- Driver will use the Blaze app to capture a signature, DL images, and cash out the order.
- Task will then be automatically closed within Onfleet.
If you are running into any errors with your Onfleet integrations please feel free to reach out to the Onfleet Support Team at email@example.com. We strongly recommend reaching out to the Blaze's support team as well, since some issues may be originating on the partner's end and Onfleet is unable to view activity on third-party integrations.
Usually, the most common causes of errors may be due to location and task completion times. Since Onfleet uses Google Maps API to geocode all task locations, we recommend you cross-reference your task address in Google Maps to ensure the location information is correct and in the correct format.
Task completion times must be in the future, and tasks that are past-dated are, unfortunately, unable to be created or completed within the Onfleet integrations.