Your example this morning exposed a rounding issue in the modeling we used to create the Dynamic Pricing for these sets that resulted in users who owned most of the collection (58 vols or more) seeing prices that were pennies above the $14.99 individual volume price.
Do sales data need to be created on a product-by-product basis, based on some person plugging values into some model, which they then use to update (or fix) a product page by hand?
Is this process dependent on a person making these calculations, versus technology automating it for them? Isn't it possible for the front/back end to serve up these pages, without having to rely on some intermediate data that had to be generated by a person?
Is there a reason why recurring problems can't be addressed? Money? Lack of manpower? Can't hire/assign anyone to fix it?
I understand that Faithlife isn't as big as other online merchants. Perhaps FL even designed their own storefront instead of using another vendor's product, and the whole process has grown into a tangled mess of procedures that are held together by human intervention.
But the storefront isn't Logos, and the store isn't stuck with past decisions or schemas or human processes. Even though it might be an expensive undertaking to replace it, surely it needs be redone from the ground up, to modernize the store and automatically generate consistent product pages with accurate (dynamic) pricing?
Isn't it possible for a technology company like Faithlife to get past the "we plan to address this or that in the future" approach, which has only led to months or years of unresolved product page and pricing issues, and continues to impact customer satisfaction?
