null Skip to main content

3145 Glamour S - 12 Mil Satin

Item#Item NameRegular PriceSale PriceQty
3145 Glamour S - 12 Mil Satin

3145 Glamour™ S is a 12.8 mil, semi-rigid photo board that delivers premium photo quality on solvent inkjet printers. Glamour™ S expands the capabilities of solvent printers; truly bridging the gap between UV flatbed and solvent roll-to-roll printing. With an instant dry, photo coating, Glamour™ provides outstanding image quality and dot gain control on a board that is stiff enough to stand or hang, yet flexible enough to roll. Glamour™ is perfect for applications ranging from high end photo finishing to hanging signs, easel signs and point of sale displays.


Applications:

  • Posters & Signage
  • Photo Prints
  • Retail Signage
  • Promotional Materials
  • Certificates & Awards
  • Table Tents

Features & Benefits:

  • Flexible, Semi-Rigid Board
  • Premium Satin Finish
  • High Density and Color Gamut
  • Instant Dry/Water Resistant Coating

Properties:

Caliper/Thickness: 13 mil
Basis Weight (gsm): 280
Finish: Satin
Opacity: 98
Whiteness: 135
Blockout: No

Free Local Delivery
Next Day Delivery
Order By 5PM CST
Save 2% On Pickup
Low Rate Financing
Flat Rate Shipping
Join Our Mailing List

Sign up to receive updates, special offers, and discounts!

// Uses React's native (unpatched) value setter + a real dispatched event, // so the app's own onChange / validation / append logic fires correctly. // build the visible field the user will actually type into // copy the real field's classes + computed styles so it looks identical // preload with existing value (formatted) if the real field already has one // hide the real field visually but keep it in the DOM and functional, // so your app's own validation / append event still works as before // place the visible field right where the real one used to be // send only the plain digits to the real field — this matches what // the numeric field type expects, so no "invalid phone number" error // keep focus/blur events flowing to the real field too, in case your // app's validation triggers specifically on those