---
title: "Plan your Integration as a Carrier with Bringg"
slug: "plan-your-integration-as-a-carrier-with-bringg"
tags: ["On Demand", "IT Integrations", "Partner", "Delivery Hub", "DP integrations Portal", "Set up delivery providers", "Planned"]
updated: 2023-06-19T07:53:25Z
published: 2023-06-19T07:53:25Z
canonical: "help.bringg.com/plan-your-integration-as-a-carrier-with-bringg"
---

> ## 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.

# Plan your Integration as a Carrier with Bringg

As a carrier, you can grow your business by independently integrating with *the Bringg Platform* to gain access to more shippers who choose you to fulfill their orders.

Start by defining order flows that reflect each fulfillment scenario your company supports, including standard flows, white glove services like installation, or verification methods like taking a photo or obtaining a signature. Also define edge cases like canceled, or returned items.

TipWe recommend sending regular real-time updates, like *driver* location updates or added notes or signatures to a delivery. Sending more information to Bringg means more transparency to consumers, which improves CSAT scores for shippers. This leads to a higher likelihood they choose you as their preferred carrier.

Plan your integration working closely with your company's IT integrator who is responsible for the technical implementation on your end. You may choose to integrate first with Bringg alone, or in coordination with one or more contracted shippers. The process can take as little as a couple of weeks, but varies according to your company's configuration and the scope of implementation.

![](https://cdn.document360.io/a18074ef-073a-4ab1-bcab-12625715280e/Images/Documentation/image-1678710925787.png)***Design the flow of information between you and a Bringg shipper***

### Before You Begin

- Identify different types of order flows. Perhaps some items require assembly on site, or include repair services. An order could also include bulk pickup. Include edge case scenarios as well, like cancellations or returns. Each type requires its own end-to-end process.
- Identify the technical capabilities you support such as quotes, driver location updates, proof of delivery, multi-package shipment, and so on.
- Determine how much advanced notice you require to fulfill an order, and the service levels you have available such as *planned* or on demand deliveries.
- Verify your pricing policy in charging shippers.
- Define your *service areas* in terms of the maximum radius your drivers can travel to deliver goods and services.
- Finalize agreements with interested shippers so that you can tailor your integration to their fulfillment needs.

### Procedure

**Step 1**: Join a kickoff meeting that Bringg initiates with you and your IT integrator, and perhaps a shipper interested in working with you.

The main purpose of this meeting is to align expectations and understand more in depth your company's capabilities and how they correlate with shippers' needs and with Bringg.

**Step 2**: Define your typical business flow of delivery requests, from the moment it arrives from a shipper until your drivers fulfill the order.

![](https://cdn.document360.io/a18074ef-073a-4ab1-bcab-12625715280e/Images/Documentation/image-1678711024703.png)***Begin with a standard delivery flow***

An ideal order flow might begin with you responding to a carrier quote request. The quote tells Bringg about the price and when you can fulfill the delivery. Then Bringg informs you that the shipper accepted your quote and has created a delivery request that Bringg shares with you. You then assign a driver to an order. You can continue to notify Bringg as the driver arrives at pickup and dropoff locations and completes the delivery process.

You can tailor flows for different types of white glove services like installation or repairs, as well as different verification methods like taking a photo or obtaining a signature.

**Step 3**: Build robust plans for edge cases. For example, define the steps which a driver must perform if an item arrives damaged and the driver needs to return it to the store or fulfillment center.

![](https://cdn.document360.io/a18074ef-073a-4ab1-bcab-12625715280e/Images/Documentation/image-1678711043617.png)***Create a cancelation and return flow***

**Step 4**: List all possible updates you can send and receive while fulfilling an order, distinguishing those that are mandatory or optional.

Your IT integrator communicates data with Bringg through data transfer mechanisms called APIs and webhooks. The more information you transfer, the more transparency you have with your shippers, and the more they are likely to choose you as their partner.

For example, you can send a **Start Order** API to notify Bringg when your driver begins the delivery process.

![](https://cdn.document360.io/a18074ef-073a-4ab1-bcab-12625715280e/Images/Documentation/image-1678711240360.png)***Track the flow of information between your company and Bringg***

**Step 5**: Convert each step of the order flow into a high level conversation between systems in your company and the Bringg Platform.

| When this happens... | Transfer this data... | Direction of flow |
| --- | --- | --- |
| **New shipper registration** | Bringg sends you the identification information of a shipper who registers to work with you. Your IT integrator can then access their credentials in the integration sandbox. | Bringg to carrier |
| **Shipper requests a quote** | (Recommended) Send a quote response with your estimated delivery price and your availability to complete the order. The shipper may also request details like ETA, ability to fulfill green delivery, and so on. | Bringg to carrier |
| **Shipper sends order** | Bringg notifies you that a shipper wants you to deliver goods, so you create a delivery in your system with an identification and the terms of the delivery that you quoted. | Bringg to carrier |
| **You assign a driver** | Share any authorized identification information about the driver who receives the assignment or reassignment. The shipper passes this to consumers for better customer experience, added feeling of safety, and so on. This is also where you can add a cost to the order once you know who is delivering it. | carrier to Bringg |
| **Driver starts the delivery** | Notify Bringg that the driver has begun the delivery process. Include the location, time, delivery price, and whether or not it is a green delivery. | carrier to Bringg |
| **Update driver location** | (Recommended) Share the timestamp and exact geolocation of the driver. | carrier to Bringg |
| **Driver arrives** | (Recommended) Share the timestamp and exact geolocation of the driver upon arrival at either the pickup or dropoff location. | carrier to Bringg |
| **Driver adds information** | (Recommended) Update the order when the driver adds a note, signature, proof of delivery, or any other delivery documentation the driver collects. | carrier to Bringg |
| **Driver leaves** | (Recommended) Share the timestamp and exact geolocation of the driver as they leave the pickup location. Upon leaving the dropoff location, use the **Complete Order** API instead. | carrier to Bringg |
| **Shipper cancels order** | Bringg notifies you that the shipper canceled the order and includes a reason why, like if the customer decides to cancel it. This helps you know you can end a delivery immediately and avoid wasting time and resources. | Bringg to carrier |
| **You cancel order** | Cancel a delivery, like if the customer is not home, or there are no available drivers. | carrier to Bringg |
| **You update order** | (Optional) Update the scheduled pickup or delivery time, the time window, driver ETA, green delivery, delivery price, and so on. | carrier to Bringg |
| **Shipper updates order** | The shipper makes changes to the address, goods, time window, or customer information. | Bringg to carrier |
| **Driver completes order** | Send the timestamp, delivery price, order number, or geolocation of the driver when you complete the delivery. | carrier to Bringg |
| **Bringg creates return delivery** | (Optional) The Shipper requests that your driver take the inventory item back to the fulfillment center, so it creates a new delivery with the same order id. | Bringg to carrier |
| **Driver arrives at or leaves bulk pickup location** | (Optional) Do a bulk pickup of orders from a *fulfillment center* or other similar location and deliver them to your warehouse or store location. | carrier to Bringg |

Work with your IT integrator to define the event triggers for each update in every flow as the order moves from one stage of delivery to the next.

**Step 6**: Coordinate with your IT integrator to test and implement the updates between your system and Bringg, by using the Bringg Integrations Portal. [Learn more](/v1/docs/implement-your-integration-with-bringg-as-a-carriert).

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.

Quotes are carrier-provided fulfillment estimates and often include pricing, availability, and ETA. You can display quotes to customers at checkout, auto-assign carriers based on order attributes with Carrier Selector rules, or manually assign carriers in the Bringg platform.

For each order, Bringg sends quote requests to carriers who match your Carrier Selector rules and delivery terms.

You can also set up rate cards for carriers whose quotes do not match agreed-upon pricing.

As a driver using the Bringg Driver App, you can sign up to a shift and see the orders in your route as a list of destinations and breaks, with contact information for each order, extra notes from the consumer or dispatcher and step-by-step instructions to handoff successfully. The Bringg Platform has already optimized your route, and you can navigate turn-by-turn with your favorite map app.

An on demand order is dispatched as soon as possible after it is received. This is typical for food deliveries and emergency services, where the order must reach its destination within a few minutes or hours. Bringg dispatches on demand orders using AutoDispatch.

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.

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.

The estimated time of arrival (ETA) is the time a driver is expected to arrive at a destination. Bringg's route optimization typically schedules an order's ETA to be within its time window.

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 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.