Website Checkout Customizer — Custom Checkout Fields
by OAKLAND - odooERP.ae https://odooerp.ae$ 34.28
Key Features
Add your own questions to the eCommerce checkout â no code â validate the required ones and store every answer on the order
Five field types
Add single-line text, multiline text, dropdown, date picker and checkbox fields to the checkout â no code.
Required or optional
Mark any field required; the customer is sent back with a clear red warning if a required field is empty.
Show to the right people
Display each field to everyone, only to logged-in customers, or only to guests.
Multi-website
A field can apply to all websites or just one â perfect for multi-store setups.
Drag-and-drop ordering
Arrange fields in any order with a handle so the checkout reads exactly how you want.
Placeholder & help text
Guide customers with hint text inside the input and helpful text below it.
Answers on the order
Every answer is saved on the sale order under a Checkout Information tab your team can see.
Instant saving
Answers save as the customer types, so nothing is lost when they move between checkout steps.
Enable / disable anytime
Switch a field off without deleting it or its saved answers â turn seasonal questions on and off at will.
Checkout Fields
Field Config
Field Form
Required Warning
Sale Order Info
User guide
Create your own checkout questions from a simple backend screen â text, dropdown, date or checkbox â and every answer is saved on the sale order.
1. Create a field
- Open Website → Configuration → Checkout Fields and click New.
- Choose a type (text, multiline, dropdown, date or checkbox), a label, and placeholder/help text.
- Mark it required if needed and set who sees it and on which website.
2. See it on checkout
- The field appears in an Additional Information box on the checkout page instantly.
- Required fields block payment with a clear warning until they're filled.
3. Read the answers
- Open the resulting sale order and check the Checkout Information tab.
- Every question and the customer's answer are stored there for your team.
Frequently Asked Questions
1. Do I need a developer to add fields?
2. What field types are supported?
3. Can I make a field mandatory?
4. Where do the answers go?
5. Can I show a field only to guests or only to logged-in customers?
6. Does it work with multiple websites?
7. Will answers be lost between checkout steps?
Module Support & SLA
Standard response time (SLA) for support queries is typically 1 to 2 working days.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
eCommerce (website_sale)
• Website (website) • Discuss (mail) • Invoicing (account) |
| Lines of code | 410 |
| Technical Name |
oe_website_checkout_customizer |
| License | OPL-1 |
| Website | https://odooerp.ae |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module