A small but satisfying cleanup of the Purchase Order Received notifications. The email and the Slack message both had quiet formatting issues that showed up whenever a product name carried hidden whitespace from an old import. The Resend Notification button also only handled the email side. All three are sorted out in this release.
Email items table renders cleanly every time
- The Items received table in the receive confirmation email now renders every row with the same styled name + SKU + quantity badge, no matter what's in the product data.
- Previously, a stray invisible character in a product name could cause the table to break mid-list and dump raw HTML into the rest of the email — easy to miss in short orders, very obvious in long ones.
- Long POs with a dozen or more line items now arrive looking the way they should: tidy alternating rows, a totals footer, and a clear View Purchase Order button at the bottom.
Slack message keeps each item on one line
- Items in the Slack post for a received PO now show the bold product name, SKU, and quantity together on a single line — even when the underlying product name has trailing whitespace.
- The old behavior could split each item across two visual lines and leave a literal
*showing on the wrap, which made the message harder to skim. - The colored status dot (green / yellow / red) still reflects fully / partially / not received, so you can see at a glance whether anything is short.
Resend Notification now covers Slack too
- The Resend Notification button on the Purchase Order page used to only re-send the email. If you turned Slack notifications on after a PO was already received, there was no way to back-fill the Slack post for that PO.
- It now re-posts to Slack as well, provided the channel is enabled in Settings → Slack Notifications.
- The confirmation dialog text was updated so it's clear both channels will go out.
Quieter, more reliable going forward
- Product names and SKUs are now cleaned up automatically when they're saved, so this category of formatting issue can't sneak back in through future CSV imports or webhooks.
- Existing product names that already had stray whitespace are untouched in the database — the notification templates now handle them defensively, so you'll see clean output whether the underlying data is pristine or not.