Quote PDFs and emails

Every quote produces an A4 PDF and an email. Both use your organisation logo and address, set under Settings, then Organisation.

The PDF

The PDF carries a brand header band with your logo, the addresses, the lines table with a specification summary line under each description, the totals and a terms footer, with accent rules in your brand colour where set. Configured lines include their rendering, up to four images per document.

The email

The send flow opens an email composer addressed to the contact, with optional cc, an editable subject that defaults to "Quotation {number} from {org}" and a body built from merge fields. The body supports {{number}}, {{company}} and {{valid_until}}, filled at send time. The recipient resolves from your explicit choice, then the named contact, then the customer's primary contact. The email goes out branded, and Kabaido logs it.

The specification line

Under each description the PDF prints a short specification summary drawn from the line's own attributes, rather than only what somebody typed in the description box. On a technical quote that is often the difference between a document a buyer can check and one they have to ring you about: the diameter, the material and the coating are on the page, in the same place on every line.

Why a PDF at all

Because it is what gets filed. An industrial buyer forwards the quote to their purchasing system, prints it for a folder, or attaches it to an internal approval. A link alone survives none of that, which is why the email carries both: the PDF for the file and the portal link for the decision.

Branding by plan

What gets recorded

Sending moves the quote to sent and logs the email against it: who it went to, when, and what was said. That record is what makes "we never received it" a checkable claim rather than an argument, and it is what the portal link in the customer's copy points back at.