Stay organized with collections
Save and categorize content based on your preferences.
Route Optimization API product SKUs
Route Optimization bills per shipment, and has two SKUs
that determine the cost. Which SKU is triggered is based on the number of
vehicles in your Route Optimization request:
Requests that contain one vehicle: Billed to the Single Vehicle Routing
SKU
Requests that contain 2 or more vehicles: Billed to Fleet Routing
SKU
The per-request charge is based on the number of shipments in the optimization
request, times the shipment unit price per SKU.
Billing and pricing for the Route Optimization API
This SKU is triggered for each shipment returned when you make a request to the
Route Optimization API that specifies exactly one vehicle.
You won't be charged for the following shipments:
Shipments in requests that fail due to validation errors, such as syntax or data validation errors, or any internal service error.
Shipments in requests in VALIDATE_ONLY solve mode (that only do validation).
Shipments that are either determined as infeasible shipments at validation,
or ones that are explicitly ignored, excluded from optimization, or
constrained from being optimized by InjectedSolutionConstraint.
Example
If you have a Route Optimization request that has:
1 vehicle
10 unique shipments (with 10 unique shipment locations or loads)
Billing is triggered for the 10 shipments in on the Single Vehicle Routing SKU. The same request with 5 vehicles triggers billing on the Route Optimization: Fleet Routing SKU instead.
This SKU is triggered for each shipment returned from a request to the
Route Optimization API that specifies more than one vehicle.
You won't be charged for the following shipments:
Shipments in requests that fail due to validation errors, such as syntax or data validation errors, or any internal service error.
Shipments in requests in VALIDATE_ONLY solve mode (that only do validation).
Shipments that are either determined as infeasible shipments at validation,
or ones that are explicitly ignored, excluded from optimization, or
constrained from being optimized by InjectedSolutionConstraint.
Example
If you have a Route Optimization request that has:
5 vehicles
10 unique shipments (with 10 unique shipment locations or loads)
Billing is triggered for the 10 shipments in on the Fleet Routing SKU. The same request with one vehicle triggers billing on the Route Optimization: Single Vehicle SKU instead.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-07 UTC."],[[["The Route Optimization API is billed based on the number of shipments in each request and falls under two SKUs: Single Vehicle Routing (for one vehicle) and Fleet Routing (for two or more vehicles)."],["Charges apply per shipment unit, with pricing varying based on monthly volume and the specific SKU used (Single Vehicle or Fleet Routing)."],["Requests failing validation, in `VALIDATE_ONLY` mode, or with infeasible/ignored shipments are not billed."],["You can manage your costs by setting daily quota limits in the Google Cloud console to control API usage."],["Google Maps Platform provides a $200 monthly credit for qualifying SKUs, applicable until February 28, 2025, after which a free usage threshold will be implemented."]]],[]]
