> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/getting-started/why-roadmap.md). # Why Roadmap? Why lifestyle brands choose Roadmap over a stack of disconnected apps. Roadmap is a strong fit for lifestyle brands because it brings growth, retention, and merchandising into one native Shopify ecosystem. That matters when your brand needs speed, consistency, and less app sprawl. ### Why lifestyle brands choose Roadmap Lifestyle brands rarely need one isolated tool. They need loyalty, reviews, bundles, subscriptions, promotions, and segmentation to work together. Roadmap brings those together in one platform. That gives brands: * fewer apps to install, manage, and pay for * one shared customer, product, and order context * less duplicated setup across teams * a more consistent storefront experience * faster campaign launches ### What sets Roadmap apart Roadmap is built as a single native ecosystem. It is not a loose bundle of disconnected tools. Across the platform, brands can run: * loyalty and referrals * reviews and review syndication * subscriptions * discounts and Gift with Purchase * bundles * forms and data capture * customer access rules with Tag Library * Shopify POS workflows * B2B and trade experiences This matters because each part can support the others. A brand can reward reviews with loyalty points. It can trigger flows from customer actions. It can run offers by tag, loyalty status, or purchase history. It can carry the same experience from storefront to POS. ### Native integrations are a core strength Roadmap is built around native Shopify data. It is designed as a native platform, with data stored at metaobject level to support smart, fast integrations. That creates cleaner connections and better reuse across the stack. In practice, brands can connect Roadmap with tools such as: * Klaviyo * Shopify POS * Google Shopping * Google Sheets * Retail Express * Shopify B2B The advantage is not only that integrations exist. The advantage is that the same loyalty, review, promotion, and customer data can be used across the platform without heavy custom glue. {% hint style="info" %} For product-level detail and brand examples, see [roadmap.so](https://roadmap.so/). {% endhint %} ### Why this matters for growth Lifestyle brands usually compete on brand, repeat purchase, and customer experience. Roadmap supports that directly. Use it when you want to: * grow repeat purchase with loyalty, tiers, referrals, and subscriptions * add trust with product and store reviews * lift AOV with bundles, discounts, and Gifts with Purchase * segment experiences by audience, tags, or membership * keep online and retail experiences aligned * reduce operational overhead from too many point solutions ### Built for real ecommerce teams Roadmap is not only a feature set. It is also an operating model. The platform combines native Shopify workflows, managed infrastructure, and direct human support. Roadmap runs on a modern managed stack with serverless infrastructure, PostgreSQL, GCP, and Cloudflare protection. That helps growing brands reduce technical risk and day-to-day friction. ### In short Roadmap if the ideal choice for brands who want one platform to handle the parts of commerce that usually get split across multiple apps. It is a strong choice for lifestyle brands that want native Shopify workflows, strong integrations, less complexity, and a more connected customer experience. ### Related reading * [Technology](/getting-started/technology.md) * [Customer Support](/getting-started/customer-support.md) * [Required Shopify permissions](/getting-started/shopify-permissions.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.roadmap.so/getting-started/why-roadmap.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.