One of my favorite features are the Logos blogs. (Thanks to the people who publish them!)
Today's entry about Abraham Kuyper’s Theology of Everyday Life got me to check out the 3-volume cultural engagement bundle.
It wasn't immediately obvious that 1) dynamic pricing had not been turned on, until I visited the Logos store to see if there were any other deals that included those particular books. I did find a collection, but 2) there seemed to be a different pricing issue with it.
I guess what I'm wondering is if other departments know before products will be mentioned in a blog, so they can check in advance to see that the blogged products are correctly priced?
I understand that mistakes happen, but it would be beneficial when FL can catch these problems before the blog readers.
(I understand we do that for free, and it's cheaper for them in the short term to rely on us to report problems than to pay someone to catch them in-house. But surely it's more cost-effective in the long term to automate and fix detection of pricing issues, than to constantly have to manually fix them after the fact, freeing up that employee's time to productively work on other things?)