<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Modeling dynamic store + quantity data for client-facing quotes (no line items) in &amp;#128172 RevOps Discussions</title>
    <link>https://community.hubspot.com/t5/128172-RevOps-Discussions/Modeling-dynamic-store-quantity-data-for-client-facing-quotes-no/m-p/1248431#M3645</link>
    <description>&lt;HR /&gt;&lt;P&gt;This is a pretty common RevOps pain point. One pattern I’ve seen work is using a &lt;STRONG&gt;structured custom object&lt;/STRONG&gt; (store name + quantity) tied to the deal, then rendering that object in a &lt;STRONG&gt;custom quote template&lt;/STRONG&gt; or via a coded module. That keeps quotes readable while still giving you exportable, structured data that reps can self-manage.&lt;/P&gt;&lt;P&gt;If you’re looking for examples of how communities handle edge-case tooling and self-serve workarounds at scale, some niche ecosystems (even outside RevOps, like &lt;STRONG&gt;&lt;A class="" href="https://deltaexecuter.com/" target="_new" rel="noopener"&gt;roblox epxloiters&lt;/A&gt;&lt;/STRONG&gt; communities) rely heavily on structured metadata + client-facing abstractions rather than line items. The same principle applies here: keep raw data structured behind the scenes, and surface only what clients need to see.&lt;/P&gt;&lt;P&gt;Not perfect, but often the least-bad compromise until native support improves.&lt;/P&gt;</description>
    <pubDate>Thu, 05 Feb 2026 07:38:10 GMT</pubDate>
    <dc:creator>ASoklov9</dc:creator>
    <dc:date>2026-02-05T07:38:10Z</dc:date>
    <item>
      <title>Modeling dynamic store + quantity data for client-facing quotes (no line items)</title>
      <link>https://community.hubspot.com/t5/128172-RevOps-Discussions/Modeling-dynamic-store-quantity-data-for-client-facing-quotes-no/m-p/1247942#M3640</link>
      <description>&lt;P&gt;Looking for guidance from a RevOps / data-modeling perspective.&lt;/P&gt;&lt;P&gt;We use HubSpot quotes for &lt;STRONG&gt;client-facing subscription pricing&lt;/STRONG&gt;, but we also need to show a &lt;STRONG&gt;store-level quantity breakdown&lt;/STRONG&gt; to clients. Line items are already used for subscriptions and can’t be repurposed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Constraints:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Store lists and quantities vary by deal/client&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;AEs and CSMs must manage this themselves (self-serve)&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Store + quantity must be visible to clients&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Quotes need to remain clean and readable&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Multi-select properties don’t work due to quantity requirements&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Has anyone found a scalable pattern that balances:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Clean client-facing quotes&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Rep-managed inputs&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Structured, exportable data?&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Open to hearing about:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Property-based approaches&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Custom quote templates&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Known limitations and “least bad” compromises&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Appreciate any real-world implementations.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Feb 2026 22:09:03 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/128172-RevOps-Discussions/Modeling-dynamic-store-quantity-data-for-client-facing-quotes-no/m-p/1247942#M3640</guid>
      <dc:creator>SRussell_FA</dc:creator>
      <dc:date>2026-02-03T22:09:03Z</dc:date>
    </item>
    <item>
      <title>Re: Modeling dynamic store + quantity data for client-facing quotes (no line items)</title>
      <link>https://community.hubspot.com/t5/128172-RevOps-Discussions/Modeling-dynamic-store-quantity-data-for-client-facing-quotes-no/m-p/1248431#M3645</link>
      <description>&lt;HR /&gt;&lt;P&gt;This is a pretty common RevOps pain point. One pattern I’ve seen work is using a &lt;STRONG&gt;structured custom object&lt;/STRONG&gt; (store name + quantity) tied to the deal, then rendering that object in a &lt;STRONG&gt;custom quote template&lt;/STRONG&gt; or via a coded module. That keeps quotes readable while still giving you exportable, structured data that reps can self-manage.&lt;/P&gt;&lt;P&gt;If you’re looking for examples of how communities handle edge-case tooling and self-serve workarounds at scale, some niche ecosystems (even outside RevOps, like &lt;STRONG&gt;&lt;A class="" href="https://deltaexecuter.com/" target="_new" rel="noopener"&gt;roblox epxloiters&lt;/A&gt;&lt;/STRONG&gt; communities) rely heavily on structured metadata + client-facing abstractions rather than line items. The same principle applies here: keep raw data structured behind the scenes, and surface only what clients need to see.&lt;/P&gt;&lt;P&gt;Not perfect, but often the least-bad compromise until native support improves.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Feb 2026 07:38:10 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/128172-RevOps-Discussions/Modeling-dynamic-store-quantity-data-for-client-facing-quotes-no/m-p/1248431#M3645</guid>
      <dc:creator>ASoklov9</dc:creator>
      <dc:date>2026-02-05T07:38:10Z</dc:date>
    </item>
    <item>
      <title>Re: Modeling dynamic store + quantity data for client-facing quotes (no line items)</title>
      <link>https://community.hubspot.com/t5/128172-RevOps-Discussions/Modeling-dynamic-store-quantity-data-for-client-facing-quotes-no/m-p/1248464#M3646</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/925352"&gt;@SRussell_FA&lt;/a&gt;&amp;nbsp;and Happy Thursday!&lt;BR /&gt;&lt;BR /&gt;Thanks so much for your thoughtful question on the HubSpot Community and for outlining your requirements so clearly!&lt;BR /&gt;&lt;BR /&gt;I'd love to put you in touch with our Top Experts: Hi&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/123775"&gt;@danmoyle&lt;/a&gt;,&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/9629"&gt;@HubDoPete&lt;/a&gt;&amp;nbsp;and&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/141"&gt;@TomM2&lt;/a&gt;&amp;nbsp;have you tackled this with property-based solutions or other creative workarounds?&lt;BR /&gt;&lt;BR /&gt;If so, please feel free to share your experiences with&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/925352"&gt;@SRussell_FA&lt;/a&gt;!&lt;BR /&gt;&lt;BR /&gt;Thanks so much in advance for your valuable insights!&lt;BR /&gt;&lt;BR /&gt;Have a wonderful day!&lt;BR /&gt;Bérangère&lt;/P&gt;</description>
      <pubDate>Thu, 05 Feb 2026 10:09:43 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/128172-RevOps-Discussions/Modeling-dynamic-store-quantity-data-for-client-facing-quotes-no/m-p/1248464#M3646</guid>
      <dc:creator>BérangèreL</dc:creator>
      <dc:date>2026-02-05T10:09:43Z</dc:date>
    </item>
    <item>
      <title>Re: Modeling dynamic store + quantity data for client-facing quotes (no line items)</title>
      <link>https://community.hubspot.com/t5/128172-RevOps-Discussions/Modeling-dynamic-store-quantity-data-for-client-facing-quotes-no/m-p/1250059#M3667</link>
      <description>&lt;P&gt;Hey there&amp;nbsp;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/925352"&gt;@SRussell_FA&lt;/a&gt;. This is interesting. In my experience, when you add inventory to HubSpot, it complicates things pretty quickly. Not impossible, but depending on technical skills, HubSpot hubs + tiers, and budget, you have a few options.&amp;nbsp;HubSpot can support this pattern, but you’ll hit some limits if you try to do it purely with standard quotes and line items. I think the most scalable approach is usually a mix of custom quote templates plus either structured properties or a lightweight CPQ add‑on for the store matrix.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I haven't built this kind of thing, but I've seen it discussed over the last couple of years in the Community. So while I don't have a roadmap to share, if I were in your shoes I'd use Gemini and Perplexity to see if there's a map you can envision. I'd want it to include help with custom design&amp;nbsp;(like showing how to have a quote include a table of line items in the design manager) and data entry options like ensuring consistent entry across stores.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Sorry it's not a mapped out,&amp;nbsp;"here's your solution" type answer. But I'd see this as a longer conversation with either a HubSpot partner, a freelancer, or at the very least a developer.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Feb 2026 15:20:02 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/128172-RevOps-Discussions/Modeling-dynamic-store-quantity-data-for-client-facing-quotes-no/m-p/1250059#M3667</guid>
      <dc:creator>danmoyle</dc:creator>
      <dc:date>2026-02-11T15:20:02Z</dc:date>
    </item>
  </channel>
</rss>

