Body Care Menu Icon
ดูแลผิวกาย
Hair Care Menu Icon
ดูแลเส้นผม
Hair Style Menu Icon
จัดแต่งผม
Facial Care Menu Icon
ดูแลผิวหน้า
Oral Care Menu Icon
ดูแลช่องปาก
สุขภาพและสปา
สุขภาพและสปา

สกินแคร์: แคร์บิว ครีมขัดหน้า

แคร์บิว
ครีมสครับหน้า

แนะนำสินค้า สกินแคร์: แคร์บิว ครีมขัดหน้า

แคร์บิว ครีมขัดหน้า

เป็นทั้งสครับและมาส์กในหนึ่งเดียว อุดมด้วยส่วนผสมจากธรรมชาติ เช่น วิตามินอี มะขาม ขมิ้น และทานาคา ช่วยขจัดเซลล์ผิวที่ตายแล้วและความหมองคล้ำ ทำให้ผิวหน้าดูเนียนนุ่มและสดใส

คุณสมบัติของสินค้า สกินแคร์: แคร์บิว ครีมขัดหน้า

ส่วนผสมจากธรรมชาติ: ผลิตจากมะขาม ขมิ้น นมผง และทานาคา 100% ช่วยในการสครับผิวอย่างอ่อนโยน เหมาะสำหรับทุกสภาพผิว  

การทำความสะอาดล้ำลึก: ทำความสะอาดผิวอย่างล้ำลึก ขจัดสิ่งสกปรกและความมันส่วนเกินที่สะสมในรูขุมขน  

ขจัดเซลล์ผิวที่ตายแล้ว: ช่วยขจัดเซลล์ผิวที่ตายแล้ว เผยผิวที่เรียบเนียนและกระจ่างใสทุกครั้งที่ใช้  

ฟื้นฟูผิวที่หมองคล้ำ: มะขามและขมิ้นทำงานร่วมกันเพื่อช่วยให้ผิวกระจ่างใสขึ้น และทานาคามีคุณสมบัติในการปลอบประโลมผิว  

สครับและมาส์กในหนึ่งเดียว: ใช้ได้ทั้งเป็นสครับและมาส์กบำรุงผิว ให้ประโยชน์สองต่อในการใช้เพียงครั้งเดียว  

เพิ่มความชุ่มชื้น: สูตรผสมวิตามินอีและนมผงที่ช่วยให้ผิวนุ่มและชุ่มชื้น  

สูตรสินค้า

แคร์บิว ครีมขัดหน้า

วิธีการใช้

ทาครีมสครับในปริมาณที่พอเหมาะลงบนใบหน้าที่เปียกน้ำ  

นวดเบา ๆ เป็นวงกลม โดยเน้นบริเวณที่มีเซลล์ผิวที่ตายแล้ว  

 หากใช้เป็นมาส์ก ทิ้งไว้ประมาณ 5–10 นาที  

 ล้างออกด้วยน้ำสะอาด  

 ใช้ 2-3 ครั้งต่อสัปดาห์เพื่อผลลัพธ์ที่ดีที่สุด 

ข้อมูลบรรจุภัณฑ์
◉ อายุการเก็บรักษา:
3
ปี
◉ จำนวนสินค้าต่อลัง:
12
ชิ้น
◉ น้ำหนักสุทธิ (สินค้า):
500g
◉ น้ำหนักรวม (ลัง):

6.6 kg

◉ ขนาดลังสินค้า (กว้าง x ยาว x สูง):

30 x 40 x 12.3 cm

◉ อุปกรณ์ภายในกล่อง:
ข้อมูลจำเพาะ
◉ เลขที่จดแจ้ง (อย.):
◉ เลขที่บาร์โค้ด:
◉ ผลิตโดย:
บริษัท เอสบี อินเตอร์แลบ จำกัด
◉ ประเทศต้นกำเนิด:
ประเทศไทย
บอกเล่าประสบการณ์ดีๆ เกี่ยวกับสินค้านี้ให้เราฟังหน่อย
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Learn how to use a honeypot in Webflow

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.

Styling your hidden elements

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.

Using JavaScript to prevent submission

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:

Filtering out spam form submissions with Webflow Logic + Honeypot

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:

Screenshot of Webflow Logic taking no action when the honeypot field is completed

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.

Learn how to use a honeypot in Webflow

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.

Styling your hidden elements

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.

Using JavaScript to prevent submission

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:

Filtering out spam form submissions with Webflow Logic + Honeypot

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:

Screenshot of Webflow Logic taking no action when the honeypot field is completed

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.

Learn how to use a honeypot in Webflow

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.

Styling your hidden elements

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.

Using JavaScript to prevent submission

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:

Filtering out spam form submissions with Webflow Logic + Honeypot

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:

Screenshot of Webflow Logic taking no action when the honeypot field is completed

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.

Learn how to use a honeypot in Webflow

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.

Styling your hidden elements

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.

Using JavaScript to prevent submission

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:

Filtering out spam form submissions with Webflow Logic + Honeypot

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:

Screenshot of Webflow Logic taking no action when the honeypot field is completed

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.

Learn how to use a honeypot in Webflow

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.

Styling your hidden elements

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.

Using JavaScript to prevent submission

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:

Filtering out spam form submissions with Webflow Logic + Honeypot

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:

Screenshot of Webflow Logic taking no action when the honeypot field is completed

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.

สินค้าที่อยู่ในหมวดเดียวกันกับ
สกินแคร์: แคร์บิว ครีมขัดหน้า