Carebeau Body Massage Oil is formulated with natural extracts to deeply moisturize and nourish your skin. Ideal for dry and damaged skin, this massage oil provides a relaxing and soothing experience without leaving a greasy residue. Available in various scents, it caters to different preferences for a personalized touch.
Our body massage oil is made from Mineral Oil which acts as an occlusive agent that helps retain moisture by forming a protective barrier on the skin. This barrier prevents dryness and reduces water evaporation from the outermost layer of the skin, leaving it smooth and soft. By filling in the gaps between skin cells, it smooths out rough patches. Additionally, Mineral Oil has cleansing properties due to its ability to lower surface tension, making it effective at removing dirt, dust, and various impurities. Below are the promising benefits you must love:
● Deep Moisturization: Helps to lock in moisture, keeping your skin soft and hydrated throughout the day.
● Skin Protection: Protects against aging and damaged skin, promoting a youthful and healthy appearance.
● Variety of Scents: Choose from a range of scents including coconut, jasmine, lavender, peppermint, and more, each offering unique aromatic benefits.
● Versatile Use: Suitable for relaxing massages, skin treatments, and everyday hydration.
● No Rinse Required: Convenient to use without the need to rinse off with water.
Massage Oil 450 ml:
● Carebeau Body Massage Oil (450 ml) - No scent
● Carebeau Body Massage Oil (450 ml) - Citronella
● Carebeau Body Massage Oil (450 ml) - Rachawadee
● Carebeau Body Massage Oil (450 ml) - Peppermint
● Carebeau Body Massage Oil (450 ml) - Rice Milk
● Carebeau Body Massage Oil (450 ml) - Lavender
● Carebeau Body Massage Oil (450 ml) - Spa Refreshing
● Carebeau Body Massage Oil (450 ml) - Rosemary
● Carebeau Body Massage Oil (450 ml) - Rose
● Carebeau Body Massage Oil (450 ml) - Moke Flower
● Carebeau Body Massage Oil (450 ml) - Leelawadee
● Carebeau Body Massage Oil (450 ml) - Jasmine
● Carebeau Body Massage Oil (450 ml) - Coconut
Massage Oil 1,000ml:
● Carebeau Body Massage Oil (1,000 ml) - No scent
● Carebeau Body Massage Oil (1,000 ml) - Citronella
● Carebeau Body Massage Oil (1,000 ml) - Rachawadee
● Carebeau Body Massage Oil (1,000 ml) - Rice Milk
● Carebeau Body Massage Oil (1,000 ml) - Lavender
● Carebeau Body Massage Oil (1,000 ml) - Spa Refreshing
● Carebeau Body Massage Oil (1,000 ml) - Rosemary
● Carebeau Body Massage Oil (1,000 ml) - Moke Flower
● Carebeau Body Massage Oil (1,000 ml) - Peppermint
● Carebeau Body Massage Oil (1,000 ml) - Rose
● Carebeau Body Massage Oil (1,000 ml) - Leelawadee
● Carebeau Body Massage Oil (1,000 ml) - Jasmine
● Carebeau Body Massage Oil (1,000 ml) - Coconut
Massage Oil 3,000ml:
● Carebeau Body Massage Oil (3,000 ml) - No scent
● Carebeau Body Massage Oil (3,000 ml) - Citronella
● Carebeau Body Massage Oil (3,000 ml) - Rachawadee
● Carebeau Body Massage Oil (3,000 ml) - Peppermint
● Carebeau Body Massage Oil (3,000 ml) - Rice Milk
● Carebeau Body Massage Oil (3,000 ml) - Lavender
● Carebeau Body Massage Oil (3,000 ml) - Spa Refreshing
● Carebeau Body Massage Oil (3,000 ml) - Rosemary
● Carebeau Body Massage Oil (3,000 ml) - Rose
● Carebeau Body Massage Oil (3,000 ml) - Moke Flower
● Carebeau Body Massage Oil (3,000 ml) - Jasmine
● Carebeau Body Massage Oil (3,000 ml) - Coconut
● Carebeau Body Massage Oil (3,000 ml) - Leelawadee
Massage Butter 450 ml and 3,000 ml:
● Carebeau Milky Massage Butter (450 ml) - Coconut
● Carebeau Milky Massage Butter (3,000 ml) - Moke Flower
After cleansing your skin, apply a generous amount of Carebeau Body Massage Oil and massage gently all over your body. It can be used for both relaxation and skin treatment purposes. There is no need to rinse off with water after application.
● Massage Oil 450 ml: 5.86 kg
● Massage Oil 1000 ml: 12.5 kg
● Massage Oil 450 ml: 16.74 kg
● Massage Butter 450 ml: 5.21 kg
● Massage Oil 450 ml: 21 x 27.5 x 20 cm
● Massage Oil 1,000 ml: 25 x 33 x 26.8 cm
● Massage Oil, Massage Butter 3,000 ml: 30 x 43 x 33 cm
● Massage Butter 450 ml: 20.9 x 27.1 x 21.5 cm
-
Massage Buter:
● Coconut: 10-1-5981675
● Moke Flower: 10-1-5905299
Massage Oil:
● Coconut: 10-1-5863566
● Jasmine: 10-1-5863566
● Moke Flower: 10-1-5863566
● Rachavadee: 13-1-6600002607
● Leelawadee: 13-1-6600002607
● Spa Refreshing: 13-1-6600002607
● Rose: 10-1-5863566
● Citronella: 10-1-5863566
● Lavender: 13-1-6600002607
● Peppermint: 10-1-5863566
● Rice Milk: 10-1-5863566
● Rosemary: 10-1-5863566
● No Scent: 10-1-5863566
Massage Butter:
● Coconut 450 ml: 8851427010941
● Moke Flower 450 ml: 8851427005589
● Moke Flower 3,000 ml: 8851427008696
Massage Oil:
● Coconut
● Jasmine
● Moke Flower
● Rachavadee
● Leelawadee
● Spa Refreshing
● Rose
● Citronella
● Lavender
● Peppermint
● Rice Milk
● Rosemary
● No Scent
Here is some great advice and guidance provided by Felippe Regazio. In an article on dev.to, he provided some great guidance and I would recommend reading through the entire post there. I'm also referencing a wonderful article from Rachele DiTullio to make sure it's accessibility friendly. WCAG recommends using honeypots for your forms to deflect bots and keep things accessible.
I was still seeing submissions with this approach, so I modified this and added a tabindex="-1" to the honeypot input to keep screenreaders from focusing it.
Add in some inputs and make sure they have realistic names that a bot wouldn't be fooled by. Wrap them in a div and add a class. I did this and my class is business. Then I set the CSS in Webflow to the following:
Make sure your hidden input is also set to display:none so that users can't tab over to index it. Or, if you want to leave it with display: block, then you can try adding a custom attribute of tabindex="-1".
Also, make sure the label on for the hidden input has a custom attribute of aria-hidden="true". This will prevent screen readers from reading that label.
Now your form is set so that sighted users and users who rely on assistive technology will never know that hidden input exists.
Now you need to use JavaScript to prevent the form from submitting if the honeypot filled is submitted. What I did, was added an event on input that disables the submit button. Feel free to improve this or try other methods.
A lot of the time, folks check to see if it's spam on the backend if that field exists and has been filled out. But, that still allows submissions to go through so set this up in a way that works best for you. Here's my JS I'm using:
Credit: Henry Lee, Webflow Technical Support
Webflow has a feature called Logic Flows, that allows us to respond to incoming form data in customised ways.
We can use it to stop spam from submissions reaching our email inbox, if we combine it with our honeypot field.
Here’s an overview of how to use Logic Flows.If we use a Conditional Block, we can set our Flow to only send us an Email when the honeypot field is blank:
In this example, I’ve set the Conditional Rule so that if my Honeypot Field submitted value = [blank], then send me an Email Notification.
If the form is submitted with the Honeypot field not blank, meaning a spambot filled it out, then the Logic Flow just terminates right there, and the spam data never reaches our inbox.
This is a useful way to filter submissions automatically, and will work even when the spambot isn’t running javascript.
Here is some great advice and guidance provided by Felippe Regazio. In an article on dev.to, he provided some great guidance and I would recommend reading through the entire post there. I'm also referencing a wonderful article from Rachele DiTullio to make sure it's accessibility friendly. WCAG recommends using honeypots for your forms to deflect bots and keep things accessible.
I was still seeing submissions with this approach, so I modified this and added a tabindex="-1" to the honeypot input to keep screenreaders from focusing it.
Add in some inputs and make sure they have realistic names that a bot wouldn't be fooled by. Wrap them in a div and add a class. I did this and my class is business. Then I set the CSS in Webflow to the following:
Make sure your hidden input is also set to display:none so that users can't tab over to index it. Or, if you want to leave it with display: block, then you can try adding a custom attribute of tabindex="-1".
Also, make sure the label on for the hidden input has a custom attribute of aria-hidden="true". This will prevent screen readers from reading that label.
Now your form is set so that sighted users and users who rely on assistive technology will never know that hidden input exists.
Now you need to use JavaScript to prevent the form from submitting if the honeypot filled is submitted. What I did, was added an event on input that disables the submit button. Feel free to improve this or try other methods.
A lot of the time, folks check to see if it's spam on the backend if that field exists and has been filled out. But, that still allows submissions to go through so set this up in a way that works best for you. Here's my JS I'm using:
Credit: Henry Lee, Webflow Technical Support
Webflow has a feature called Logic Flows, that allows us to respond to incoming form data in customised ways.
We can use it to stop spam from submissions reaching our email inbox, if we combine it with our honeypot field.
Here’s an overview of how to use Logic Flows.If we use a Conditional Block, we can set our Flow to only send us an Email when the honeypot field is blank:
In this example, I’ve set the Conditional Rule so that if my Honeypot Field submitted value = [blank], then send me an Email Notification.
If the form is submitted with the Honeypot field not blank, meaning a spambot filled it out, then the Logic Flow just terminates right there, and the spam data never reaches our inbox.
This is a useful way to filter submissions automatically, and will work even when the spambot isn’t running javascript.
Here is some great advice and guidance provided by Felippe Regazio. In an article on dev.to, he provided some great guidance and I would recommend reading through the entire post there. I'm also referencing a wonderful article from Rachele DiTullio to make sure it's accessibility friendly. WCAG recommends using honeypots for your forms to deflect bots and keep things accessible.
I was still seeing submissions with this approach, so I modified this and added a tabindex="-1" to the honeypot input to keep screenreaders from focusing it.
Add in some inputs and make sure they have realistic names that a bot wouldn't be fooled by. Wrap them in a div and add a class. I did this and my class is business. Then I set the CSS in Webflow to the following:
Make sure your hidden input is also set to display:none so that users can't tab over to index it. Or, if you want to leave it with display: block, then you can try adding a custom attribute of tabindex="-1".
Also, make sure the label on for the hidden input has a custom attribute of aria-hidden="true". This will prevent screen readers from reading that label.
Now your form is set so that sighted users and users who rely on assistive technology will never know that hidden input exists.
Now you need to use JavaScript to prevent the form from submitting if the honeypot filled is submitted. What I did, was added an event on input that disables the submit button. Feel free to improve this or try other methods.
A lot of the time, folks check to see if it's spam on the backend if that field exists and has been filled out. But, that still allows submissions to go through so set this up in a way that works best for you. Here's my JS I'm using:
Credit: Henry Lee, Webflow Technical Support
Webflow has a feature called Logic Flows, that allows us to respond to incoming form data in customised ways.
We can use it to stop spam from submissions reaching our email inbox, if we combine it with our honeypot field.
Here’s an overview of how to use Logic Flows.If we use a Conditional Block, we can set our Flow to only send us an Email when the honeypot field is blank:
In this example, I’ve set the Conditional Rule so that if my Honeypot Field submitted value = [blank], then send me an Email Notification.
If the form is submitted with the Honeypot field not blank, meaning a spambot filled it out, then the Logic Flow just terminates right there, and the spam data never reaches our inbox.
This is a useful way to filter submissions automatically, and will work even when the spambot isn’t running javascript.
Here is some great advice and guidance provided by Felippe Regazio. In an article on dev.to, he provided some great guidance and I would recommend reading through the entire post there. I'm also referencing a wonderful article from Rachele DiTullio to make sure it's accessibility friendly. WCAG recommends using honeypots for your forms to deflect bots and keep things accessible.
I was still seeing submissions with this approach, so I modified this and added a tabindex="-1" to the honeypot input to keep screenreaders from focusing it.
Add in some inputs and make sure they have realistic names that a bot wouldn't be fooled by. Wrap them in a div and add a class. I did this and my class is business. Then I set the CSS in Webflow to the following:
Make sure your hidden input is also set to display:none so that users can't tab over to index it. Or, if you want to leave it with display: block, then you can try adding a custom attribute of tabindex="-1".
Also, make sure the label on for the hidden input has a custom attribute of aria-hidden="true". This will prevent screen readers from reading that label.
Now your form is set so that sighted users and users who rely on assistive technology will never know that hidden input exists.
Now you need to use JavaScript to prevent the form from submitting if the honeypot filled is submitted. What I did, was added an event on input that disables the submit button. Feel free to improve this or try other methods.
A lot of the time, folks check to see if it's spam on the backend if that field exists and has been filled out. But, that still allows submissions to go through so set this up in a way that works best for you. Here's my JS I'm using:
Credit: Henry Lee, Webflow Technical Support
Webflow has a feature called Logic Flows, that allows us to respond to incoming form data in customised ways.
We can use it to stop spam from submissions reaching our email inbox, if we combine it with our honeypot field.
Here’s an overview of how to use Logic Flows.If we use a Conditional Block, we can set our Flow to only send us an Email when the honeypot field is blank:
In this example, I’ve set the Conditional Rule so that if my Honeypot Field submitted value = [blank], then send me an Email Notification.
If the form is submitted with the Honeypot field not blank, meaning a spambot filled it out, then the Logic Flow just terminates right there, and the spam data never reaches our inbox.
This is a useful way to filter submissions automatically, and will work even when the spambot isn’t running javascript.
Here is some great advice and guidance provided by Felippe Regazio. In an article on dev.to, he provided some great guidance and I would recommend reading through the entire post there. I'm also referencing a wonderful article from Rachele DiTullio to make sure it's accessibility friendly. WCAG recommends using honeypots for your forms to deflect bots and keep things accessible.
I was still seeing submissions with this approach, so I modified this and added a tabindex="-1" to the honeypot input to keep screenreaders from focusing it.
Add in some inputs and make sure they have realistic names that a bot wouldn't be fooled by. Wrap them in a div and add a class. I did this and my class is business. Then I set the CSS in Webflow to the following:
Make sure your hidden input is also set to display:none so that users can't tab over to index it. Or, if you want to leave it with display: block, then you can try adding a custom attribute of tabindex="-1".
Also, make sure the label on for the hidden input has a custom attribute of aria-hidden="true". This will prevent screen readers from reading that label.
Now your form is set so that sighted users and users who rely on assistive technology will never know that hidden input exists.
Now you need to use JavaScript to prevent the form from submitting if the honeypot filled is submitted. What I did, was added an event on input that disables the submit button. Feel free to improve this or try other methods.
A lot of the time, folks check to see if it's spam on the backend if that field exists and has been filled out. But, that still allows submissions to go through so set this up in a way that works best for you. Here's my JS I'm using:
Credit: Henry Lee, Webflow Technical Support
Webflow has a feature called Logic Flows, that allows us to respond to incoming form data in customised ways.
We can use it to stop spam from submissions reaching our email inbox, if we combine it with our honeypot field.
Here’s an overview of how to use Logic Flows.If we use a Conditional Block, we can set our Flow to only send us an Email when the honeypot field is blank:
In this example, I’ve set the Conditional Rule so that if my Honeypot Field submitted value = [blank], then send me an Email Notification.
If the form is submitted with the Honeypot field not blank, meaning a spambot filled it out, then the Logic Flow just terminates right there, and the spam data never reaches our inbox.
This is a useful way to filter submissions automatically, and will work even when the spambot isn’t running javascript.
export@carebeau-enjoy.com
info@carebeau-enjoy.com
.webp)
.webp)
