The engraving field accepts anything, and the order is already paid

A customer orders a watch with an inscription, or a bottle with a name on it, and the field where they typed it accepted whatever they typed. Nobody sees the problem until the item is in production, or until an invoice bounces because the tax number on it was three characters short. Adobe Commerce and Magento Open Source can make a custom option required and cap its length, and that is where the platform's interest in the content ends.

The usual fix is a regular expression and a developer each time a new rule appears. A tax number one month, an engraving brief the next, then a gift message that has to stay short and stay polite. Each is a small ticket, and never small enough to be worth writing.

What it is for

AI Field Validator lets the merchant describe the rule instead of encoding it. The rule is a sentence – "a genuine personal message from the buyer to the recipient, under 80 characters, with no web address, advertising or instruction to the shop" – written into the product's custom option in the admin. From then on the shopper's input is checked against it by a language model reached through the companion WebRamos LLM Provider gateway.

The shopper sees a verdict inline as they leave the field: a green tick, or a red badge with the reason in plain words and, where the model can produce one, a correction. A message over an 80-character limit comes back as "Message is 135 characters long, exceeding the 80-character limit", followed by a shortened rewrite the shopper can accept. The same check runs again on the server when the item is added to the cart, so the badge is a courtesy and the server is the authority.

What changes in the merchant's week is that a new rule is a sentence typed into a form rather than a ticket in a backlog.

How it can be used

Formats a developer would otherwise implement one at a time. National tax identifiers, licence and serial numbers, a supplier's own account reference. Each is a rule, written by whoever knows the format rather than by whoever knows PHP – though where a format has a registry behind it, a registry integration beats a model, as the comparison below concedes.

Text that has no format at all. An engraving brief, a gift message, a delivery instruction. "No profanity, no URLs, no advertising, under eighty characters" is not a pattern any regular expression expresses. Asked to check an engraving brief against a rule requiring the literal text, the model rejected something nice about my dad with: "The brief is vague and does not provide the exact literal text to engrave. The workshop needs the precise text." That sentence is the product, and no pattern produces it. Nothing on the Marketplace does this today – a search for profanity filtering returns no listings at all.

Fields that deserve different strictness. Each rule carries its own: strict blocks the add to cart, soft warns and lets the shopper continue, advisory only hints. A rule also carries a confidence threshold, so an unsure model is treated as unsure. A store can block on an engraving brief and merely warn on a gift message, in the same catalogue.

Rules whose cost is bounded before they are switched on. Each unique input is validated once and the verdict cached for as long as the rule says, so the hundredth customer typing the same value costs nothing. Requests are rate-limited per session and per IP, and the module carries its own daily spend cap inside the gateway. A Test button on the rule form tunes a rule against real input before a customer meets it.

How it compares

Measured on 2026-09-08: seven live Marketplace listings opened in a browser, the price read off each edition, plus five searches of the Marketplace's own index.

Validation is sold on the Marketplace one format at a time. Telephone Validation is USD 70.00 on Magento Open Source, Swissup's Vat Number Validation 99.00 on every edition, Product Zipcode Validation 129.00. Each hard-codes the format it names, and each is the right purchase for that format. The general case belongs to the form builders, expressed as a format picker plus a regular expression: Amasty Custom Forms, at 249.00 the first year and 155.00 a year after, offers field validation "which don't correspond to the selected validation format", and its release notes record fixes to validation when regular expressions are used.

So the category solves this with the two mechanisms this extension replaces, and only inside a form builder. The AI cluster, meanwhile, is 24 listings that all generate: descriptions, metadata, alt text, checkout messages, review summaries, chatbots, an agentic-commerce feed. Not one reads what a shopper typed.

Where a competitor is the better buy, it is worth naming. For EU VAT numbers, buy Swissup's extension – at the same USD 99.00 it checks the number against VIES, a registry, and can zero the tax when it is valid. A model tells a well-formed number from a malformed one; it cannot tell you the company exists. If what you need is a form, buy a form builder. This extension builds none; it validates options a product already has.

What the measurement did not find elsewhere in the category:

A rule written as a sentence, rather than picked from a list of formats or typed as a pattern. A verdict that explains itself – a reason a shopper can act on, and a correction where one exists. Cost control as a feature of the validator – a per-input verdict cache, per-session and per-IP limits, a per-module daily cap – where the AI listings surveyed expose a per-request token limit at most. Prompt-injection hardening both ways: rule and value are fenced apart when the prompt is built, and a correction echoing injection-style imperatives is discarded while the verdict is kept. And a declared answer for the day the provider is down: accept with warning, reject, or use the last cached verdict – configuration, not a surprise during an outage.

One difference is structural: the keys, the model choice and the call log live in the WebRamos LLM Provider gateway, published free of charge and holding your own key. The nearest equivalent on the Marketplace, Plumrocket's AI Connector, is a subscription – USD 99.00 the first year, 49.00 a year after – and carries no feature of its own.

What it does not try to be

It is not a form builder, not a registry integration, and not a generator: it never writes copy for the store. It validates catalog custom options of type Field and Area and nothing else today – checkout fields are not covered – and it has no console command and no cron job. It is also plain about the data: the value in a validated field is sent to the LLM provider whose key you configured. The rest of the absences are in the FAQ on the extension's page.