Watch Straps

In 2011, Casa Fagliano has come together with Jaeger leCoultre in a unique collaboration on the Reverso.

Jaeger LeCoultre originally created the Reverso in 1931 for the british polo players of the Army of India. The watch casing is able to pivot 180 degrees on itself in order to protect the dial from the hits that come with the sport, a potential risks that comes with riding horses at high-speed whilst swinging mallets. The watch was re-introduced in 2011 for its 80th anniversary with a special partnership with the world renowned polo boots craftsman, Casa Fagliano.

Casa Fagliano hand-crafts the reverse’s watch strap with the same cordovan leather that is used to make the signature polo boots. It takes the family 24 hours to make a single strap from scratch.

If you wish to order a cordovan watch strap for your Reverso, please contact us through our form with the reference number of your watch. Special sizes and customisations are available

Our watch straps are made from a selection of the finest pieces of cordovan leather. Each strap is made to order, in a range of combination, allowing you to chose the colour of your leather and stitching. Special customisation are possible.

The Reverso 2018 Boutique Edition, was launched as a limited edition, and 100 watch straps were manufactured using a two-tone brown cordovan watch strap by Casa Fagliano. The strap was entirely handmade in our Hurlingham atelier. Today the watch strap is only available as a replacement or special modification for clients whom already own it.

The 2019 Edition of the Fagliano Reverso was also produced as a limited edition, with only 100 pieces created. The design was created in a two-tone blue cordovan strap by Casa Fagliano. The watch strap was entirely handmade in our Hurlingham atelier. Today the watch strap is only available as a replacement or special modification for clients whom already own it.

Contact and inquiries about our products

Experience and Love

Devoted to the pursuit of excelence since 1892

Name	Provider	Purpose	Expiration
wordpress_lp_guest	Wordpress	Cookie de sesión para detectar fallos, permite ver el número de visitas, las secciones más visitada	Sesión
ct_checkjs	CleanTalk	Utilizado por nuestro sistema anti-spam para verificar si JavaScript está disponible en el navegador	Sesión
ct_fkp_timestamp	CleanTalk	Utilizado por nuestro sistema anti-spam para almacenar el tiempo de visita.	Sesión
ct_pointer_data	CleanTalk	Almacenar variables dinámicas desde el navegador.	Sesión
ct_ps_timestamp	CleanTalk	Almacenar la hora de la visita.	Sesión
ct_sfw_pass_key	CleanTalk	Proporcionar protección contra spam.	30 días
ct_timezone	CleanTalk	Almacenar la hora de la visita.	Sesión
tk_ai	Automattic	Guardar un ID de usuario único	Sesión
moove_gdpr_popup	GDPR Cookie Compliance	Esta cookie guarda la opción de guardar o no cookies en el navegador del usuario	Sesión
wordpress_test_cookie	Wordpress	Esta cookie se usa para que el gestor de contenidos WordPress compruebe si el navegador tiene las cookies activadas	Sesión
comment_author, comment_author_ email, comment_author_ url	Wordpress	Cookies de WordPress que el CMS utiliza para que los usuarios que realizan más de un comentario no tengan que reintroducir otra vez toda su información	6 meses
wordpress_logged_in_*	Wordpress	Después del iniciar sesión, WordPress activa la cookie wordpress_logged_in_, cuya función es indicar cuando se ha conectado y quién es, siendo utilizado por la interfaz de WordPress	Sesión
wordpress_sec_*	Wordpress	Estas cookies son utilizadas por WordPress para mantener la sesión del Usuario	Sesión
itsec-hb-login-*	iThemes Security	Gestionar la url de panel WP	10 minutos
woocommerce_cart_hash	Woocommerce	Cookie que almacena información sobre el carrito de la compra del cliente y sus artículos	Sesión
woocommerce_items_in_cart	Woocommerce	Cookie que almacena información sobre el carrito de la compra del cliente y sus artículos	Sesión
Wp-settings-*	Wordpress	Se usa para mantener la configuración del usuario en wp-admin	1 año
wp-settings-time-*	Wordpress	Hora en la que se estableció wp-settings-*	1 año
wp_woocommerce_session_*	Woocommerce	Esta cookie contiene un código único para cada cliente para que sepa dónde encontrar los datos de compra en la base de datos para cada cliente	1 día
apbct_timestamp	Cleantalk		sesión
apbct_antibot	Cleantalk	Para comprobar si se pueden colocar cookies.	Sesión
apbct_page_hits	Cleantalk		Sesión
apbct_prev_referer	Cleantalk	Para almacenar los IDs de referencia.	Sesión
apbct_site_landing_ts	Cleantalk		Sesión
apbct_visible_fields	Cleantalk		Sesión
fagliano_newslettersnp_snppopup-exit	Popup	Control de popup newsletter	Sesión
wp-wpml_current_language	WPML	Almacenar configuración idioma	1 día
quform_session_*	quform	Garantiza el correcto funcionamiento de los formularios de este sitio web	Sesión

Name	Provider	Purpose	Expiration
_ga	Google Analytics	Esta cookie es instalada por Google Analytics. La cookie se utiliza para calcular los datos de visitantes, sesiones, campañas y realizar un seguimiento del uso del sitio para el informe de análisis del sitio. Las cookies almacenan información de forma anónima y asignan un número generado aleatorio para identificar visitantes únicos.	1 año
_gat	Google Analytics	Forma parte de Google Analytics. Se usa para limitar el porcentaje de solicitudes.	1 año
_gid	Google Analytics	Forma parte de Google Analytics. Se usa para distinguir a los usuarios.	24 horas
_hjClosedSurveyInvites	Hotjar	Hotjar cookie that is set once a user interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown.	365 days
_hjDonePolls	Hotjar	Hotjar cookie that is set once a user completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in.	365 days
_hjMinimizedPolls	Hotjar	Hotjar cookie that is set once a user minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the user navigates through your site.	365 days
_hjShownFeedbackMessage	Hotjar	Hotjar cookie that is set when a user minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the user navigates to another page where it is set to show.	365 days
_hjSessionTooLarge	Hotjar	Causes Hotjar to stop collecting data if a session becomes too large. This is determined automatically by a signal from the WebSocket server if the session size exceeds the limit.	Session
_hjSessionRejected	Hotjar	If present, this cookie will be set to '1' for the duration of a user's session, if Hotjar rejected the session from connecting to our WebSocket due to server overload. This cookie is only applied in extremely rare situations to prevent severe performance issues.	Session
_hjSessionResumed	Hotjar	Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.	365 days
_hjRecordingLastActivity	Hotjar	This should be found in Session storage (as opposed to cookies). This gets updated when a user recording starts and when data is sent through the WebSocket (the user performs an action that Hotjar records).	Session
_hjTLDTest	Hotjar	When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.	Session
_hjUserAttributesHash	Hotjar	User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated.	Session
_hjCachedUserAttributes	Hotjar	This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. Collected attributes will only be saved to Hotjar servers if the user interacts with a Hotjar Feedback tool, but the cookie will be used regardless of whether a Feedback tool is present.	Session
_hjLocalStorageTest	Hotjar	This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created.	Under 100ms
_hjIncludedInPageviewSample	Hotjar	This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit.	30 minutes
_hjIncludedInSessionSample	Hotjar	This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's daily session limit.	30 minutes
_hjAbsoluteSessionInProgress	Hotjar	This is set to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.	Session
_hjViewportId	Hotjar	This stores information about the user viewport such as size and dimensions.	Session
_hjRecordingEnabled	Hotjar	This is added when a Recording starts and is read when the recording module is initialized to see if the user is already in a recording in a particular session.	Session

Name	Provider	Purpose	Expiration
_fbp	Facebook	Cookie de Facebook utilizadas para recoger estadísticas sobre las visitas al sitio y el rendimiento de las campañas publicitarias	3 meses
mailchimp_landing_site	Mailchimp	Almacena qué página fue visitada primero	1 mes

Stores & Distributors

Where to Buy

Watch Straps

Contact and inquiries about our products

Experience and Love

POLO

MEN'S SHOES

WOMEN'S SHOES

WHERE TO BUY