Cybersecurity
The Checkout Skimmer Problem on Magento
Checkout skimmers steal card data from Magento stores without breaking anything. What they really cost you, why you won't notice, and how to cut the risk.
For twenty years your storefront has been built for one kind of visitor: a person. They land on a page, skim the photos, read a little, and decide. That visitor is no longer the only one who matters. A growing share of shoppers now start inside ChatGPT or Gemini, ask for a recommendation, and let the assistant do the comparing. The question for store owners is simple and slightly uncomfortable: when an AI agent goes looking for a product like yours, can it actually read your store, or does it quietly move on to a competitor it understands better?
Your store has a second kind of shopper now
This is not a prediction about 2030. Shoppers are already using large language models to find products, compare options, and narrow down what to buy before they ever touch a storefront. The assistant reads product data, weighs it against the request, and hands back a short list. Your store is either on that list or it isn't.
The uncomfortable part is that being on the list has very little to do with how good your website looks to a human. An AI agent never sees your hero banner or your carefully art-directed product photography. It reads structured data: the title, the specs, the price, whether the item is in stock. If that data is thin or messy, the best-looking store in your category can still lose the recommendation to a plainer competitor with cleaner information.
The money is already moving
The numbers behind this shift are not subtle. Over the 2025 holiday season, traffic to retail sites coming from generative AI tools jumped close to 700% compared with the year before, according to Adobe's data on AI-driven shopping. And these are not low-quality visits. Adobe found that shoppers arriving from AI assistants convert about 31% higher, generate roughly 254% more revenue per visit, and spend noticeably more time on-site than visitors from traditional channels.
Read that again, because it's most of the argument in one line: the visitors that your competitors' AI recommendations send to checkout are more likely to buy, and worth more when they do. A channel that barely existed eighteen months ago is now delivering some of the most valuable traffic on the web, and it rewards whoever the agent decides to trust.
Agents read attributes, not adjectives
Here's the part most owners miss. When a shopper asks an assistant for "a quiet espresso machine under $400 with a built-in grinder," the agent doesn't read your product description the way a person would. It looks for concrete, machine-readable fields it can match against that request: noise level, price, grinder yes or no, in stock or not. Marketing copy that reads beautifully to a human ("cafe-quality mornings, redefined") tells the agent nothing it can use.
So the stores that win the recommendation are the ones whose catalogs answer questions in a structured form. Complete attributes. Consistent categories. Accurate, real-time stock and pricing. When the data is ambiguous or missing, the agent does the rational thing and recommends a competitor whose data it can actually evaluate. You never see that loss. There's no abandoned cart and no bounce in your analytics, just a sale that quietly happened somewhere else.
What "agent-ready" actually means
Strip away the jargon and agent-ready comes down to a few unglamorous things being true about your product data.
Your catalog needs rich, complete attributes — not just a name and a price, but the specific properties shoppers ask about in your category. Those attributes need to be consistent, so the same kind of product is described the same way across your whole range. Your stock and pricing need to be accurate in real time, because an agent that recommends a sold-out item makes the shopper distrust the assistant, and the platforms work hard to avoid that. And all of it needs to be readable by a machine through a clean, queryable feed rather than buried in your page layout.
None of that requires reinventing your store. It is closer to good housekeeping than to a rebuild. The catch is that most catalogs have quietly drifted over years of edits, bulk imports, and quick fixes, so the gap between "looks fine" and "actually clean" is usually wider than owners expect.
Don't let the hype talk you into a rebuild
A fair question at this point: if this is so big, should you drop everything and re-platform around it? No. And anyone telling you otherwise is selling something.
The honest read is that agentic commerce is still early. J.P. Morgan's assessment of agentic commerce points out that most of what's marketed as "agentic shopping" today is really embedded discovery, where the agent suggests but the actual purchase still finishes on the merchant's own site. Fully autonomous checkout, where an agent buys without a human approving, will take longer still. OpenAI even paused its in-chat checkout feature after the early rollout proved harder than expected.
That early-ness is exactly why the smart move is cheap. You don't need to bet on which protocol wins, and you don't need to rebuild your checkout for robots. You need clean, rich, well-structured product data, which also happens to help your human shoppers, your search ranking, and your marketplace feeds today. It is the rare no-regret investment: useful now, essential later.
Where Magento and Adobe Commerce fit
If you're on Magento or Adobe Commerce, the platform is already moving in this direction, which works in your favor. In early 2026 Adobe publicly committed Adobe Commerce to support the new agentic commerce standards, the shared protocols that let AI assistants read a store's catalog, pricing, and inventory and, eventually, complete a purchase. In plain terms, the plumbing to make your store legible to agents is being built into the platform rather than left for you to invent.
But a platform supporting a standard and your store being ready for it are two different things. The protocols only matter if the data flowing through them is good. A store running on years of inconsistent attributes won't suddenly get recommended because the platform now speaks the right language. The groundwork of getting your catalog clean and your data exposed safely is the part that's on you, and it's worth being deliberate about what to expose to an AI agent and what to keep locked down.
A sensible first move this quarter
You don't need a grand agentic strategy. You need to know how big the gap is, and that starts with a clear-eyed look at your own catalog.
Pick your top-selling categories and ask the practical questions an agent would ask. Do your products carry the attributes shoppers actually filter on, filled in completely and consistently? Is your stock and pricing data correct the moment it's queried, not an hour later? When you ask ChatGPT or Gemini to recommend a product in your category today, does your store show up at all? That last test takes five minutes and is often a humbling place to start.
From there it's mostly cleanup and structure: enriching thin product records, fixing inconsistent categories, and making sure your data can be served to an agent through a reliable feed. It is the kind of unglamorous groundwork that compounds, and the stores that do it now will be the ones the next wave of assistants learns to recommend first.
Getting ready for what's next
If you're trying to tell whether your catalog is genuinely agent-ready or only looks fine to humans, that's the kind of problem we work on at Encomage. The work usually starts with an honest audit of your product data before connecting it cleanly to the AI channels now driving sales.
