Customise Wix or rebuild your website?
By TechBooks Solutions · Updated
A missing feature is a reason to investigate, not automatically a reason to replace your whole website.
Start with the business requirement
Write down what a customer or staff member needs to do. For example: a trade buyer should see an agreed price, or an administrator should maintain a product mapping. Separate the outcome from assumptions about technology.
Check the smallest workable change
Review native functionality, suitable existing apps and a custom extension in that order. Verify relevant APIs, permissions, plan and supported journeys. A prototype should answer the hardest compatibility question first.
Test the whole purchase journey
Showing a custom price on a product page is only part of the job. Validate variant, quantity, member permissions, cart, checkout and resulting order. Agree how price rules interact with discounts and prevent unauthorised access.
When is a rebuild worth assessing?
Consider a rebuild when a verified platform constraint blocks an essential workflow, or repeated workarounds are no longer justified. Compare implementation, hosting, maintenance, content editing and ownership costs over time.
Include migration in the decision
Plan for content, product data, URLs, redirects and analytics. Document which records can move. Agree a rollback approach and post-launch checks so the decision includes operational disruption as well as new features.
Official references
Platform capabilities change. Confirm the details for your product and project before implementation.