<?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>thread Square Reporting API - Sales Attribution Bug, need for Service Provider in AI Tools</title>
    <link>https://community.squareup.com/t5/AI-Tools/Square-Reporting-API-Sales-Attribution-Bug-need-for-Service/m-p/843161#M41</link>
    <description>&lt;P&gt;I have chronicled my attempts to use &lt;A href="https://community.squareup.com/t5/Feature-Requests/Appointment-to-Payment-Matching-Challenges/idi-p/841298" target="_self"&gt;Square MCP&lt;/A&gt; to create an Appointments report. However, there is no &lt;SPAN&gt;booking_id on an order to link customer -&amp;gt; appointment -&amp;gt; transaction.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Well... I got a glimmer of hope today when I saw &lt;A href="https://developer.squareup.com/forums/t/reporting-api-open-beta/25897/4" target="_self"&gt;this post&lt;/A&gt; in the Developer forum introducing a new Reporting API. What? Access to ALL the data?!&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;So I learned how to vibe code with Claude, use Python.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Here's the thing. Garbage in -&amp;gt; Garbage out. The database just doesn't know how to document who the &lt;STRONG&gt;&lt;U&gt;service provider&lt;/U&gt;&lt;/STRONG&gt; is for an Appointment, or it does know how and just fails to provide the tools to sellers.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Here's my issue:&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="font-claude-response-body break-words whitespace-normal leading-[1.7]"&gt;There is an attribution bug:&lt;/P&gt;
&lt;UL class="[li_&amp;amp;]:mb-0 [li_&amp;amp;]:mt-1 [li_&amp;amp;]:gap-1 [&amp;amp;:not(:last-child)_ul]:pb-1 [&amp;amp;:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3"&gt;
&lt;LI class="font-claude-response-body whitespace-normal break-words pl-2"&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt; When a customer pre-books online (no human booker) → API correctly attributes to the service provider&lt;/LI&gt;
&lt;LI class="font-claude-response-body whitespace-normal break-words pl-2"&gt;&lt;span class="lia-unicode-emoji" title=":cross_mark:"&gt;❌&lt;/span&gt; When &lt;U&gt;a cashier&lt;/U&gt; books the appointment → API attributes to the booker (cashier), not the service provider&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;or give us ServiceProvider, ServiceWith, ServiceDoneBy&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We need it desperately, please!&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 22 May 2026 21:45:52 GMT</pubDate>
    <dc:creator>TCSlaguna</dc:creator>
    <dc:date>2026-05-22T21:45:52Z</dc:date>
    <item>
      <title>Square Reporting API - Sales Attribution Bug, need for Service Provider</title>
      <link>https://community.squareup.com/t5/AI-Tools/Square-Reporting-API-Sales-Attribution-Bug-need-for-Service/m-p/843161#M41</link>
      <description>&lt;P&gt;I have chronicled my attempts to use &lt;A href="https://community.squareup.com/t5/Feature-Requests/Appointment-to-Payment-Matching-Challenges/idi-p/841298" target="_self"&gt;Square MCP&lt;/A&gt; to create an Appointments report. However, there is no &lt;SPAN&gt;booking_id on an order to link customer -&amp;gt; appointment -&amp;gt; transaction.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Well... I got a glimmer of hope today when I saw &lt;A href="https://developer.squareup.com/forums/t/reporting-api-open-beta/25897/4" target="_self"&gt;this post&lt;/A&gt; in the Developer forum introducing a new Reporting API. What? Access to ALL the data?!&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;So I learned how to vibe code with Claude, use Python.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Here's the thing. Garbage in -&amp;gt; Garbage out. The database just doesn't know how to document who the &lt;STRONG&gt;&lt;U&gt;service provider&lt;/U&gt;&lt;/STRONG&gt; is for an Appointment, or it does know how and just fails to provide the tools to sellers.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Here's my issue:&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="font-claude-response-body break-words whitespace-normal leading-[1.7]"&gt;There is an attribution bug:&lt;/P&gt;
&lt;UL class="[li_&amp;amp;]:mb-0 [li_&amp;amp;]:mt-1 [li_&amp;amp;]:gap-1 [&amp;amp;:not(:last-child)_ul]:pb-1 [&amp;amp;:not(:last-child)_ol]:pb-1 list-disc flex flex-col gap-1 pl-8 mb-3"&gt;
&lt;LI class="font-claude-response-body whitespace-normal break-words pl-2"&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt; When a customer pre-books online (no human booker) → API correctly attributes to the service provider&lt;/LI&gt;
&lt;LI class="font-claude-response-body whitespace-normal break-words pl-2"&gt;&lt;span class="lia-unicode-emoji" title=":cross_mark:"&gt;❌&lt;/span&gt; When &lt;U&gt;a cashier&lt;/U&gt; books the appointment → API attributes to the booker (cashier), not the service provider&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;or give us ServiceProvider, ServiceWith, ServiceDoneBy&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We need it desperately, please!&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 22 May 2026 21:45:52 GMT</pubDate>
      <guid>https://community.squareup.com/t5/AI-Tools/Square-Reporting-API-Sales-Attribution-Bug-need-for-Service/m-p/843161#M41</guid>
      <dc:creator>TCSlaguna</dc:creator>
      <dc:date>2026-05-22T21:45:52Z</dc:date>
    </item>
  </channel>
</rss>

