The supplier sees only the lines that went wrong

A branded email carrying just the affected lines, each with ordered, arrived and claimed — the three numbers that settle the conversation.

What it is

A server-rendered email with one section per problem, headed by what it is and how many units it covers, ruled in that problem's colour. Every row states what was ordered, what arrived and what is being claimed, with the claimed figure the only coloured thing on the row. Photos render inline. The remedy is stated as a plain sentence. A shortage and a damage claim on the same delivery travel together in one email, shortage first.

Also called: claim email · report a short delivery · email the supplier about damage

See it
The supplier sees only the lines that went wrong
Area
Operations
Group
Claims
System
Supplier Order Lifecycle
Solves
3 named problems
01POST /api/orders/claim takes claim ids and a recipient, and refuses claims from different orders
02Claims are sorted shortage-first 'because it is the one that stops work'
03Ordered and arrived counts are read from the items so the supplier sees the full arithmetic
The received email: builder's brand, a red-ruled 'Damaged on arrival' card, an Ordered/Arrived/Damaged table, a row of inline photos and 'What we need: the account credited'. api/orders/claim. Sample data — no customer information appears here.
How it works
  1. 1POST /api/orders/claim takes claim ids and a recipient, and refuses claims from different orders
  2. 2Claims are sorted shortage-first 'because it is the one that stops work'
  3. 3Ordered and arrived counts are read from the items so the supplier sees the full arithmetic
  4. 4Up to six photos render as a table row so Outlook keeps them in line, each linking to full size
  5. 5The whole thing is wrapped in the tenant's brand and sent through the org's channel
  6. 6On success the claims flip to sent, the journey is stamped, and an audit entry is written
Why we built it

The route header: 'ONLY the lines that went wrong. The original order might be 400 rows; making someone scroll past 390 that arrived perfectly to find the 10 that didn't is how a claim gets ignored.' On the photos: 'Numbered links made the photos invisible: nobody at a lumber yard clicks "1 2 3" in an email.' On combining: 'A delivery that arrived short AND damaged is one conversation with the supplier, not two emails they have to cross-reference.' And a formatting fix: 'Passing bare <p>/<table> markup made the content butt against the card edges, because the shell puts its horizontal padding on these rows.'

The problem
  • A claim buried in a 400-row order gets ignored
  • Two emails for one delivery cross-referenced by nobody
  • Photo links nobody clicks
Sound familiar?
What you get
A claim the supplier can act on without hunting
Evidence visible without a click
One email per delivery

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →