Skip to content
Moosewave
Demo

TransactionalBilling & payments

Purchase order required email template

An invoice held because the buyer's process needs a reference first.

See the full preview Use it with MCP

Illustrative example. Replace the fictional sender, dates, amounts, locations, and account details before use.

Responsive design preview

See the message before you make it yours.

Compare the desktop and mobile compositions, or unfold the full design. The complete starting copy remains readable below.

Purchase order requiredIllustrative preview
Purchase order required email template preview

Auto follows your screen width. Scroll inside the frame to inspect the complete email.

A reviewed browser rendition of the purchase order required structure. It is not a send receipt or an inbox-placement claim.

Want to change the copy and style?

Try one of the editable browser templates.

This page is a read-only reference. The five hands-on studios let you edit a local preview, compare desktop and mobile, and review every change before continuing.

See editable templates

Message anatomy

A useful starting point, with the important parts named.

Your organisation rejects invoices without a purchase order reference. Sending one anyway would only delay payment further.

What you can change

  • Brand name
  • Subject line
  • Preheader
  • Eyebrow
  • Headline
  • Supporting copy
  • Primary action label
  • Primary action URL

What to keep clear

  1. State or event context
  2. Plain-language explanation
  3. Three labelled facts
  4. Primary and secondary action
  5. Support or privacy footer

Complete starting copy

Read it as text, not only as a picture.

Sample details are fictional. Replace them with reviewed customer and event data before use.
From
Oakhanger Orders
Subject
We need a purchase order before invoicing
Preheader
Your finance team asked us to wait for one.

Order needed

We are holding the invoice rather than sending one that bounces

Your organisation rejects invoices without a purchase order reference. Sending one anyway would only delay payment further.

Work completed

12 September

Value

£3,200.00

Waiting for

Your order reference

Send us the referenceAsk us to invoice anyway
Payment terms start from the invoice date, not the completion date, so the wait pushes everything back for both of us.

Moosewave MCP

Give an agent the structure, the job, and a stopping point.

A compatible MCP app can inspect this reference and create a separate workspace draft when it has permission. The brief cannot send.

The brief asks for a new draft and stops before send.

Read the complete brief

Connected work

Take the design beyond the canvas.

Transactional email APIConnect the message to a real product event and keep its outcome visible.IntegrationsCarry the right customer and event context into the draft.SecurityKeep account, access, and recovery boundaries explicit.MCP for agentsAdapt presentation without quietly changing the event being explained.

Keep exploring

Browse all 1405