Distru's Onfleet integration keeps your sales orders and your last-mile delivery routing in sync automatically, so your dispatch team never has to enter the same delivery twice.

This article explains what the integration does, what it doesn't do, and the key rules to know before you turn it on. If you're ready to set it up, see the companion article
​

Onfleet is delivery and logistics software. It's where your team plans routes, assigns drivers and vehicles, and tracks deliveries in real time. Drivers use the Onfleet mobile app on their phones to see their stops, navigate, and capture proof of delivery.

Distru is where your orders, inventory, and METRC compliance live. The integration connects the two so that an order you create in Distru can be pushed into Onfleet as a delivery task. It's a one-way integration — Distru sends orders to Onfleet, and only a small amount of information comes back at the end (the driver's name on a transfer template, and the signature/photos on the order).

At a high level, you push orders from Distru into Onfleet for routing. This is a one-way ("one-and-a-half-way") integration: Distru sends order data to Onfleet, and only two things ever come back, both at the end. The capabilities are:
​

• Orders in Distru become tasks in Onfleet. When you flag a sales order to sync, Distru creates a delivery task in Onfleet carrying the order's data: address, order and invoice numbers, delivery city, customer and contact info, and the delivery window.
​

• Optionally, the driver's name can be written to a METRC Transfer Template. If you use the Populate Transfer Template option, the driver assigned in Onfleet is written into a transfer template in Distru. This is optional and it only applies to METRC-tracked accounts.
​

• At the end, proof of delivery comes back. When the driver completes the delivery in Onfleet, the signature and photo they captured are attached to the Distru sales order.
​

Once the integration is enabled, four custom fields are added to your sales orders: Onfleet Integration, Complete After, Complete Before, and Transfer Type. The main control is the Onfleet Integration field, which has three options:
​

• Create Task: Creates a delivery task in Onfleet from this order. The task carries the order's address, customer info, and delivery window. Once created, the Onfleet task ID is noted back on the order.

• Don't Create Task: No task is created. This is also the default behavior if you leave the field blank; an order with no option selected is treated as "Don't Create Task."

• Populate Transfer Template: After a driver is assigned in Onfleet, this writes the driver's name into a METRC Transfer Template — driver name only, not license or vehicle. Optional, and available on METRC-tracked accounts only.
​

Proof of delivery is the end of the workflow and the main thing that syncs back into Distru. When a driver completes a task in the Onfleet app, Onfleet can require a photo and a signature. Once the delivery is completed, those images are pulled into Distru and attached to the sales order's Attachments tab. Nothing else about the delivery comes back — the order's status does not change based on Onfleet activity.

Note on storage: Because signature images and drop-off photos are imported into your Distru account, high delivery volumes can use up your file storage over time. If you're a heavy Onfleet user and notice you're running low on storage, reach out to your CSM, you can check this in Settings > Company > Company Storage
​

This is an optional feature, and it only applies to METRC-tracked accounts. It's for operators who juggle many drivers and don't want to retype driver details on every transfer template.
​
How it works: Assign Onfleet Tasks that were created by Distru to a Driver. Then, back in Distru, edit the sales order, set Onfleet Integration to Populate Transfer Template, and choose the Transfer Type. Distru creates the transfer template and writes the driver's name into it. It writes the driver's name only — not vehicle details or other driver data. You can still edit the transfer template before registering it in METRC.

No. Only orders you set to Create Task are sent to Onfleet. Orders left blank or set to Don't Create Task stay in Distru only.
​

An order with no option selected behaves as Don't Create Task. Set it to Create Task and save to send it to Onfleet.
​

No. Onfleet doesn't push status changes back to Distru. The order keeps its existing status even after the task is started or completed in Onfleet.
​

They're attached to the order's Attachments tab in Distru after the driver completes the delivery in Onfleet.
​

Yes. Re-run the same workflow on the sales order: set the Onfleet Integration field to blank (or Don't Create Task) and save, then set it back to Create Task and save. A new task will be created in Onfleet.