Route Optimization
BRIGHTREE HME + SUITEFLEET

Brightree HME Route Optimization with SuiteFleet

ERP

Plan routes for Brightree HME delivery work using origin, destination, and receiving windows. Review assignments and unassigned stops.

Free Trial
Brightree HME order with SuiteFleet delivery fields
Big & bulky last mile delivery — oversized goods and furniture delivery
Planning inputs
Carry verified destinations, shipment references, receiving windows, and departure locations into the planning workflow before assignment.
Geographic selection
Use the operations map to identify eligible stops and resolve missing locations before calculating a proposed route.
Preview review
Inspect driver workload, stop sequence, and unassigned tasks before applying the plan to the intended fleet.
Actual outcomes
Reconcile customer delivery after execution while keeping route planning separate from shipment posting and accounting activity.

The Brightree HME–SuiteFleet workflow turns released work from sales orders and delivery tickets into stops with a loading point, destination, and receiving window. Dispatchers review drivers, optimization objectives, and unassigned stops before applying a route. Actual completion is reconciled afterward using equipment lines and asset references.

Connector availability: SuiteFleet plans to seek a listing for its Brightree HME connector in Brightree Integrations, the vendor’s official partner or integration directory, subject to onboarding and approval.

1. Start with the Brightree HME sales order

Open the sales order BT-01842 for Patricia Hayes and inspect its delivery destination, line quantities, and configured SuiteFleet relationship. The example contains HME-100 | Walker | 1 EA and HME-200 | Seat cushion | 1 EA.

Brightree HME starting order BT-01842 with SuiteFleet extension
Sales order BT-01842: review the SuiteFleet delivery fields before release.

Review the sales order, delivery ticket, equipment allocation, destination, and required documentation. Release only the items approved by the provider’s operational workflow.

Brightree already supports delivery and documentation workflows. Define the boundary between those functions and SuiteFleet so technicians receive one dispatch instruction and evidence reaches the correct ticket. Brightree inventory and delivery.

2. Configure the planning mapping

Preserve this relationship before exporting delivery work:

Provider organization → sales order → delivery ticket and equipment lines → SuiteFleet task
Brightree HME to SuiteFleet field mapping and return mapping
Brightree HME–SuiteFleet field mapping. Confirm source fields, destination fields, and transformation rules during configuration.
Brightree HME sourceSuiteFleet destinationRule
Provider + sales order IDOrder correlationRetain organization scope.
Delivery ticket IDReference numberExecution record.
Equipment line / item IDItems / line linkPreserve individual assets.
Serial / lot referenceControlled item referenceUse only required operational data.
Delivery address / contactShip ToUse confirmed destination.
Provider branch / warehouseBranch / hubMap physical origin.
Appointment date / windowDelivery Date; After / BeforePreserve local zone.
Delivery / pickup directionTask typeSeparate exchanges and returns.
SuiteFleet resultBrightree HME destinationWriteback rule
Task ID / trackingDelivery correlation for Delivery ticket DT-01842Confirm field access during configuration.
Delivered / FailedConfigured delivery outcomeConfirm field access during configuration.
Recipient / completion timeDelivery evidence metadataConfirm field access during configuration.
Photos / signatureControlled evidence referenceConfirm field access during configuration.

Plan around appointment windows, equipment handling, technician availability, and pickup requirements. Use the provider location as the departure hub and the confirmed delivery address as the stop.

3. Select eligible stops and available drivers

Open Workbench for the intended date and filters. Inspect task, driver, and hub layers; resolve tasks without a location before optimization. Use geographic selection to choose the intended area, then confirm the selected task set contains only released work.

SuiteFleet Workbench with task clusters and hubs
Dallas–Fort Worth planning example. Review task clusters, driver coverage, and hub locations.

Choose Plan & Optimize when assigning eligible tasks across drivers, or Optimize Existing Routes when retaining assignments and improving stop sequence. Review enabled drivers, shift windows, departure hubs, and the displayed task-capacity limits. Do not assume those limits represent weight or volume.

SuiteFleet driver panel beside the operations map
Review available drivers and task capacity alongside the Dallas–Fort Worth service area.

Brightree already supports delivery and documentation workflows. Define the boundary between those functions and SuiteFleet so technicians receive one dispatch instruction and evidence reaches the correct ticket.

4. Review objectives, constraints, and results

Choose the supported objective: Fastest Completion, Shortest Distance, Fewest Vehicles, or Balanced Workload. Review Respect Time Windows, Reassign Assigned Tasks, and Time Per Stop before running the preview. Select the objective that matches the dispatch plan and confirm which routing constraints are enabled.

SuiteFleet route optimization objective selection
Choose the routing objective that matches the dispatch plan.

Inspect the returned driver assignments, stop sequence, projected completion, and every unassigned task. Check stop times against driver shifts as well as customer windows; confirm that the proposed schedule is feasible. Missing locations and conflicting requirements need explicit resolution.

SuiteFleet route preview and unassigned-task review
Review planned stops, distances in miles, completion time, and unassigned tasks before applying the route.

Review the Dallas–Fort Worth planning example, with distances in miles and local receiving times. Dispatchers should check stop sequence, road access, and unresolved work before applying a plan.

5. Execute the route and process actual outcomes

Keep assignment and planned arrival separate from customer delivery. Monitor failed, rescheduled, and completed stops during execution. A route application must not post inventory, close an order, or trigger billing by itself.

An equipment exchange can contain both a delivery and a pickup. Keep each asset, serial reference, and direction distinct; a completed delivery must not retire an unrelated rental asset.

After a stop completes, match its task ID to the source shipment, review required proof, and reconcile accepted quantities. Record actual event time and a separate sync outcome. If the source changes after planning, compare the change with the dispatched allocation before overwriting operational data.

6. Verify the result in Brightree HME

Return the verified handover result, equipment references, and required documentation to the delivery ticket. Keep billing readiness and financial processing under the provider’s established rules. Brightree inventory and delivery.

Brightree HME completed delivery example linked to BT-01842
Delivery ticket DT-01842: review delivery evidence and outstanding quantities on the linked record.
Completion example

Delivery ticket DT-01842; task SF-US-8111; recipient Patricia Hayes; actual handover October 15, 2026 · 2:35 PM CDT (America/Chicago). First line: 1 shipped and accepted. Second line: 1 shipped and accepted, in the units shown.

Read back the linked record and review every outstanding allocation before reporting the full delivery requirement complete. Test partial shipment, partial acceptance, failed delivery, duplicate completion, and delayed writeback. Keep inventory posting, receipt evidence, and payment reconciliation under their respective configured rules.

Frequently asked questions

Which Brightree HME details are needed for route planning?

Plan around appointment windows, equipment handling, technician availability, and pickup requirements. Use the provider location as the departure hub and the confirmed delivery address as the stop.

How are partial deliveries handled for Brightree HME?

An equipment exchange can contain both a delivery and a pickup. Keep each asset, serial reference, and direction distinct; a completed delivery must not retire an unrelated rental asset.

SuiteFleet dashboard
Review the source records, field mapping, delivery workflow, and return updates for your Brightree HME implementation.
Brightree HME + SuiteFleet

Connect Brightree HME delivery operations with SuiteFleet

The Brightree HME–SuiteFleet workflow turns released work from sales orders and delivery tickets into stops with a loading point, destination, and receiving window. Dispatchers review drivers, optimization objectives, and unassigned stops before applying a route. Actual completion is reconciled afterward using equipment lines and asset references.
Multi-stop sequencing
Capacity-based planning
Traffic-aware routing

Brightree HME delivery workflow

Planning inputs

Carry verified destinations, shipment references, receiving windows, and departure locations into the planning workflow before assignment.

Geographic selection

Use the operations map to identify eligible stops and resolve missing locations before calculating a proposed route.

Preview review

Inspect driver workload, stop sequence, and unassigned tasks before applying the plan to the intended fleet.

Actual outcomes

Reconcile customer delivery after execution while keeping route planning separate from shipment posting and accounting activity.

Match each delivery result to its source shipment and line quantities. Keep partial receipts and outstanding allocations distinct.

Other Solutions

All Solutions