<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Thomas Scott (India) Ltd. (THOMASCOTT) — Tipsheet</title>
    <link>https://tipsheet.markets/company/thomascott/</link>
    <atom:link href="https://tipsheet.markets/company/thomascott/feed.xml" rel="self" type="application/rss+xml" />
    <description>Every Tipsheet Editorial note covering Thomas Scott (India) Ltd. (THOMASCOTT), newest first. Grounded in BSE/NSE primary-source filings.</description>
    <language>en-in</language>
    <lastBuildDate>Tue, 28 Jul 2026 14:38:36 GMT</lastBuildDate>
    <item>
      <title>Thomas Scott earnings transcript adds nothing new to prior results</title>
      <link>https://tipsheet.markets/thomascott-thomas-scott-earnings-transcript-adds-nothing-new-to-prior-results-106206/</link>
      <guid isPermaLink="true">https://tipsheet.markets/thomascott-thomas-scott-earnings-transcript-adds-nothing-new-to-prior-results-106206/</guid>
      <pubDate>Sat, 06 Jun 2026 15:15:06 GMT</pubDate>
      <description>The Q4 and FY25-26 conference call transcript contains no material information beyond what was already disclosed in the financial results.</description>
      <content:encoded><![CDATA[<p><em>The Q4 and FY25-26 conference call transcript contains no material information beyond what was already disclosed in the financial results.</em></p>
<h3>What’s new</h3><ul><li>Thomas Scott published the transcript for its Q4 and FY2025-26 earnings conference call.</li><li>The analyst rationale states it contains no new material information beyond previously announced results.</li><li>The filing is categorized as a standard earnings call transcript with no tradeable surprises.</li></ul>
<h3>Why it matters</h3><p>Earnings transcripts matter when they contain forward guidance, operational detail, or management commentary that diverges from the headline numbers. This one doesn't. The analyst rationale explicitly states there are no new developments, making it a routine disclosure.</p>
<h3>What we’re watching</h3><ul><li>Any future guidance or strategic shifts from the management team</li><li>Next quarter's operational performance and margin trajectory</li><li>Whether subsequent calls contain material new information</li></ul>
<h3>The full read</h3><p>Thomas Scott published the transcript for its Q4 and FY25-26 earnings call. The analyst rationale is blunt: it adds nothing. No new financials, no guidance shifts, no operational surprises beyond what the market already knew. A 5/10 score reflects this. For investors, the value of an earnings call lies in the delta between what was expected and what was said. Here, there is no delta. The transcript is a procedural record, not a market event.</p>
<p>Primary source: <a href="https://www.bseindia.com/corporates/ann.html?scrip=533941&dur=A">BSE</a> · <a href="https://www.nseindia.com/companies-listing/corporate-filings-announcements?symbol=THOMASCOTT">NSE</a></p>]]></content:encoded>
      <category>Earnings</category>
      <dc:creator>Tipsheet Editorial</dc:creator>
    </item>
    <item>
      <title>Thomas Scott plans 60% growth but won&#39;t explain a 32% drop in SKUs.</title>
      <link>https://tipsheet.markets/thomascott-thomas-scott-plans-60-growth-but-won-t-explain-a-32-drop-in-skus-105101/</link>
      <guid isPermaLink="true">https://tipsheet.markets/thomascott-thomas-scott-plans-60-growth-but-won-t-explain-a-32-drop-in-skus-105101/</guid>
      <pubDate>Wed, 03 Jun 2026 15:23:46 GMT</pubDate>
      <description>FY26 revenue jumped 58% to ₹255 cr. Management wants to do it again, but a warehouse-fire payout and an unexplained drop in SKU counts are the real story.</description>
      <content:encoded><![CDATA[<p><em>FY26 revenue jumped 58% to ₹255 cr. Management wants to do it again, but a warehouse-fire payout and an unexplained drop in SKU counts are the real story.</em></p>
<h3>What’s new</h3><ul><li>Thomas Scott plans 60% revenue growth for FY27 after posting 58% growth in FY26 to ₹255 cr.</li><li>EBITDA margins hit 13.1%, but raw-material costs from regional conflicts are a headwind.</li><li>SKU count dropped from over 22,000 to 15,000, a change management didn't fully explain.</li></ul>
<h3>Why it matters</h3><p>The growth target is aggressive given rising input costs. The bigger issue is reporting transparency. A 32% drop in SKU count is a major operational shift that needs a clear narrative, especially for a nano-cap where investor trust is everything.</p>
<h3>What we’re watching</h3><ul><li>Whether the ₹22 cr fire insurance claim is settled in the next quarter.</li><li>How management explains the sharp SKU reduction and its impact on sales channels.</li><li>Margin durability if raw-material costs keep climbing as projected.</li></ul>
<h3>The full read</h3><p>Thomas Scott delivered <strong>58% revenue growth</strong> in FY26, hitting <strong>₹255 crore</strong>, and management wants more, guiding for <strong>60% growth</strong> in the year ahead. EBITDA margins of <strong>13.1%</strong> look solid. But raw-material costs tied to regional conflicts are squeezing profitability. The growth story is straightforward, but the operational details are not. SKU counts plunged from over <strong>22,000 to 15,000</strong>. Management did not fully explain the drop. For a nano-cap shifting toward B2B wholesale, that kind of unexplained consolidation is a red flag. The near-term balance-sheet fix is a <strong>₹22 crore</strong> insurance payout from a warehouse fire, which management says will cut short-term borrowing. Until that money arrives, the company is juggling ambitious growth targets and rising input costs with a balance sheet that is still under pressure.</p>
<p>Primary source: <a href="https://www.bseindia.com/corporates/ann.html?scrip=533941&dur=A">BSE</a> · <a href="https://www.nseindia.com/companies-listing/corporate-filings-announcements?symbol=THOMASCOTT">NSE</a></p>]]></content:encoded>
      <category>Concalls</category>
      <dc:creator>Tipsheet Editorial</dc:creator>
    </item>
  </channel>
</rss>