The Regex Field in the Price Calculator requires an Item Number (SKU) to be identified to discount a product. A product SKU is a customer derived number and can sometimes be a very long identifying number. Some Item Numbers in my inventory are 15 to 25 characters long. This severely limits the number of products that can be entered into the Regex field. Wildcards can not be used if you are targeting specific products to discount and are not discounting every product that begins with a (T5D-*) which would encompass all products that begin with that part number, but save a lot of characters in the Regex field for entry. The only way to overcome this currently is to build multiple (Identical) Price Calculators and enter the products that do not fit into the fields in the first Price Calculator, in the Second one. This is cumbersome and very hard to maintain, especially if you have a line of products that are 1000 and you want to discount 100 of them but not the remaining 900. Targeting 100 of 1000 products would be a nightmare scenario and would require a website owner to make so many identical Price Calculators that it would be very hard to maintain them much less find a product to remove or edit. By increasing the Regex field from the current limit of 100 characters to the database maximum, we could at least alleviate some of the hardship of this limitation as long as we are stuck using the Item Number (SKU). Another Solution would be to allow the Cart.com Product ID (PID) to be used in this field to identify the product which is usually 4 or 5 characters long. The Database can Identify the product using either of these identifiers in the search bar, so why can't they be used in this field as well?