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.

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.

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.

A tracking number on its own doesn't tell you anything. To find out whether an order actually reached the customer — or whether a supplier shipment is anywhere near your dock — you had to copy the number, open the carrier's website, and check shipments one at a time. Failed deliveries and stalled packages stayed invisible until a customer complained or a receipt came up overdue. 17TRACK Delivery Tracking changes that: connect your own 17TRACK account and SKU.io registers every new tracking number automatically, pulls live carrier status for it, and shows a delivery-status chip beside the tracking number everywhere it appears — across outbound fulfillments, purchase order inbound shipments, warehouse transfers, customer returns, and shipments back to vendors.

Every merchant that sells online lives with returns, and the awkward ones are the blemished and open-box items: a watch comes back with a scratched bezel, you can't sell it as new, so it drifts into a corner and quietly loses value until someone finally gets around to listing it somewhere. That "someone" was a job — a person opening each product, writing a listing, setting a price, and babysitting it. Automatic eBay listing for blemished SKUs hands that whole job to SKU.io. The moment a return is received and marked as a new blemished SKU, SKU.io can publish it to eBay as an auction — with the item's condition written into the listing — and then keep relisting it, stepping the price down on a schedule you choose, until it sells.

Until now, refunding a customer meant leaving SKU.io. Your CS rep would look up the order here — what shipped, what came back, what's already been credited — then open Shopify admin, or Seller Hub, or Seller Center, re-key the same line items and amounts into that channel's refund form, and hope nothing got transposed along the way. Every channel meant another login, another tab, another place a decimal could slip. Channel Refunds ends the round trip: pick the lines, quantities, and amounts right on the SKU.io sales order and the refund goes out to the channel itself — the customer gets their money back through the original payment method, and the matching sales credit lands in your books automatically, linked to the request that created it.

If your fulfillment lives in a third-party warehouse, your operational truth lives in someone else's system. Orders get shipped in the WMS, inventory moves in the WMS, returns land in the WMS — and SKU.io only finds out if someone re-keys it, or if you commissioned a bespoke integration for that one provider. Switch 3PLs, add a second warehouse, or work with a partner running a different platform, and you start over. The new Trackstar integration removes that per-provider tax. Trackstar is a unified API that sits in front of dozens of warehouse systems — ShipBob, ShipHero, Extensiv and more — so a single connection in SKU.io keeps your orders, inventory, products, inbound shipments, returns, shipping methods and bills in sync no matter which WMS is actually doing the work.

Still running a Magento 1 (or OpenMage) storefront? It hasn't had an official update in years, but plenty of stores still sell on it every day — and keeping it in step with the rest of your operation has meant re-keying every order by hand and hoping your published stock levels haven't drifted since the last time someone checked. Magento 1 is now a first-class sales channel in SKU — connect your store once and orders import automatically, your catalog syncs in, and a side-by-side inventory view shows exactly where your real stock and your storefront disagree so you can push the correct numbers back with one click. It lives right alongside Shopify, Amazon, and every other channel, using the same screens you already know.