<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[zilancerc]]></title><description><![CDATA[zilancerc]]></description><link>https://zilancercer.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Wed, 18 Nov 2026 15:07:37 GMT</lastBuildDate><atom:link href="https://zilancercer.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[How Shopify selling plans power pre-orders, deposits and subscriptions]]></title><description><![CDATA[If you build for Shopify, sooner or later a merchant asks for "pay later", "pre-order with a deposit" or "subscribe and save". On Shopify all three run on…]]></description><link>https://zilancercer.hashnode.dev/how-shopify-selling-plans-power-pre-orders-deposits-and-subscriptions</link><guid isPermaLink="true">https://zilancercer.hashnode.dev/how-shopify-selling-plans-power-pre-orders-deposits-and-subscriptions</guid><category><![CDATA[shopify]]></category><category><![CDATA[ecommerce]]></category><category><![CDATA[Web Development]]></category><dc:creator><![CDATA[zilancerllc]]></dc:creator><pubDate>Sat, 14 Nov 2026 08:28:51 GMT</pubDate><content:encoded><![CDATA[<p>If you build for Shopify, sooner or later a merchant asks for "pay later", "pre-order with a deposit" or "subscribe and save". On Shopify all three run on the same building block: <strong>selling plans</strong>.</p>
<p>This is a practical overview of how they fit together, written from building apps on top of them.</p>
<h2>What a selling plan is</h2>
<p>A selling plan describes <em>how</em> a product is sold, separately from <em>what</em> is sold. It can say:</p>
<ul>
<li>when the customer is billed (now, later, or on a schedule),</li>
<li>when the order is delivered (now, later, or on a schedule),</li>
<li>what price adjustment applies (for example 10% off).</li>
</ul>
<p>Plans live in a <strong>selling plan group</strong>, and the group is attached to products or variants. On the product page the shopper picks a plan (or the theme picks it for them), and the cart line carries the selling plan ID into checkout.</p>
<h2>Three common setups</h2>
<p><strong>1. Subscription (subscribe and save).</strong> A recurring billing policy (every month, every two weeks) with a matching delivery policy and a percentage discount. Checkout creates a <em>subscription contract</em>; your app then creates the renewal orders when each billing cycle is due.</p>
<p><strong>2. Pre-order with full payment.</strong> One-time billing at checkout, with a delivery policy that says the item ships later (for example at a fixed date or when stock arrives). The order is created now and fulfilled later.</p>
<p><strong>3. Pre-order with a deposit.</strong> The billing policy charges part of the price at checkout and the remaining balance later. The order shows the outstanding amount; your app (or the merchant) charges it when the product is ready.</p>
<h2>Things that trip people up</h2>
<ul>
<li><strong>The theme has to show the plan.</strong> Online Store 2.0 themes render selling plan pickers through the product form, but many custom or older themes need a block or snippet. Always test the product page, not just the admin.</li>
<li><strong>One plan group per purpose.</strong> Mixing subscription plans and pre-order plans in the same group confuses both shoppers and your own code.</li>
<li><strong>Inventory.</strong> A pre-order usually needs "continue selling when out of stock" on the variant, otherwise the product cannot be added to the cart at zero stock.</li>
<li><strong>Payment methods.</strong> Deferred and recurring charges need a payment method that supports vaulting. Test with the payment providers your merchants actually use.</li>
<li><strong>Edits after checkout.</strong> Changing a plan does not change existing orders or contracts. Plan for migrations.</li>
</ul>
<h2>Working out the money side</h2>
<p>For merchants the real question is cash flow: how much arrives now and how much later. We built two small free tools that model exactly that:</p>
<ul>
<li>Pre-order deposit and cash-flow calculator: <a href="https://zs-presell.zilancer.com/pre-order-deposit-calculator.html">https://zs-presell.zilancer.com/pre-order-deposit-calculator.html</a></li>
<li>Subscription revenue and LTV calculator: <a href="https://zs-subscriptions.zilancer.com/subscription-revenue-calculator.html">https://zs-subscriptions.zilancer.com/subscription-revenue-calculator.html</a></li>
</ul>
<h2>Summary</h2>
<p>Selling plans are one concept with many faces. Once you see pre-orders, deposits and subscriptions as different billing and delivery policies on the same object, the APIs, the theme work and the support questions all get simpler.</p>
<p>(Disclosure: we build ZS PreSell and ZS Subscriptions on Shopify selling plans.)</p>
]]></content:encoded></item></channel></rss>