<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <id>https://www.sku.io/docs/release-notes/</id>
    <title>SKU.io Release Notes</title>
    <updated>2026-11-12T23:48:48.000Z</updated>
    <generator>https://github.com/jpmonette/feed</generator>
    <link rel="alternate" href="https://www.sku.io/docs/release-notes/"/>
    <subtitle>New features, improvements, and fixes for the SKU.io platform.</subtitle>
    <icon>https://www.sku.io/docs/img/favicon.ico</icon>
    <rights>Copyright © 2026 SKU.io.</rights>
    <entry>
        <title type="html"><![CDATA[Shopify payments — PayPal, Sezzle and reserves land in the right account]]></title>
        <id>https://www.sku.io/docs/release-notes/2026/11/12/shopify-payment-gateways-and-reserves/</id>
        <link href="https://www.sku.io/docs/release-notes/2026/11/12/shopify-payment-gateways-and-reserves/"/>
        <updated>2026-11-12T23:48:48.000Z</updated>
        <summary type="html"><![CDATA[Map each Shopify payment gateway to its own payment type, hold payments from unmapped gateways until you do, and book Shopify Payments reserves to a balance-sheet account.]]></summary>
        <content type="html"><![CDATA[<p>Not every Shopify payment reaches you through a Shopify payout. A PayPal or Sezzle payment lands in your PayPal balance or your bank, yet until now an unmapped gateway's payment was booked as Shopify Payments money, and it sat in your Shopify Payments clearing account for good. And when Shopify held part of a payout back as a reserve, the hold posted as an expense and the release as a sale. <strong>Payment gateway mapping</strong> and <strong>Shopify Payments reserve accounts</strong> fix both.</p>
<p><strong>✨ What this means for you:</strong></p>
<ul>
<li class=""><strong>Every gateway gets its own payment type.</strong> The <strong>Payment Methods</strong> tab lists each gateway found on your orders and flags the ones that <strong>need mapping</strong>.</li>
<li class=""><strong>Nothing posts to the wrong account while you decide.</strong> With <strong>Hold payments from unmapped gateways</strong> on, payments from an unmapped gateway wait in Needs Attention, and move to the type you pick as soon as you map it. The switch is on for stores connected from now on; for stores you already have, it's off until you turn it on.</li>
<li class=""><strong>Reserves stay on your balance sheet.</strong> On the payout setup card, one click creates a <strong>Shopify Payments Reserve</strong> asset account. Each hold adds to it and each release takes it back out, and the payout still equals the bank deposit.</li>
<li class=""><strong>Month-end catches what's left.</strong> Two new close checks, <strong>Payment gateways mapped</strong> and <strong>Shopify Payments reserve reconciled</strong>, flag unmapped gateways and a reserve account that doesn't match what Shopify still holds.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="map-your-payment-gateways">Map your payment gateways<a href="https://www.sku.io/docs/release-notes/2026/11/12/shopify-payment-gateways-and-reserves/#map-your-payment-gateways" class="hash-link" aria-label="Direct link to Map your payment gateways" title="Direct link to Map your payment gateways" translate="no">​</a></h2>
<p>Open your Shopify connection's <strong>Settings → Payment Methods</strong>. Shopify's own gateways already use the <strong>Shopify Payment</strong> type. Pick a payment type for every other gateway and click <strong>Save Mappings</strong>.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/guides/map-shopify-payment-methods/payment-methods-tab.png" alt="The Payment Methods tab with PayPal and Sezzle marked Needs mapping and payments waiting" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="track-shopify-payments-reserves">Track Shopify Payments reserves<a href="https://www.sku.io/docs/release-notes/2026/11/12/shopify-payment-gateways-and-reserves/#track-shopify-payments-reserves" class="hash-link" aria-label="Direct link to Track Shopify Payments reserves" title="Direct link to Track Shopify Payments reserves" translate="no">​</a></h2>
<p>On the store's <strong>Finance</strong> tab, open <strong>Payout Mappings</strong>. Once Shopify has held funds back from a payout, the setup card offers a <strong>Shopify Payments reserve account</strong>, marked <strong>Recommended</strong>.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/guides/track-shopify-payments-reserves/reserve-setup-step.png" alt="The Shopify Payments reserve account step on the payout setup card" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-to-find-it">Where to find it<a href="https://www.sku.io/docs/release-notes/2026/11/12/shopify-payment-gateways-and-reserves/#where-to-find-it" class="hash-link" aria-label="Direct link to Where to find it" title="Direct link to Where to find it" translate="no">​</a></h2>
<p>Go to <strong>Apps &amp; Integrations</strong>, open your Shopify connection, and choose <strong>Settings → Payment Methods</strong> for gateways, or the <strong>Finance</strong> tab → <strong>Payout Mappings</strong> for the reserve account.</p>
<p><strong>Full guides:</strong> <a href="https://www.sku.io/docs/guides/integrations/shopify/set-up/map-shopify-payment-methods" target="_blank" rel="noopener noreferrer" class="">Map Shopify payment methods</a> · <a href="https://www.sku.io/docs/guides/integrations/basics/map-products-stock-and-payouts/track-shopify-payments-reserves" target="_blank" rel="noopener noreferrer" class="">Track Shopify Payments reserves</a></p>]]></content>
        <author>
            <name>SKU.io Product Team</name>
            <uri>https://sku.io</uri>
        </author>
        <category label="Minor Feature" term="Minor Feature"/>
        <category label="New" term="New"/>
        <category label="Improved" term="Improved"/>
        <category label="Integrations" term="Integrations"/>
        <category label="Accounting" term="Accounting"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Shiptheory — book UK carriers and print labels, with tracking and costs back in SKU.io]]></title>
        <id>https://www.sku.io/docs/release-notes/2026/11/12/shiptheory/</id>
        <link href="https://www.sku.io/docs/release-notes/2026/11/12/shiptheory/"/>
        <updated>2026-11-12T06:51:30.000Z</updated>
        <summary type="html"><![CDATA[Connect Shiptheory to SKU.io: send fulfillment orders to Shiptheory, let it book Royal Mail, DPD, Evri and more, and get tracking and shipping cost back automatically.]]></summary>
        <content type="html"><![CDATA[<p>If you ship in the UK with Shiptheory, every order used to mean entering it in Shiptheory by hand, waiting for the label, then copying the tracking number back so your sales channel could tell the customer it shipped. Shipping costs stayed in Shiptheory, away from your fulfillment costs. <strong>The Shiptheory integration</strong> connects the two. Fulfillment orders from the warehouses you route to Shiptheory go straight to it, Shiptheory books each one with Royal Mail, DPD, Evri or any other carrier on your account, and the booking comes back to SKU.io as a shipment.</p>
<p><strong>✨ What this means for you:</strong></p>
<ul>
<li class=""><strong>No more re-keying orders.</strong> Submit a fulfillment order and Shiptheory receives the address, items, weight, value and parcels, plus the delivery service to book.</li>
<li class=""><strong>Your carriers, your rules.</strong> Pair each Shiptheory delivery service with a SKU.io shipping method, or leave it to Shiptheory's own rules engine to choose. <strong>Auto-match unmapped</strong> pairs services and methods that share a name.</li>
<li class=""><strong>Tracking flows back on its own.</strong> Once Shiptheory books an order, SKU.io records the shipment with its carrier and tracking number, and sends the tracking to your sales channel.</li>
<li class=""><strong>Shipping costs where they belong.</strong> Each booking's cost is saved on its fulfillment, in your Shiptheory billing currency.</li>
<li class=""><strong>Labels on demand.</strong> Download any booked order's label again from the <strong>Orders</strong> tab.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="connect-with-your-shiptheory-login">Connect with your Shiptheory login<a href="https://www.sku.io/docs/release-notes/2026/11/12/shiptheory/#connect-with-your-shiptheory-login" class="hash-link" aria-label="Direct link to Connect with your Shiptheory login" title="Direct link to Connect with your Shiptheory login" translate="no">​</a></h2>
<p>Choose <strong>Shiptheory</strong> under <strong>Apps &amp; Integrations</strong>, enter a Shiptheory user's email and password, and click <strong>Test Connection</strong>. There's no API key to generate. SKU.io downloads your delivery services and package sizes straight away, and the dashboard shows what's left to set up.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/shiptheory/dashboard.png" alt="The Shiptheory dashboard after connecting, with the setup banners, the order counts and the sync status" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="map-services-and-route-your-warehouses">Map services and route your warehouses<a href="https://www.sku.io/docs/release-notes/2026/11/12/shiptheory/#map-services-and-route-your-warehouses" class="hash-link" aria-label="Direct link to Map services and route your warehouses" title="Direct link to Map services and route your warehouses" translate="no">​</a></h2>
<p>On <strong>Shipping Methods</strong>, pair each delivery service with the SKU.io shipping method it stands for, or leave it on <strong>Rules engine (default)</strong>. On <strong>Warehouses</strong>, turn on routing for each warehouse that ships through Shiptheory. Its address goes on the label as the sender.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/shiptheory/shipping-methods.png" alt="The Shipping Methods tab with Royal Mail, DPD and Evri services paired to SKU.io shipping methods" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="from-submitted-to-booked">From submitted to booked<a href="https://www.sku.io/docs/release-notes/2026/11/12/shiptheory/#from-submitted-to-booked" class="hash-link" aria-label="Direct link to From submitted to booked" title="Direct link to From submitted to booked" translate="no">​</a></h2>
<p>Submit a fulfillment order from a routed warehouse and it appears on the Shiptheory <strong>Orders</strong> tab. Shiptheory has no webhooks, so SKU.io checks for bookings every 5 minutes, or straight away when you click <strong>Refresh from Shiptheory</strong>. A booked order shows <strong>Complete</strong> with its tracking number. One that Shiptheory can't book comes back to the fulfillment order with Shiptheory's reason.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/shiptheory/orders-complete.png" alt="The Shiptheory Orders tab with an order Complete, booked with Royal Mail and a tracking number" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-to-find-it">Where to find it<a href="https://www.sku.io/docs/release-notes/2026/11/12/shiptheory/#where-to-find-it" class="hash-link" aria-label="Direct link to Where to find it" title="Direct link to Where to find it" translate="no">​</a></h2>
<p>Go to <strong>Apps &amp; Integrations → All Integrations</strong> and choose <strong>Shiptheory</strong> under <strong>Shipping &amp; Fulfillment</strong>. After you connect, its tabs cover <strong>Dashboard</strong>, <strong>Orders</strong>, <strong>Shipments</strong>, <strong>Shipping Methods</strong>, <strong>Warehouses</strong> and <strong>Settings</strong>.</p>
<p><strong>Full guide:</strong> <a href="https://www.sku.io/docs/guides/integrations/shiptheory/connect-shiptheory" target="_blank" rel="noopener noreferrer" class="">Connect Shiptheory</a></p>]]></content>
        <author>
            <name>SKU.io Product Team</name>
            <uri>https://sku.io</uri>
        </author>
        <category label="Major Feature" term="Major Feature"/>
        <category label="New" term="New"/>
        <category label="Integrations" term="Integrations"/>
        <category label="Shipping" term="Shipping"/>
        <category label="Fulfillment" term="Fulfillment"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Stockout-adjusted velocity — a sell-out no longer shrinks your next order]]></title>
        <id>https://www.sku.io/docs/release-notes/2026/11/12/stockout-adjusted-velocity/</id>
        <link href="https://www.sku.io/docs/release-notes/2026/11/12/stockout-adjusted-velocity/"/>
        <updated>2026-11-12T04:06:53.000Z</updated>
        <summary type="html"><![CDATA[Demand forecasts can now measure sales velocity over the days a product could actually sell, so best sellers that ran out get reordered at their real demand.]]></summary>
        <content type="html"><![CDATA[<p>Your best sellers are the products most likely to run out, and that used to work against them. While a product is out of stock it sells nothing, and those zero days dragged its average down, so the next suggested order came out too small and it ran out again. Demand Planning now has <strong>Adjust for out-of-stock days</strong>: a forecast measures each product's velocity over the days it could sell, not every day on the calendar. It's on for every new forecast.</p>
<p><strong>✨ What this means for you:</strong></p>
<ul>
<li class=""><strong>Reorder at real demand.</strong> A product that sold 165 units in the 16 days it was in stock plans at about 10 a day, not 5, and its suggested order nearly doubles.</li>
<li class=""><strong>Backorder sales still count.</strong> A day the product was out of stock but still sold counts as a day it could sell.</li>
<li class=""><strong>Guardrails built in.</strong> The adjustment never goes above three times the calendar velocity, and it skips products with too few days in stock to judge.</li>
<li class=""><strong>Every adjusted number explains itself.</strong> A badge on the line and new rows in <strong>Calculation Details</strong> show the days in stock, the calendar velocity and the velocity the order used.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="turn-it-on-in-sales-order-filters">Turn it on in Sales Order Filters<a href="https://www.sku.io/docs/release-notes/2026/11/12/stockout-adjusted-velocity/#turn-it-on-in-sales-order-filters" class="hash-link" aria-label="Direct link to Turn it on in Sales Order Filters" title="Direct link to Turn it on in Sales Order Filters" translate="no">​</a></h2>
<p>The option sits under <strong>Sales Order Filters</strong> in the forecast's configuration, next to <strong>Exclude returns</strong> and <strong>Exclude cancelled</strong>. New forecasts start with it selected. Configurations you saved earlier load with it off, so your existing numbers don't change until you choose.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/stockout-adjusted-velocity/sales-order-filters.png" alt="The Sales Order Filters panel with Exclude returns, Exclude cancelled and Adjust for out-of-stock days selected" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="see-which-lines-it-changed">See which lines it changed<a href="https://www.sku.io/docs/release-notes/2026/11/12/stockout-adjusted-velocity/#see-which-lines-it-changed" class="hash-link" aria-label="Direct link to See which lines it changed" title="Direct link to See which lines it changed" translate="no">​</a></h2>
<p>A badge next to <strong>Avg/d</strong> marks every product the adjustment touched. Hover it for the days in stock and the calendar figure next to the adjusted one. A blue badge means the velocity was adjusted, orange means it hit the 3× cap, so check that line before you order, grey means there were too few days in stock to adjust, and red means the product was out of stock for the whole window.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/stockout-adjusted-velocity/adjusted-badge.png" alt="A forecast line with a blue badge whose tooltip reads In stock 15 days; could sell on 16 days. Calendar 5.32/d → adjusted 10.31/d." class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="check-the-working">Check the working<a href="https://www.sku.io/docs/release-notes/2026/11/12/stockout-adjusted-velocity/#check-the-working" class="hash-link" aria-label="Direct link to Check the working" title="Direct link to Check the working" translate="no">​</a></h2>
<p>Open a line's calculation details to see <strong>In-Stock Days</strong>, <strong>Sellable Days</strong>, <strong>Calendar Velocity</strong>, <strong>Velocity Used</strong> and the outcome. The forecast export carries the same figures when you include calculation details.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/stockout-adjusted-velocity/calculation-details.png" alt="The Sales History section of Calculation Details with In-Stock Days, Sellable Days, Calendar Velocity, Velocity Used and Out-of-Stock Adjustment" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-to-find-it">Where to find it<a href="https://www.sku.io/docs/release-notes/2026/11/12/stockout-adjusted-velocity/#where-to-find-it" class="hash-link" aria-label="Direct link to Where to find it" title="Direct link to Where to find it" translate="no">​</a></h2>
<p>Go to <strong>Inventory → Demand Planning</strong>, open <strong>Sales Order Filters</strong> in the configuration, and build a <strong>Sales Based</strong> forecast.</p>
<p><strong>Full guide:</strong> <a href="https://www.sku.io/docs/guides/inventory/demand-planning/tune-the-forecast/adjust-velocity-for-out-of-stock-days" target="_blank" rel="noopener noreferrer" class="">Adjust velocity for out-of-stock days</a></p>]]></content>
        <author>
            <name>SKU.io Product Team</name>
            <uri>https://sku.io</uri>
        </author>
        <category label="Minor Feature" term="Minor Feature"/>
        <category label="Improved" term="Improved"/>
        <category label="Inventory" term="Inventory"/>
        <category label="Purchasing" term="Purchasing"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Purple Dot pre-orders — your purchase orders and pre-orders finally in step]]></title>
        <id>https://www.sku.io/docs/release-notes/2026/11/12/purple-dot-pre-orders/</id>
        <link href="https://www.sku.io/docs/release-notes/2026/11/12/purple-dot-pre-orders/"/>
        <updated>2026-11-12T00:18:30.000Z</updated>
        <summary type="html"><![CDATA[Connect Purple Dot to SKU.io: held pre-orders join your backorder queue, incoming purchase orders become Purple Dot's planned inventory, and receipts release pre-orders.]]></summary>
        <content type="html"><![CDATA[<p>If you sell pre-orders through Purple Dot, the shopper's order sits in Purple Dot until stock arrives, so your inventory system never sees it. Purchasing can't tell how much incoming stock is already sold, Purple Dot doesn't know when your purchase orders will really land, and when stock arrives someone has to work out by hand how many pre-orders can go out. The new <strong>Purple Dot integration</strong> connects the two. Every held pre-order joins your backorder queue and is covered by a purchase order. Your incoming stock and its dates go to Purple Dot as planned inventory. Receiving stock tells Purple Dot exactly how many pre-orders it may release.</p>
<p><strong>✨ What this means for you:</strong></p>
<ul>
<li class="">Held pre-orders show up in your <strong>backorder queue</strong>, each covered by the purchase order that will fill it, so incoming stock is never promised twice.</li>
<li class="">Your incoming purchase orders (and, if you choose, warehouse transfers) are sent to Purple Dot as <strong>planned inventory</strong> with their expected dates, so it sells against real supply.</li>
<li class="">When a purchase order's date slips, SKU.io <strong>holds the new date for your approval</strong> before Purple Dot emails shoppers.</li>
<li class="">Receiving a purchase order allocates the stock to the waiting pre-orders and tells Purple Dot how many it may <strong>export to Shopify</strong>.</li>
<li class="">When Purple Dot exports a pre-order, the new Shopify order <strong>takes over its reserved stock</strong> instead of being allocated twice.</li>
<li class="">Returned pre-orders can be <strong>refunded through Purple Dot</strong> from the order's return.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="one-dashboard-for-every-held-pre-order">One dashboard for every held pre-order<a href="https://www.sku.io/docs/release-notes/2026/11/12/purple-dot-pre-orders/#one-dashboard-for-every-held-pre-order" class="hash-link" aria-label="Direct link to One dashboard for every held pre-order" title="Direct link to One dashboard for every held pre-order" translate="no">​</a></h2>
<p>Connect Purple Dot from <strong>Apps &amp; Integrations</strong> with your Purple Dot API token and the Shopify store it runs on. A dry run shows exactly what will be sent before anything goes live. After that, the Purple Dot dashboard shows how many pre-orders are held, how many units are covered by purchase orders, and anything that needs you, such as a Purple Dot product that isn't matched to a SKU.io product yet.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/purple-dot-pre-orders/dashboard.png" alt="The Purple Dot dashboard: held pre-orders, units covered by purchase orders, allocated units awaiting export, a Needs attention list and sync health" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="every-pre-order-with-its-coverage-and-status">Every pre-order, with its coverage and status<a href="https://www.sku.io/docs/release-notes/2026/11/12/purple-dot-pre-orders/#every-pre-order-with-its-coverage-and-status" class="hash-link" aria-label="Direct link to Every pre-order, with its coverage and status" title="Direct link to Every pre-order, with its coverage and status" translate="no">​</a></h2>
<p>The <strong>Pre-orders</strong> tab lists each pre-order with its shopper, product, quantity, what covers it (a purchase order line, shelf stock, or the Shopify order it became), its expected date, payment status and state. Filter to uncovered or unmapped pre-orders to see what needs attention, and open any row for its full detail.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/purple-dot-pre-orders/preorders.png" alt="The Pre-orders list showing exported, ready-to-export and held pre-orders with their coverage, payment status and state" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="planned-inventory-that-follows-your-purchase-orders">Planned inventory that follows your purchase orders<a href="https://www.sku.io/docs/release-notes/2026/11/12/purple-dot-pre-orders/#planned-inventory-that-follows-your-purchase-orders" class="hash-link" aria-label="Direct link to Planned inventory that follows your purchase orders" title="Direct link to Planned inventory that follows your purchase orders" translate="no">​</a></h2>
<p>The <strong>Planned inventory</strong> tab shows exactly what SKU.io has sent to Purple Dot: each incoming purchase order or transfer line, the units expected and already arrived, the expected date and the warehouse. It's updated as your purchase orders change. The <strong>Release budgets</strong> and <strong>ETA reviews</strong> views next to it show how many pre-orders Purple Dot may export, and any slipped dates waiting for your approval.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/purple-dot-pre-orders/planned-inventory.png" alt="The Planned inventory tab listing purchase order lines sent to Purple Dot, with expected and arrived units, dates, location and push status" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-to-find-it">Where to find it<a href="https://www.sku.io/docs/release-notes/2026/11/12/purple-dot-pre-orders/#where-to-find-it" class="hash-link" aria-label="Direct link to Where to find it" title="Direct link to Where to find it" translate="no">​</a></h2>
<p>Go to <strong>Apps &amp; Integrations → All Integrations</strong>, search for <strong>Purple Dot</strong> and choose it under <strong>Pre-orders</strong> to connect it. Once it's live, its dashboard, pre-orders, Waitlists, planned inventory, activity and settings are all on the connection's page, and Purple Dot pre-orders appear in <strong>Inventory → Backorder Queue</strong> with their own demand type.</p>
<p><strong>Full guide:</strong> <a href="https://www.sku.io/docs/guides/integrations/purple-dot/connect-purple-dot-pre-orders" target="_blank" rel="noopener noreferrer" class="">Connect Purple Dot pre-orders</a>, with a <a href="https://youtu.be/VpPtfNMz0m8" target="_blank" rel="noopener noreferrer" class="">video walkthrough</a>.</p>]]></content>
        <author>
            <name>SKU.io Product Team</name>
            <uri>https://sku.io</uri>
        </author>
        <category label="Major Feature" term="Major Feature"/>
        <category label="New" term="New"/>
        <category label="Integrations" term="Integrations"/>
        <category label="Inventory" term="Inventory"/>
        <category label="Purchasing" term="Purchasing"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Amazon AWD in the inbound wizard — send stock to AWD without leaving SKU.io]]></title>
        <id>https://www.sku.io/docs/release-notes/2026/11/09/send-stock-to-awd/</id>
        <link href="https://www.sku.io/docs/release-notes/2026/11/09/send-stock-to-awd/"/>
        <updated>2026-11-09T06:10:00.000Z</updated>
        <summary type="html"><![CDATA[Build, confirm, label and track Amazon AWD inbound orders in SKU.io, from the inbound wizard or straight from a purchase order.]]></summary>
        <content type="html"><![CDATA[<p>Sending stock to Amazon Warehousing and Distribution has meant leaving your inventory system: re-keying cases in Seller Central, downloading labels, emailing them to your supplier and then copying the tracking back by hand. Your purchase order, your stock and your AWD shipment all ended up in different places. Now the <strong>inbound wizard sends to AWD as well as FBA</strong>. Choose where the stock ships from and what to send, let Amazon check every case group, then confirm the order, send the labels to your supplier and add the carrier, all in SKU.io.</p>
<p><strong>✨ What this means for you:</strong></p>
<ul>
<li class=""><strong>One wizard for FBA and AWD.</strong> Pick AWD on the same screen you already use for FBA inbound plans.</li>
<li class=""><strong>Start from a purchase order.</strong> Bring a PO's open lines straight into an AWD order instead of retyping them.</li>
<li class=""><strong>Problems show up before you commit.</strong> SKU.io flags products that aren't ready for AWD, and Amazon's check runs on each case group before you confirm.</li>
<li class=""><strong>Labels reach your supplier in one click</strong>, using an email you can edit.</li>
<li class=""><strong>Every AWD order in one list</strong>, whether it came from the wizard, the Send Planner or Seller Central.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="choose-awd-on-the-screen-you-already-know">Choose AWD on the screen you already know<a href="https://www.sku.io/docs/release-notes/2026/11/09/send-stock-to-awd/#choose-awd-on-the-screen-you-already-know" class="hash-link" aria-label="Direct link to Choose AWD on the screen you already know" title="Direct link to Choose AWD on the screen you already know" translate="no">​</a></h2>
<p>Open the inbound wizard and a new <strong>Send To</strong> choice sits next to FBA. Pick <strong>Amazon Warehousing and Distribution (AWD)</strong>, then ship from one of your warehouses or directly from a supplier. AWD takes whole cases and chooses its own warehouse, so the wizard skips the box packing, placement and transport steps that FBA needs.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/send-stock-to-awd/choose-awd.png" alt="The Create New Inbound Plan page with Amazon Warehousing and Distribution selected as the Send To destination, next to FBA fulfillment centers" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="build-the-order-in-whole-cases">Build the order in whole cases<a href="https://www.sku.io/docs/release-notes/2026/11/09/send-stock-to-awd/#build-the-order-in-whole-cases" class="hash-link" aria-label="Direct link to Build the order in whole cases" title="Direct link to Build the order in whole cases" translate="no">​</a></h2>
<p>Add products one by one or bring them in from a purchase order. Each row shows the case pack, case size, number of cases, total units and what's already at AWD, with a <strong>Ready</strong> check so you can see what needs fixing. Missing case details can be added right from the wizard.</p>
<p>Already have the purchase order open? Click <strong>Send to Amazon</strong>, then <strong>Send to Amazon AWD</strong>, and its open lines come across for you. <strong>Send to Amazon FBA</strong> is on the same menu, and when Amazon splits that plan into several shipments, each shipment gets its own purchase order so receiving and costs stay correct.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/send-stock-to-awd/whole-cases.png" alt="The SKU Selection step of an AWD plan created from a purchase order, showing case pack, case size, cases, units, stock at AWD and a Ready check on each product" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="confirm-send-labels-and-add-the-carrier">Confirm, send labels and add the carrier<a href="https://www.sku.io/docs/release-notes/2026/11/09/send-stock-to-awd/#confirm-send-labels-and-add-the-carrier" class="hash-link" aria-label="Direct link to Confirm, send labels and add the carrier" title="Direct link to Confirm, send labels and add the carrier" translate="no">​</a></h2>
<p>When you create the draft, Amazon checks each case group. If it rejects anything, you see which SKU and why, and you can fix it, remove it and retry, or finish in Seller Central. A draft changes nothing at Amazon until you confirm it.</p>
<p>Once you confirm, the shipment, its assigned AWD warehouse and ship-by date appear on one page. Generate one case label per carton, download the PDF or <strong>send it to your supplier</strong>, then add your carrier and tracking and save it back to Amazon. Booking an Amazon Partnered Carrier or AGL ocean freight? <strong>Open in Seller Central</strong> takes you there to book it, and you paste the tracking back in.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/send-stock-to-awd/confirm-and-ship.png" alt="The Confirm and ship page showing a confirmed AWD order, the shipment Amazon created, labels ready to download or send to the supplier, and carrier and tracking fields" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="see-every-awd-order-in-one-place">See every AWD order in one place<a href="https://www.sku.io/docs/release-notes/2026/11/09/send-stock-to-awd/#see-every-awd-order-in-one-place" class="hash-link" aria-label="Direct link to See every AWD order in one place" title="Direct link to See every AWD order in one place" translate="no">​</a></h2>
<p>The new <strong>Inbound Orders</strong> tab lists every AWD inbound order on the account, with cards for drafts, orders confirmed but not shipped, stock in transit and what was received in the last 30 days. Each order shows where it came from and links to its purchase order, and <strong>Track</strong> follows the shipment from created through shipped, in transit, receiving and closed.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/send-stock-to-awd/inbound-orders.png" alt="The AWD Inbound Orders tab with summary cards above a list of orders showing their source, cases, units, status and linked purchase order" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-to-find-it">Where to find it<a href="https://www.sku.io/docs/release-notes/2026/11/09/send-stock-to-awd/#where-to-find-it" class="hash-link" aria-label="Direct link to Where to find it" title="Direct link to Where to find it" translate="no">​</a></h2>
<p>Go to <strong>Apps &amp; Integrations</strong>, open your Amazon connection, click <strong>AWD Inbound</strong>, then <strong>Inbound Orders</strong> and <strong>New AWD inbound</strong>. You can also click <strong>Send to Amazon</strong> on an open purchase order. Your Amazon account needs to be enrolled in AWD, and AWD inbound is available for Amazon US.</p>
<p><strong>Full guide:</strong> <a href="https://www.sku.io/docs/guides/integrations/amazon/awd/send-stock-to-awd-from-the-inbound-wizard" target="_blank" rel="noopener noreferrer" class="">Send stock to AWD from the inbound wizard</a></p>]]></content>
        <author>
            <name>SKU.io Product Team</name>
            <uri>https://sku.io</uri>
        </author>
        <category label="Major Feature" term="Major Feature"/>
        <category label="New" term="New"/>
        <category label="Integrations" term="Integrations"/>
        <category label="Inventory" term="Inventory"/>
        <category label="Purchasing" term="Purchasing"/>
        <category label="Shipping" term="Shipping"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Repairs & Warranty — run every repair from claim to credit in SKU.io]]></title>
        <id>https://www.sku.io/docs/release-notes/2026/11/08/repairs-and-warranty/</id>
        <link href="https://www.sku.io/docs/release-notes/2026/11/08/repairs-and-warranty/"/>
        <updated>2026-11-08T16:24:38.000Z</updated>
        <summary type="html"><![CDATA[Take in repair and warranty claims from any channel, check coverage, work them on your bench or at a vendor, and see what your guarantee really costs.]]></summary>
        <content type="html"><![CDATA[<p>If you stand behind what you sell, repairs tend to live outside your system: a spreadsheet of who sent what, an inbox of "where's my piece?", and no real answer to what your guarantee costs. Send a customer's item through a normal return and it can even end up counted as your own stock. <strong>Repairs &amp; Warranty</strong> gives after-sales its own home in SKU.io. Every claim, from any channel, gets a coverage decision, a place on the board, a cost record, and a clear ending — repaired and returned, replaced, credited, or written off.</p>
<p><strong>✨ What this means for you:</strong></p>
<ul>
<li class=""><strong>One queue for every claim</strong> — your own repair form, the Customer Portal for wholesale buyers, the Receive Station, Gorgias, Loop Returns, AfterShip Warranty, Corso, Claimlane, or your own system through the API.</li>
<li class=""><strong>Coverage answered for you</strong> — warranty policies and registrations decide whether a piece is in warranty, so nobody checks purchase dates by hand.</li>
<li class=""><strong>A customer's item stays the customer's</strong> — a piece sent in for repair is never counted as your stock.</li>
<li class=""><strong>Every cost in the right place</strong> — parts, labour and freight are recorded on the repair and billed to warranty or to the customer.</li>
<li class=""><strong>Money back from suppliers</strong> — charge manufacturing defects back to the supplier that made them, and spot failing products and lots early.</li>
<li class=""><strong>Customers kept in the loop</strong> — a status page they can follow, and emails you can edit.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="one-list-and-one-board-for-every-repair">One list and one board for every repair<a href="https://www.sku.io/docs/release-notes/2026/11/08/repairs-and-warranty/#one-list-and-one-board-for-every-repair" class="hash-link" aria-label="Direct link to One list and one board for every repair" title="Direct link to One list and one board for every repair" translate="no">​</a></h2>
<p><strong>Orders → Repairs</strong> shows every piece in repair with its coverage, stage, turnaround clock and technician. Filter it, save a view such as <em>My queue</em> or <em>Overdue</em>, and act on several repairs at once.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/repairs-and-warranty/repairs-list.png" alt="The Repairs list showing each repair's customer, unit, issue, coverage, stage, turnaround clock and status" class="img_ev3q"></p>
<p>Prefer to see the work move? The <strong>Board</strong> gives each piece one card and a column for every stage, from <em>Pending receipt</em> to <em>In repair</em> and beyond. Drag a card to move it on. Technicians get a <strong>Bench</strong> view of their own queue, where they can scan a repair tag to pull up the next job.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/repairs-and-warranty/board.png" alt="The Repair board with a card for each piece under stages such as Pending receipt, Triage, Diagnosing, Awaiting approval and Awaiting parts" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="everything-about-a-repair-on-one-page">Everything about a repair on one page<a href="https://www.sku.io/docs/release-notes/2026/11/08/repairs-and-warranty/#everything-about-a-repair-on-one-page" class="hash-link" aria-label="Direct link to Everything about a repair on one page" title="Direct link to Everything about a repair on one page" translate="no">​</a></h2>
<p>A repair's own page holds the whole story: the turnaround clock, what's been spent so far, linked records, photos, notes and every email sent. SKU.io suggests the next message to send, and each customer gets a status page where they can follow their repair, approve quotes and add photos.</p>
<p>From here you diagnose each unit against your inspection checklists, add parts and labour, and quote the customer when the repair isn't covered. Then choose how it ends.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/repairs-and-warranty/repair-detail.png" alt="A repair's page showing its coverage, turnaround clock, costs to date, linked records, customer status page and a suggested next message" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="send-work-out-and-get-your-money-back">Send work out, and get your money back<a href="https://www.sku.io/docs/release-notes/2026/11/08/repairs-and-warranty/#send-work-out-and-get-your-money-back" class="hash-link" aria-label="Direct link to Send work out, and get your money back" title="Direct link to Send work out, and get your money back" translate="no">​</a></h2>
<p>When a piece needs outside work, a <strong>vendor dispatch</strong> tracks it there and back, and a <strong>plating batch</strong> groups pieces of the same finish into one trip.</p>
<p>If the fault was the supplier's, <strong>Supplier recovery</strong> gathers those units by supplier, with the unit cost and the repair cost next to each one. Raise a claim, record the supplier's answer, and settle it. The <strong>Quality spikes</strong> tab flags products and suppliers failing more often than usual.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/repairs-and-warranty/supplier-recovery.png" alt="Supplier recovery showing amounts claimed and recovered, with defective units grouped by supplier, ready to claim" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="finally-see-what-your-guarantee-costs">Finally see what your guarantee costs<a href="https://www.sku.io/docs/release-notes/2026/11/08/repairs-and-warranty/#finally-see-what-your-guarantee-costs" class="hash-link" aria-label="Direct link to Finally see what your guarantee costs" title="Direct link to Finally see what your guarantee costs" translate="no">​</a></h2>
<p>The repairs <strong>Dashboard</strong> and reports cover repair rates, warranty cost, margin, turnaround and technician productivity. If you accrue for future warranty costs, the <strong>Warranty reserve</strong> page shows the balance, runs each month's accrual, and lets you post a true-up.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-to-find-it">Where to find it<a href="https://www.sku.io/docs/release-notes/2026/11/08/repairs-and-warranty/#where-to-find-it" class="hash-link" aria-label="Direct link to Where to find it" title="Direct link to Where to find it" translate="no">​</a></h2>
<ul>
<li class=""><strong>Repairs:</strong> <strong>Orders → Repairs</strong> — List, Board, Bench, Dashboard, Registrations, Vendor dispatches, Supplier recovery and Warranty reserve.</li>
<li class=""><strong>Set it up:</strong> <strong>Settings → Repairs &amp; Warranty</strong> — warranty policies, issue types, inspection checklists, turnaround targets, rates, your customer repair portal and claim sources.</li>
<li class=""><strong>In the app:</strong> press <strong>H</strong> on a Repairs screen to open its guide and video.</li>
</ul>
<p><strong>Full guide:</strong> <a href="https://www.sku.io/docs/guides/orders/repairs" target="_blank" rel="noopener noreferrer" class="">Repairs &amp; Warranty overview</a></p>]]></content>
        <author>
            <name>SKU.io Product Team</name>
            <uri>https://sku.io</uri>
        </author>
        <category label="Major Feature" term="Major Feature"/>
        <category label="New" term="New"/>
        <category label="Orders" term="Orders"/>
        <category label="Inventory" term="Inventory"/>
        <category label="Accounting" term="Accounting"/>
        <category label="Reporting" term="Reporting"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Bills for every supplier cost — enter, read, sync and track them in one place]]></title>
        <id>https://www.sku.io/docs/release-notes/2026/11/07/generic-bills/</id>
        <link href="https://www.sku.io/docs/release-notes/2026/11/07/generic-bills/"/>
        <updated>2026-11-07T18:51:57.000Z</updated>
        <summary type="html"><![CDATA[Bills now cover rent, software, marketing and 3PL fees as well as landed costs, with a plain view of what each bill does to your books.]]></summary>
        <content type="html"><![CDATA[<p>Until now, a bill in SKU.io had to hang off a purchase order: freight, duty and other landed costs. Everything else your suppliers send, like the warehouse rent, the ad agency or the monthly 3PL fee, had to be entered in your accounting system, and again in SKU.io if you wanted it in your profit numbers. <strong>Bills</strong> now handles any supplier cost. Enter an <strong>expense bill</strong> with no purchase order, read it from the invoice, send it to Xero or QuickBooks, and track its cost against the products it relates to. If your team prefers to keep entering bills in Xero or QuickBooks, a new review finds the bills SKU.io doesn't know about yet and brings them in without changing anything in your accounting system.</p>
<p><strong>✨ What this means for you:</strong></p>
<ul>
<li class=""><strong>Enter each bill once.</strong> Expense bills and landed cost bills live on one <strong>Bills</strong> list, with a <strong>Type</strong> column so you can tell them apart.</li>
<li class=""><strong>Know what a bill does to your books before you save it.</strong> A <strong>What this does to your books</strong> panel shows the debit and credit lines and the posting date, and states whether the bill reaches Xero.</li>
<li class=""><strong>No accidental stock costs.</strong> An expense bill needs an expense account, and SKU.io refuses inventory and clearing accounts, so a service charge can't end up in your stock value.</li>
<li class=""><strong>Choose who enters bills.</strong> Send bills from SKU.io to Xero or QuickBooks, keep entering them there, or keep them in SKU.io only, with exceptions by supplier.</li>
<li class=""><strong>Bring in the bills you already have.</strong> <strong>Find bills in Xero</strong> (or QuickBooks) lists the bills SKU.io doesn't know about and lets you classify each one. Nothing is written back to your accounting system.</li>
<li class=""><strong>Put overhead into product profit.</strong> Turn bill lines into cost entries, and let AI suggest how to allocate them. Nothing is allocated until a person confirms it.</li>
<li class=""><strong>A more accurate Unallocated figure.</strong> Unallocated now counts landed cost bills only. Expense bills were never meant to be allocated to purchase lines, so if you had expense bills, this figure drops. Your landed cost bills are unchanged.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="one-list-for-every-bill">One list for every bill<a href="https://www.sku.io/docs/release-notes/2026/11/07/generic-bills/#one-list-for-every-bill" class="hash-link" aria-label="Direct link to One list for every bill" title="Direct link to One list for every bill" translate="no">​</a></h2>
<p>The <strong>Bills</strong> list (formerly Landed Cost Bills) shows both kinds of bill. Amber <strong>Expense</strong> bills are supplier costs with no purchase document. Blue <strong>Landed cost</strong> bills add freight, duty and similar charges to a purchase order's inventory cost, the same way they always have. Switch between <strong>All</strong>, <strong>Expense</strong> and <strong>Landed cost</strong> above the table.</p>
<p>Two new columns show where each bill stands. <strong>Accounting</strong> shows whether it's in Xero, booked in Xero, waiting on you, or kept in SKU.io only. <strong>Cost tracking</strong> shows how much of an expense bill is tracked against your products. The cards at the top separate unpaid expense bills from unpaid landed cost bills and count the bills that need your attention. Your existing filters and saved views keep working, and a new <strong>No purchase document</strong> option in the Linked To filter finds expense bills.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/generic-bills/bills-list.png" alt="The Bills list with Type, Accounting and Cost tracking columns, an All / Expense / Landed cost switch, and summary cards for unpaid expense bills, unpaid landed cost bills, bills needing attention and costs not tracked yet" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="enter-a-bill-and-see-what-it-does-to-your-books">Enter a bill and see what it does to your books<a href="https://www.sku.io/docs/release-notes/2026/11/07/generic-bills/#enter-a-bill-and-see-what-it-does-to-your-books" class="hash-link" aria-label="Direct link to Enter a bill and see what it does to your books" title="Direct link to Enter a bill and see what it does to your books" translate="no">​</a></h2>
<p>Click <strong>New bill</strong> to enter an expense bill: supplier, invoice number, dates, currency, payment term, and lines with an expense account, amount, tax and channel. The <strong>What this does to your books</strong> panel on the right updates as you type. It shows the accounts debited and credited, the date the bill posts, and whether it goes to Xero. If the bill is dated in a locked period, you see the first open day it posts on before you save.</p>
<p>SKU.io also checks for duplicates as you enter the bill. A bill from the same supplier with the same amount and a nearby date is flagged, and you can open it or mark it <strong>Not a duplicate</strong>. Invoice numbers only need to be unique for each supplier, so two suppliers can both send you an "INV-1001".</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/generic-bills/new-bill-books-panel.png" alt="The New bill page with a rent line for a service supplier, a possible-duplicate warning, and the What this does to your books panel showing a debit to Rent, a credit to Accounts payable and the posting date" class="img_ev3q"></p>
<p>Expense bills are for service suppliers. If you pick a supplier that sells you stock, SKU.io points you to the purchase order instead, so freight and duty still go into inventory cost.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="start-from-the-invoice">Start from the invoice<a href="https://www.sku.io/docs/release-notes/2026/11/07/generic-bills/#start-from-the-invoice" class="hash-link" aria-label="Direct link to Start from the invoice" title="Direct link to Start from the invoice" translate="no">​</a></h2>
<p>Have the PDF? Click <strong>Upload invoice</strong> and drop in the file. With invoice OCR turned on, SKU.io reads it and opens <strong>Review invoice</strong>, with the invoice on the left and a draft bill on the right: the supplier name as it was read, invoice number, invoice date, due date, total, tax and every line. A value SKU.io isn't sure of is highlighted and tells you how confident the read was, so you know exactly what to check. Each line needs an expense account. SKU.io suggests one when this supplier's earlier bills or a cost category point to it, and asks you to pick one otherwise. <strong>Create bill</strong> stays off until the lines and tax add up to the invoice total. The file stays attached to the bill.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/generic-bills/ocr-review.png" alt="The Review invoice page with a freight invoice on the left and the extracted bill on the right: supplier read as &quot;Northwind Freight&quot;, invoice number, dates, a total flagged at 53% confidence, four lines waiting for an expense account, and a check that the lines add up to the invoice total" class="img_ev3q"></p>
<p>When invoice OCR is off, the file is simply attached and you enter the bill by hand.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="decide-who-enters-bills-skuio-or-your-accounting-system">Decide who enters bills: SKU.io or your accounting system<a href="https://www.sku.io/docs/release-notes/2026/11/07/generic-bills/#decide-who-enters-bills-skuio-or-your-accounting-system" class="hash-link" aria-label="Direct link to Decide who enters bills: SKU.io or your accounting system" title="Direct link to Decide who enters bills: SKU.io or your accounting system" translate="no">​</a></h2>
<p>Under <strong>Expense bills: who enters them?</strong> in your accounting sync settings, choose how expense bills are handled for your Xero or QuickBooks connection:</p>
<ul>
<li class=""><strong>Send to Xero / QuickBooks:</strong> enter bills in SKU.io, and SKU.io creates them in your accounting system. A <strong>Start from</strong> date leaves older bills alone.</li>
<li class=""><strong>Keep entering in Xero / QuickBooks:</strong> your accounting system stays in charge. SKU.io never sends these bills, and the review below brings them in.</li>
<li class=""><strong>Keep in SKU.io only:</strong> nothing moves.</li>
</ul>
<p>Add a <strong>supplier rule</strong> when one supplier needs different handling from the rest. Bills that look like one already in your accounting system wait under <strong>Possible duplicates</strong> for you to decide. Landed cost bills keep their own separate switch, so your current setting carries over.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="find-bills-in-xero-or-quickbooks">Find bills in Xero or QuickBooks<a href="https://www.sku.io/docs/release-notes/2026/11/07/generic-bills/#find-bills-in-xero-or-quickbooks" class="hash-link" aria-label="Direct link to Find bills in Xero or QuickBooks" title="Direct link to Find bills in Xero or QuickBooks" translate="no">​</a></h2>
<p><strong>Find bills in Xero</strong> (or <strong>Find bills in QuickBooks</strong>) on the Bills list reviews your accounting system for bills SKU.io doesn't have yet, in three steps:</p>
<ol>
<li class=""><strong>Classify.</strong> Bills are grouped by supplier, with the number of bills and their total. <strong>What Xero has</strong> shows at a glance how many carry a number, line detail and a file, and <strong>Why</strong> explains the suggestion for each supplier. Choose <strong>Expense bill</strong>, <strong>Purchase invoice</strong> or <strong>Ignore</strong> under <strong>Treat as</strong>, expand a supplier to decide bill by bill, and <strong>Create or match a supplier</strong> when the supplier isn't in SKU.io yet. <strong>Save and finish later</strong> keeps your progress.</li>
<li class=""><strong>Add invoices.</strong> Bills in accounting systems often carry little detail. Drop in the real invoices, and SKU.io matches them to the bills and keeps the extra detail for cost tracking. Your accounting system's amounts always stay as they are.</li>
<li class=""><strong>Confirm.</strong> Review the counts and bring the bills in.</li>
</ol>
<p>Nothing goes back to Xero or QuickBooks, whatever you choose. Bills brought in this way are marked <strong>Booked in Xero</strong> (or QuickBooks): their amounts, lines and payments stay in step with your accounting system, while you can still add documents and notes and track their cost. If a bill changes in your accounting system after you bring it in, the review lists the change and lets you choose what to do.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/generic-bills/find-bills-in-xero.png" alt="The Find bills in Xero page on the Classify step: 42 bills totalling $25,661.38 grouped by supplier, each with its bill count, total, what Xero has (number, detail, file), a Treat as choice and the reason for the suggestion" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="track-bill-costs-against-your-products">Track bill costs against your products<a href="https://www.sku.io/docs/release-notes/2026/11/07/generic-bills/#track-bill-costs-against-your-products" class="hash-link" aria-label="Direct link to Track bill costs against your products" title="Direct link to Track bill costs against your products" translate="no">​</a></h2>
<p>Click <strong>Track as cost entries</strong> on an expense bill to turn its lines into cost entries, then allocate them to products so marketing, storage and fulfillment fees show up in product profitability. The bill's <strong>Cost tracking</strong> tab shows how much of each line is tracked, how much is already on orders as cost lines, and how much is left. A dollar is never counted twice, and tax is left out. Tracking and allocating never touch your accounts; only the bill reaches Xero. Landed cost bills already count in inventory cost, so they can't be tracked this way too.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/generic-bills/cost-tracking.png" alt="The Cost tracking tab on an expense bill showing the bill total, the amounts on cost entries and on orders, each line's availability, and an Allocate with AI button on each cost entry" class="img_ev3q"></p>
<p><strong>Allocate with AI</strong> suggests where each line of a cost entry belongs. Every suggestion shows the product, a confidence level and <strong>why</strong>: for example, the SKU matched exactly, the product existed before the period ended, and it had stock on hand. SKU.io only suggests products that existed and were active during the billed period. Lines it can't place stay unallocated with a reason, such as <strong>Not yet created</strong> for a product launched after the period, or <strong>Account fee</strong> for a charge no product caused. High-confidence lines start selected. Change any target you disagree with, then click <strong>Confirm allocations</strong>, or <strong>Reject all</strong>. Nothing is saved until you confirm, and confirming writes cost allocations only: nothing is posted to your accounting system.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/generic-bills/ai-allocation.png" alt="The Allocate with AI review on a cost entry: four pick-fee lines matched to products at high confidence with the evidence for each, one line held as &quot;Not yet created&quot;, one held as &quot;Account fee&quot;, and a Confirm 4 allocations button" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="importing-bills">Importing bills<a href="https://www.sku.io/docs/release-notes/2026/11/07/generic-bills/#importing-bills" class="hash-link" aria-label="Direct link to Importing bills" title="Direct link to Importing bills" translate="no">​</a></h2>
<p><strong>Import Bills</strong> now handles expense bills too: leave Linked Document blank and give each line an expense account. Bill imports are all or nothing. If any row has a problem, nothing in the file is imported, and every row shows what needs fixing ("Nothing was imported. Fix the rows below and import again."). This means a half-imported file can never leave you with a partly updated bill. Bill payment imports still go row by row.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-to-find-it">Where to find it<a href="https://www.sku.io/docs/release-notes/2026/11/07/generic-bills/#where-to-find-it" class="hash-link" aria-label="Direct link to Where to find it" title="Direct link to Where to find it" translate="no">​</a></h2>
<ul>
<li class=""><strong>Bills list:</strong> <strong>Orders → Bills</strong>.</li>
<li class=""><strong>Enter an expense bill:</strong> <strong>Orders → Bills → New bill</strong>, or <strong>Upload invoice</strong> to start from a PDF.</li>
<li class=""><strong>Review bills already in your accounting system:</strong> <strong>Orders → Bills → Find bills in Xero</strong> (or <strong>Find bills in QuickBooks</strong>).</li>
<li class=""><strong>Choose who enters bills:</strong> <strong>Accounting → Settings → Sync</strong>, under <strong>Bills</strong>.</li>
<li class=""><strong>Turn on invoice reading:</strong> <strong>Settings → Purchasing → Document OCR</strong>.</li>
<li class=""><strong>Track and allocate a bill's cost:</strong> open an expense bill and click <strong>Track as cost entries</strong>, then use its <strong>Cost tracking</strong> tab.</li>
<li class=""><strong>Landed cost bills:</strong> see <a href="https://www.sku.io/docs/guides/orders/landed-cost-bills/record-landed-cost-bills" target="_blank" rel="noopener noreferrer" class="">Record landed cost bills</a>.</li>
</ul>
<p><strong>Full guides:</strong> <a href="https://www.sku.io/docs/guides/orders/landed-cost-bills/enter-an-expense-bill" target="_blank" rel="noopener noreferrer" class="">Enter an expense bill</a> · <a href="https://www.sku.io/docs/guides/orders/landed-cost-bills/track-an-expense-bill-as-cost-entries" target="_blank" rel="noopener noreferrer" class="">Track an expense bill as cost entries</a> · <a href="https://www.sku.io/docs/guides/orders/landed-cost-bills/choose-how-expense-bills-sync" target="_blank" rel="noopener noreferrer" class="">Choose how expense bills sync</a> · <a href="https://www.sku.io/docs/guides/orders/landed-cost-bills/find-bills-in-xero-or-quickbooks" target="_blank" rel="noopener noreferrer" class="">Find bills in Xero or QuickBooks</a> · <a href="https://www.sku.io/docs/guides/orders/landed-cost-bills/import-landed-cost-bills" target="_blank" rel="noopener noreferrer" class="">Import bills</a></p>]]></content>
        <author>
            <name>SKU.io Product Team</name>
            <uri>https://sku.io</uri>
        </author>
        <category label="Major Feature" term="Major Feature"/>
        <category label="New" term="New"/>
        <category label="Purchasing" term="Purchasing"/>
        <category label="Accounting" term="Accounting"/>
        <category label="Integrations" term="Integrations"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Product lifecycle — retire products cleanly and sell through what's left]]></title>
        <id>https://www.sku.io/docs/release-notes/2026/11/06/product-lifecycle/</id>
        <link href="https://www.sku.io/docs/release-notes/2026/11/06/product-lifecycle/"/>
        <updated>2026-11-06T19:48:53.000Z</updated>
        <summary type="html"><![CDATA[Phase out or discontinue products, see the impact first, hand their history to a successor, and clear the remaining stock with markdowns and closeout offers.]]></summary>
        <content type="html"><![CDATA[<p>Every catalog has products on the way out, and until now "discontinued" mostly meant remembering not to reorder something. Open purchase orders kept arriving, backorders kept piling up, the replacement product started with no sales history, and the leftover stock sat in the warehouse until someone noticed. <strong>Product lifecycle</strong> gives every product a state — <strong>Active</strong>, <strong>Phasing out</strong> or <strong>Discontinued</strong>, plus any of your own — and SKU.io acts on it: it stops reordering, shows you exactly what a change will affect before you confirm it, and gives you one place to watch the remaining stock sell through and clear it with markdowns or a closeout offer.</p>
<p><strong>✨ What this means for you:</strong></p>
<ul>
<li class=""><strong>See the impact before you commit.</strong> Discontinuing a product shows how much stock keeps selling, which purchase order lines and backorders are still open, and which wholesale customers bought it — and can cancel and notify in the same step.</li>
<li class=""><strong>Plan a final buy.</strong> Phase a product out with a discontinue date: SKU.io plans demand only up to that date, and switches it to Discontinued on the day.</li>
<li class=""><strong>Hand over to the replacement.</strong> Link a successor so the new product inherits the old one's sales history for planning, uses up the old stock first and can be substituted on orders.</li>
<li class=""><strong>Change one product or hundreds</strong> — now, on a date, or in bulk from the products list — and undo a change if you got it wrong.</li>
<li class=""><strong>Sell through what's left</strong> with clearance plans that step prices down for your approval, closeout catalogs, PDF linesheets and emailed offers to wholesale buyers.</li>
<li class=""><strong>Let SKU.io spot candidates.</strong> Suggestions flag products that look ready to phase out, and seasons show what carries over and what to end.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="know-what-a-change-does-before-you-make-it">Know what a change does before you make it<a href="https://www.sku.io/docs/release-notes/2026/11/06/product-lifecycle/#know-what-a-change-does-before-you-make-it" class="hash-link" aria-label="Direct link to Know what a change does before you make it" title="Direct link to Know what a change does before you make it" translate="no">​</a></h2>
<p>Choose <strong>Change lifecycle…</strong> on a product and the dialog works out the impact live: how many units keep selling and where they are, which open purchase order lines are still to be received, which backorders are waiting, and which wholesale customers bought the product recently. Tick the follow-ups you want — cancel the unreceived PO lines, cancel the backorders, email the customers — and they happen together with the change. Apply it now, or schedule it for a date and SKU.io applies it for you.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/product-lifecycle/impact-preview.png" alt="The Change lifecycle dialog with Discontinued selected and an Impact panel listing stock that keeps selling, an open PO line to cancel, an open backorder and a wholesale customer to notify" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="watch-the-leftovers-sell-through">Watch the leftovers sell through<a href="https://www.sku.io/docs/release-notes/2026/11/06/product-lifecycle/#watch-the-leftovers-sell-through" class="hash-link" aria-label="Direct link to Watch the leftovers sell through" title="Direct link to Watch the leftovers sell through" translate="no">​</a></h2>
<p><strong>PIM → Lifecycle</strong> gathers everything that's on its way out. Sell-through shows each phasing-out and discontinued product with what's on hand, its value, how fast it's selling, when it's projected to sell out and whether it's <strong>on track</strong>, <strong>at risk</strong> or <strong>stalled</strong>. Next to it are the scheduled changes, the suggestions, the successor links and an FBA checklist for getting discontinued stock out of Amazon before the next aged-inventory surcharge.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/product-lifecycle/sell-through.png" alt="The Lifecycle workspace's Sell-through tab: summary cards for phasing out, discontinued and at-risk products, and a table of sell-through, value, velocity, cover, projected sell-out and status" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="clear-stock-with-markdowns-you-approve">Clear stock with markdowns you approve<a href="https://www.sku.io/docs/release-notes/2026/11/06/product-lifecycle/#clear-stock-with-markdowns-you-approve" class="hash-link" aria-label="Direct link to Clear stock with markdowns you approve" title="Direct link to Clear stock with markdowns you approve" translate="no">​</a></h2>
<p>A <strong>clearance plan</strong> steps prices down on a schedule — for example 25% off at the start, then deeper if a product isn't selling. Each step is proposed for your review with the price, the "was" price that will show beside it, and the reason. Prices below landed cost are held for you to decide, and nothing reaches your channels until you approve it. For what's still left, export a closeout list, build a PDF linesheet, publish a closeout catalog on your B2B portal, or email an offer to your wholesale buyers.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/product-lifecycle/markdown-review.png" alt="A clearance plan's Review tab listing proposed markdowns with current, proposed and &quot;was&quot; prices, and one held because it would sell below landed cost" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="set-it-up-the-way-you-work">Set it up the way you work<a href="https://www.sku.io/docs/release-notes/2026/11/06/product-lifecycle/#set-it-up-the-way-you-work" class="hash-link" aria-label="Direct link to Set it up the way you work" title="Direct link to Set it up the way you work" translate="no">​</a></h2>
<p>Under <strong>Settings → Products → Product Lifecycle</strong> you decide what each state allows, add your own states such as a quality hold, choose what each sales channel does when a discontinued product sells out — keep the listing at zero, end it, or end it and archive the product — and set up Shopify touches like a "Final stock" label or redirecting a sold-out page to its replacement.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-to-find-it">Where to find it<a href="https://www.sku.io/docs/release-notes/2026/11/06/product-lifecycle/#where-to-find-it" class="hash-link" aria-label="Direct link to Where to find it" title="Direct link to Where to find it" translate="no">​</a></h2>
<ul>
<li class=""><strong>Change a product's lifecycle:</strong> open the product and click <strong>Actions → Change lifecycle…</strong>, or select products on <strong>PIM → Products</strong> and click <strong>Change lifecycle</strong> in the bar above the table.</li>
<li class=""><strong>Watch sell-through, scheduled changes and suggestions:</strong> <strong>PIM → Lifecycle</strong>.</li>
<li class=""><strong>Markdowns:</strong> <strong>PIM → Clearance Plans</strong>.</li>
<li class=""><strong>Settings:</strong> <strong>Settings → Products → Product Lifecycle</strong>.</li>
</ul>
<p><strong>Full guide:</strong> <a href="https://www.sku.io/docs/guides/products/lifecycle/" target="_blank" rel="noopener noreferrer" class="">Product lifecycle</a></p>]]></content>
        <author>
            <name>SKU.io Product Team</name>
            <uri>https://sku.io</uri>
        </author>
        <category label="Major Feature" term="Major Feature"/>
        <category label="New" term="New"/>
        <category label="Inventory" term="Inventory"/>
        <category label="Purchasing" term="Purchasing"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Ship with preorder — stop parking shelf stock on orders that can't ship yet]]></title>
        <id>https://www.sku.io/docs/release-notes/2026/11/05/ship-with-preorder/</id>
        <link href="https://www.sku.io/docs/release-notes/2026/11/05/ship-with-preorder/"/>
        <updated>2026-11-05T15:06:20.000Z</updated>
        <summary type="html"><![CDATA[When an order is already waiting on a preorder item, SKU.io can reserve its in-stock items from an incoming PO instead, so shelf stock ships to orders that are ready now.]]></summary>
        <content type="html"><![CDATA[<p>A customer orders a throw that's on your shelf and a table that's on preorder. The order can't ship until the table arrives, but the throw still comes off your shelf and sits there for weeks. Meanwhile a newer order that only wants the throw gets backordered, and your store shows it as out of stock or on preorder while a unit is sitting in the warehouse. <strong>Ship with preorder</strong> fixes that. When an incoming purchase order for the in-stock item will arrive in time for the preorder item, SKU.io reserves the in-stock item from that purchase order instead of the shelf. The order still ships at about the same time, and the shelf unit goes to the next order waiting for it or stays free to sell.</p>
<p><strong>✨ What this means for you:</strong></p>
<ul>
<li class=""><strong>Shelf stock goes to orders that can ship today</strong>, not to orders that are waiting weeks for a preorder item anyway.</li>
<li class=""><strong>Your sales channels keep selling what's physically on hand.</strong> A freed unit counts as available again, so Shopify and your other channels no longer show it as preorder.</li>
<li class=""><strong>Delivery promises hold.</strong> A line is only moved to a purchase order that arrives by the preorder item's ETA (or within a few days of it, if you allow that).</li>
<li class=""><strong>Nothing moves without your review.</strong> Preview every open order first, export the list, and apply only when you're happy.</li>
<li class=""><strong>SKU.io keeps it right as dates change.</strong> If a purchase order slips, it moves the line to another purchase order, puts it back on the shelf, or flags it for you.</li>
<li class=""><strong>Received stock goes where it was promised.</strong> When the purchase order lands, its units go to the lines reserved from it first.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="choose-how-it-works">Choose how it works<a href="https://www.sku.io/docs/release-notes/2026/11/05/ship-with-preorder/#choose-how-it-works" class="hash-link" aria-label="Direct link to Choose how it works" title="Direct link to Choose how it works" translate="no">​</a></h2>
<p>Ship with preorder is off until you switch it on, and it lives in its own section of the backorder settings. Set how many days after the preorder ETA an incoming purchase order may arrive (0 means it must arrive by the preorder ETA). You can also count only stock already on an inbound shipment marked <strong>In Transit</strong>, and choose how orders on hold are treated.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/ship-with-preorder/settings.png" alt="The Ship with preorder settings: the master switch, the arrival window in days, the In Transit switch, and three choices for orders on hold" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="preview-before-anything-moves">Preview before anything moves<a href="https://www.sku.io/docs/release-notes/2026/11/05/ship-with-preorder/#preview-before-anything-moves" class="hash-link" aria-label="Direct link to Preview before anything moves" title="Direct link to Preview before anything moves" translate="no">​</a></h2>
<p>Click <strong>Preview open orders</strong> for a dry run across every open order. The preview counts the orders, lines and shelf units it would free. Each row shows the in-stock line, the purchase order it would be reserved from with its ETA, the preorder item it ships with, and which order is likely to get the freed unit. Export it to CSV to share with your team, then apply it once the feature is on. Each line is checked again as it's applied, and anything that no longer qualifies is skipped.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/ship-with-preorder/preview.png" alt="A ready preview with summary cards for orders affected, lines, units freed, SKUs and POs used, above one row per line that would move" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="see-it-on-every-order">See it on every order<a href="https://www.sku.io/docs/release-notes/2026/11/05/ship-with-preorder/#see-it-on-every-order" class="hash-link" aria-label="Direct link to See it on every order" title="Direct link to See it on every order" translate="no">​</a></h2>
<p>A line reserved this way shows a blue <strong>Ships with preorder</strong> chip on the sales order. Click it to see which purchase order the line is reserved from, the preorder item it ships with, and both ETAs. If you'd rather ship that line from the shelf, click <strong>Use shelf stock instead</strong>, and SKU.io won't move it again. On the purchase order, the same sales orders are listed in the line's allocation coverage, so the incoming units are never promised twice.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/ship-with-preorder/chip-popover.png" alt="The Ships with preorder popover on a sales order line, naming the purchase order, the preorder item it ships with, and a Use shelf stock instead button" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="know-when-a-purchase-order-slips">Know when a purchase order slips<a href="https://www.sku.io/docs/release-notes/2026/11/05/ship-with-preorder/#know-when-a-purchase-order-slips" class="hash-link" aria-label="Direct link to Know when a purchase order slips" title="Direct link to Know when a purchase order slips" translate="no">​</a></h2>
<p>SKU.io re-checks a line whenever its purchase order or inbound shipment changes, and again every night. If a purchase order no longer arrives in time and no other one fits, the line goes back to shelf stock when there's free stock. If there isn't, it stays as a normal backorder and appears under <strong>Needs attention</strong> with the reason, such as "PO slipped past the preorder ETA". <strong>Active</strong> lists every line shipping with a preorder item, and <strong>History</strong> records every change.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/ship-with-preorder/needs-attention.png" alt="The Needs attention view listing a line whose purchase order slipped past the preorder ETA, with the reason and a Dismiss button" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-to-find-it">Where to find it<a href="https://www.sku.io/docs/release-notes/2026/11/05/ship-with-preorder/#where-to-find-it" class="hash-link" aria-label="Direct link to Where to find it" title="Direct link to Where to find it" translate="no">​</a></h2>
<ul>
<li class=""><strong>Settings and preview:</strong> <strong>Inventory → Backorder Queue → Settings</strong>, then the <strong>Ship with preorder</strong> section.</li>
<li class=""><strong>Previews, active lines, flagged lines and history:</strong> <strong>Inventory → Backorder Queue → Ship with preorder</strong>.</li>
<li class=""><strong>On an order:</strong> the <strong>Ships with preorder</strong> chip under the line's SKU.</li>
</ul>
<p><strong>Full guide:</strong> <a href="https://www.sku.io/docs/guides/inventory/allocations-and-backorders/ship-in-stock-items-with-a-preorder" target="_blank" rel="noopener noreferrer" class="">Ship in-stock items with a preorder</a></p>]]></content>
        <author>
            <name>SKU.io Product Team</name>
            <uri>https://sku.io</uri>
        </author>
        <category label="Major Feature" term="Major Feature"/>
        <category label="New" term="New"/>
        <category label="Inventory" term="Inventory"/>
        <category label="Orders" term="Orders"/>
        <category label="Purchasing" term="Purchasing"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Mercury bill pay — pay suppliers from your bank without leaving SKU.io]]></title>
        <id>https://www.sku.io/docs/release-notes/2026/11/04/mercury-bill-pay/</id>
        <link href="https://www.sku.io/docs/release-notes/2026/11/04/mercury-bill-pay/"/>
        <updated>2026-11-04T23:33:53.000Z</updated>
        <summary type="html"><![CDATA[Connect your Mercury account to pay bills and vendor deposits from SKU.io, approve every payment first, and match each Mercury transaction to what it paid.]]></summary>
        <content type="html"><![CDATA[<p>Paying a supplier used to mean two systems. You approved the bill in SKU.io, opened your bank, retyped the payee, the amount and the invoice numbers, then came back to SKU.io to record the payment by hand. Wires you sent straight from the bank, like a deposit to start production, never reached the purchase order at all. <strong>Mercury bill pay</strong> connects your Mercury business account to SKU.io. Pay a purchase invoice, a freight or duty bill, or a vendor deposit with a few clicks. Every payment is approved before any money moves, and SKU.io records it on the bill the day it leaves the bank.</p>
<p><strong>✨ What this means for you:</strong></p>
<ul>
<li class=""><strong>Pay with Mercury</strong> from the bill itself, by ACH, domestic wire or check, in full or in part. No retyping in your bank.</li>
<li class=""><strong>Every payment is approved first</strong>, either by a teammate in SKU.io or by an admin in Mercury's own app. You choose which.</li>
<li class="">A bill or deposit can only have <strong>one Mercury payment in progress</strong>, so it's never paid twice.</li>
<li class="">When Mercury sends the money, the payment is <strong>recorded on the bill or deposit, dated on the bank date</strong>, and syncs to QuickBooks or Xero like any other payment.</li>
<li class="">A new <strong>Bank transactions</strong> view matches every Mercury transaction to the bill or deposit it paid, including wires you sent from Mercury directly.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="pay-a-bill-or-deposit-in-a-few-clicks">Pay a bill or deposit in a few clicks<a href="https://www.sku.io/docs/release-notes/2026/11/04/mercury-bill-pay/#pay-a-bill-or-deposit-in-a-few-clicks" class="hash-link" aria-label="Direct link to Pay a bill or deposit in a few clicks" title="Direct link to Pay a bill or deposit in a few clicks" translate="no">​</a></h2>
<p>Open a purchase invoice, a landed-cost bill or a vendor deposit and click <strong>Add Payment</strong>, then <strong>Pay with Mercury</strong>. Choose the amount (the open balance, or less to pay part of it), the Mercury account to pay from, and the method. The dialog shows what's left in the account after the payment. The first time you pay a supplier, link them to their Mercury recipient, or invite them to add their own bank details. SKU.io never sees or stores their account numbers.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/mercury-bill-pay/pay-with-mercury.png" alt="The Pay with Mercury dialog: $1,000.00 to a linked recipient by ACH from Operating Checking, with the balance left after the payment and Submit for approval" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="approve-before-money-moves">Approve before money moves<a href="https://www.sku.io/docs/release-notes/2026/11/04/mercury-bill-pay/#approve-before-money-moves" class="hash-link" aria-label="Direct link to Approve before money moves" title="Direct link to Approve before money moves" translate="no">​</a></h2>
<p>Each connection chooses where payments are approved. With <strong>In Mercury</strong>, SKU.io sends a payment request and an admin approves it in Mercury's app, with your Mercury approval rules. With <strong>In SKU.io</strong>, anyone with the new <strong>Approve payments</strong> permission approves on the Mercury <strong>Payments</strong> tab, and SKU.io sends the money straight from Mercury. Payments your bill or deposit approval policy has already approved go straight through, without a second approval.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/mercury-bill-pay/payments-tab.png" alt="The Mercury Payments tab with two payments marked Paid, each approved in SKU.io, and the bill or deposit each one paid" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="every-mercury-transaction-matched-to-what-it-paid">Every Mercury transaction, matched to what it paid<a href="https://www.sku.io/docs/release-notes/2026/11/04/mercury-bill-pay/#every-mercury-transaction-matched-to-what-it-paid" class="hash-link" aria-label="Direct link to Every Mercury transaction, matched to what it paid" title="Direct link to Every Mercury transaction, matched to what it paid" translate="no">​</a></h2>
<p>The <strong>Bank transactions</strong> tab mirrors every transaction in your Mercury accounts. Payments sent from SKU.io are matched automatically. For everything else, SKU.io suggests the bill or deposit that fits on amount, supplier and the numbers on the transfer, and you confirm it in one click. A deposit wire sent straight from Mercury is marked paid on its purchase order, dated on the day it left the bank. Payroll, transfers and fees can be ignored. Your accounting bank reconciliation still happens in QuickBooks or Xero, against the bank feed.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/mercury-bill-pay/bank-transactions.png" alt="The Bank transactions tab: counts of Matched, Suggested, Unmatched and Ignored, with deposit, balance and freight wires suggested against their vendor deposits and freight bill" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-to-find-it">Where to find it<a href="https://www.sku.io/docs/release-notes/2026/11/04/mercury-bill-pay/#where-to-find-it" class="hash-link" aria-label="Direct link to Where to find it" title="Direct link to Where to find it" translate="no">​</a></h2>
<p>Go to <strong>Apps &amp; Integrations → All Integrations</strong> and choose <strong>Mercury</strong> under <strong>Bill Payments</strong> to connect your account. Then pay from any purchase invoice, landed-cost bill or vendor deposit with <strong>Add Payment → Pay with Mercury</strong>. To open bills on Mercury by default, set <strong>Default payment method</strong> in <strong>Settings → Purchasing → Payment Approvals</strong>.</p>
<p><strong>Full guide:</strong> <a href="https://www.sku.io/docs/guides/integrations/mercury" target="_blank" rel="noopener noreferrer" class="">Mercury</a>. Walkthroughs: <a href="https://www.sku.io/docs/guides/integrations/mercury/pay-a-bill-with-mercury" target="_blank" rel="noopener noreferrer" class="">Pay a bill with Mercury</a> and <a href="https://www.sku.io/docs/guides/integrations/mercury/review-mercury-bank-transactions" target="_blank" rel="noopener noreferrer" class="">Review Mercury bank transactions</a>.</p>]]></content>
        <author>
            <name>SKU.io Product Team</name>
            <uri>https://sku.io</uri>
        </author>
        <category label="Major Feature" term="Major Feature"/>
        <category label="New" term="New"/>
        <category label="Integrations" term="Integrations"/>
        <category label="Purchasing" term="Purchasing"/>
        <category label="Accounting" term="Accounting"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Buy within your cash — know what you can afford to order this week, and what has to wait]]></title>
        <id>https://www.sku.io/docs/release-notes/2026/11/02/buy-within-your-cash/</id>
        <link href="https://www.sku.io/docs/release-notes/2026/11/02/buy-within-your-cash/"/>
        <updated>2026-11-02T20:51:49.000Z</updated>
        <summary type="html"><![CDATA[Set your cash, credit and the reserve you never go below. SKU.io ranks every reorder line across suppliers and draws the line where your weekly cash runs out.]]></summary>
        <content type="html"><![CDATA[<p>A demand plan tells you what you need. It doesn't tell you what you can pay for. When stock ties up most of your cash, the real question is "what should I buy with the money I actually have this week, and what can wait?" Until now you answered it in a spreadsheet, supplier by supplier, guessing which bills land when. <strong>Buy within your cash</strong> answers it inside Demand Planning. Tell SKU.io your cash, your credit line and the balance you never plan below. It works out what you can spend each week after the bills you already owe. Then it ranks every reorder line from every supplier and shows where the money runs out.</p>
<div class="container_jWnl facadeShell_Lr1y"><button type="button" class="facadeButton_E7oD" aria-label="Play video: Set your buying capacity"><img class="poster_VPFb" src="https://www.sku.io/docs/img/guides/set-your-buying-capacity/poster.jpg" alt="" loading="lazy"><span class="playButton_xPSl" aria-hidden="true"><svg viewBox="0 0 24 24" width="28" height="28" fill="currentColor"><path d="M8 5v14l11-7z"></path></svg></span><span class="durationBadge_INHS">1:02</span></button><noscript><a href="https://www.youtube.com/watch?v=ujDGE6kNLSA">Watch on YouTube</a></noscript></div>
<p><strong>✨ What this means for you:</strong></p>
<ul>
<li class="">One <strong>buying capacity</strong> for the whole business: cash on hand plus available credit, minus the reserve you always keep. You can type your cash in or read it from your QuickBooks Online or Xero bank balance.</li>
<li class=""><strong>Spendable cash by week</strong>, after supplier deposits, balances, invoices and bills you already owe, with the <strong>tightest week</strong> flagged before you commit to anything.</li>
<li class="">A <strong>Ranked by cash</strong> list across all your suppliers, best value for your cash first, with a <strong>cut line</strong> where the budget runs out.</li>
<li class=""><strong>Generate orders</strong> creates draft purchase orders for the lines that fit now. Lines that wait for cash, or aren't due yet, stay listed.</li>
<li class="">A <strong>cash-flow calendar</strong> that shows month by month whether you'll have enough.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="set-your-buying-capacity-once">Set your buying capacity once<a href="https://www.sku.io/docs/release-notes/2026/11/02/buy-within-your-cash/#set-your-buying-capacity-once" class="hash-link" aria-label="Direct link to Set your buying capacity once" title="Direct link to Set your buying capacity once" translate="no">​</a></h2>
<p>In <strong>Inventory → Demand Planning</strong>, the <strong>Buying capacity</strong> card holds three numbers: your <strong>Cash on hand</strong>, your <strong>Credit line limit</strong> and how much is <strong>Drawn</strong>, and your <strong>Base reserve</strong>, the bank balance you never plan below. Cash on hand can come from <strong>Use QuickBooks balance</strong> (or Xero): SKU.io reads the bank accounts you tick and uses the figure only after you confirm it.</p>
<p>Need more cash in the bank for a busy season? Add a reserve override such as <strong>Holiday peak</strong>, with dates and an amount. <strong>Reserve by week</strong> shows which reserve each week uses. The card then shows the spendable cash for each week and flags the tightest one.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/buy-within-your-cash/buying-capacity.png" alt="The Buying capacity card: cash, available credit and base reserve, with spendable cash for each week and the tightest week flagged during a Holiday peak reserve" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="see-what-to-buy-first-across-every-supplier">See what to buy first, across every supplier<a href="https://www.sku.io/docs/release-notes/2026/11/02/buy-within-your-cash/#see-what-to-buy-first-across-every-supplier" class="hash-link" aria-label="Direct link to See what to buy first, across every supplier" title="Direct link to See what to buy first, across every supplier" translate="no">​</a></h2>
<p>Build a forecast as usual, then click <strong>Ranked by cash</strong>. Every reorder line from every supplier sits in one list, scored by the margin it protects for each dollar it costs. Each line shows its stockout <strong>Risk</strong>, <strong>Qty</strong>, the <strong>Cash</strong> it costs, the week it <strong>Pays</strong>, its <strong>Order by</strong> date and its <strong>$/ $1</strong> score. The <strong>Cut line — budget runs out here</strong> row splits the lines that fit your weekly headroom from the ones that wait. Lines that wait show the week they would fit.</p>
<p>A line marked <strong>Buy now</strong> has reached its order-by date. Disagree with the ranking? <strong>Keep in</strong> pins a line above the cut, and <strong>Push out</strong> pins it below. The cut line moves and the pin is logged. To see why a line landed where it did, open its calculation details: the <strong>Cash</strong> step shows its pay weeks, the headroom before and after, and its rank.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/buy-within-your-cash/ranked-by-cash.png" alt="The Ranked by cash view: lines ranked across suppliers with cash, pay week, order-by date and score, and a cut line where the budget runs out" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="turn-the-lines-that-fit-into-purchase-orders">Turn the lines that fit into purchase orders<a href="https://www.sku.io/docs/release-notes/2026/11/02/buy-within-your-cash/#turn-the-lines-that-fit-into-purchase-orders" class="hash-link" aria-label="Direct link to Turn the lines that fit into purchase orders" title="Direct link to Turn the lines that fit into purchase orders" translate="no">​</a></h2>
<p>Click <strong>Generate orders</strong> to review before anything is created. Lines in <strong>Fits</strong> that are due now come ticked. Lines in <strong>Waits</strong> are unticked, and you can tick one to include it anyway. <strong>Order later</strong> lists lines that fit but aren't due yet, each with the date to order it. The summary shows the ticked total, what's paid in the next 12 weeks and the headroom left in the tightest week. Then click <strong>Create</strong>, one purchase order per supplier. SKU.io checks the headroom again first, so a bill added since you built the plan can't slip through.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/buy-within-your-cash/generate-orders.png" alt="The Generate orders dialog with Fits ticked, Waits unticked, and Order later lines with their order-on dates" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="check-the-months-ahead-on-the-cash-flow-calendar">Check the months ahead on the cash-flow calendar<a href="https://www.sku.io/docs/release-notes/2026/11/02/buy-within-your-cash/#check-the-months-ahead-on-the-cash-flow-calendar" class="hash-link" aria-label="Direct link to Check the months ahead on the cash-flow calendar" title="Direct link to Check the months ahead on the cash-flow calendar" translate="no">​</a></h2>
<p><strong>Inventory → Cash Flow</strong> projects your cash by month. It starts from the cash in your buying capacity, adds expected sales payouts and takes off the supplier deposits and balances due. Click a month to list what you owe. Each payable links to its purchase order or bill and shows where its due date came from. Change <strong>Starting cash</strong> to try another figure without touching your saved capacity.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/buy-within-your-cash/cash-flow.png" alt="The cash-flow calendar showing opening cash, money in from sales, deposits and balances due, and closing cash for each month" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-to-find-it">Where to find it<a href="https://www.sku.io/docs/release-notes/2026/11/02/buy-within-your-cash/#where-to-find-it" class="hash-link" aria-label="Direct link to Where to find it" title="Direct link to Where to find it" translate="no">​</a></h2>
<ul>
<li class=""><strong>Set your capacity:</strong> <strong>Inventory → Demand Planning → Buying capacity → Set your buying capacity</strong> (or <strong>Edit</strong>).</li>
<li class=""><strong>Rank a plan:</strong> build a forecast on <strong>Inventory → Demand Planning</strong>, then click <strong>Ranked by cash</strong> in <strong>Results</strong>.</li>
<li class=""><strong>Create the orders:</strong> click <strong>Generate orders</strong> on the plan's results.</li>
<li class=""><strong>See the months ahead:</strong> <strong>Inventory → Cash Flow</strong>.</li>
</ul>
<p><strong>Full guide:</strong> <a href="https://www.sku.io/docs/guides/inventory/demand-planning/buy-within-your-cash/set-your-buying-capacity" target="_blank" rel="noopener noreferrer" class="">Set your buying capacity</a>. See also <a href="https://www.sku.io/docs/guides/inventory/demand-planning/buy-within-your-cash/rank-the-plan-by-cash" target="_blank" rel="noopener noreferrer" class="">Rank the plan by cash</a>, <a href="https://www.sku.io/docs/guides/inventory/demand-planning/buy-within-your-cash/generate-orders-within-your-cash" target="_blank" rel="noopener noreferrer" class="">Generate orders within your cash</a> and <a href="https://www.sku.io/docs/guides/inventory/cash-flow/read-the-cash-flow-calendar" target="_blank" rel="noopener noreferrer" class="">Read the cash-flow calendar</a>.</p>]]></content>
        <author>
            <name>SKU.io Product Team</name>
            <uri>https://sku.io</uri>
        </author>
        <category label="Major Feature" term="Major Feature"/>
        <category label="New" term="New"/>
        <category label="Purchasing" term="Purchasing"/>
        <category label="Inventory" term="Inventory"/>
        <category label="Accounting" term="Accounting"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Open-to-buy planning — a buying budget for every category, every month of the season]]></title>
        <id>https://www.sku.io/docs/release-notes/2026/11/02/open-to-buy-planning/</id>
        <link href="https://www.sku.io/docs/release-notes/2026/11/02/open-to-buy-planning/"/>
        <updated>2026-11-02T20:51:48.000Z</updated>
        <summary type="html"><![CDATA[Plan a season's sales, markdowns and ending stock by category or brand. SKU.io works out what's left to buy each month and can hold purchase orders to it.]]></summary>
        <content type="html"><![CDATA[<p>Seasonal buyers plan months ahead and manage month by month, and the budget usually lives in a spreadsheet nobody else can see. It goes stale the moment a purchase order lands. <strong>Open-to-buy planning</strong> brings that budget into SKU.io. Create a season, plan what each category or brand should sell, mark down and hold at month end, and SKU.io works out how much you still need to buy. Purchase orders count against the budget as they're placed. Once the season starts, plan sits beside actual so you can see a category drifting before it's over budget.</p>
<div class="container_jWnl facadeShell_Lr1y"><button type="button" class="facadeButton_E7oD" aria-label="Play video: Build an open-to-buy plan"><img class="poster_VPFb" src="https://www.sku.io/docs/img/guides/build-an-open-to-buy-plan/poster.jpg" alt="" loading="lazy"><span class="playButton_xPSl" aria-hidden="true"><svg viewBox="0 0 24 24" width="28" height="28" fill="currentColor"><path d="M8 5v14l11-7z"></path></svg></span><span class="durationBadge_INHS">1:03</span></button><noscript><a href="https://www.youtube.com/watch?v=oAZaerR93Bo">Watch on YouTube</a></noscript></div>
<p><strong>✨ What this means for you:</strong></p>
<ul>
<li class="">A season plan by <strong>Category</strong> or <strong>Brand</strong>, one column per month, with the open-to-buy worked out for you: planned sales + markdowns + ending stock − starting stock − on order.</li>
<li class=""><strong>Seed</strong> planned sales from your demand forecast or last year's sales instead of typing them.</li>
<li class="">Ending stock you can type, or set as <strong>stock-to-sales</strong> or <strong>weeks of supply</strong>.</li>
<li class=""><strong>Remaining to buy</strong> for each row, coloured green, amber or red, with an optional <strong>Cash cap</strong>.</li>
<li class=""><strong>Enforce on buys</strong>, an optional guardrail that holds back demand plans and purchase orders that would take a category over budget, with logged overrides.</li>
<li class=""><strong>Plan vs Actual</strong> once the season starts.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="seed-a-season-in-a-few-clicks">Seed a season in a few clicks<a href="https://www.sku.io/docs/release-notes/2026/11/02/open-to-buy-planning/#seed-a-season-in-a-few-clicks" class="hash-link" aria-label="Direct link to Seed a season in a few clicks" title="Direct link to Seed a season in a few clicks" translate="no">​</a></h2>
<p>Go to <strong>Inventory → Merchandise Planning</strong>, click <strong>New Season</strong>, and pick the season and year. Its months become the grid's columns. Click <strong>Seed</strong> and choose <strong>Seed from forecast</strong> or <strong>Seed from last year</strong>, then pick the categories to plan. <strong>Plan Sales</strong> fills in for every month. Add planned <strong>Markdowns</strong>, set ending stock in the <strong>EOP Inv</strong> row, and every change saves as you leave the cell.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/open-to-buy-planning/seed-from-forecast.png" alt="The Seed from forecast dialog with a recent demand window of 90 days and two categories picked to seed" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="know-whats-left-to-buy">Know what's left to buy<a href="https://www.sku.io/docs/release-notes/2026/11/02/open-to-buy-planning/#know-whats-left-to-buy" class="hash-link" aria-label="Direct link to Know what's left to buy" title="Direct link to Know what's left to buy" translate="no">​</a></h2>
<p>Each row ends in <strong>Remaining to buy</strong>: what you can still spend on that category this season. Purchase orders due in the season count as <strong>On-Order</strong> and come off the budget automatically. Green means room to buy, amber means 10% or less is left, and red means over budget. Over-budget rows are always shown, never hidden. If cash is tight, type a <strong>Cash cap</strong> and the budget becomes the smaller of the plan and the cap. <strong>Plan in</strong> switches the whole grid between <strong>Units</strong>, <strong>Cost $</strong> and <strong>Retail $</strong>.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/open-to-buy-planning/otb-grid.png" alt="The open-to-buy grid for two categories with planned sales by month, the open-to-buy row and Remaining to buy shown in red for an over-budget category" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="hold-purchasing-to-the-budget">Hold purchasing to the budget<a href="https://www.sku.io/docs/release-notes/2026/11/02/open-to-buy-planning/#hold-purchasing-to-the-budget" class="hash-link" aria-label="Direct link to Hold purchasing to the budget" title="Direct link to Hold purchasing to the budget" translate="no">​</a></h2>
<p>Turn on <strong>Enforce on buys</strong> under <strong>Budget on buys &amp; overrides</strong>, and the plan starts guarding purchasing. A demand plan or purchase order that would take a category over its remaining budget is held back, across every supplier for that category, not just one order. When one product must go through anyway, add an override with the quantity to <strong>Keep up to</strong> and a <strong>Reason</strong>. Every override, and every removal, is logged.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="track-plan-vs-actual-through-the-season">Track plan vs actual through the season<a href="https://www.sku.io/docs/release-notes/2026/11/02/open-to-buy-planning/#track-plan-vs-actual-through-the-season" class="hash-link" aria-label="Direct link to Track plan vs actual through the season" title="Direct link to Track plan vs actual through the season" translate="no">​</a></h2>
<p>Tick <strong>Plan vs Actual</strong> and each month shows actual sales, markdowns and receipts beside the plan, with the difference as a percentage. Months that have closed are marked, and months that haven't started stay empty. If a row turns red, rebalance it: lower planned sales or ending stock, or move budget from another month.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/open-to-buy-planning/plan-vs-actual.png" alt="Plan vs Actual: actual sales and receipts under each month's plan, with the variance as a percentage" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-to-find-it">Where to find it<a href="https://www.sku.io/docs/release-notes/2026/11/02/open-to-buy-planning/#where-to-find-it" class="hash-link" aria-label="Direct link to Where to find it" title="Direct link to Where to find it" translate="no">​</a></h2>
<ul>
<li class=""><strong>Build a plan:</strong> <strong>Inventory → Merchandise Planning → New Season</strong>, then <strong>Seed</strong>.</li>
<li class=""><strong>Hold purchases to it:</strong> <strong>Inventory → Merchandise Planning → Budget on buys &amp; overrides → Enforce on buys</strong>.</li>
<li class=""><strong>Compare with actuals:</strong> tick <strong>Plan vs Actual</strong> on the grid.</li>
</ul>
<p><strong>Full guide:</strong> <a href="https://www.sku.io/docs/guides/inventory/merchandise-planning/build-an-open-to-buy-plan" target="_blank" rel="noopener noreferrer" class="">Build an open-to-buy plan</a>. See also <a href="https://www.sku.io/docs/guides/inventory/merchandise-planning/track-plan-vs-actual" target="_blank" rel="noopener noreferrer" class="">Track plan vs actual</a> and <a href="https://www.sku.io/docs/guides/inventory/merchandise-planning/how-open-to-buy-works" target="_blank" rel="noopener noreferrer" class="">How open-to-buy works</a>.</p>]]></content>
        <author>
            <name>SKU.io Product Team</name>
            <uri>https://sku.io</uri>
        </author>
        <category label="Major Feature" term="Major Feature"/>
        <category label="New" term="New"/>
        <category label="Purchasing" term="Purchasing"/>
        <category label="Inventory" term="Inventory"/>
        <category label="Reporting" term="Reporting"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Sizes and colours — buy the size run your customers actually buy]]></title>
        <id>https://www.sku.io/docs/release-notes/2026/11/02/sizes-and-colours/</id>
        <link href="https://www.sku.io/docs/release-notes/2026/11/02/sizes-and-colours/"/>
        <updated>2026-11-02T20:51:47.000Z</updated>
        <summary type="html"><![CDATA[Build size curves from real sales, see a style's stock as a size × colour grid and reorder the gaps, and compare sizes across vendors in the new Sales by Size report.]]></summary>
        <content type="html"><![CDATA[<p>If you sell apparel, you don't buy a style: you buy a size run. Order every size evenly and you sell out of the middle sizes while the ends sit on the shelf. A style's stock is spread across dozens of variants, so spotting the gaps means scrolling a long list. <strong>Sizes and colours</strong> puts the size run front and centre. Derive a size curve from how a style really sold. See its stock as a grid of sizes and colours and reorder the gaps in one go. Compare sizes across every vendor in one report.</p>
<div class="container_jWnl facadeShell_Lr1y"><button type="button" class="facadeButton_E7oD" aria-label="Play video: Build size curves from sales"><img class="poster_VPFb" src="https://www.sku.io/docs/img/guides/build-size-curves-from-sales/poster.jpg" alt="" loading="lazy"><span class="playButton_xPSl" aria-hidden="true"><svg viewBox="0 0 24 24" width="28" height="28" fill="currentColor"><path d="M8 5v14l11-7z"></path></svg></span><span class="durationBadge_INHS">0:51</span></button><noscript><a href="https://www.youtube.com/watch?v=azj9E9kefP0">Watch on YouTube</a></noscript></div>
<p><strong>✨ What this means for you:</strong></p>
<ul>
<li class=""><strong>Size curves from real sales</strong>, corrected for sizes that sold out early so your best sellers aren't under-bought.</li>
<li class="">A <strong>Stock by Size &amp; Color</strong> grid on every style's product page, with one-click reordering of the gaps.</li>
<li class="">A <strong>Sales by Size</strong> report: units and revenue for every size, by vendor and silhouette, in size-run order.</li>
<li class=""><strong>Velocity labels and scorecards that are right for styles.</strong> A style is now labelled and scored from its variants' combined sales, so a best-selling style shows as a <strong>Winner</strong> instead of looking idle.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="build-a-size-curve-from-how-a-style-sold">Build a size curve from how a style sold<a href="https://www.sku.io/docs/release-notes/2026/11/02/sizes-and-colours/#build-a-size-curve-from-how-a-style-sold" class="hash-link" aria-label="Direct link to Build a size curve from how a style sold" title="Direct link to Build a size curve from how a style sold" translate="no">​</a></h2>
<p>On <strong>Inventory → Size Profiles</strong>, click <strong>Derive from Sales</strong>, pick the style and a history window, and preview its curve. Turn on <strong>Correct for sold-out sizes</strong>: a size that ran out early is weighted on how fast it sold while it was in stock, so its share isn't understated. <strong>Full-price sales only</strong> leaves markdown sales out. Sizes sold in several colours are combined into one share per size. Save the result as a size profile, and forecasts split a style's buy across sizes the way your customers buy.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/sizes-and-colours/size-curve.png" alt="A size curve derived from a year of sales and corrected for sold-out sizes, with each size's share totalling 100%" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="see-a-styles-stock-by-size-and-colour">See a style's stock by size and colour<a href="https://www.sku.io/docs/release-notes/2026/11/02/sizes-and-colours/#see-a-styles-stock-by-size-and-colour" class="hash-link" aria-label="Direct link to See a style's stock by size and colour" title="Direct link to See a style's stock by size and colour" translate="no">​</a></h2>
<p>Open a style under <strong>PIM → Products</strong> and scroll to <strong>Stock by Size &amp; Color</strong>: one row per colour, one column per size, with totals for each. A zero stands out straight away. Pick a warehouse to see one location, and hover a cell for available and allocated stock. Tick the gaps, a whole colour or a whole size, or click <strong>Reorder all</strong>. The reorder window groups lines by supplier with suggested quantities, and creates draft purchase orders.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/sizes-and-colours/size-colour-grid.png" alt="The Stock by Size &amp; Color grid for a style in two colours and six sizes, with on-hand stock in each cell and totals" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="compare-sizes-across-every-vendor">Compare sizes across every vendor<a href="https://www.sku.io/docs/release-notes/2026/11/02/sizes-and-colours/#compare-sizes-across-every-vendor" class="hash-link" aria-label="Direct link to Compare sizes across every vendor" title="Direct link to Compare sizes across every vendor" translate="no">​</a></h2>
<p>The new <strong>Sales by Size</strong> report, under <strong>Insights → Reports</strong>, shows units and revenue for every size in one view, instead of a report per vendor. Sizes run left to right in size-run order, grouped by vendor and then by silhouette. The cards up top show units sold, revenue, the number of suppliers and the best-selling size. Filter by supplier, silhouette, category, channel or warehouse, and export the table to CSV.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/sizes-and-colours/sales-by-size.png" alt="The Sales by Size report: units sold by size for a vendor's rompers, leggings and tees, with the best-selling size shown in the cards above" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="velocity-labels-now-work-for-styles">Velocity labels now work for styles<a href="https://www.sku.io/docs/release-notes/2026/11/02/sizes-and-colours/#velocity-labels-now-work-for-styles" class="hash-link" aria-label="Direct link to Velocity labels now work for styles" title="Direct link to Velocity labels now work for styles" translate="no">​</a></h2>
<p>Products carry a velocity label, <strong>Winner</strong>, <strong>Chaser</strong>, <strong>Steady</strong>, <strong>Slow mover</strong> or <strong>Dormant</strong>, on the product page and in the product list. A style doesn't sell under its own SKU: its variants do. So styles used to look like they weren't selling at all. A style's label and its <strong>Performance Scorecard</strong> now roll up from its variants' combined sales, so a strong style reads as a <strong>Winner</strong> or <strong>Chaser</strong>, scored on the orders its sizes actually took.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/sizes-and-colours/style-velocity.png" alt="A style's Performance Scorecard rated Good from 17 orders and $10.6K in sales, beside its Winner velocity label in Selling &amp; Stock" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-to-find-it">Where to find it<a href="https://www.sku.io/docs/release-notes/2026/11/02/sizes-and-colours/#where-to-find-it" class="hash-link" aria-label="Direct link to Where to find it" title="Direct link to Where to find it" translate="no">​</a></h2>
<ul>
<li class=""><strong>Size curves:</strong> <strong>Inventory → Size Profiles → Derive from Sales</strong>.</li>
<li class=""><strong>Size × colour grid and reorder:</strong> <strong>PIM → Products →</strong> <em>(a style)</em> <strong>→ Stock by Size &amp; Color</strong>.</li>
<li class=""><strong>Sales by Size:</strong> <strong>Insights → Reports → Sales by Size</strong>.</li>
</ul>
<p><strong>Full guide:</strong> <a href="https://www.sku.io/docs/guides/inventory/size-profiles/build-size-curves-from-sales" target="_blank" rel="noopener noreferrer" class="">Build size curves from sales</a>. See also <a href="https://www.sku.io/docs/guides/inventory/stock-levels/see-and-reorder-stock-by-size-and-colour" target="_blank" rel="noopener noreferrer" class="">See and reorder stock by size and colour</a> and <a href="https://www.sku.io/docs/guides/insights/reports/products-and-suppliers/read-the-sales-by-size-report" target="_blank" rel="noopener noreferrer" class="">Read the Sales by Size report</a>.</p>]]></content>
        <author>
            <name>SKU.io Product Team</name>
            <uri>https://sku.io</uri>
        </author>
        <category label="Major Feature" term="Major Feature"/>
        <category label="New" term="New"/>
        <category label="Inventory" term="Inventory"/>
        <category label="Purchasing" term="Purchasing"/>
        <category label="Reporting" term="Reporting"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Create a PO from a supplier document — upload the CSV, PDF or photo instead of retyping it]]></title>
        <id>https://www.sku.io/docs/release-notes/2026/11/02/po-from-supplier-document/</id>
        <link href="https://www.sku.io/docs/release-notes/2026/11/02/po-from-supplier-document/"/>
        <updated>2026-11-02T20:51:46.000Z</updated>
        <summary type="html"><![CDATA[Upload a supplier's order sheet, PDF confirmation or a photo of it. SKU.io reads the lines, matches them to your products and builds a draft purchase order for you to check.]]></summary>
        <content type="html"><![CDATA[<p>Orders often start outside SKU.io: an order sheet filled in at a trade show, a PDF confirmation from a supplier, a market app's export. Retyping every line, size by size, is slow, and one wrong code means the wrong stock arrives. <strong>Create a PO from a supplier document</strong> skips the retyping. Upload the file, or snap a photo of the paper sheet. SKU.io reads the supplier, order number, dates and lines, matches each line to your products, and builds a draft purchase order for you to check before anything is created.</p>
<div class="container_jWnl facadeShell_Lr1y"><button type="button" class="facadeButton_E7oD" aria-label="Play video: Create a purchase order from a supplier document"><img class="poster_VPFb" src="https://www.sku.io/docs/img/guides/create-a-po-from-a-supplier-document/poster.jpg" alt="" loading="lazy"><span class="playButton_xPSl" aria-hidden="true"><svg viewBox="0 0 24 24" width="28" height="28" fill="currentColor"><path d="M8 5v14l11-7z"></path></svg></span><span class="durationBadge_INHS">1:09</span></button><noscript><a href="https://www.youtube.com/watch?v=a_BBQxRYJ18">Watch on YouTube</a></noscript></div>
<p><strong>✨ What this means for you:</strong></p>
<ul>
<li class=""><strong>Any format your supplier sends:</strong> CSV and XLSX spreadsheets, market-app exports, PDFs, and JPG or PNG photos, up to 20 MB.</li>
<li class=""><strong>The order details are read for you:</strong> supplier, vendor order number, order date and expected delivery.</li>
<li class=""><strong>Lines matched to your products</strong> on the supplier's code first, then barcode, then name, size and colour.</li>
<li class=""><strong>Nothing is guessed:</strong> loose matches are flagged, and a line with no match stays out until you pick its product.</li>
<li class=""><strong>It learns:</strong> the supplier codes you match are remembered, so the next sheet from that supplier matches on its own.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="upload-the-sheet-or-take-a-photo">Upload the sheet, or take a photo<a href="https://www.sku.io/docs/release-notes/2026/11/02/po-from-supplier-document/#upload-the-sheet-or-take-a-photo" class="hash-link" aria-label="Direct link to Upload the sheet, or take a photo" title="Direct link to Upload the sheet, or take a photo" translate="no">​</a></h2>
<p>On <strong>Orders → Purchase Orders</strong>, click <strong>New PO from Document</strong>. Drop the file in, or tap to choose one or take a photo. Picking the supplier is optional, since it's read off the sheet. Choose the warehouse to ship to and click <strong>Read Document</strong>.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/po-from-supplier-document/upload.png" alt="The New PO from Document window: drop an order or take a photo, with an optional supplier and a ship-to warehouse" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="check-the-matches-then-create-the-draft">Check the matches, then create the draft<a href="https://www.sku.io/docs/release-notes/2026/11/02/po-from-supplier-document/#check-the-matches-then-create-the-draft" class="hash-link" aria-label="Direct link to Check the matches, then create the draft" title="Direct link to Check the matches, then create the draft" translate="no">​</a></h2>
<p>The review page shows the <strong>Order details</strong> it read and every line: what was <strong>On the sheet</strong> beside the <strong>Product</strong> it matched. Tick <strong>Only lines to check</strong> to see just the lines that need you. A line with no match is left out until you pick its product, and lines that matched loosely are flagged. When it looks right, click <strong>Create Draft PO</strong>. Spreadsheets and exports work as they are. PDFs and photos are read with document OCR, which is turned on per account.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/po-from-supplier-document/review-lines.png" alt="Reviewing a supplier's order sheet: order details read from the file, and one unmatched line flagged for a product to be picked" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-to-find-it">Where to find it<a href="https://www.sku.io/docs/release-notes/2026/11/02/po-from-supplier-document/#where-to-find-it" class="hash-link" aria-label="Direct link to Where to find it" title="Direct link to Where to find it" translate="no">​</a></h2>
<ul>
<li class=""><strong>Orders → Purchase Orders → New PO from Document.</strong></li>
</ul>
<p><strong>Full guide:</strong> <a href="https://www.sku.io/docs/guides/orders/purchase-orders/create-and-submit/create-a-po-from-a-supplier-document" target="_blank" rel="noopener noreferrer" class="">Create a purchase order from a supplier document</a></p>]]></content>
        <author>
            <name>SKU.io Product Team</name>
            <uri>https://sku.io</uri>
        </author>
        <category label="Major Feature" term="Major Feature"/>
        <category label="New" term="New"/>
        <category label="Purchasing" term="Purchasing"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Damage capture and vendor claims — record a damaged item in one step and claim it back]]></title>
        <id>https://www.sku.io/docs/release-notes/2026/11/02/damage-capture-and-vendor-claims/</id>
        <link href="https://www.sku.io/docs/release-notes/2026/11/02/damage-capture-and-vendor-claims/"/>
        <updated>2026-11-02T20:51:45.000Z</updated>
        <summary type="html"><![CDATA[Record a damaged return or shelf item in one step. SKU.io moves it to a blemished SKU, writes down the loss and can raise a draft credit claim with the supplier.]]></summary>
        <content type="html"><![CDATA[<p>A torn seam at the register, a crushed box on the shelf: damaged items are small, constant and easy to lose track of. Creating an RMA for every one is too much work, so they get binned, the stock count drifts, and the money the supplier owes you is never claimed. <strong>Damage capture</strong> records a damaged item in one step. It moves the unit to a blemished SKU so it stops counting as sellable stock and records the loss in your books. If the supplier should pay for it, it raises a draft credit claim with them in the same step.</p>
<div class="container_jWnl facadeShell_Lr1y"><button type="button" class="facadeButton_E7oD" aria-label="Play video: Capture damaged items and claim from the vendor"><img class="poster_VPFb" src="https://www.sku.io/docs/img/guides/capture-damaged-items-and-claim-from-the-vendor/poster.jpg" alt="" loading="lazy"><span class="playButton_xPSl" aria-hidden="true"><svg viewBox="0 0 24 24" width="28" height="28" fill="currentColor"><path d="M8 5v14l11-7z"></path></svg></span><span class="durationBadge_INHS">0:52</span></button><noscript><a href="https://www.youtube.com/watch?v=D1Cn68qlvpI">Watch on YouTube</a></noscript></div>
<p><strong>✨ What this means for you:</strong></p>
<ul>
<li class=""><strong>One step, no RMA first:</strong> record a <strong>Customer return</strong> or an item <strong>Damaged on our shelf</strong> from the product page, the RMA list or the receive station.</li>
<li class=""><strong>Stock stays honest:</strong> the damaged unit moves to a <strong>blemished SKU</strong>, generated for you, so it no longer counts as sellable.</li>
<li class=""><strong>Claim it back from the supplier:</strong> tick <strong>Claim it from the vendor</strong> and a draft credit claim is created with the product's default supplier.</li>
<li class=""><strong>Refund the customer in the same step</strong> with an optional cash credit, linked to the sales order it came from.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="capture-it-in-one-window">Capture it in one window<a href="https://www.sku.io/docs/release-notes/2026/11/02/damage-capture-and-vendor-claims/#capture-it-in-one-window" class="hash-link" aria-label="Direct link to Capture it in one window" title="Direct link to Capture it in one window" translate="no">​</a></h2>
<p>Open the product, click <strong>Actions</strong> and choose <strong>Capture Damage</strong>, or <strong>Damaged at Register → Claim from Vendor</strong> for an item you'll claim from the supplier. Say where it came from, enter the quantity and a short damage description, and leave the blemished SKU blank to have one generated. For a customer return, you can link the sales order, a return reason and a credit to refund the customer.</p>
<p>To claim it back, tick <strong>Claim it from the vendor</strong>. The product's default supplier is filled in, so check the claim amount per unit and add the supplier's return authorisation number if you have one.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/damage-capture-and-vendor-claims/damage-window.png" alt="The Capture Damaged Return window: product, warehouse, quantity, damage description, a generated blemished SKU and the option to claim it from the vendor" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="tracked-not-trashed">Tracked, not trashed<a href="https://www.sku.io/docs/release-notes/2026/11/02/damage-capture-and-vendor-claims/#tracked-not-trashed" class="hash-link" aria-label="Direct link to Tracked, not trashed" title="Direct link to Tracked, not trashed" translate="no">​</a></h2>
<p>Click <strong>Capture &amp; Claim</strong>. The confirmation shows the units captured, the new blemished SKU, the loss recorded and the vendor claim raised. <strong>Capture another</strong> records the next item for the same product. The claim lands as a draft credit on the supplier's <strong>Payables → Credits</strong> panel, marked as a damage claim and linked back to the product or return. Nothing posts until you authorise it, once the supplier agrees, and authorising writes the damaged unit off stock once.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/damage-capture-and-vendor-claims/captured.png" alt="The confirmation after capturing a damaged item: one unit captured, the new blemished SKU and a vendor claim raised with the supplier" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-to-find-it">Where to find it<a href="https://www.sku.io/docs/release-notes/2026/11/02/damage-capture-and-vendor-claims/#where-to-find-it" class="hash-link" aria-label="Direct link to Where to find it" title="Direct link to Where to find it" translate="no">​</a></h2>
<ul>
<li class=""><strong>From a product:</strong> <strong>PIM → Products →</strong> <em>(the product)</em> <strong>→ Actions → Capture Damage</strong> (or <strong>Damaged at Register → Claim from Vendor</strong>).</li>
<li class=""><strong>From returns and receiving:</strong> the same window opens from the RMA list and the receive station.</li>
<li class=""><strong>Follow up the claim:</strong> <strong>Contacts → Suppliers →</strong> <em>(the supplier)</em> <strong>→ Payables → Credits</strong>.</li>
</ul>
<p><strong>Full guide:</strong> <a href="https://www.sku.io/docs/guides/orders/returns/process-returns/capture-damaged-items-and-claim-from-the-vendor" target="_blank" rel="noopener noreferrer" class="">Capture damaged items and claim from the vendor</a></p>]]></content>
        <author>
            <name>SKU.io Product Team</name>
            <uri>https://sku.io</uri>
        </author>
        <category label="Major Feature" term="Major Feature"/>
        <category label="New" term="New"/>
        <category label="Inventory" term="Inventory"/>
        <category label="Purchasing" term="Purchasing"/>
        <category label="Accounting" term="Accounting"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Marketplace facilitator tax — stays out of your revenue and your Sales Tax]]></title>
        <id>https://www.sku.io/docs/release-notes/2026/11/02/marketplace-facilitator-tax/</id>
        <link href="https://www.sku.io/docs/release-notes/2026/11/02/marketplace-facilitator-tax/"/>
        <updated>2026-11-02T19:42:57.000Z</updated>
        <summary type="html"><![CDATA[Sales tax that Amazon, Walmart, eBay and other marketplaces collect and pay for you now nets to zero in its own account, instead of inflating your Sales Tax liability.]]></summary>
        <content type="html"><![CDATA[<p>In the US, Amazon, Walmart, eBay, Etsy, Temu, TikTok Shop and Faire collect sales tax from your buyers and pay it to the states themselves. That tax was never yours. Your books didn't always know that: some channels imported it onto the order and credited it to your <strong>Sales Tax</strong> account, so the balance kept growing and someone had to write it off by hand each month. Settlement tax lines were just more codes to map, and they sometimes landed in revenue or fees. <strong>Marketplace facilitator tax</strong> fixes this. Tax a marketplace collects and pays for you now posts through its own <strong>Marketplace Facilitator Tax</strong> account, which nets to zero on every order and never reaches your Sales Tax.</p>
<p><strong>✨ What this means for you:</strong></p>
<ul>
<li class="">Your <strong>Sales Tax</strong> balance shows only the tax you owe, so it agrees with your Sales Tax Liability report.</li>
<li class="">Marketplace tax stays out of your revenue and your fees, on every channel, whether you book sales per order or per payout.</li>
<li class="">Each order records who collected its tax, so an Amazon.com sale and an Amazon.ca sale are each treated correctly.</li>
<li class="">Past months that put marketplace tax in the wrong place can be repaired in one step, without editing anything already posted.</li>
<li class="">The month-end close checks that the clearing account is empty and nothing slipped into Sales Tax.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="one-switch-in-your-accounting-settings">One switch in your accounting settings<a href="https://www.sku.io/docs/release-notes/2026/11/02/marketplace-facilitator-tax/#one-switch-in-your-accounting-settings" class="hash-link" aria-label="Direct link to One switch in your accounting settings" title="Direct link to One switch in your accounting settings" translate="no">​</a></h2>
<p>Turn it on with <strong>Adopt clearing treatment</strong> on the <strong>Marketplace facilitator tax</strong> card. SKU.io sets up the <strong>Marketplace Facilitator Tax</strong> clearing account for you, and from then on each new marketplace order posts a matching collected and remitted pair through it. Orders created before you adopted it keep the entries they already have.</p>
<p>The card also shows a health check: which channels are marketplaces, whether every tax code in your settlements is mapped, whether every sales channel says who collects its tax, and whether any marketplace tax is still sitting in your Sales Tax. If you change your mind, <strong>Revert</strong> turns it off for new orders.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/marketplace-facilitator-tax/settings-card.png" alt="The Marketplace facilitator tax card in accounting settings, showing the clearing account and four green health checks" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="settlement-tax-codes-get-a-sensible-home">Settlement tax codes get a sensible home<a href="https://www.sku.io/docs/release-notes/2026/11/02/marketplace-facilitator-tax/#settlement-tax-codes-get-a-sensible-home" class="hash-link" aria-label="Direct link to Settlement tax codes get a sensible home" title="Direct link to Settlement tax codes get a sensible home" translate="no">​</a></h2>
<p>Tax lines in Amazon, Walmart, eBay and Shopify settlements are now recognised as tax, and come with suggested accounts. If one is mapped to an income or expense account, SKU.io flags it for review and sends you an alert, so tax doesn't end up in revenue or fees by mistake.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="see-what-landed-in-the-wrong-place-and-fix-it">See what landed in the wrong place, and fix it<a href="https://www.sku.io/docs/release-notes/2026/11/02/marketplace-facilitator-tax/#see-what-landed-in-the-wrong-place-and-fix-it" class="hash-link" aria-label="Direct link to See what landed in the wrong place, and fix it" title="Direct link to See what landed in the wrong place, and fix it" translate="no">​</a></h2>
<p>The <strong>Facilitator Tax</strong> report lists marketplace tax by channel and month: the tax on your orders, how much reached your Sales Tax, what the settlements reported, and the reclass needed to move it out. <strong>Repair</strong> posts that reclass for open months in one step. Locked months are shown but never changed.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/marketplace-facilitator-tax/facilitator-tax-report.png" alt="The Facilitator Tax report, listing marketplace tax by channel and month with repaired amounts" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-to-find-it">Where to find it<a href="https://www.sku.io/docs/release-notes/2026/11/02/marketplace-facilitator-tax/#where-to-find-it" class="hash-link" aria-label="Direct link to Where to find it" title="Direct link to Where to find it" translate="no">​</a></h2>
<ul>
<li class=""><strong>Accounting → Settings → General</strong>, on the <strong>Marketplace facilitator tax</strong> card, to adopt the clearing treatment.</li>
<li class=""><strong>Accounting → Reports → Facilitator Tax</strong> to see the impact and repair past months.</li>
<li class="">The <strong>Tax</strong> tab on any sales order shows who collected its tax and which account it posted to.</li>
</ul>
<p><strong>Full guide:</strong> <a href="https://www.sku.io/docs/guides/accounting/set-up/invoices-tax-and-revenue/account-for-marketplace-facilitator-tax" target="_blank" rel="noopener noreferrer" class="">Account for marketplace facilitator tax</a></p>]]></content>
        <author>
            <name>SKU.io Product Team</name>
            <uri>https://sku.io</uri>
        </author>
        <category label="Major Feature" term="Major Feature"/>
        <category label="New" term="New"/>
        <category label="Accounting" term="Accounting"/>
        <category label="Integrations" term="Integrations"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Customs entries — duty rates, HTS codes and exact duty splits from your broker's 7501]]></title>
        <id>https://www.sku.io/docs/release-notes/2026/11/02/customs-entries/</id>
        <link href="https://www.sku.io/docs/release-notes/2026/11/02/customs-entries/"/>
        <updated>2026-11-02T04:50:33.000Z</updated>
        <summary type="html"><![CDATA[Import your broker's 7501 entry summaries or an ACE ES-003 report, apply the duty rates and product codes they prove, and split duty bills by the duty actually charged.]]></summary>
        <content type="html"><![CDATA[<p>Every shipment you import into the United States gets a customs entry, and it already lists everything your duty setup needs. For each line it gives the HTS code, the value, the base rate, every Section 301, IEEPA or Section 122 duty stacked on top, and the duty actually charged. Until now that data sat in a PDF from your broker. You typed rates and product codes in by hand, and the broker's duty bill was split across products by cost. <strong>Customs entries</strong> reads the entry for you. Import a broker's 7501 or your ACE ES-003 report, and SKU.io matches each line to your purchase order. It proposes the duty rates and product codes the entry proves, and lets you split the duty bill by what each product was actually charged.</p>
<p><strong>✨ What this means for you:</strong></p>
<ul>
<li class=""><strong>Set up duty in minutes, not days.</strong> One entry proposes a dated rate for every tariff it lists, plus the HTS code and country of origin for every matched product. You review the proposals and apply them in one click.</li>
<li class=""><strong>Duty lands on the right products.</strong> A duty bill split by customs entry gives each product the duty charged on its own entry line. A product taxed at 25% is no longer averaged with one taxed at 7.5%, so landed cost and margins come out right.</li>
<li class=""><strong>Problems with an entry show up on their own.</strong> SKU.io flags a declared value far from what you paid, a product filed under a different HTS code, an invoice converted at the wrong currency rate, and an entry filed for another company.</li>
<li class=""><strong>Your IEEPA refund list is ready.</strong> A banner totals the IEEPA duty on your entries, and <strong>Export worksheet</strong> downloads the lines for your refund claim.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="bring-in-your-entries">Bring in your entries<a href="https://www.sku.io/docs/release-notes/2026/11/02/customs-entries/#bring-in-your-entries" class="hash-link" aria-label="Direct link to Bring in your entries" title="Direct link to Bring in your entries" translate="no">​</a></h2>
<p>Open the new <strong>Customs entries</strong> tab under <strong>Settings → Purchasing → Duty Rates</strong> and click <strong>Import entries</strong>. Choose <strong>7501 PDF</strong> for a single entry from your broker, or <strong>ACE ES-003 report</strong> to import every entry under your importer number at once, from CSV or Excel. The file is read in the background, and each entry lands in the list for review. Nothing changes until you apply it. Importing the same file again does nothing. An amended entry becomes a new revision, with a banner listing what changed.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/customs-entries/customs-entries-list.png" alt="The Customs entries tab, with the IEEPA duty banner above the list of imported entries" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="review-what-the-entry-proves-then-apply-it">Review what the entry proves, then apply it<a href="https://www.sku.io/docs/release-notes/2026/11/02/customs-entries/#review-what-the-entry-proves-then-apply-it" class="hash-link" aria-label="Direct link to Review what the entry proves, then apply it" title="Direct link to Review what the entry proves, then apply it" translate="no">​</a></h2>
<p>Open an entry to see its totals, its checks and its lines. Each line shows the full tariff stack and the purchase order lines it was matched to, with how confident the match is. You can fix any match by hand. Under <strong>Proposals</strong>, SKU.io ticks the changes it's sure about. These are the HTS code and origin for each product, a dated duty rate for each tariff, and the empty customs fields on the inbound shipment. Each rate card says whether it's new, matches a rate you already have, or differs from it. Untick anything you're unsure of and click <strong>Apply selected</strong>. Your purchase orders then estimate duty with the new rates and codes.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/customs-entries/entry-proposals.png" alt="Duty rate proposals for each tariff on the entry, ticked and ready to apply" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="split-the-duty-bill-by-what-was-actually-charged">Split the duty bill by what was actually charged<a href="https://www.sku.io/docs/release-notes/2026/11/02/customs-entries/#split-the-duty-bill-by-what-was-actually-charged" class="hash-link" aria-label="Direct link to Split the duty bill by what was actually charged" title="Direct link to Split the duty bill by what was actually charged" translate="no">​</a></h2>
<p>Link the broker's bill to the entry with <strong>Link duty bill</strong>. On the bill, set <strong>Proration Method</strong> to <strong>By cost category</strong>. The duty line then splits <strong>By customs entry</strong>, while freight and brokerage keep their own method. <strong>How this bill is split</strong> shows the result per product. When every line on the entry is matched, the duty split is exact to the cent. If no fully matched entry is linked, the duty falls back to estimated duty, then to cost, as before.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/customs-entries/bill-split-by-entry.png" alt="A broker bill whose duty line is split By customs entry while the other lines are split By cost" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-to-find-it">Where to find it<a href="https://www.sku.io/docs/release-notes/2026/11/02/customs-entries/#where-to-find-it" class="hash-link" aria-label="Direct link to Where to find it" title="Direct link to Where to find it" translate="no">​</a></h2>
<p>Go to <strong>Settings → Purchasing → Duty Rates</strong> and open the <strong>Customs entries</strong> tab. Roles that can already manage duty rates get access automatically.</p>
<p><strong>Full guide:</strong> <a href="https://www.sku.io/docs/guides/orders/duties-and-tariffs/import-customs-entries" target="_blank" rel="noopener noreferrer" class="">Import customs entries</a></p>]]></content>
        <author>
            <name>SKU.io Product Team</name>
            <uri>https://sku.io</uri>
        </author>
        <category label="Major Feature" term="Major Feature"/>
        <category label="New" term="New"/>
        <category label="Purchasing" term="Purchasing"/>
        <category label="Accounting" term="Accounting"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Ecommerce standard chart of accounts — a chart built for selling on marketplaces]]></title>
        <id>https://www.sku.io/docs/release-notes/2026/11/02/ecommerce-standard-chart/</id>
        <link href="https://www.sku.io/docs/release-notes/2026/11/02/ecommerce-standard-chart/"/>
        <updated>2026-11-02T02:01:42.000Z</updated>
        <summary type="html"><![CDATA[New accounts now start with a chart made for ecommerce sellers, and existing accounts can add the missing pieces in one reviewed step, without changing anything already set.]]></summary>
        <content type="html"><![CDATA[<p>A general-purpose chart of accounts doesn't fit how an online seller makes money. Shipping you charge lands in Sales, marketplace fees, fulfillment fees and storage fees pile into one line, and anything a payout can't place falls back to a catch-all you have to clean up at month end. Fixing it by hand means creating a dozen accounts and pointing every mapping at the right one. The <strong>ecommerce standard chart of accounts</strong> does that for you. New accounts start with it, and if you're already set up, <strong>Apply ecommerce standard</strong> shows you exactly what's missing and adds only that, leaving everything you've already set exactly as it is.</p>
<p><strong>✨ What this means for you:</strong></p>
<ul>
<li class=""><strong>A chart made for marketplace selling:</strong> shipping income, sales discounts, marketplace reimbursements, separate accounts for referral, fulfillment, storage and other marketplace fees, merchant processing fees, advertising, and a clearing account for each channel.</li>
<li class=""><strong>Fees sit above gross margin:</strong> marketplace and processing fees are cost of sales, so your gross margin is what you keep after selling on each channel. Advertising stays an operating expense.</li>
<li class=""><strong>Purchases are split properly:</strong> goods you've received but not been billed for and bills you've paid ahead of delivery go to two separate accounts, so each one can be reconciled.</li>
<li class=""><strong>Payouts have somewhere sensible to go:</strong> lines with no mapping post to <strong>Marketplace Reimbursements</strong> (money in) or <strong>Marketplace Fees: Other</strong> (money out), so they're easy to find and reclassify.</li>
<li class=""><strong>Adding it is safe:</strong> you see a full preview first. Nothing already set is remapped, renamed or deleted, and nothing is written in a locked period.</li>
<li class=""><strong>One chart, every channel in your reports:</strong> tag revenue, cost of goods sold, marketplace fees and FBA inventory with the sales channel in Xero or QuickBooks Online.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="see-exactly-whats-missing-before-anything-changes">See exactly what's missing before anything changes<a href="https://www.sku.io/docs/release-notes/2026/11/02/ecommerce-standard-chart/#see-exactly-whats-missing-before-anything-changes" class="hash-link" aria-label="Direct link to See exactly what's missing before anything changes" title="Direct link to See exactly what's missing before anything changes" translate="no">​</a></h2>
<p>On <strong>Nominal Code Mappings</strong>, click <strong>Apply ecommerce standard</strong>. SKU.io compares your chart and mappings with the standard and lists every difference in one table: accounts it would add, mappings it would fill, and how many settings are <strong>already set and left untouched</strong>. When you already have a matching account, it's reused instead of duplicated. When a standard account number is already taken, the new account uses the next free number, and the row tells you so.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/ecommerce-standard-chart/preview.png" alt="The Apply ecommerce standard preview: 16 accounts to add, 19 mappings to fill and 20 settings already set and left untouched, with rows to add 4200 Marketplace Reimbursements, the 5200–5250 marketplace and processing fee accounts, 6201 Advertising and channel clearing accounts" class="img_ev3q"></p>
<p>Every row says what ticking it does to your books. <strong>No posting change</strong> means the account simply becomes available. <strong>Changes future postings</strong> means entries that fall back to another account today will post to the new one, starting from the date shown. Earlier entries and payouts keep their accounts. If you use Xero or QuickBooks Online, accounts are created there only where you switch it on.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="put-marketplace-fees-in-the-right-place">Put marketplace fees in the right place<a href="https://www.sku.io/docs/release-notes/2026/11/02/ecommerce-standard-chart/#put-marketplace-fees-in-the-right-place" class="hash-link" aria-label="Direct link to Put marketplace fees in the right place" title="Direct link to Put marketplace fees in the right place" translate="no">​</a></h2>
<p>The standard also fills payout mappings that are still empty. Fee types SKU.io recognizes are matched to the right fee account (for example, referral and final value fees to <strong>Marketplace Fees: Referral</strong> and ad fees to <strong>Advertising</strong>), and each channel's fallback for unmapped lines is set. Types it doesn't recognise, and anything you've already mapped, are left alone.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/ecommerce-standard-chart/payout-mappings.png" alt="The Payout mappings section of the preview: Amazon and Walmart fallbacks filled with 4200 Marketplace Reimbursements and 5230 Marketplace Fees: Other, and eBay fee types mapped to 5200 Marketplace Fees: Referral, 5230 Marketplace Fees: Other and Advertising, each marked as changing future postings from the date shown" class="img_ev3q"></p>
<p>A few rows start unticked on purpose. The split for goods received but not billed changes how purchases post, so you choose it yourself, and existing history is only restated with SKU support's help. Clearing accounts for channels whose deposits SKU.io doesn't post through yet are offered for your bank-feed reconciliation, but are off by default.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="apply-in-one-step">Apply in one step<a href="https://www.sku.io/docs/release-notes/2026/11/02/ecommerce-standard-chart/#apply-in-one-step" class="hash-link" aria-label="Direct link to Apply in one step" title="Direct link to Apply in one step" translate="no">​</a></h2>
<p>Tick the rows you want and click <strong>Apply</strong> (the button shows how many changes you picked). SKU.io confirms how many accounts it added and how many mappings it filled, and from which date, and links each new account so you can open it straight away.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/ecommerce-standard-chart/applied.png" alt="The confirmation after applying: 7 accounts added and 15 mappings filled, nothing already set changed, listing 4200 Marketplace Reimbursements, 5200 to 5250 marketplace and processing fee accounts and 6201 Advertising" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="report-by-channel-without-a-longer-chart">Report by channel without a longer chart<a href="https://www.sku.io/docs/release-notes/2026/11/02/ecommerce-standard-chart/#report-by-channel-without-a-longer-chart" class="hash-link" aria-label="Direct link to Report by channel without a longer chart" title="Direct link to Report by channel without a longer chart" translate="no">​</a></h2>
<p>The standard keeps one short chart and uses <strong>channel tracking</strong> to tell your channels apart. On <strong>Tracking Categories</strong>, the <strong>Channel tracking</strong> card shows exactly what it will create in your accounting software: a <strong>Channel</strong> tracking category in Xero, or a set of classes in QuickBooks Online, with one option per kind of sales channel. It applies to revenue, cost of goods sold, marketplace fees and FBA inventory. Nothing is created until you tick the box confirming it. New accounts that connect Xero or QuickBooks Online are offered the same step during setup. See <a href="https://www.sku.io/docs/guides/accounting/set-up/accounts-and-channels/tag-entries-by-channel-with-tracking-categories" target="_blank" rel="noopener noreferrer" class="">Tag entries by channel with tracking categories</a> for how tagging works.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/ecommerce-standard-chart/channel-tracking.png" alt="The Channel tracking card for QuickBooks Online: options for Amazon, Shopify, eBay, Walmart, Temu, Website and other channels, applied to revenue, cost of goods sold, marketplace fees and FBA inventory, with the confirmation ticked and the Create in QuickBooks Online button enabled" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-to-find-it">Where to find it<a href="https://www.sku.io/docs/release-notes/2026/11/02/ecommerce-standard-chart/#where-to-find-it" class="hash-link" aria-label="Direct link to Where to find it" title="Direct link to Where to find it" translate="no">​</a></h2>
<p>Go to <strong>Accounting</strong>, click <strong>Settings</strong>, and open <strong>Nominal Code Mappings</strong>. <strong>Apply ecommerce standard</strong> is at the top of the panel. Channel tracking is under <strong>Settings</strong> → <strong>Tracking Categories</strong>. New accounts get the ecommerce standard chart automatically when they set up accounting.</p>]]></content>
        <author>
            <name>SKU.io Product Team</name>
            <uri>https://sku.io</uri>
        </author>
        <category label="Major Feature" term="Major Feature"/>
        <category label="New" term="New"/>
        <category label="Accounting" term="Accounting"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Month-end split — marketplace settlements post to the month they belong to]]></title>
        <id>https://www.sku.io/docs/release-notes/2026/11/02/settlement-month-end-split/</id>
        <link href="https://www.sku.io/docs/release-notes/2026/11/02/settlement-month-end-split/"/>
        <updated>2026-11-02T01:56:06.000Z</updated>
        <summary type="html"><![CDATA[Amazon, Walmart, eBay and TikTok Shop settlements that cross a month end now book each month's sales and fees in that month, and still add up to the deposit.]]></summary>
        <content type="html"><![CDATA[<p>Marketplaces don't pay out on the 1st of the month. An Amazon settlement deposited on August 11 can carry two weeks of July sales, so July's revenue, fees and refunds land in your August books, and every month-end close needs a manual adjustment. <strong>Month-end split</strong> fixes that for Amazon, Walmart, eBay and TikTok Shop. When a settlement or payout runs across a month end, SKU.io posts one set of documents per month: each month's lines are booked in that month, and together they still add up to the deposit.</p>
<p><strong>✨ What this means for you:</strong></p>
<ul>
<li class="">Sales, fees and refunds land in the <strong>month they happened</strong>, not the month Amazon or Walmart happened to pay you.</li>
<li class="">The parts <strong>still add up to the deposit</strong>, so bank reconciliation works exactly as before.</li>
<li class=""><strong>Locked months never change.</strong> Lines dated in a closed period post in the first open month.</li>
<li class="">New marketplace connections have it <strong>on from the start</strong>; existing ones switch it on with a date you choose.</li>
<li class="">Every settlement shows <strong>which months it posted to</strong>, with links to each month's documents.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="one-set-of-documents-per-month">One set of documents per month<a href="https://www.sku.io/docs/release-notes/2026/11/02/settlement-month-end-split/#one-set-of-documents-per-month" class="hash-link" aria-label="Direct link to One set of documents per month" title="Direct link to One set of documents per month" translate="no">​</a></h2>
<p>Turn on <strong>Split settlements at month end</strong> (eBay and TikTok Shop call it <strong>Split payouts at month end</strong>) on the channel's settlement or payout mappings page, and pick a <strong>Split from</strong> date. From then on, a settlement whose lines cross a month end posts in parts:</p>
<ul>
<li class="">Each earlier month posts on <strong>that month's last day</strong>. Its reference carries the month, for example <code>-2026-07</code>.</li>
<li class="">The last part keeps the <strong>settlement date</strong> and the usual reference.</li>
</ul>
<p>A settlement whose lines all fall in one month posts exactly as it always has. Settlements already sent to Xero or QuickBooks keep the shape they were sent with.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/settlement-month-end-split/part-reference.png" alt="An invoice for the July part of a Walmart settlement: dated Jul 31, 2026, with the month added to its reference" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="see-where-every-settlement-landed">See where every settlement landed<a href="https://www.sku.io/docs/release-notes/2026/11/02/settlement-month-end-split/#see-where-every-settlement-landed" class="hash-link" aria-label="Direct link to See where every settlement landed" title="Direct link to See where every settlement landed" translate="no">​</a></h2>
<p>Each settlement and payout page has a new <strong>Months posted to</strong> card. It shows each month the settlement posted to, the date its documents carry, how many lines fell in that month, their net, and links to the documents themselves. A chip at the top tells you at a glance whether the settlement was split.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/settlement-month-end-split/months-posted-to.png" alt="The Months posted to card on a Walmart settlement: July 2026 posts on Jul 31 and August 2026 on the settlement date, Aug 11, each with its own invoice and bill" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="shopify-and-temu">Shopify and Temu<a href="https://www.sku.io/docs/release-notes/2026/11/02/settlement-month-end-split/#shopify-and-temu" class="hash-link" aria-label="Direct link to Shopify and Temu" title="Direct link to Shopify and Temu" translate="no">​</a></h2>
<p>Shopify and Temu payouts already split at month end with their own settings, on their payout mappings pages. Nothing changes there.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-to-find-it">Where to find it<a href="https://www.sku.io/docs/release-notes/2026/11/02/settlement-month-end-split/#where-to-find-it" class="hash-link" aria-label="Direct link to Where to find it" title="Direct link to Where to find it" translate="no">​</a></h2>
<p><strong>Apps &amp; Integrations → your Amazon, Walmart, eBay or TikTok Shop store → Finance → Settlement Mappings</strong> (eBay and TikTok Shop: <strong>Payout Mappings</strong>). The <strong>Months posted to</strong> card is on each settlement or payout page.</p>
<p><strong>Full guide:</strong> <a href="https://www.sku.io/docs/guides/integrations/basics/map-products-stock-and-payouts/split-settlements-at-month-end/" target="_blank" rel="noopener noreferrer" class="">Split settlements and payouts at month end</a> (with a short video walkthrough).</p>]]></content>
        <author>
            <name>SKU.io Product Team</name>
            <uri>https://sku.io</uri>
        </author>
        <category label="Major Feature" term="Major Feature"/>
        <category label="New" term="New"/>
        <category label="Accounting" term="Accounting"/>
        <category label="Integrations" term="Integrations"/>
    </entry>
    <entry>
        <title type="html"><![CDATA[Amazon min/max allowed price — stop Seller Central limits from deactivating your listings]]></title>
        <id>https://www.sku.io/docs/release-notes/2026/11/01/amazon-min-max-allowed-price/</id>
        <link href="https://www.sku.io/docs/release-notes/2026/11/01/amazon-min-max-allowed-price/"/>
        <updated>2026-11-01T22:33:03.000Z</updated>
        <summary type="html"><![CDATA[SKU.io now reads the minimum and maximum on every Amazon offer, checks each price against them before sending, and lists and fixes listings Amazon deactivated for their price.]]></summary>
        <content type="html"><![CDATA[<p>Amazon lets every offer carry a minimum and a maximum price, and it quietly deactivates a listing whose price falls outside them. Those limits often get set in Seller Central, sometimes with the minimum and maximum equal to pin a price, and the next price SKU.io sent could land outside them. The listing stopped selling, and nothing in SKU.io said why. <strong>Amazon min/max allowed price</strong> fixes that: SKU.io now reads Amazon's limits back for every listing, checks each price against them before it goes out, and shows you every listing that's outside its limits, with a one-click fix that doesn't change your prices.</p>
<p><strong>✨ What this means for you:</strong></p>
<ul>
<li class="">See every Amazon listing that's <strong>outside its minimum or maximum</strong>, including the ones Amazon has already <strong>deactivated</strong>, in one place.</li>
<li class="">Know <strong>who set each limit</strong>: Seller Central, or SKU.io.</li>
<li class=""><strong>Fix them in bulk</strong> after a preview. The usual fix moves the conflicting limit to the listing's current price, so your prices don't change.</li>
<li class="">A new price that would land outside a limit set in Seller Central is <strong>held instead of sent</strong>, so the listing stays live.</li>
<li class="">Manage Amazon's minimum and maximum <strong>separately from your SKU.io price guardrails</strong>, which still protect your prices on every channel.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="every-listing-outside-its-limits-in-one-place">Every listing outside its limits, in one place<a href="https://www.sku.io/docs/release-notes/2026/11/01/amazon-min-max-allowed-price/#every-listing-outside-its-limits-in-one-place" class="hash-link" aria-label="Direct link to Every listing outside its limits, in one place" title="Direct link to Every listing outside its limits, in one place" translate="no">​</a></h2>
<p>The new <strong>Amazon min/max</strong> tab on your Amazon <strong>Pricing</strong> page opens with the answer: how many listings are outside their limits, how many Amazon has deactivated, how many prices SKU.io held, and how many it hasn't checked yet. Below that, the problems are grouped by cause, each with a plain explanation and a recommended fix. The table shows each listing's price drawn on Amazon's allowed range, and a chip on every minimum and maximum says whether it was set in Seller Central or by SKU.io.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/amazon-min-max-allowed-price/tab.png" alt="The Amazon min/max tab: counts of listings outside their limits, deactivated, held and not yet checked, and problems grouped by cause with a recommended fix" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="compare-skuio-and-amazon-side-by-side">Compare SKU.io and Amazon side by side<a href="https://www.sku.io/docs/release-notes/2026/11/01/amazon-min-max-allowed-price/#compare-skuio-and-amazon-side-by-side" class="hash-link" aria-label="Direct link to Compare SKU.io and Amazon side by side" title="Direct link to Compare SKU.io and Amazon side by side" translate="no">​</a></h2>
<p>Click a listing to see both halves of the story: the price SKU.io decided on the left, and the range Amazon enforces on the right, with Amazon's own message when it deactivated the listing. From there, <strong>Fix</strong> previews exactly what will be sent before anything reaches Amazon.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/amazon-min-max-allowed-price/drawer.png" alt="A listing's comparison drawer: SKU.io's price on the left, Amazon's minimum and maximum on the right, and Amazon's message that the price is above the maximum" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="amazons-limits-kept-apart-from-your-price-guardrails">Amazon's limits, kept apart from your price guardrails<a href="https://www.sku.io/docs/release-notes/2026/11/01/amazon-min-max-allowed-price/#amazons-limits-kept-apart-from-your-price-guardrails" class="hash-link" aria-label="Direct link to Amazon's limits, kept apart from your price guardrails" title="Direct link to Amazon's limits, kept apart from your price guardrails" translate="no">​</a></h2>
<p>Your <strong>SKU.io price guardrails</strong> (floor, ceiling and maximum change) decide what price SKU.io sends to every channel. Amazon's minimum and maximum are now a separate, Amazon-only card under <strong>Pricing Sync</strong>. For each limit you choose whether SKU.io leaves Seller Central's value alone, removes it, or sets it, for example as a percentage of the price sent. You also choose what happens when a new price falls outside a limit SKU.io doesn't manage: <strong>hold</strong> it, <strong>widen</strong> Amazon's limit to it, or <strong>send</strong> it anyway. Profiles, marketplaces and single listings can override it, and the Amazon Automate Pricing rule now lives here too.</p>
<p><img decoding="async" loading="lazy" src="https://www.sku.io/docs/img/release-notes/amazon-min-max-allowed-price/settings-card.png" alt="The Amazon min/max allowed price card on Pricing Sync, tagged Amazon only, with the minimum and maximum settings and the choice of what happens when a price is outside a limit" class="img_ev3q"></p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-changed-for-your-account">What changed for your account<a href="https://www.sku.io/docs/release-notes/2026/11/01/amazon-min-max-allowed-price/#what-changed-for-your-account" class="hash-link" aria-label="Direct link to What changed for your account" title="Direct link to What changed for your account" translate="no">​</a></h2>
<ul>
<li class=""><strong>If you used a price floor or ceiling on Amazon</strong>, SKU.io used to copy it into Amazon's minimum and maximum. It still does, now shown as <strong>Use the SKU.io guardrail floor</strong> and <strong>ceiling</strong> on the new card, set to send prices as before. Nothing you send has changed.</li>
<li class=""><strong>If you didn't</strong>, SKU.io leaves Amazon's limits as Seller Central has them, and now <strong>holds</strong> a new price that falls outside them instead of sending it. Held listings stay live at their current price and appear on the <strong>Amazon min/max</strong> tab.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="where-to-find-it">Where to find it<a href="https://www.sku.io/docs/release-notes/2026/11/01/amazon-min-max-allowed-price/#where-to-find-it" class="hash-link" aria-label="Direct link to Where to find it" title="Direct link to Where to find it" translate="no">​</a></h2>
<p>Go to <strong>Apps &amp; Integrations → All Integrations → Amazon → Pricing → Amazon min/max</strong> to see listings outside their limits, and <strong>Amazon → Amazon Settings → Pricing Sync</strong> for the <strong>Amazon min/max allowed price</strong> card.</p>
<p><strong>Full guides:</strong> <a href="https://www.sku.io/docs/guides/integrations/amazon/pricing/amazon-min-max-vs-price-guardrails" target="_blank" rel="noopener noreferrer" class="">Amazon min/max and SKU.io price guardrails</a> · <a href="https://www.sku.io/docs/guides/integrations/amazon/pricing/set-amazon-min-max-allowed-prices" target="_blank" rel="noopener noreferrer" class="">Set Amazon min/max allowed prices</a> · <a href="https://www.sku.io/docs/guides/integrations/amazon/pricing/fix-listings-outside-amazon-min-max" target="_blank" rel="noopener noreferrer" class="">Fix Amazon listings outside their min/max</a></p>]]></content>
        <author>
            <name>SKU.io Product Team</name>
            <uri>https://sku.io</uri>
        </author>
        <category label="Major Feature" term="Major Feature"/>
        <category label="New" term="New"/>
        <category label="Integrations" term="Integrations"/>
    </entry>
</feed>