null Skip to main content

MPI 1105 Supercast LTR SF - 2 Mil Cast Gloss

Item#Item NameRegular PriceSale PriceQty

Avery Dennison MPI1105 SuperCast Series Vinyl is a premium gloss opaque vinyl designed for use in fleet marking and vehicle wrap as well as corporate identity applications. MPI1105 provides superior conformability to irregular surfaces. 

Face: 2.0 mil (51 microns) high gloss cast film

Adhesive: Long Term Removable Acrylic (clear with gray opacifying layer)

Liner: 90# StaFlat™ (Smooth)

Application Surfaces: Flat, Flat with Rivets, Corrugations, Complex Curves (vehicle wraps)

Features:

  • Superior conformability to irregular substrates
  • High gloss finish
  • Outstanding durability and outdoor performance
  • Dimensionally stable liner for easy converting
  • Excellent dimensional stability
  • Long term removable provides permanent adhesion, but removes cleanly
  • ICC profiles available on the Avery Dennison’s website (http://avery-us.color-base.com)
  • Meets the requirements of IMO FTP Code Part 2 & 5 for all material categories

Conversion:

  • Latex Inkjet
  • Solvent Based Inkjet
  • Mild/Eco Solvent Inkjet
  • UV Inkjet*
  • Screen Print**

* For flat surfaces only, except for qualified flexible UV inks

**Approved for use with Nazdar 3500 Series Ink and Nazdar 3529 or 3539 Clear

Common Applications:

  • Vehicle
  • Fleet
  • POP/Trade Show
  • Outdoor Signage
  • Marine / Watercraft
// 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