Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/virtual/vps-4ecb39/a/a080404e0a/staging/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpfront-user-role-editor domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/virtual/vps-4ecb39/a/a080404e0a/staging/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the gravityperks domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/virtual/vps-4ecb39/a/a080404e0a/staging/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the rocket domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/virtual/vps-4ecb39/a/a080404e0a/staging/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpfront-user-role-editor domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/virtual/vps-4ecb39/a/a080404e0a/staging/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/virtual/vps-4ecb39/a/a080404e0a/staging/wp-includes/functions.php on line 6170

Warning: Cannot modify header information - headers already sent by (output started at /home/virtual/vps-4ecb39/a/a080404e0a/staging/wp-includes/functions.php:6170) in /usr/share/php/wp-stack-cache.php on line 2092

Warning: Cannot modify header information - headers already sent by (output started at /home/virtual/vps-4ecb39/a/a080404e0a/staging/wp-includes/functions.php:6170) in /usr/share/php/wp-stack-cache.php on line 2093

Warning: Cannot modify header information - headers already sent by (output started at /home/virtual/vps-4ecb39/a/a080404e0a/staging/wp-includes/functions.php:6170) in /home/virtual/vps-4ecb39/a/a080404e0a/staging/wp-content/plugins/betterdocs-pro/includes/Admin/Analytics.php on line 25

Warning: Cannot modify header information - headers already sent by (output started at /home/virtual/vps-4ecb39/a/a080404e0a/staging/wp-includes/functions.php:6170) in /usr/share/php/wp-stack-cache.php on line 2092

Warning: Cannot modify header information - headers already sent by (output started at /home/virtual/vps-4ecb39/a/a080404e0a/staging/wp-includes/functions.php:6170) in /usr/share/php/wp-stack-cache.php on line 2093

Warning: Undefined array key 0 in /home/virtual/vps-4ecb39/a/a080404e0a/staging/wp-content/themes/flemingHowland/inc/theme-overrides.php on line 47

Warning: Attempt to read property "name" on null in /home/virtual/vps-4ecb39/a/a080404e0a/staging/wp-content/themes/flemingHowland/inc/theme-overrides.php on line 47
Understanding the cushion exchange program | Knowledge Base | FLEMING HOWLAND
Fleming Howland Monogram Logo
View Categories

Understanding the cushion exchange program

Overview of the Cushion Exchange Programme

The Cushion Exchange Programme reflects Fleming Howland’s commitment to enduring comfort as well as craft. For customers who find the initial feel of their sofa or chair cushions different from expectation, the programme offers an exchange of fillings to achieve the preferred level of softness or firmness.

Eligibility and Process

Once the furniture has been delivered, customers may request an exchange within the first 60 days if they wish to adjust cushion comfort. It is important to note that certain fillings require time to settle: they may feel firm when fresh from the factory but will gradually ease with regular use. For this reason, customers are encouraged to live with the furniture for several weeks before making a request. Unless Fleming Howland advises otherwise, there is no need to return the original set; replacement cushion fillings will be supplied in the selected comfort option. To begin the process, customers should provide their order number along with details of the preferred filling.

Limitations and Conditions

The programme applies only to qualifying removable cushion fillings and is limited to two filling exchanges within 60 days of delivery. It does not apply to fixed upholstery, frames, covers, decorative detailing, non-removable seats, bespoke comfort constructions or other elements of the furniture. Where an order is outside the United Kingdom, any local duties, taxes, customs charges or handling costs connected with replacement fillings may remain the customer’s responsibility unless Fleming Howland agrees otherwise in writing.

The programme is subject to our Terms and Conditions.

WordPress database error: [You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ')) AND p.post_type = 'docs' AND tt.taxonomy = 'doc_category' AND tt.term_id I...' at line 1]
SELECT p.ID FROM fh_posts AS p INNER JOIN fh_term_relationships AS tr ON p.ID = tr.object_id INNER JOIN fh_term_taxonomy AS tt ON tr.term_taxonomy_id = tt.term_taxonomy_id WHERE p.ID = '159162' AND p.ID < 168409)) AND p.post_type = 'docs' AND tt.taxonomy = 'doc_category' AND tt.term_id IN (4467) AND p.ID NOT IN ( SELECT tr.object_id FROM fh_term_relationships tr LEFT JOIN fh_term_taxonomy tt ON (tr.term_taxonomy_id = tt.term_taxonomy_id) WHERE tt.term_id IN (0) ) AND p.post_status = 'publish' ORDER BY p.post_date DESC, p.ID DESC LIMIT 1

WordPress database error: [You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ')) AND p.post_type = 'docs' AND tt.taxonomy = 'doc_category' AND tt.term_id I...' at line 1]
SELECT p.ID FROM fh_posts AS p INNER JOIN fh_term_relationships AS tr ON p.ID = tr.object_id INNER JOIN fh_term_taxonomy AS tt ON tr.term_taxonomy_id = tt.term_taxonomy_id WHERE p.ID = '168402' AND p.ID > 168409)) AND p.post_type = 'docs' AND tt.taxonomy = 'doc_category' AND tt.term_id IN (4467) AND p.ID NOT IN ( SELECT tr.object_id FROM fh_term_relationships tr LEFT JOIN fh_term_taxonomy tt ON (tr.term_taxonomy_id = tt.term_taxonomy_id) WHERE tt.term_id IN (0) ) AND p.post_status = 'publish' ORDER BY p.post_date ASC, p.ID ASC LIMIT 1