Email themes and the block editor: order emails worth opening

Your quote email has a simple job: help the customer recognize the store and open the quote. Yet it can arrive with a subject like “Order 1042,” from an unfamiliar address, wrapped in whatever design came with the software. The salesperson then hears, “I never got it.”

OrderPilot's email groups, themes, and block editor let you build a message around the customer's next action. Begin with that action, choose a suitable design, and let the order supply the details. A well-organized email should feel like a continuation of the showroom conversation.

Decide what each message asks the customer to do

Different stages need different messages. A quote asks for review. A signature request asks the customer to read and sign the agreement. A payment request identifies the amount requested and how to pay. A progress update explains what changed.

Write that purpose before arranging blocks. If the message asks the customer to sign, review a fabric, pay, browse accessories, and follow a social account with equal emphasis, you haven't chosen its job yet.

A stage update can have no immediate action at all. “The maker has confirmed the order” may be the information the customer needs. In that case, a link to the order is useful without pretending the customer has another task to complete.

The stage-message guide helps match wording to the event. Keep the email's claim as narrow as the event it reports: sent to the vendor doesn't mean delivered to the warehouse.

Use email groups to connect messages with the workflow

OrderPilot includes groups such as Quote, Invoice, Quote follow-up, Request signature, and Request payment, and supports your own groups. A workflow status can trigger the group intended for that stage.

Each group has a default template and can have brand versions. The group identifies the kind of message; the template determines its wording and design. This is useful when several showrooms share a workflow but send differently branded emails. Review the status trigger and the email together. A handsome “Ready for delivery” message is still wrong if the triggering event only means one piece has arrived. Use wording that matches the actual order condition and points the customer to the details.

Sending on creation is a separate setting within the notification setup. Don't assume that designing a quote email means every newly saved draft will send it. Choose the intended behavior and test it with sample orders.

Choose a theme for the reading job

The six themes give you different starting points: Ledger, Gallery, Summary card, Paper, Statement, and Minimal. Choose one by reading the sample content, not simply by liking the empty design. Gallery is a sensible editorial choice for an image-led furniture quote. A customer reviewing a sofa benefits from a recognizable product picture near the relevant information. Ledger or Statement can suit an invoice where the amounts and reference need to lead.

Paper can support a quieter, letter-like message. Summary card can give the central information a defined place. Minimal is useful when a short update needs very little around it. These are design judgments, not restrictions on what each theme can send.

Keep related messages recognizable even when their themes differ. The same logo, sender identity, and general button treatment can connect a detailed quote email with a brief production update. The shared branding guide explains that common foundation.

Arrange blocks in the order the customer needs them

The template editor separates Details, Design, and Blocks. Use Details for the message identity and subject, Design for the overall treatment, and Blocks for the content the customer reads.

Blocks can include order status, an amount summary, callout boxes, contact grids, detail rows, promotional material, and dividers. Dragging them into order should follow the customer's questions: who is this from, what happened, what do I need to know, and what do I do next? For a quote email, start with a short message about the prepared quote. Put the relevant order details and main action where they are easy to find. Contact details belong where they help the customer reply or ask a question.

Use callouts sparingly. If everything sits in a highlighted box, nothing is especially noticeable. A delivery-access question can justify a callout; a decorative welcome sentence usually doesn't.

A promo banner is available, but it doesn't belong in every message. When someone is approving a fabric or arranging a balance payment, a second sales pitch competes with the work already underway.

Let merge fields supply the order's details

Merge fields bring record-specific information into a reusable template. Use the picker for supported fields, including links, rather than typing a sample order number or destination into the design. Test the fields with an actual sample order. A field can be valid while the record it reads is incomplete. A missing customer detail or an unexpected location is easier to catch in the rendered message than in a template full of field labels.

For the subject, include the store's name in the saved template wording, or use a supported merge field where appropriate. The saved subject then supplies that identity on later sends using the template. Review every default and brand version; don't assume one global subject setting has renamed all messages.

A sample subject such as “Oak House: your dining-room quote” gives the customer more context than “Update.” The store name here is fictional. Use the name the customer recognizes and enough order context to identify the conversation.

Work through a quote email from top to bottom

Suppose a customer has selected a walnut dining table and chairs in a navy fabric. The team has prepared the quote, and the customer wants to review it at home.

A useful opening says that the quote includes those choices and asks the customer to review the configuration. The main button leads to the appropriate quote or customer page. The email's summary should agree with the saved record and its attached document.

Keep any expected timing in honest wording. A maker's estimated production window isn't a booked delivery date. OrderPilot doesn't automatically insert option lead time into these emails, so write the update from the information the team has actually confirmed.

If warranty wording is needed, keep it connected to the relevant piece and the recorded terms. Don't let a broad sentence in the email promise more than the quote's coverage.

On a revised quote, explain what changed. “Updated quote attached” makes the customer play spot-the-difference with a dining table. The revised-quote guide shows how to call out a changed finish, quantity, or charge without repeating the whole sale.

Publish the version you have actually reviewed

Changes made through Apply this look in Settings › Branding produce email drafts. They don't silently replace the published template. Review the draft's content and rendered design, then publish the intended version.

Keep that distinction visible during a branding update. A team can finish the shared palette and still have several customer emails awaiting publication. The work is complete when the intended templates are live and tested, not when the editor looks right.

Brand versions need the same review as defaults. Test the correct brand and location with sample data, and look at what the default would send if a brand version isn't assigned.

Before publishing, use the phone and dark-mode preview routine. It checks whether the design still works in the conditions where the customer will read it.

Treat sending identity and customer preferences as part of the message

A recognizable design works best with a recognizable sending identity. Set up the store's sending domain and review sender and reply details so the customer can connect the message with the showroom.

The own-domain setup guide covers that work. A correct domain setup supports delivery, but no template design can guarantee placement in every inbox.

Customer emails include an unsubscribe route, and customer preferences affect future sending. If a message is suppressed, investigate the record and use the store's appropriate communication process rather than repeatedly trying the same email.

Quote reminders are optional and send at most one automatic reminder for a quiet quote still in Draft. Design the reminder as a useful return to the quote, with a clear route back to the conversation.

SMS doesn't inherit the email's blocks, fonts, or layout. Status texts use separate fixed templates, with no one-off or edited SMS wording. The email editor gives you the rich design surface for the detailed customer message.

Use a short checklist before a customer sees it

Review each finished template for the following:

• The subject and sender identify the store.
• The message describes the correct stage of the order.
• The main action has a clear purpose and working destination.
• Merge fields resolve to the intended sample record.
• Amounts and configuration agree with the quote or order.
• Images support the information instead of delaying it.
• Contact details and customer-preference links remain readable.
• The correct default or brand version is published.
• A test email reads comfortably on a phone.

Send yourself the message and follow its main link. That final small exercise connects the design to the actual sale. Continue with email previewing on phones and in dark mode before putting the template into regular use.