`tk11041-innovations-reconcile/rescrape/DISCOUNT-LINE-TO-ADD.md`

58 lines

# One line to add to the Whistler draft — settles the discount at zero extra outbound cost

**Draft:** `r-5469570474427181957` (msg `1a09124ac539ff62`), info@ → hmartinez@innovationsusa.com,
subject *"Re: Current trade price list request"*. **UNSENT.**

## Why bother
TK-11041 cannot compute retail for the 39 live items until one question is answered:
`vendor_registry.innovations` says **10%**, and every DW sample request since 17 Aug says
**"acct 58315 - Net Less 20%"**. A 10-point cost-basis error propagates straight through
`cost/0.65/0.85` to customers.

Hektor is the person who can end the argument in one line, he has proven responsive
(he answered the price-list request the same day), and he volunteers exactly this class of
fact unprompted — on 2026-09-10 he wrote *"Chevron Cork has been discontinued. CRC-02 - 62LY
in stock."* with no one asking.

**There is already an unsent email going to him.** Adding one sentence to it settles the
discount for the cost of zero extra emails. Sending the Whistler question alone, and then
discovering later that we still need the discount, costs a second outbound.

It also closes the *second* unknown the portal pull cannot resolve on its own: whether the
number behind our login is our **net** price or the **list** price. The sentence below asks
that too, in the vendor's own terms.

## The sentence (drop in after the Whistler paragraph, before "Thank you,")

**Prose:**

> While we're updating our records — could you also confirm the discount on our account
> (58315)? Our file shows two different figures and we'd rather use yours than guess. And so
> we read the site correctly: are the prices shown when we log in already our net, or are they
> list with our discount applied at order?

**HTML (matches the draft's existing markup):**

```html
<p>While we're updating our records &mdash; could you also confirm the discount on our account
(58315)? Our file shows two different figures and we'd rather use yours than guess. And so we
read the site correctly: are the prices shown when we log in already our net, or are they list
with our discount applied at order?</p>
```

## Why it is written this way
- **Does not name either number.** Saying "we have you at 10%" invites a courtesy "yes" to a
figure that may be wrong; asking open gets his figure.
- **"we'd rather use yours than guess"** gives an honest reason for asking something a customer
arguably should already know, without sounding like our records are a mess.
- **Second sentence is the one the portal cannot answer.** Net-vs-list is invisible from a page
that just prints a number, and guessing it is the same error as guessing the discount.
- **Zero DW or private-label names**, so Steve's "none of our names" directive holds.

## Status
**NOT merged into the draft.** This draft is `agent_composed=false` and the next action on it is
Steve clicking send — an agent-rewritten vendor letter becomes unwitting approval of wording he
never saw. The one prior merge happened only because he approved it explicitly ("I merge it now").
Same offer here: say the word and it goes in with one call, with a pre-edit restore point captured
first, exactly as the last merge was done.