Your Catalog, Your Packages, Your Real Price

Sprint 2026.14 puts merchandising back in your hands. Locally created caskets that a distribution-centre rule had quietly hidden are visible again, showroom cards pick the right image and sort by the price you charge, and the general price list now tells you which packages an item belongs to before you change its price or its visibility. Allow One Package Only finally does what it says. Your SAP net price sits beside retail on GPL Pricing, behind its own permission. And around all of that: a rebuilt Order History, posted cases that stay posted on every screen, activity times in your own time zone at last, and a new-case save that can no longer fail and leave a duplicate behind.

Your Catalog, Back in Full

A rule written to stop us offering a Matthews Aurora casket your distribution centre doesn't carry was reaching much too far. Anything without a Matthews Aurora identity — which is to say every casket and container you created yourself — looked to that rule like something the centre didn't stock, so it was hidden from the Catalog, the Arranger, the Kiosk and Connections alike, no matter what your price list or your location visibility said. The rule now applies only to Matthews Aurora products, which is what it was always meant to mean.

Expect items to reappear. If your catalog contains caskets or alternative containers you created locally, they are back — including the basic cremation containers this was reported about.

• Your Own Items Are Yours — Locally created caskets and containers show in every catalog surface again, governed by your price list and location visibility rather than a stocking rule that never applied to them
• The Right Photo — A showroom card now picks its image deliberately rather than taking whichever one came back first, and prefers an item you've switched on
• Sorted by What You Charge — Showroom cards sort by retail price, not cost, so a casket that costs more but sells for less stops jumping the queue
• Search That Finds Things — Keyword search in the showroom item picker no longer drops every item without a price — at some homes that was the great majority of the catalog
• Visibility Respected — Showroom item lists exclude products you've switched off in Visibility
• Nothing Found, Said Plainly — A search with no matches shows a message instead of an empty pane

Packages That Behave

Changing an item's price on the general price list can change what a package sells for, and switching an item off can change what a package contains — but nothing on those screens told you so. Now they do. And the company preference that limits a case to a single package, which had quietly never been read by anything, is enforced on every screen that can add one.

• See the Packages Before You Change the Item — GPL Pricing, Visibility and the item edit screen show which packages an item belongs to, so a price or visibility change is never a surprise
• One Package Means One Package — Allow One Package Only is honoured in Advisor, Arranger 1.0, Arranger 2.0 and both Connections guides, and on the server, so a second package can't slip in from any direction
• Select Means Selected — In the Arranger 2.0 package details window, pressing Select This Package on the package you already chose confirms it instead of silently removing it
• Catalog Edition Boundaries — In a Catalog edition company, products and services can no longer be created from the GPL screens, the deep links, the spreadsheet importer or the API

The Price You Actually Pay

Until now, finding out what an item actually costs you meant generating a net price list and reading it alongside the screen you were working on. Your net price now appears on GPL Pricing itself, loaded quietly in the background while you work so the screen never waits on it.

• Net Beside Retail — GPL Pricing in Retail mode shows the net price for each item, gated by a new View Net Pricing permission so it's visible only to the people who should see it
• Loaded in the Background — Prices warm as you enter the general price list, with a progress banner that never blocks the screen
• Discounts That Reconcile — Where terms discount conditions are switched off, the price list no longer adds a discount back that was never taken — the correction that had been overstating net price on most lines
• Several Accounts at Once — Administrators get a Run Batch dialog that prices multiple accounts into a single download
• Progress You Can Watch — Price list generation moved out of toasts that scrolled away and into a dialog that stays put for the whole run, with a real step counter

Orders, End to End

Order History hid each order's detail behind a per-row expander whose control was, in practice, invisible. It is now a proper master/detail screen: the list on one side, the order you're looking at on the other.

• Read the Order Beside the List — Order History is rebuilt as a master/detail split, so an order's detail opens next to the list instead of behind a control nobody could find
• Insurance Carries Through — Insurance entered at Vital Information > Funding flows onto the case's cart lines, so the policy and company reach the order rather than being retyped or lost
• Insurance You Can Edit — The insurance boxes on cart lines that came from a case are editable, matching catalog lines
• Add To Cart, Once — The Catalog's Add To Cart button reflects that an item is already in the cart, so a second press doesn't create a duplicate line
• Engraving Dialogs That Close — Closing the engraving window with its X behaves the same as Cancel, and it no longer reappears when you open View Contract

Posted Cases Stay Posted

When your layout marks arrangement fields as locked once a case is posted, Vital Information honoured that — but the Gatherings screens, the Arranger libraries and the Digital Whiteboard did not, so the same four values could still be moved from a different door. Every door now has the same lock on it, and the screens show it rather than letting you type and then refusing.

• The Same Rule Everywhere — The Arrangement Conference's date, start time, location and notes are protected on a posted or exported case on every path that could change them, including deleting the conference outright
• Locks You Can See — The case Gatherings list and editor, Arranger 1.0 Library Gatherings and the Arranger 2.0 Gatherings component render those fields read-only with a padlock, and the Whiteboard's Add Gathering dialog withholds the Arrangement Conference type on a frozen case
• Changing Location Doesn't Strand Values — A location change no longer wipes a case's events while leaving the old arrangement values behind, and is refused outright on a frozen case
• Deleting a Person Can't Damage a Posted Case — A person delete that would clear an authorizing agent on a posted or exported case is refused, naming the case, the decedent and the slot
• Only Family Time and the Rest Move Freely — Every other gathering type, and End Time, are untouched

Right Time, Right Place

The Arranger Activity Timeline is meant to be the record of what happened and when. Outside the Eastern time zone it wasn't — because almost no funeral home had a time zone recorded at all, and the timeline had nothing to fall back on but Eastern. Roughly ten and a half thousand homes now have their own zone, derived from their address.

• Your Time Zone, Recorded — Every funeral home's time zone is set from its physical address, including the states that straddle a zone boundary
• Timeline Times That Match the Clock — Activity Timeline entries display in the funeral home's time zone in both Arranger 1.0 and 2.0, instead of being shifted four or five hours
• Set It Yourself — Settings > Funeral Homes gains a Time Zone dropdown, and a new home is given a sensible default rather than none
• Kept Right Going Forward — A home without a zone picks one up the first time an address is saved, and a recorded timestamp that couldn't possibly be right is corrected on arrival rather than displayed

Saved Once, Saved Properly

The worst kind of error message is one that says a save failed when part of it succeeded. Saving a new at-need case on a company with a New Call designer could report "Error creating case" on a case that had, in fact, already been created — and then the still-open form invited you to press Save again, creating another.

• No More Duplicate Cases — A new case save that fails partway now resumes rather than starting over, and the entered values stay on the form instead of clearing
• One Press Is One Press — Save, the Escape key, dismissing the overlay and the dashboard Case Creator widget all guard against a second submission
• Disclaimers That Fit — The Case Disclaimer box now caps at the length that can actually be stored and shows a counter, instead of accepting a pasted disclaimer and failing with a raw database error
• Notes That Persist — The case disclaimer and death certificate notes save when you save immediately after typing
• Reactivating Clears Lost — Reactivating a case clears its Lost status as well as the inactive flag, so it stops reading Lost and returns to the sales reports
• Concurrent Posting, Handled — A case that becomes posted while you are saving gives a clear refusal naming the locked field rather than an unexplained error

CareSign and CareAssist

CareSign was switched on or off for an entire environment, which meant accounts that hadn't bought it could reach it. It's now entitlement-based, per company — and building a signing template no longer requires a live case to build it in.

• Enabled Where It's Bought — CareSign is available on the accounts entitled to it, rather than to everyone in an environment
• Only the Documents You Use — The document picker lists only documents your account has active
• Build Templates from Settings — A CareSign template builder lives in Settings > Report Management > Reports, so templates can be prepared ahead of time
• Signature Fields That Stay — The family-side signing page no longer loses its signature fields on documents carrying text annotations
• CareAssist Summaries You Can Shape — The sections of a CareAssist summary are defined by the prompt, so a card can be added or reworded without waiting for a release, and a new Service Ideas card is built from what the family actually said
• Approvals That Hold — Sensitive values wait for approval before reaching the screen, a missed approval stays open until it's decided, and a refused value isn't quietly re-offered as approved

Families and the Guides They See

A family filling in a guide should never be asked to prove who they are twice, and should never be told nothing at all when something doesn't save. Both were happening.

• Stay Signed In — A family's session no longer ends with a full-screen error when their access code validation ages out; the guide refreshes it as they turn pages
• Failures That Say So — A vital field that doesn't save now tells the family, in plain words, instead of accepting the answer and losing it
• A Wobble Isn't the End — A brief connectivity loss no longer replaces the whole guide with an error card that nothing could clear
• Content That Fits Its Card — In the Minimal template, long pages such as Summary and Biography keep all their content inside the white card instead of spilling onto the page background
• Imports That Work — Guide imports accept the full size the server allows rather than rejecting archives it would have taken, and a failed import no longer leaves half a guide behind
• Duplicates That Match — A duplicated guide reproduces the original's layout, zones, ordering and media instead of arriving with labels on the wrong side of a split page

Arranger Polish

A round of fit-and-finish across both generations of the Arranger, aimed at the small frictions arrangers hit several times a day.

• Address Same as Deceased, Back — Arranger 2.0's People tab regains the checkbox Arranger 1.0 has, and says so plainly when the deceased has no address to copy
• Adding an Authorizing Agent Works — A newly created person reaches the authorizing agent dropdown instead of leaving the field blank, in both Arranger 1.0 and 2.0
• Duplicate People, Flagged — The Add Person flow warns when the person you're adding looks like one already on the case
• Running Total That Updates — The Arranger 1.0 Selection page total reflects a product as soon as it's added or removed
• Payment Dialogs That Make Sense — Choosing a payer type on the anticipated payment dialogs disables the other one, rather than leaving both live
• Readable Biography Fields — Membership, Organization and Life Accomplishment labels no longer clip on the Arranger 1.0 Biography screen
• No Phantom Unsaved Changes — A masked field on Basic Information no longer marks the form dirty the moment it loads
• Conclusion Page, Clean — The Arranger 1.0 Conclusion page loads without an error toast
• Deductions Deduct — Adding a deduction on the original contract reduces the balance instead of increasing it

Bug Fixes

• #11056: Locally created caskets and containers appear in the Arranger, Catalog, Kiosk and Connections again
• #11000 / #11032: Showroom cards pick the right image and sort by retail price rather than cost
• #11001: Casket keyword search in the showroom item picker returns unpriced items instead of nothing
• #11142: Showroom item lists exclude products switched off in Visibility
• #10998: Allow One Package Only limits a case to a single package on every surface
• #11063: Select This Package in the Arranger 2.0 details window confirms the package instead of removing it
• #11004: A Catalog edition company can no longer create products or services
• #11226: GPL Visibility finishes loading on a fresh page load or refresh
• #9955: Insurance entered on the case reaches the cart line, and cart insurance is editable
• #10904: The Catalog Add To Cart button reflects items already in the cart
• #11073: The engraving window closes cleanly on its X and does not reappear on View Contract
• #9718: Buy It Now on Merchandise no longer errors
• #10995 / #11070: A failed new-case save no longer reports failure while creating a case, or creates a duplicate on retry
• #9827 / #11225: Case disclaimer and death certificate notes save, and the disclaimer caps at a length that can be stored
• #11041: Basic Information stops warning about unsaved changes on load
• #11062 / #11116: Arrangement fields locked on a posted case are enforced and shown read-only in the Gatherings editor
• #11061 / #11066 / #11075: Posted-case protection holds on the Connections write paths and on person deletes, and a concurrent post gives a clear refusal
• #11030 / #11106 / #11107: Arranger Activity Timeline times display in the funeral home's own time zone
• #10934: A corporate workflow condition no longer matches a sibling company's case
• #10928: Connections Minimal template keeps long pages inside the content card
• #10942 / #11002: Guide imports accept the documented size, and duplicated guides match the original's layout and media
• #11105: Guide Export, Duplicate and Import verify the guide belongs to your company
• #11049: Arranger 2.0's People tab regains the Address Same as Deceased checkbox
• #11080: The Add Person flow warns about a potential duplicate authorizing agent
• #11079: The Arranger 1.0 Selection page total updates after a product is added
• #11081: Anticipated payment dialogs disable the payer type you didn't choose
• #10964: Biography labels no longer clip on the Arranger 1.0 Biography screen
• #10963 / #11072: The Arranger 1.0 Conclusion page loads without an error
• #10076: A deduction added on the original contract reduces the balance
• #10943: A miscellaneous sale requires a sale date before it can be posted
• #11064 / #11084 / #11118 / #11119 / #11120: CareSign is entitlement-gated, lists only active documents, keeps its signature fields, and gains a template builder in Settings
• #11043: Notes copied during a pre-need conversion keep their original author and date
• #11054: Settings > Users and Settings > Reports export to CSV
• #9963: A Family Link / My Website integration requires a funeral home before it can be saved
• #9727: The Resource Types settings page no longer freezes

What's Next?

Net pricing on the general price list is the first screen to show it; the same figure belongs in more places, and forward-dated pricing is already built and waiting on a date range to be set. Now that analytics datasets are defined by stored procedures rather than by code, correcting or adding one is a database change instead of a release — expect that list to grow much faster. And with every funeral home's time zone finally recorded, times across the application can start reading the way your clock does rather than the way ours does.

As always, if you run into issues or have feature requests, let us know.

— The Solution Center Dev Team