Obsidian Jet Docs

Build and price a quote

Price a trip in the Quotes workspace — single-leg or multi-leg, with negotiated rate cards applied automatically.

This page covers building and pricing a quote in the OS console's Quotes workspace (/os → Quotes). It does not cover sending — once a quote is priced, sending it to the customer is a separate job (linked at the end).

1. Start a quote

You can start a quote three ways:

  • From the RFQ Inbox — convert a request in one click, or hand it to the build pane pre-filled. See Triage the RFQ inbox and convert it to a quote.
  • Guided quote — click Guided quote in the Quotes workspace for a 4-step stepper (Customer → Trip → Options → Send) that validates each step before letting you continue. It wraps the same pricing and send calls as the direct build form, aimed at a rep who's new to quoting.
  • Build tab, direct — click the BUILD tab in the Quotes workspace for the full form in one screen — this is the only path that supports a multi-leg itinerary (see below).

2. Single-leg or multi-leg

The direct Build tab has a toggle at the top: SINGLE LEG or ROUND-TRIP / MULTI-LEG.

  • Single leg — origin, destination, date, and pax price one trip.
  • Multi-leg — add as many legs as the itinerary needs; each leg is priced and itemized, and the line items sum to the quote's total price.

Switching from single-leg to multi-leg carries over whatever you've already typed as the itinerary's first leg, rather than discarding it.

In both modes, attach a customer (from your CRM accounts, or free text) before pricing — the customer link is what a negotiated rate card and a sendable quote both depend on.

3. Price the trip

Click BUILD QUOTE (single-leg) or BUILD ITINERARY QUOTE (multi-leg).

This runs your fleet against the trip and returns, per eligible tail, a price and a compliance status:

  • a passing tail, priced and selectable,
  • a PENDING_VERIFICATION tail — priced, but its compliance gates haven't cleared against authoritative data yet,
  • or a suppressed tail — hard-blocked by a gate, never selectable.

Pricing never asserts a trip is "compliant." A quote's compliance status is PENDING_VERIFICATION until the gate's data is verified, and a suppressed tail always blocks regardless of price. See Read compliance verdicts.

4. Rate cards apply automatically

If the customer attached to the quote has an active negotiated rate card on file, it's applied to the price automatically — you don't pick a card in the build form. The build result discloses the adjustment rather than silently moving the number: a rate-card chip shows the card name, the negotiated discount or markup, and what the price moved from and to. This applies to both single-leg quotes and every itemized leg of a multi-leg itinerary.

A rate card itself is set up and linked to a customer separately — see Publish rate cards and jet cards. A quote built for a customer with no active card just prices normally, with no adjustment shown.

Next: send the quote

Once a quote is priced, the next step is sending it to the customer — covered in Send a quote to the customer.

On this page

Build and price a quote — Obsidian Jet