When a customer checks out with an offline payment method — a bank transfer, a purchase order, a "pay on delivery" — the order lands in SKU.io unpaid, yet until now it behaved exactly like an order you'd already been paid for: it allocated your stock immediately and could sail straight through to fulfillment. So a wire that might never arrive could quietly tie up inventory for weeks, and there was no way to say "hold this until the money's in." The new Unpaid Orders settings let you decide, per sales channel, exactly how an unpaid order is handled — bring it in as a held reserve with an automatic expiry, park it as a draft for review, or treat it as open and let it ship — with per-payment-method overrides and control over when it reaches your accounting software.

You went to the trouble of entering your marketing spend, 3PL fees, software subscriptions and Amazon storage costs, and allocating them to the right products and brands — but your Profitability Report acted like none of it existed. It stopped at gross profit, so a brand that looked healthy on paper could be underwater once its share of overhead landed. The Profitability Report now includes the cost entries you allocate — every marketing campaign, fee and overhead cost folds into the report as a distinct, auditable cost line, and the bottom line becomes a full margin ladder: Revenue → Gross Profit → Contribution Margin → Operating Profit.

If you sell on more than one channel, your Xero or QuickBooks profit and loss report probably can't tell you which channel actually makes money — Amazon revenue, Shopify revenue and your wholesale orders all land in the same sales and cost-of-goods accounts. Until now the only way to split them out was to create a separate account for every channel, which bloats your chart of accounts and makes month-end a chore. SKU.io now supports Tracking Categories — map each of your sales channels to a Xero tracking category option (or a QuickBooks class), and every invoice, credit and cost-of-goods journal we post carries that tag. Run your provider's normal P&L-by-tracking-category report and your numbers are already split by channel — no extra accounts required.

The number Shopify deposits into your bank account is never your sales number. Every payout bundles sales, refunds, processing fees, and adjustments into a single net amount — so at month end someone has to reconstruct each deposit from dozens of individual invoices, or worse, book the whole thing to one income account and quietly misstate revenue, tax, and fees. SKU.io now syncs your Shopify Payments payouts and can post one summarized accounting entry per payout — sales, refunds, fees, and adjustments each routed to the right ledger account, with the net matching your bank deposit to the cent. When the deposit appears in your bank feed, it reconciles in one click.

When a product comes in five colours, "Red", "Blue" and "Green" in a dropdown tell you almost nothing — is that red a crimson or a brick? And for anything with a pattern or texture, a word can't describe it at all. Shoppers pick with their eyes, and so do the marketplaces you list on. SKU.io now supports swatches — give each option of a product attribute a colour chip or a small image, and that swatch shows up on your variant products and flows out to the channels that support variant swatches, like Walmart and Shopify. No more guessing which "Red" is which.

You close the books for a month, reconcile everything to QuickBooks or Xero, and move on — and then a customer return, a late supplier bill, or a marketplace settlement shows up dated back in that closed period. Do you let it silently change a month you've already reported? Block it and lose the transaction entirely? Neither is a good answer. SKU.io now has first-class accounting lock dates — set the date your books are closed through, and any activity that arrives afterward dated on or before it is automatically posted to the first open day instead, with its original date preserved and clearly flagged. Your closed periods stay closed, and nothing falls through the cracks.

Shopify's profit and margin reports are only as good as the Cost per item you enter on each product — and that number goes stale the moment your costs change. Keeping it up to date by hand across a whole catalog is tedious, easy to forget, and the reason so many Shopify profit reports quietly drift out of line with reality. SKU.io now syncs your costs to Shopify for you. Turn on Cost Sync for a Shopify store and SKU.io pushes each mapped product's real average cost into Shopify's "Cost per item" field — so Shopify's own profit reports, and any margin app that reads that field, finally show the truth.

Until now, getting data out of SKU.io meant polling the API, exporting spreadsheets, or asking a developer to build something custom. Want a Slack message when goods are received? A Google Sheets row for every new sales order? A customer added to your email tool the moment they first buy? Each one was a mini engineering project. SKU.io now has a native Zapier integration, powered by a new outbound webhooks platform — when something happens in SKU.io, SKU.io tells the outside world about it, in real time. Connect the official SKU.io app on Zapier — now live in the Zapier App Directory in beta — and build those automations in minutes, or point a webhook at your own endpoint and build anything you like.

Customizing your PDF documents — invoices, purchase orders, packing slips, quotes, credit notes — used to mean wrestling a word-processor-style editor that had its own ideas about your layout. Simple requests like "make the items table span the full page" were surprisingly hard, and anyone comfortable with HTML had to fight the editor's constant reformatting. The new PDF Template Editor replaces all of that with a proper split-pane workspace: your template's HTML on one side, a live PDF preview on the other, and a built-in Template AI assistant that can make layout changes for you from a plain-English instruction — "make the items table full width", "add a Supplier SKU column", "match a clean Stripe-style invoice". Every AI edit is validated, shown as a reviewable diff, and never saved until you say so.

When your FBA inventory hits zero, the ASIN goes dark: the Buy Box disappears, rankings decay, and sales stop until your next shipment checks in — often weeks later. The standard workaround is a "backup" merchant-fulfilled offer on the same ASIN, but keeping it live all the time means it can steal the Buy Box while FBA still has stock, and zeroing it in and out by hand doesn't scale past a handful of SKUs. FBM Backup Mode automates the whole dance: SKU.io publishes 0 to your merchant-fulfilled (FBM) listing while a linked FBA offer still has sellable stock, then publishes the real quantity the moment FBA runs out — and re-suppresses it automatically when FBA is replenished. Your offer never flips fulfillment type and never leaves the ASIN; it just waits its turn.