Your demand-planning forecast has always turned recent sales into a reorder quantity — but it treated every product as if it sold at one steady pace. A SKU that has tripled over the last quarter was still planned off its flat average, so you under-bought your fastest movers and over-bought the ones winding down. And when you wanted to plan for a promotion you'd run before, you had to eyeball last year's numbers and mentally scale them up. Trend-aware forecasting changes both: the baseline can now follow a product's trend instead of a flat mean, every recommendation shows exactly how it was built, and a promotion you measured once becomes a reusable lift that automatically scales with how much your business has grown.

Your suppliers rarely reach every one of your warehouses in the same number of days. The same vendor might land stock at your main warehouse in two weeks but take six by sea to a warehouse in another region — yet SKU.io applied a single lead time to every destination, so one of those reorder recommendations was always built on the wrong number. Per-warehouse lead times let you set a default lead time on a supplier and then override it for individual warehouses, and demand planning automatically uses the right one for each destination you forecast.

Your demand-planning forecast has always given you a reorder quantity — but not a way to tell whether that number was built on two years of steady sales or two days of noise. A brand-new SKU with almost no history looked exactly as authoritative as a proven bestseller, and once you exported the results, the reasoning behind each number disappeared. Forecast confidence fixes that: every recommendation now carries a confidence level, a likely range around the quantity, and a plain-English explanation of how it was calculated — right in the results table, in the calculation detail, and in the export you hand to finance.

You tweak a kit's recipe — swap a component, bump a quantity — and suddenly your history and your forecasts look different, as if the previous version never existed. Worse, you can't answer a simple question: what was actually in this bundle back in the spring? Until now, a bundle or kit had exactly one recipe — whatever it happens to be right now. Recipe History changes that. Every bundle and kit now keeps a full, dated history of its recipe, so you can see what it contained on any date, edit it without rewriting the past, schedule a change ahead of time, and correct a past recipe when something was recorded wrong.

If you sell regulated, high-value, or warranty-backed goods — electronics, medical devices, cosmetics, anything with a recall or authenticity requirement — "how many do we have" was never enough. You needed to know which one, and where it went. Until now SKU.io tracked quantities but not the individual units behind them. Serial Number Tracking closes that gap — and now follows each unit end to end: opt in per product, capture a serial as stock arrives, choose the exact units when you fulfill, print them on your pick lists and packing slips, and trace any serial's full history.

Adjusting stock used to be a leap of faith. When you removed units — for damage, loss, a recount, or a correction — you couldn't see what that stock was already promised to. Take a few units, and a customer's order could quietly slip into backorder with nobody the wiser. Add stock, and you had no idea which waiting orders it would unblock. Now every inventory adjustment shows its impact before you commit — the exact orders it will fill or backorder — so nothing happens behind your back.

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.

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.

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.

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.