---
title: "Rolling Out the Bringg Platform"
slug: "rolling-out-the-bringg-platform"
tags: ["Admin", "Strategic Business", "On Demand", "Getting started, onboarding", "Planned"]
updated: 2024-08-07T06:36:06Z
published: 2024-08-07T06:36:06Z
canonical: "help.bringg.com/rolling-out-the-bringg-platform"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.bringg.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Rolling Out the Bringg Platform

When rolling out the Bringg Platform you build end-to-end workflows and manage your employees efficiently to fulfill your company's goals. Determine the , routing mechanisms (like route optimization and AutoDispatch), and how Bringg assigns drivers and vehicles to routes. Build clear instructions for your dispatchers, drivers, and store associates to ensure maximum efficiency in delivering goods and services to consumers. Define order flows for each fulfillment offering, including variations like canceled or returned items.

For example, you can create separate flows for assigning time windows for basic versus premium delivery. You may need separate flows for catering (planned) and takeaway (on demand) orders. If you sell pharmaceuticals and the like, you can distinguish between standard and specialty items that legally require different steps for the driver to take like signing a liability waiver or requesting a customer signature.

![](https://cdn.document360.io/a18074ef-073a-4ab1-bcab-12625715280e/Images/Documentation/image-1678433530840.png)***Roll out Bringg step by step***

Launching Bringg successfully is a multifaceted and multi-phase process demanding in-depth knowledge of your company's goals and needs. The process can take as little as a few months but varies according to size and scope of implementation. We recommend allowing between 6 and 12 months to fully roll out the platform while working with Bringg representatives.

Depending on your roll-out plan, you may first pilot Bringg on a smaller-scale phased rollout and later scale it up to the rest of your company.

Complete the setup and testing process in the staging environment, and then move the system over to production to perform final tests and go live.

### Before You Begin

- Confirm you have a Bringg user of type Admin.
- Understand your company's fulfillment goals. For example, perhaps your company wants to prioritize green delivery whenever possible, or is most focused on saving costs rather than speedy delivery.
- Know the types of available resources like vehicles, skills, inventory management systems, and facilities you have available.
- Identify different types of goods or services that require different order flows, like refrigerated, alcoholic, or heavy items. Perhaps some items require assembly on site, or include repair services. Each type requires its own end-to-end process.
- Define your KPIs so that you can build workflows that achieve them.
- Discuss with your colleagues in marketing, design, and business development to determine the look, feel, and content of your messages to consumers, the Bringg customer page and the Bringg Driver App.
- Verify your organization's rollout strategy, understanding when and how to bring the processes and flows from pilot phase to scale across the organization.

### Kickoff Meeting

Join a kickoff meeting that Bringg initiates with a select group of leaders and dispatchers in charge of rolling out and implementing Bringg in your organization. The main purpose of the meeting is to align success criteria and expectations for the next phases.

The kickoff meeting usually includes at least one representative from your sales, marketing, or procurement team, the ops manager and project manager in charge of Bringg implementation, one or more subject matter expert(s) (SMEs) like dispatchers responsible for defining flows, resources, and so on, the IT integrator managing the technical integration, and the person responsible for training and change management in your company.

- Ensure your team has completed the initial steps of collecting data, resources, and KPIs so that the meeting is as productive as possible.
- Align the steps and time frames for the implementation phases: planning and design, execution, stabilization, and closing.

### Define Order Flows

Define order flows by translating your organization's fulfillment processes and policies into clear flows for each eventuality, like a customer not being present at arrival.

**![](https://cdn.document360.io/a18074ef-073a-4ab1-bcab-12625715280e/Images/Documentation/image-1678433605416.png) *Chart the order process for regular as well as edge cases*** 

- You can define order flows for different types of goods and consumers to fit your company's policy. These flows can determine who prepares the order, its time window, and the driver actions to complete fulfillment.
- If you mark a step as mandatory, the flow cannot proceed until the driver starts and completes this step. For example, you may define a separate flow for prescription medicines to require a signature at handoff.
- Build robust plans for edge cases. For example, define the steps which a driver must perform if an item gets damaged. Or, if you work mostly with s you may need a spillover plan to assign orders to carriers during high volume periods.
- You can add variations to your order flows using service plans in order to offer consumers different levels of service. For example, a basic plan may assign default delivery slots, while over the threshold plans may offer consumers faster fulfillment, or the option to choose a specific arrival date or time.

**Step 1**: Define how you collect orders from consumers.

Work with your IT integrator to integrate with the order management system (OMS) to offer dynamic consumer quotes for delivery choices.

![](https://cdn.document360.io/a18074ef-073a-4ab1-bcab-12625715280e/Images/Documentation/image-1678433629515.png)

***Automatically offer delivery windows to consumers***

- As part of building the order flow, you define the events for which APIs and webhooks should trigger the transfer of information ([payloads](/v1/docs/)) between systems. You also determine the inputs and outputs of each payload and coordinate with your IT integrator to implement them.
- Share any security requirements with your IT integrator so that they can implement them as needed in the configuration.

**Step 2**: Specify rules for assigning orders for fulfillment.

- Determine whether you are using own fleets, carriers, or a combination of both. Match skills of drivers and vehicles to the order flows. Skills could include installation or repair licenses or specialty vehicles like refrigeration trucks.
- (Own fleets only) For planned orders, use route optimization to automatically create a route based on your defined priorities. For on demand orders, use AutoDispatch(AD) to instantly assign orders to drivers based on criteria you define.![](https://cdn.document360.io/a18074ef-073a-4ab1-bcab-12625715280e/Images/Documentation/image-1678433664591.png)***Bringg creates efficient optimized routes***
- (Carriers only) Select the carriers that match your needs. Then define your delivery terms so that the carrier selector knows when to assign orders to whom. [Learn more](/v1/docs/add-your-delivery-strategy-to-bringg).![](https://cdn.document360.io/a18074ef-073a-4ab1-bcab-12625715280e/Images/Documentation/image-1678433668519.png)***The carrier selector follows your rules to assign orders***

### Add Resources to Bringg

#### Set up teams

[Set up your teams](/v1/docs/set-up-a-team), deciding how you want to distinguish them.

A team groups together the people and vehicles needed to fulfill orders from a specific fulfillment center or service area. It can contain drivers, dispatchers, vehicles, and orders.

![](https://cdn.document360.io/a18074ef-073a-4ab1-bcab-12625715280e/Images/Documentation/image-1678433692283.png)***Define teams around the people and vehicles who fulfill orders***

Perhaps you want one team per store location, or you prefer teams divided by planned versus on-demand orders, or different types of Click and Collect orders such as curbside versus in-store pickup. Perhaps you want to separate teams that deliver on foot from those who use vehicles.

Set up distribution rules for each team to define how to assign orders and drivers to routes.

#### Add users

[Add users to Bringg](/v1/docs/add-a-bringg-user), defining the roles, skills, and privileges for each.

![](https://cdn.document360.io/a18074ef-073a-4ab1-bcab-12625715280e/Images/Documentation/image-1678433711210.png)***Add new drivers and assign them to teams***

#### Plan resource management

Set up your plan for resource management in Bringg.

- Define and validate your distribution network including fulfillment centers, pick up or drop off locations, lockers, and so on.
- Align Bringg with your warehouse activities.
- Incorporate parts of the fulfillment process, such as picking, packing, staging, driver preparation time, loading, and so on, into the Bringg order flows.
- (Own fleets only) Contact your Bringg customer service representative to set up pools of drivers, vehicles, trailers, and so on. Configure the rules to auto-assign a vehicle and trailer to a route. [Learn more](/v1/docs/assign-a-different-driver-for-orders-on-a-planned-route).![](https://cdn.document360.io/a18074ef-073a-4ab1-bcab-12625715280e/Images/Documentation/image-1678433738835.png)***Select appropriate vehicles and trailers for a route***

### Track and Communicate Delivery Statuses

#### Configure handoffs

Seamless handoffs are critical to successful fulfillment. They clarify liability and minimize complications. They ensure clarity and ownership over each delivery stage, and enable you to identify and resolve issues easily, like if an item arrives damaged.

- This includes handoffs between fulfillment centers and drivers, drivers and consumers, and in the case of Click and Collect, store locations and consumers.
- Define the driver flow rules, specifying which actions the driver needs to complete along the way.  
For example, [define how drivers start and end their shifts](/v1/docs/set-up-driver-actions-in-order-flows). Or determine if the driver needs to scan a customer signature upon delivery. Perhaps they need to take a photo of the delivery if the customer is not at the destination.

#### Set up alerts

**Step 1**: Work with your IT integrator to [configure SMS and email notifications](/v1/docs/integration-guide-set-up-sms-and-email-notifications-to-connect-with-consumers) for different stages of the fulfillment process. Use tags to map different branding and communication flows for different subsidiaries, partners, customer languages, or types of goods within your company.

**Step 2:** Configure alerts to notify your dispatchers and drivers of different events, whether planned or unexpected. These help you as well as your dispatchers and drivers to monitor processes and focus on the exceptions. [Learn more](/v1/docs/set-up-alerts).

### Access and Use Your Data

[Set up reports](/v1/docs/dispatcher-guide-build-reports-for-custom-analytics) to track trends and create actionable insights in the fulfillment process.

Build reports to track the data you want to measure. For example, perhaps you want to test the on-time delivery rate or the number of orders that drivers complete per shift. You can also compare KPIs with your old system to ensure progress and maintain consistency of metrics. Use the widgets in the BI dashboard to easily track specific metrics.

![](https://cdn.document360.io/a18074ef-073a-4ab1-bcab-12625715280e/Images/Documentation/image-1678433819146.png)***Build your own report by selecting database fields to assemble your own data table***

### Bringg It All Together

#### Test

Test your order flows end-to-end before moving from staging to production.

- Contact your Bringg customer service representative to verify that all the connection points in each flow work as needed.
- Make sure your organization's Bringg accounts are configured correctly. Verify that each user has the permissions, skills, team assignments, and so on necessary to work effectively.
- Ensure that you can create, update, and cancel orders successfully, testing each flow.
- Check that payloads for webhooks events and APIs contain the necessary data to communicate effectively between your systems and Bringg.

#### Train your yeams

Encourage your dispatchers and teams to access the Bringg [help portal](https://help.bringg.com/) to learn the benefits and how to use the platform independently.

#### Move to production

Contact your Bringg customer service representative to copy your settings from your staging to your production account.

- This includes updating the users from test accounts to actual members of your teams.
- Work with your Bringg representative to troubleshoot and resolve issues if they arise. For example, perhaps you discover that an optimization setting needs adjustment, or perhaps a webhook is not firing at the right moment in the order flow.

#### Scale up

Assess the status of your KPIs, and work with your colleagues and Bringg to scale up the use of Bringg in your company.

Run Bringg's route optimization (RO) to reduce costs by organizing your orders into the fastest, most efficient planned routes, where each order arrives at its destination within its designated time window. If you have an Own Fleet, RO can also assign each route to a vehicle or driver who is available at that time and has the correct skills to fulfill the orders. You can configure RO with preferences like the maximum length of a route, the time on site (TOS), the time to load the vehicle, predicted and real time traffic patterns, and so on.

For example, you can ask to set route optimization (RO) to limit the number of destinations on a route, or to use the minimum number of vehicles in a route.

Each time you run route optimization on the same group of orders you may well receive a different result, as there are multiple ways to organize the same group of orders into efficient routes. Instead of reshuffling all orders each time, build on your existing plans by making focused changes where they are required using the route planner.

You can run RO manually or automatically at set days and times, for select teams or across the entire organization.

On demand orders typically use AutoDispatch (AD) instead.

AutoDispatch (AD) continuously and automatically assigns orders to a team: drivers, vehicles, creating quick ad-hoc routes as orders come in. AD enables you to prioritize efficiency, by automatically batching orders together, while adhering to very short SLAs. Bringg typically uses AD when you have an Own Fleet fulfilling on demand orders, such as deliveries for restaurants, grocery stores and pharmacies, or roadside assistance. You can use AD to build routes for select teams, or across the entire organization. Planned routes typically use route optimization instead.

A vehicle in your Own Fleet is paired with a driver to reach a destination on a route. Each vehicle has a type, capacity (maximum weight or dimensions), and you assign specific skills to each one to allow Bringg to choose the correct vehicle for each order. You can define the availability of vehicles in delivery blocks.

A route is a sequence of destinations from one or more orders. Bringg can automatically create routes by calculating the fastest and most efficient route which fulfills the orders. Bringg can also help you assign the most appropriate vehicle and the driver with the correct skills to complete the order.

There are two types of routes:

1. A planned route is a route containing planned orders that you create in advance, either manually or using route optimization. For example, you can run route optimization every day at 10pm so that drivers can start their routes when they start their shifts the next morning.
2. An on demand route is a route which contains on demand orders that you create on the fly by using Autodispatch (AD), which continuously and automatically assigns orders to a team's drivers, vehicles, and routes. Common examples are deliveries for restaurants, grocery and pharmacy stores, or roadside assistance.

After you dispatch the orders in a route, drivers receive their route in their Driver App as a series of destinations, each with their associated order which they pick up or hand off to the consumer.

A time window is the time range when you intend to fulfill an order. Therefore, an order is considered fulfilled on time if it arrives within the time window. The time window is set when you schedule an order in Bringg and is usually defined by the no_earlier_than and no_later_than fields. Narrower time windows are seen as better service, like 9 to 10 am, while longer windows are more typical of larger carriers.

You can share the time window with your consumers for an improved experience. For example, if a consumer places an order for the 8:00-12:00 the following day, in the morning notify them that you intend to arrive between 8:00-9:00.

If you allow consumers to select their preferred delivery slot, the time window is scheduled accordingly.

Green delivery defines when an Own Fleet or carrier can fulfill orders using sustainable and eco-friendly means. This can be accomplished by using sustainable materials and eco-friendly vehicles (such as electric or hybrid vehicles, bicycles, or electric scooters) or committing to achieving carbon neutrality by investing in carbon offset projects (such as planting trees).

Set up skills in Bringg to automatically assign orders to routes with the right drivers and vehicles that have the capabilities necessary to fulfill them. For example, when delivering groceries you can set up a refrigerated skill that applies to all perishable orders so that route optimization and AutoDispatch automatically assign these orders to the vehicles that also have the refrigerated skill.

Note that vehicle type and capacity (weight or volume) are properties of the vehicle, not skills.

The Bringg Driver App is a mobile app on iOS and Android which extends Bringg's functionality to you, a driver. When dispatchers assign orders or update routes, each appears instantly in the Driver App as a list of destinations, which you can navigate to by launching your preferred navigation app directly from the Driver App, view all order details and instructions, complete handoff actions, and keep dispatchers automatically updated on the progress of your route, such as when traffic causes delays. When you approach a destination or fulfillment center, the Driver App can automatically check you in, triggering automatic notifications to the consumer and dispatcher that you are about to arrive, all without you taking your hands off the wheel.

An order flow defines all the stages of fulfillment from when an order enters Bringg to when the order is completed or cancelled.

You can define order flows for different types of goods and consumers to fit your company's policy. These flows can determine who prepares the order, its time window, and the driver actions to complete fulfillment.

If you mark a step as mandatory, the flow cannot proceed until the driver starts and completes this step. For example, you may define a separate flow for prescription medicines to require a signature at handoff.

Building order flows includes all eventualities, including defining the steps for drivers if goods are damaged. Or, if you work mostly with Own Fleet, you may need a spillover plan to assign orders to carriers during high volume periods.

The Bringg Driver App can prompt drivers to perform driver actions for any order, or only those which have certain types of goods. It can suggest to perform these actions at the start of a shift, at the end, or during handoff (after check-in or before checkout).

You can add variations to your order flows using service plans in order to offer consumers different levels of service. For example, a basic plan may assign default delivery slots, while over the threshold plans may offer consumers faster fulfillment, or the option to choose a specific arrival date or time.

An order is a request for the fulfillment of goods and services at a specific address. It includes all information needed to complete it, such as the requested service or goods, the customer’s contact information, required services (such as fragile care), and the time window.

Driver actions are the stages in an order flow which a driver performs in the Bringg Driver App to complete the fulfillment of that order. You can set up mandatory and optional actions to prompt drivers to take a payment, obtain the consumer's signature, take a photo, fill out a form, open a webpage, and scan a barcode to confirm a handoff.

If you mark a step as mandatory, the flow cannot proceed until the driver starts and completes this step. For example, you may define a separate flow for prescription medicines to require a signature at handoff.

A handoff is any transfer of goods from one person or location to another during fulfillment of an order. Drivers usually validate handoffs with a driver action like a scan, signature, or photo. For example, when a driver scans items at a warehouse, this handoff transfers custody of the items from the dispatcher to the driver. The final handoff is when the consumer accepts the goods and the driver records proof of delivery.

A delivery provider (DP) offers their fleet of vehicles to fulfill orders on behalf of the shipper. carriers promise different levels of service, cover specific territories, and may specialize in different types of goods and services, such as parcel retail, restaurant, and grocery delivery. You can add more carriers to expand your service coverage by finding the best fit for your business in our carrier catalog.

There are two types of carriers:

1. Carriers are often the more established carriers with their own branded fleet of vehicles and drivers, which they offer to shippers to fulfill their orders. Carriers can typically deliver higher volumes and a wider variety of goods around the world, and can therefore batch planned orders together, sometimes several days in advance, to offer shippers cheaper rates.
2. A crowd-sourced last mile carrier uses independently contracted drivers to populate its fleet. Since the drivers usually use their own vehicles, this type of carrier often fulfills hyper local orders that require more immediate fulfillment (on demand, same day, or next day orders). Their wide pool of local drivers enables them to offer cheaper rates for these deliveries.

A service plan is a type of service that you provide to consumers like express, basic, or over the threshold. Service plans enable you to fulfill service level agreements by letting the Bringg Platform, dispatchers, and drivers know when you have committed to providing a specific service, such as delivery at the consumer's home or workplace, or a specific handoff procedure like requiring the consumer's signature as proof of delivery.

Delivery slots define your availability to accept carrier or consumer pickups, perform deliveries or services. Bringg can calculate relevant slots for a particular order, taking into account the order's destination, your resource availability, SLAs, and more.

You can present delivery slots to your consumer, to allow them to choose when they would like to receive their order.

Inside the Bringg database and payloads a delivery slot is referred to as a planned delivery window (PDW).

A carrier quote is an estimate from a carrier for the time or price to fulfill a specific order, and often includes more details like their availability to deliver, predicted ETA, and so on.

Bringg's fleet router requests a carrier quote for each order from all qualified carriers and assigns the order to the best one according to your preferences.

Enter your delivery strategy in Bringg to qualify carriers automatically.

A Bringg event typically marks a change in an order's status, or a registered driver action, like when an order is ready for dispatch, or when a driver is approaching the order's destination. You can update other systems like an OMS whenever a specific Bringg event occurs, by configuring a webhook to be triggered by that event.

Use Bringg's APIs when an enterprise system asks Bringg to perform a specific action. For example, to tell Bringg that your order management system (OMS) just got a new order from a consumer, use Bringg's Create order API.

Just as UI (user interface) describes how users interact with a system (icons, buttons, windows, and so on), APIs (application programming interfaces) describe how an app or system uses programming code to interact with another app. An API sends information with the request in its payload, like the order number or delivery address.

Work with an IT integrator with programming skills to define the flow of data between the systems, the events which trigger each communication, and the request you're making to the other system.

Webhooks notify systems that an event occurred, whereas APIs initiate a specific request for another system to act.

Use Bringg webhooks to notify other enterprise systems in real-time as soon as a predefined event occurs, like updating your order management systems (OMS) that an order arrived at its destination.

You can have multiple systems listen to the same webhook rather than each making an independent data request. The webhook sends data in its payload to designated URLs.![download (1)](https://cdn.document360.io/a18074ef-073a-4ab1-bcab-12625715280e/Images/Documentation/download%20(1).png)

Webhooks send data to other systems when an event occurred Webhooks send data to other systems when an event occurred

Webhooks notify systems that an event occurred, whereas APIs initiate a specific request for another system to act.

Any applications subscribed to a single webhook receive the payload at the same time, but its content may vary depending on the parameters which each system requires.

For example, if you register a webhook URL in your OMS and ERP for the event Order Is Cancelled, the OMS receives one payload belonging to Order Is Cancelled to update the status of this order. At the same time, the ERP receives a slightly different payload with details to update the inventory.

You can register webhook URLs for automatic updates of events throughout the order lifecycle including when it is assigned to a driver, when a driver delivers the goods or services, and so on. Learn more

Bringg’s carrier selector automatically assign the best carrier for each order, in line with your business priorities and delivery strategy. For each order, Bringg checks the ETA or delivery price offered by each carrier. Bringg then automatically offers the order to each carrier, starting with the cheapest or fastest, until one accepts the order. Alternately, Bringg can offer order assignments to carriers according to a predefined sequence.

A team groups together the people and vehicles needed to fulfill orders from a specific fulfillment center or service area. It can contain drivers, dispatchers, vehicles, and orders.

For example, you can define a team as all orders and drivers assigned to a few stores in a small neighborhood. Or a team might consist of refrigeration trucks, their drivers, and orders of perishable goods. If you use carriers, you can define delivery terms to assign a team's orders to specific carrier and then use the fleet router to automatically choose the best one for each order.

To fulfill an order, you must assign it to a team, then Bringg can assign it to a route and driver or to a carrier.

Dispatchers only see drivers and orders assigned to their teams. If a driver belongs to multiple teams, the dispatcher or driver can choose which team to join at the start of each shift.

A fulfillment center is your home base and where you prepare orders for dispatch. It might be a store, warehouse, factory, garage, or restaurant.

You can configure Bringg to automatically perform actions when drivers approach your fulfillment center. For example, you can make a driver available for AutoDispatch, or take them on and off shift, without requiring them to manually check in. These actions are called home events.

Each team has at least one fulfillment center, and each fulfillment center can have one or more service areas.

You can draw service areas on a map in Bringg, or use a list of zip codes, to define your distribution network. Orders that arrive in Bringg are sent to the team or carrier responsible for the service area of the order's destinations.

You can assign drivers to a specific service area within your delivery scope. This way, drivers can be familiar with their specific area, or remain nearby a specific area.

You can also use service areas to separate regions on the map to align with your business practices. For example, you might have a different delivery speed, price, or availability in some areas based on their distance from your fulfillment center. You can do this in Bringg by defining rules for each service area.

A fulfillment center can have multiple service areas, but a single service area can also belong to several fulfillment centers. For example, you might want to share a service area when your inventory is split among several warehouses, or when you need to recruit drivers from another location to assist with high demand.

Use Bringg Click & Collect as an integral part of your omnichannel experience, enabling consumers to collect goods from a designated collection point, like inside a store, on the curbside, or from a secured locker. Click & Collect connects consumers with store associates in real-time to promote efficient store operations leading to exceptional customer collection experiences.

Driver actions are the stages in an order flow which a driver performs in the Bringg Driver App to complete the fulfillment of that order. You can set up mandatory and optional actions to prompt drivers to take a payment, obtain the consumer's signature, take a photo, fill out a form, open a webpage, and scan a barcode to confirm a handoff.

If you mark a step as mandatory, the flow cannot proceed until the driver starts and completes this step. For example, you may define a separate flow for prescription medicines to require a signature at handoff.

An alert is Bringg's way to tell you there is a problem with the fulfillment process, enabling you to trust Bringg's automated processes for most cases, and focus instead on managing by exception. You can check alerts about the order itself, about the driver, or relating to the automatic route creation process (route optimization).