NorthScope 2026.07.02

Software Version: 2026.07.02 Database Version: 2026.07.02

Release Date: Jul 2, 2026

New Features

System

NS-13632 - Email Queue: HTML Emails Can Finally Wear Their Fancy Pants

NorthScope’s mail queue already had a way to identify whether an email body should be sent as HTML or plain text. The problem was that our SendGrid integration was not honoring that setting, so messages were being sent as plain text even when the queue said, very politely, “HTML, please.”

We’ve updated the NorthScope mail processor so that when the email queue’s Body Format is set to HTML, the message is passed to SendGrid as HTML. Any other value will continue to send as plain text, just like before.

A couple of practical notes, because email delivery is a haunted swamp with SPF records:

• NorthScope partners with SendGrid to send email, but we do not control how SendGrid or recipient mail systems evaluate, filter, or deliver messages.

• This change does not magically convert plain text into HTML. The email body must already include valid HTML markup if it is expected to display as HTML.

• Sending properly formatted HTML email may help messages look more polished and legitimate, but it is not a guaranteed “escape the spam folder” spell. Spam filters remain tiny suspicious gatekeepers with clipboards.

In short: NorthScope now correctly tells SendGrid when an email should be sent as HTML. The message still needs to be written as HTML, and the email goblins still get a vote after that.

Improvements

Grower Accounting

NS-12788 - Farmers: Price Lists Are Editable Again—When It’s Safe

The Farmers List View was being a little too protective with Price List changes. If a Farmer had ever been tied to a Price List and had ticket activity, NorthScope could lock the field down, even when there were no open tickets left that actually needed protecting. Very cautious. Very responsible. Also slightly like putting a traffic cone in an empty parking lot.

We’ve loosened that up in a controlled way. Users can now edit or clear the Price List for a Farmer from the Farmers List View as long as there are no open tickets for that Farmer tied to the existing Price List.

Open tickets still matter, of course. If active ticket work is still in play, NorthScope will continue preventing the change so pricing does not get quietly rearranged underneath an unfinished transaction. Accounting goblins love that kind of chaos. We do not feed them.

Bugs

Purchasing

NS-13097 - Purchase Orders: Rolls, Each, and the Dangers of Unit Confusion

The Purchase Order Lines list view was having a Unit of Measure identity crisis. An item could be purchased in Rolls, received into inventory in Each, and have a perfectly valid UOM conversion already set up between the two. NorthScope knew the conversion existed. The setup was fine. The math had a map.

Unfortunately, the Purchase Order Lines list view occasionally decided to report quantities like Purchase Order UOMs and receipt UOMs were all just vibes. They are not vibes. They are accounting-adjacent measurements, which means we have to be annoyingly precise about them.

We’ve fixed the calculations so Purchase Order quantities and amounts now respect the Purchase Order’s Unit of Measure, even when related Inventory Receipts or AP Invoices/Memos use a different UOM. NorthScope will use the existing UOM conversion setup and display the values correctly in the PO context.

We also added a guardrail: once a PO line is assigned to a Posted Inventory Receipt or Posted AP Invoice/Memo, the UOM field on that PO line is disabled. Because changing the unit after posted activity exists is the sort of thing that sounds harmless right up until everyone is trapped in a reconciliation swamp wearing tiny accounting boots.

If those related transactions are later voided, and no other posted transactions are assigned to the PO line, the UOM field becomes editable again.

NS-13966 - AP Transactions: Attributes Stay in Their Own Lane

The Attributes tab on AP Transactions was getting a little too inclusive. Instead of showing only the attributes that applied to the current transaction type, it was showing all available attributes—Invoices, Credit Memos, Fisherman Sales, Tender Resales, everybody into the pool.

That is generous. It is also wrong.

We’ve fixed the filtering so the Attributes tab now displays only the attributes that apply to the specific transaction and transaction type being viewed. This keeps AP Invoices, Credit Memos, Fisherman Sales, and Tender Resales from borrowing each other’s setup like poorly labeled leftovers in the office fridge.

Sales

NS-13646 - Sales Orders: Freight Currency No Longer Needs an Item Chaperone

Sales Order shipment legs were being a little needy. If you changed a shipment leg to use a currency different from the order currency before adding any items, NorthScope would save the freight rate but skip setting the exchange rate information. Add an item first, though, and everything worked fine. Naturally. Because apparently the exchange rate needed moral support from a line item.

We’ve fixed that. When a freight rate is saved on a shipment leg, NorthScope now populates the exchange rate between the Order Currency and the Leg Currency whether or not any items have been added to the order yet.

That means the freight rate, freight amounts, and related currency fields will behave consistently no matter when you set up the shipment leg.

In short: shipment leg currency now stands on its own. No item required. No weird timing dance. No “do this in the right order or the math gets shy” nonsense.

NS-13736 - Sales Orders: Auto Allocation Stops Panicking at Multiple Lines

Sales Orders had a very specific little tantrum involving non-lot tracked inventory items, auto allocation, and multiple new lines being added before saving. If the item was set to auto allocate, and the preference to prevent shipping more than the ordered quantity was turned on, NorthScope could incorrectly complain:

“You cannot allocate more than the ordered quantity.”

Which would be a very useful message if that were actually what happened. It was not. The user had simply added multiple valid non-lot tracked inventory lines at the same time, and NorthScope got itself tangled up doing the allocation math.

We’ve fixed the issue so users can now add multiple non-lot tracked inventory items to a Sales Quote or Sales Order at the same time, save once, and have the lines allocate correctly without the bogus over-allocation warning.

In short: auto allocation now handles multiple new lines like a grown-up. No false alarms, no unnecessary scolding, and no making users add lines one at a time like we’re rationing inventory entry.

NS-13879 - Customer Favorites: Invoice Descriptions Stop Playing Two Truths and a Lie

Sales Orders had a problem where the Invoice Description for customer favorite items could look right on the screen, save differently behind the scenes, or update in one place but not the other. Very efficient, assuming the goal was to make everyone question which value was real.

We’ve fixed the behavior so invoice descriptions now follow the correct defaulting order:

• If the customer favorite item has a Customer Item Description, NorthScope uses that first.

• If not, NorthScope uses the item’s Sales Invoice Description from the Item Master file.

Users can still override the Invoice Description directly on the sales transaction when needed. That override will now display correctly and save correctly. And if the value is cleared, NorthScope will re-default it using the same sequence above.

Technical Changes

• No schema changes.

• No config file changes.