81–84 of 84 posts
Earlier quoted context omitted.
There are very strict protections in place surrounding software’s use of a users address info. It’s not just a library call to access it (which the Shopping UI might do). Requires explicit user opt in on a per feature basis.
Is that GDPR? Is it still true in America?
I’m building an agentic commerce platform where you can connect any model and the stores are served as MCP-UI components.
They’re using “traditional search” to mean the shopping specific search widget or page, which is a separate feature from traditional search. It aggregates retailer listings and sorts them by price. The AI mode is based on normal top search results, which are oriented toward information about the product like the manufacturer’s page, which is usually going to be full MSRP. So technically correct that the AI mode is no…
It's not a trick. What you receive as shipping or taxes on google shopping are not the final ones, google doesn't have your full address, neither doesn't have info from the merchant for all taxes (depends on the country) and shipping applied to the product to all possible locations.
Earlier quoted context omitted.
The general implication is the opposite effect. The corporation wants to make more money. They make larger margins with this of course. But beyond that, the implication is that whatever sales are lost from the more expensive price are simply made up otherwise. If products are 20% more expensive but this only results in 10-15% less sales, the corporation is still very happy, particularly due to the margin bit. If loss…
I think the 10-15% hypothetical reduction in sales is their point, not the effect on corporate profits. Less consumer junk for the landfill is good.