Start with the website. Add more when it helps.

Yes. Your starting site is private and editable, so you can judge the structure and direction before treating it as your public website.

No. You decide when the content and domain are ready. Draft work stays private until you deliberately publish it.

It stays in place. A BloomSites starting site or migration draft does not replace the current site while you review the new work.

In most cases, yes. You connect the domain when the new site is ready. The exact DNS steps depend on the company that manages it.

That is the point of the visual editor. Staff can change pages, images, articles, and events in context, then preview before publishing.

Not automatically. Public pages and usable assets can often be brought forward, while third-party tools, blocked files, commerce data, and outdated content need review.

Yes. Start with a content or catalogue website. Add ordering only when payments, products, receiving choices, and fulfilment are ready.

No. BloomSites can connect with supported systems where access allows it. We will be clear about what is available, in pilot, or still manual.

No. Receiving choices depend on your store, region, products, vendors, and setup. Customers see only options that are configured and eligible.

Those costs depend on the setup, payment processing, vendors, and implementation work. They are shown and confirmed before paid work or commerce is activated.

The software includes guided workflows and tutorials. The level of onboarding and support also depends on your plan and any implementation scope you choose.

That is normal. Launch the useful website first, then add catalogue, commerce, vendors, or integrations when each part has an owner and a clear benefit.