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.

Sell something on Monday, ship it on Friday, and your books tell a small lie all week: the revenue is already sitting in your P&L, but the cost of goods doesn't arrive until the shipment goes out. Inside one month it makes your daily margins jumpy; across a month-end it's worse — one period gets revenue with no cost, the next gets cost with no revenue. And if you take pre-orders or run backorders, "revenue you haven't earned yet" can sit in your income statement for weeks. Fulfillment-based revenue recognition is a new accounting policy that fixes this the way accountants say it should be fixed: invoiced sales park in a Deferred Revenue liability, and revenue is only recognized when the goods actually ship — released on the very same entry, and the very same date, as their cost.

If you sell on Magento 2 (Adobe Commerce), keeping your store and your inventory system in agreement has meant CSV exports, copy-paste order entry, and stock levels that drift out of date the moment they're published. The new Magento 2 integration connects your store to SKU.io as a first-class sales channel: orders, products, customers, and transactions flow into a dedicated workspace, SKU.io sales orders are created from Magento orders in bulk or automatically, and on-hand quantities push back to your store's inventory sources on a schedule.

Until now, listings only ever flowed into SKU.io. To actually put a product up for sale you still had to log into each channel's seller portal — eBay Seller Hub, Shopify admin, Amazon Seller Central, Walmart — and re-key the same title, description, images, price, and attributes, once per channel. And because every marketplace requires different fields per category, you often didn't discover a missing attribute until the channel rejected the listing.

Multichannel Listing & PIM closes that gap. SKU.io now doubles as a Product Information Management hub that can publish new listings to and update existing listings on every connected sales channel — so your catalog is the single source of truth and each channel stays in sync with it.

Which material actually makes you money? Which collection is quietly dragging your margin down? If you track those things as product attributes, the answer has always been in SKU — but the Profitability Report couldn't see it. It grouped by Brand, SKU, Supplier, Sales Channel, Product Type, and Sub Sales Channel, and that was it. Anything else meant exporting to a spreadsheet and pivoting by hand. Group by Attribute fixes that. The Profitability Report now offers a seventh grouping: pick any custom product attribute you've defined — Material, Collection, Season, Fit, anything — and the report builds one row per value, with the same revenue, cost, profit, and margin math as every other dimension.

If you plan how much to buy from each supplier every month, that plan probably lives in a spreadsheet — and reconciling it means exporting purchase orders, pivoting them by supplier and month, and eyeballing the result against your budget. By the time you spot an overrun, the money is already spent. Purchasing Targets brings the whole loop into SKU: set a monthly purchase target per supplier, and a live report compares it against your actual purchase orders — with variance, mid-month pacing, and exactly how much room you have left to buy.