<?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/">
  <channel>
    <title>DEV Community: Swift pos</title>
    <description>The latest articles on DEV Community by Swift pos (@swiftapps).</description>
    <link>https://dev.to/swiftapps</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4096349%2F483577cc-659f-4a05-885c-e6b597c3f4f9.png</url>
      <title>DEV Community: Swift pos</title>
      <link>https://dev.to/swiftapps</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/swiftapps"/>
    <language>en</language>
    <item>
      <title>Flat-fee affiliate tracking without third-party cookies</title>
      <dc:creator>Swift pos</dc:creator>
      <pubDate>Mon, 31 Aug 2026 03:31:51 +0000</pubDate>
      <link>https://dev.to/swiftapps/flat-fee-affiliate-tracking-without-third-party-cookies-1b1</link>
      <guid>https://dev.to/swiftapps/flat-fee-affiliate-tracking-without-third-party-cookies-1b1</guid>
      <description>&lt;p&gt;A merchant running a small programme finds that percentage-based apps charge more as sales grow, while flat-fee tools often rely on third-party cookies that browsers increasingly block. I build ZeroCut. The app charges a fixed monthly fee — Free, $19, or $39 — with 0% commission on tracked sales, enforced server-side. Attribution follows three signals in order: a &lt;code&gt;_zc_ref&lt;/code&gt; cart attribute from the theme embed, a real Shopify discount code per affiliate, then the &lt;code&gt;landing_site&lt;/code&gt; query param. A 30-day window uses first-party cookies and localStorage only; no external scripts load on the storefront. When an order is cancelled or refunded, the commission reverses automatically. Partial refunds reverse proportionally. Anything already marked paid is never rewritten. An optional hold period delays approval. The app does not store customer PII. It also does not rewrite commissions once they are marked paid, even if a later refund occurs. For very small programmes, a percentage app's free tier can cost less than any flat fee including ours.&lt;/p&gt;

</description>
      <category>shopify</category>
      <category>ecommerce</category>
      <category>affiliate</category>
      <category>saas</category>
    </item>
    <item>
      <title>Counting, locating, and verifying stock on a phone</title>
      <dc:creator>Swift pos</dc:creator>
      <pubDate>Fri, 28 Aug 2026 02:03:31 +0000</pubDate>
      <link>https://dev.to/swiftapps/counting-locating-and-verifying-stock-on-a-phone-4km0</link>
      <guid>https://dev.to/swiftapps/counting-locating-and-verifying-stock-on-a-phone-4km0</guid>
      <description>&lt;p&gt;A warehouse team opens the day with a cycle count across three Shopify locations. They scan barcodes or SKUs on their phones, and the app writes each adjustment directly to the correct location without a spreadsheet handoff. Bin locations are stored per variant, so the same scan that confirms quantity also confirms the item is in A-12, not B-04. When a picker pulls an order, they scan each line item; the app verifies the pick against the order and marks the fulfillment complete only when every scan matches. Transfers between Shopify locations and external destinations are created from the same mobile route, and a unified history logs every change with a one-click revert if a transfer was posted to the wrong destination. Staff permissions restrict who can start a count, approve a transfer, or print labels. I build Swift Stock. It does not handle purchase orders or demand forecasting, which Shopify Stocky currently provides before its 2026-08-31 retirement.&lt;/p&gt;

</description>
      <category>shopify</category>
      <category>inventory</category>
      <category>ecommerce</category>
      <category>saas</category>
    </item>
  </channel>
</rss>
