This guide outlines the standard process for managing orders in Stream, to ensure accurate tracking events are provided via our marketplace integrations.
Key steps for order processing and tracking with online marketplaces
Following these steps is crucial for meeting marketplace tracking requirements.
- Create the order in Stream
Create the order via any available method (manual, upload, or integration).
Orders should be created as “Unconfirmed” initially.
Stream automatically generates a unique Tracking ID and Tracking URL upon creation. - Add tracking information to the online marketplace
Immediately provide the Tracking ID (and if applicable, the Tracking URL) to the relevant marketplace, ensuring the correct “carrier” and “service” fields are selected.
This is vital for the marketplace to start retrieving event information in a timely manner.
Do not proceed with order confirmation or planning until this is done. - Confirm the order in Stream
Ensure the order is confirmed in Stream. The “Unconfirmed” order status should be used initially to maintain control over the “confirmed event.”
The confirmed event is often used by marketplaces as the signal that the order is ready for delivery. - Plan the order to a run in Stream
Plan the confirmed order onto a run using your usual planning method.
The order “Planned” status is another event some marketplaces may use to signal the order is ready for delivery. Ensure your planning complies with your promised delivery service levels (e.g. 3-day delivery). - Perform the delivery using the Stream mobile app
The driver executes the run and confirms the delivery in the app, as per the usual process.
This process logs events that are critical to the marketplace tracking.
If a delivery is unsuccessful, this must be processed as “Delivery Failed”.
Do’s and don’ts for online marketplace tracking
| ✅ Do | ❌ Don’t |
|---|---|
| Do provide the Tracking ID and URL to the marketplace as soon as the order is created in Stream. | Don’t wait to send the tracking ID until after the order is confirmed or planned. |
| Do provide the correct service and carrier information to the marketplace during dispatch. | Don’t make mistakes when providing service or carrier information to the marketplace, as Stream cannot correct this. |
| Do use unconfirmed orders to maintain control over the confirmed event. | Don’t delete orders in Stream once tracking information has been shared with the marketplace. |
| Do ensure your planning in Stream adheres to the promised delivery service levels (e.g., if you promise 3-day delivery, plan for delivery within 3 days). | Don’t plan new orders into ongoing runs or runs that are already in progress, as this can compromise event logging. Plan first, close the run, then execute. |
| Do log a Delivery Fail event immediately if a delivery is unsuccessful, so the marketplace retrieves the event. You can then replan the delivery. | Don’t unplan deliveries from ongoing/in-progress runs if a delivery fails. Log a failed delivery event instead. |