When is a template enough?
A template is enough when its existing pages handle your catalog clearly. You can enter your product information and try the store without commissioning a new layout.
That's useful while you're still deciding what your brand should look like. Check the full quote and ongoing bills, though. A low starting price doesn't tell you what later changes will cost.
Where does the template start to show?
It shows when you keep the default layout and swap in your logo. Your home page can end up looking much like other stores built from the same starting point.
Try a change you actually need, such as putting the lot certificate beside the buy button. Find out whether you can do it in settings or need development work. Changing a color won't move that information.
What happens when you add plugins?
Plugins can add features your template doesn't have. Open the pages they add and check whether the buttons and wording match the rest of your store.
Ask who handles updates and checks that the pieces still work together. Custom stores need that upkeep too. At checkout, RUObuilt makes no guarantee of processor approval or uninterrupted processing.
What changes in a build for your brand?
You can arrange the pages around your own catalog and brand assets. That means deciding where your product details belong before filling the page with content.
Review a product page with your actual information in it. Check the long names and the lot documents, then open the same page on a phone. Ask which changes your agreement includes before approving the build.
What should you compare?
Compare both options against the work you need your store to do. Include routine edits, such as replacing a product image or updating a supplied lot document.
Check who controls the accounts and what software rights you receive. A custom design doesn't automatically include every underlying component. The renting versus owning guide explains what to look for.
When should you wait on a custom build?
Wait if you don't yet have the product records needed to fill the pages. You also need to know who will run your store after handoff.
If the template already fits, you may have no reason to replace it yet. Spend time using it and write down the limits you actually encounter. That gives you something concrete to discuss if you commission a build later.
What do you bring to the builder?
Bring your catalog and the brand assets you already have. Point to the exact pages you want changed and explain what someone needs to do on each one.
Separate required functions from visual preferences. Ask the builder to put the included work and support dates in writing, so you can review the finished store against that agreement.
What do you check before calling it finished?
Run through these checks with a real listing from your catalog.
- Try your real catalog in the layout.
- Check how lot documents are linked.
- Ask who maintains added features.
- Read the account-transfer and licence terms.
What else might you want to know?
Here are the other questions to settle before you change your store.
Is a template a bad starting point?
No. Use one if its pages fit your information and you accept its limits.
Does custom mean every part is exclusive?
No. RUObuilt uses reusable platform components underneath the work for your store.
Will a custom build remove the upkeep?
No. You still need to maintain your records and service accounts after handoff.
What if I haven't settled on a brand?
Discuss that scope first. Applying your existing brand is different from creating its name and identity.
What does a finished build look like?
You can open the Meridian fictional demo store and Corvia fictional demo store to see our work, both shown with sample data. Your build follows the agreed scope and the information you supply.
Full brand identity is a separate scope, included in Flagship. We make no guarantee of compliance or any business outcome.
Your store and everything specific to it: the custom code, the design, the product images, the content, and the database, assigned to you once final payment clears. The repository, deployment project, database and email accounts transfer into accounts you own and control.
The reusable platform components underneath, the ones we build every store on, stay ours. You get a perpetual, royalty-free licence to use them inside your store, for your own business, forever. The only thing you can't do is resell them or use them to build stores for other people.
Third-party components keep their own licenses; the agreement's rights revert if a payment is reversed. There's no recurring licence fee, and you pay your own providers after handoff. Included services end on fixed dates; paid add-ons are separate and opt-in.