Spec Packages

Written By Timothy Murenzi

Last updated 9 days ago

When you need to send a stack of products as one polished document.

Building a spec package

  1. Open Sidebar → Products

  2. Filter down to the products you want — by project, room, category, status, or any combination

  3. Multi-select by ticking the checkbox on each row (or click the header checkbox to select all currently-filtered rows)

  4. Click ⋯ (action menu in the header) → Download Spec Package

  5. The PDF builds and downloads — typically 5-15 seconds for a 20-product package

The package keeps the products in the order they appear in your filtered Catalog view. To re-order, sort the Catalog by Spec #, Room, Category, or any other column before exporting.

What's in a spec package

Cover page:

  • Your logo (large, centered)

  • Spec Package title

  • Project name + client name (if the products share a project)

  • Date + total product count

  • Optional cover note (you can type a custom message before export)

Table of contents:

  • One row per product

  • Spec # · Name · Vendor · Page number

  • Grouped by Room (if you sort by room) or Category (if you sort by category)

Per-product pages:

  • One page per product

  • Same layout as an Individual Spec Sheet

  • Continuous page numbering across the package

  • A header strip on every page showing project + room for orientation

Back cover:

  • Studio contact info

  • Page count summary

  • Optional disclaimer / legal text from Settings

Designer-facing vs Client-facing — package edition

Same choice as individual spec sheets, applied to every product in the package:

  • Designer / Vendor copy — full pricing on every page

  • Client copy — client price only, no markup or unit cost anywhere

Pick once when you start the export and the whole package generates in that mode.

Customizing the package

Before export, a config panel lets you set:

  • Cover note — a sentence or paragraph to lead the package (e.g. "Selections for Master Suite review — please approve or comment by Friday.")

  • Sort order — by Spec #, Name, Room, Category, Vendor, or current Catalog view

  • Group by — Room, Category, or none (flat list)

  • Show table of contents — toggle off if you want a leaner doc

  • Show pricing — auto-off for Client copy; toggle for Designer copy

  • Filename — defaults to "SpecPackage-[ProjectName]-[Date].pdf"; rename if you want

Your last-used settings persist so the next package matches your style without re-configuring.

How big can a package be?

  • No hard cap — packages of 100+ products work, but expect a longer build time (30–60 seconds for 100 products)

  • Recommended max for client presentations: 30–40 products — beyond that, the package gets unwieldy to flip through

For very large FF+E books, split by floor / room into multiple packages so the client gets digestible chunks.

Sending a package to a client

You have two paths:

Email attachment:

  • Download the PDF

  • Attach to a message in Comms (or your email client)

  • The client opens and reviews offline

Shareable link (Comms embed):

  • Upload the package to the project channel as a file

  • The PDF previews inline in Comms; the client can scroll without downloading

  • Approvals stay scoped to the project channel

For most client reviews, the Comms upload path is cleaner — the client reviews + comments in the same place the conversation happens.