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.
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.
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.
Work with your IT integrator to integrate with the order management system (OMS) to offer dynamic consumer quotes for delivery choices.
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.
Set up your plan for resource management in Bringg.
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.
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.
Contact your Bringg customer service representative to copy your settings from your staging to your production account.
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:
- 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.
- 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).
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.
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.
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.
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.
Use the Own Fleet product when you have your own driver s and vehicles which can fulfill your last mile requirements. Your dispatchers can use Bringg to assign the best drivers with the most appropriate vehicles to the most efficient route.
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:
- 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.
- 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..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
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.
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 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.
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.
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.
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.
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).
Roll out Bringg step by step
Bringg creates efficient optimized routes
The carrier selector follows your rules to assign orders
Define teams around the people and vehicles who fulfill orders
Add new drivers and assign them to teams
Select appropriate vehicles and trailers for a route
Build your own report by selecting database fields to assemble your own data table.png)