管理出貨
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
本文說明如何使用 Fleet Engine 管理貨運，包括多項相關活動。
變更出貨路線
建立出貨工作後，就無法變更預計地點。如要重新安排運送路線，請關閉運送工作，但不要設定結果，然後使用更新後的預定地點建立新工作，並加入關閉工作時使用的相同追蹤 ID。建立新工作後，請將工作指派給同一部車輛。詳情請參閱「關閉工作」和「更新送貨車輛工作」。
完成出貨工作後，系統會記錄工作狀態和結果。不過，你可能想更新與出貨相關的其他中繼資訊。如要儲存可在 Fleet Engine 服務外部參照的其他中繼資訊，請使用與工作相關聯的 tracking_id 做為外部資料表中的鍵。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-09-04 (世界標準時間)。
[null,null,["上次更新時間：2025-09-04 (世界標準時間)。"],[[["\u003cp\u003eFleet Engine enables management of shipments through various activities, including rerouting and storing shipment information.\u003c/p\u003e\n"],["\u003cp\u003eRerouting a shipment involves closing the original task and creating a new one with the updated location, maintaining the same tracking ID and vehicle assignment.\u003c/p\u003e\n"],["\u003cp\u003eShipment status and outcome are automatically recorded upon task completion within Fleet Engine.\u003c/p\u003e\n"],["\u003cp\u003eTo store additional shipment meta information externally, utilize the \u003ccode\u003etracking_id\u003c/code\u003e as a key in a separate table for referencing beyond Fleet Engine.\u003c/p\u003e\n"]]],[],null,["This document describes a number of related activities you can do with Fleet\nEngine to manage shipments.\n\nReroute a shipment\n\nOnce a shipment task has been created, its planned location can't be changed. To\nreroute a shipment, close the shipment task without setting an outcome, and then\ncreate a new task with the updated planned location and include the same\ntracking ID used on the closed task. After creating the new task, assign the\ntask to the same vehicle. For more information, see [Close a task](/maps/documentation/mobility/fleet-engine/journeys/tasks/finalize-tasks#close-task) and\n[Update delivery vehicle tasks](/maps/documentation/mobility/fleet-engine/journeys/tasks/update-tasks).\n\nStore shipment status and other meta information\n\nWhen a shipment task is completed, the task state and outcome are recorded\nin the task. However, you may want to update other meta information\nspecific to the shipment. To store other meta information that you can\nreference outside the Fleet Engine service, use the `tracking_id` associated\nwith the task as a key in an external table."]]
