Overview

Manage all components for cost and revenue estimates.

Quotes are detailed estimates that outline the terms and logistics for transporting goods from one location to another. For customers, this represents revenue, and for partner carriers, it represents the cost. Rose Rocket has the functionality for managing all components of quotes as the first object in the end-to-end quote-to-cash lifecycle.

Depending on your organization, quotes act as revenue or costs. This relationship highlights the organizational role in your Rose Rocket workflow.

Customer quotes for shippers, partner, and brokers - Revenue coming in
Partner quotes for brokers - Cost of business

API configuration

When using the API to make requests, see the pages below for the process. These guides walk through the requirements and setup to access the Rose Rocket API with your application.

Authentication - Access Rose Rocket with OAuth 2.0
Object operations - Configure your requests

Object structure

Use the table below for information about the quote objects.

Object Key Name: quote

Field	Label	Type	Description
`id`	ID	string	Global unique identifier for record
`fullID`	Full ID	string	User visible ID record
`status`	Status	string, enumerated	Quote status, valid values:`new`, `sent`, `won`, `lost`
`reasonLost`	Reason lost	string	Reason for quote marked as Lost
`quoteType`	Quote type	string, enumerated	Type of quote, valid values: `buy` (equates to Partner), `sell` (equates to Customer)
`customer`	Customer	Customer connected object See Connected object section	Customer for quote Value can be shippers, receivers, brokers, or other organizations within supply chain
`csrs`	Customer service representative	User connected object array See Connected object section	Customer Service Representative of company on quote
`partner`	Partner	Partner connected object See Connected object section	Partner assigned to quote Populated if a single partner is assigned to entire quote, can be `null`
`tags`	Tags	Tag connected object array See Connected object section	Tags associated with quote
`poNum`	Purchase order number	string	Recipient provided value for reference
`refNum`	Reference number	string	General purpose field to store reference ID values from other systems
`loadTenderNum`	Load tender number	string	Reference number for a load provided by the shipper, carrier referencing for a BOL or order
`totalMiles`	Total miles	string	Total miles for quote, calculated from stops addresses using API map provider polyline distance calculations
`estimatedDuration`	Estimated duration	string	Total estimated time from origin to destination in seconds
`notes`	Notes	string	Total miles for quote, calculated from the stops addresses using API map provider polyline distance calculation
`tasks`	Tasks	Task connected object array See Connected object section	Work to fulfill contract or win quote to be completed by assignee NOTE: Tasks group together to form legs and other types of groups to be completed together. Tasks carry financial items for more granular allocation.
`quotes`	Quotes	Quote connected object array See Connected object section	Models various relationship types between quotes for buy and sell See Quotes overview section for more
`selectedBuyQuote`	Selected partner quote	Quote connected object See Connected object section	User association between buy quote to be marked as `selected` for sell quote
`parentSellQuote`	Parent customer quote	Quote connected object See Connected object section	Reverse of `selectedBuyQuote` field, association between sell quote to be marked for buy quote
`shipper`	First pickup address	Address connected object See Connected object section	Origin of load as first pickup
`consignee`	Last delivery address	Address connected object See Connected object section	Destination of load as last delivery, populates last destination stop through ECAs when set
`lineItems`	Financial line items	FinancialLineItem connected object array See Connected object section	Quote line items to model various charge types
`requestedPickupWindow`	Requested pickup	string	Date range window of customer requests for load pickup
`requestedDeliveryWindow`	Requested delivery	string	Date range window of customer request for load delivery
`order`	Order	Order connected object See Connected object section	Field populated when sell quote is converted to order
`orderFromBuyQuotes`	Order	string	Field populated when buy quote is connected to order
`documents`	Documents	Document connected object array See Connected object section	Quote associated documents
`assetType`	Asset type	AssetType connected object See Connected object section	Quote required asset type
`serviceType`	partner service	PartnerService connected object See Connected object section	Quote required partner type

Quotes object behavior

The quotes object contains many functions of buy and sell relationships. See the list below for more on multiple quotes and their connections.

Single sell quote -> multiple buy quotes
- Broker produces a single sell quote to shipper, then procures multiple buy quotes from carriers
Multiple sell quotes -> single buy quote
- Shipper quotes fulfilled by single carrier
Quote selected for order -> Connected to that order