Wix Forms vs Custom Velo Forms: What Does Your Business Need?
For most enquiry forms, start with native Wix Forms. New Wix Forms already support conditional questions and multiple pages. Consider custom Velo development when the missing requirement is a business workflow, such as a bespoke estimate, a live system lookup or a member-specific process that the available form features cannot handle.
Define what must happen before, during and after submission. Field count alone does not establish the development scope.
If you are deciding what to build, book a free 30-minute consultation. Bring your current form, the questions you need to ask and an example of what your team should receive.
Choose between three approaches
There is a middle option between accepting the default form and commissioning a complete rebuild: keep Wix Forms and extend the part that needs extra logic.
Start with the smallest implementation that supports the whole workflow. Feature availability depends on your form version and plan.
Approach | Best starting point when | Work to define |
|---|---|---|
Native Wix Forms | You collect enquiries, show relevant questions and notify your team | Fields, rules, recipients and submission handling |
Wix Forms with extensions | The existing interface works, but one validation or downstream action needs more control | The missing function, API compatibility and failure handling |
Custom interface with Velo | The interaction depends on bespoke calculations, changing data or account-specific workflows | Interface, backend rules, storage, integrations and maintenance |
Wix's overview of forms and custom frontends describes native forms and manually built forms. A custom interface can use individual page inputs and buttons, with code deciding how data is processed or saved.
An agency should be able to identify the requirement that justifies moving from one approach to another. “You need conditional logic” is not a sufficient explanation on its own.
What native Wix Forms can already do
New Wix Forms can show, hide, require or make fields optional based on answers. They also support multiple pages, which can separate contact details from project questions. You can therefore build a tailored enquiry journey without assuming that every interaction needs Velo.
For example, a contractor could ask which service the visitor needs, then show a question relevant to that service. A business requesting office cleaning might need to provide cleaning frequency; a post-construction enquiry might need a completion date instead.
Some fields and limits depend on your upgrade. Check the current form-field options, especially before promising uploads or signatures. Compare the actual plan allowance with your requirements instead of assuming a feature is either universally free or unavailable.
Walkthrough: show a question for one service
This example uses new Wix Forms in Wix Studio. It is an illustrative configuration for a business offering office cleaning and post-construction cleaning.
In the Studio Editor, open Add Elements → Contact & Forms → Create New Form. If a form already exists, select it and choose Edit Form.
Add a single-choice service question with “Office cleaning” and “Post-construction cleaning” as options. Add a second field called “Preferred cleaning frequency.”
Open Rules, then + Add Rule. Wix requires at least two fields before rules can be enabled.
Under If, choose the service field and a condition matching “Office cleaning.” Under Then, choose the frequency field and set the appropriate shown/required behaviour.
Define what should happen for the other service choice. Check that an irrelevant question cannot remain required after a visitor changes their answer.
Save the rule and form, publish the changes, then test both branches on the live site. Switch between choices before submitting, rather than testing each path only from a fresh page.
The official Wix Forms rules guide explains the conditions and outcomes. For a longer journey, the Studio form builder also provides a Pages option. Dividing the questions across pages is an organisation choice, not proof that custom development is necessary.
Check extensions before replacing the form
New Wix Forms provide advanced validation through Wix Functions. Wix documents the route as Forms & Submissions → Edit the form → Settings → Advanced form validations → Create Validation.
Its custom validation instructions include checking whether two email fields match. That checks agreement between entries; it does not prove ownership of the address.
For integrations, check supported triggers, field mapping and failure behaviour before replacing the interface. For code extensions, identify the form version: old WixForms and new WixFormsV2 APIs are different.
When custom Velo forms are worth considering
Custom development becomes more useful when the form is part of a system rather than a standalone enquiry. These are requirements to assess, not claims that native forms can never support any part of them.
Requirement | What to prove before choosing a build |
|---|---|
A bespoke estimate | Where prices come from, how the calculation works and whether the output is indicative or binding |
Options drawn from changing records | Which source owns the options, how often they change and what happens when it is unavailable |
Members editing their own records | How ownership is checked and which fields each person may view or change |
An unsupported external workflow | Whether a supported integration can do the job before commissioning a custom API connection |
A specialised interaction | Why standard fields cannot express the task clearly, and how keyboard and mobile users will complete it |
Our LumaQuote custom quote software case study describes a CodeMasters build using Wix Velo, custom logic, forms and dynamic workflows. It illustrates why the workflow can become the main development project. It does not mean a basic enquiry form needs the same scope.
CodeMasters' web development services cover custom databases, quote tools, integrations and member workflows. Define the data and rules alongside the interface so that the quotation covers the functioning system.
Specify what happens after Submit
A custom form built from page inputs is not automatically equivalent to the Wix Forms app. Decide explicitly how records, contact details, notifications and follow-up will be handled. Saving a CMS item alone does not establish that your sales team received an enquiry.
Plan the saved result and later actions separately. A notification failure should be traceable without losing the original enquiry.
Define acceptance, storage and recovery
Specify required fields, allowed values and backend checks. Browser values should not determine trusted prices or permission to edit another member's record.
Choose the authoritative destination: a Wix submission, CMS record or external system. Define how staff find it and protect restricted information. Hiding a button is not an access-control check.
Show success after the required save succeeds. Track later email and CRM actions separately so a notification failure does not lose the original enquiry. Agree how repeated clicks and retries avoid duplicate records, and who investigates failures.
If submissions are saved but notifications are missing, investigate that workflow before replacing the form. Our Wix lead-generation troubleshooting guide explains the distinction.
Compare cost by responsibility, not field count
A ten-field native form can be less work than a three-field interface that checks private records and writes to two systems. Ask for a scope that separates configuration from development and ongoing support.
Cost area | Questions for the proposal |
|---|---|
Initial setup | Which fields, branches, pages and outputs are included? |
Platform and services | Which Wix features, external subscriptions or usage charges are needed? |
Testing | Are mobile, keyboard, invalid-input and failure scenarios included? |
Handover | Can your team change questions, prices and recipients safely? |
Maintenance | Who updates integrations and investigates failed submissions? |
Use your own figures when assessing the value. For illustration, 40 enquiries a month requiring six minutes of manual transfer each represent four hours of work: 40 × 6 ÷ 60. That is the task being evaluated, not guaranteed time saved. A new workflow still needs review and exception handling.
Test these paths before launch
Use a clearly labelled test record and follow it from the published page to the destination your team actually uses.
Submit valid details and confirm the saved values and recipient.
Leave required fields empty and check that the error explains the correction.
Change the service choice after filling a conditional field. Check the final payload for irrelevant values.
Move backwards and forwards through a multi-page form and confirm that expected answers remain.
Use a phone and keyboard navigation. Check labels, focus, errors and the final button.
For custom integrations, simulate failure in a safe test environment and confirm the recovery path.
Retry a request and check whether it creates a duplicate record or repeats a notification unexpectedly.
Discuss the right form scope with CodeMasters
If you are unsure whether your Wix form needs configuration, an extension or custom Velo work, book a free 30-minute consultation.
Bring your website URL, the questions you want to ask, the destination for each answer and one example of a completed request. We can discuss the available options and what needs further investigation before quoting. If you prefer to send the requirements first, use our contact form.
Frequently asked questions
Do conditional Wix forms require Velo?
No. New Wix Forms include rules for showing, hiding, requiring and making fields optional. Check those options before commissioning a custom implementation.
Can Wix Forms have multiple steps?
Yes. New Wix Forms support multiple pages. Test navigation, conditional questions and required fields together on the published form.
Do custom validations always need a custom form?
No. New Wix Forms offer advanced validations through Wix Functions. Assess whether the available conditions and outputs cover your rule before replacing the interface.
Will a custom Velo form automatically save to Wix Forms and notify my team?
Do not assume so. Specify the storage and notification workflow. A custom interface may write to a CMS collection or external service, and its behaviour depends on the implementation.
Should I rebuild a form because notifications are missing?
First check whether the submission was saved. If it was, investigate recipients, automation configuration and delivery. Repairing that path may be sufficient.
