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.

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.

As you grow, "which shelf is that on?" becomes the question that slows your whole warehouse down. Stock lands wherever there's room, pickers wander the floor hunting for it, and the only real map lives in someone's head. Warehouse Locations gives that map a home in SKU.io: divide any warehouse into typed, barcoded bins — receiving docks, pick faces, bulk reserve, returns, shipping — and every unit of stock now has an exact address. From there, SKU.io does the thinking for you: it suggests where to put stock away on receipt, generates a guided pick route that walks staff bin-by-bin, keeps your pick faces topped up from reserve, and lets you move a whole pallet in one step. Best of all, you turn it on in place on a live warehouse — no re-creating warehouses, no stopping to count.

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.

Selling in person used to mean running a separate point-of-sale system — Square, Shopify POS, Lightspeed — and then reconciling every one of those sales back into SKU.io at the end of the day. Your on-hand counts, customer history, and financials were always a step behind, and closing the books meant matching two systems by hand. SKU.io Point of Sale removes the second system entirely: a fast, touch-friendly register lives right inside SKU.io. Ring up a sale at the counter and it instantly becomes a paid, fulfilled sales order — inventory decrements on the spot, so your numbers are correct the moment the customer walks out.

If you sell on TikTok Shop, you already know the tax it charges on your time: every order re-keyed into SKU by hand, stock levels that drift out of sync until a listing oversells, tracking numbers copied back into Seller Center one by one, and returns that stay invisible until someone reconciles them weeks later. TikTok's on-time-shipping metrics don't forgive any of it. TikTok Shop is now a first-class sales channel in SKU — connect your seller account once and orders import automatically, available inventory pushes out on a schedule, tracking submits back the moment you fulfill, and returns and refunds land where you can see them. It lives right alongside Shopify, Amazon, and the rest, using the exact same screens you already know.

If you sell decorated goods — embroidered caps, screen-printed tees, engraved tumblers — the details that actually drive the job have never had a real home in your order. Placement, technique, thread or ink colors, stitch count, which logo and whether it's even been digitized yet: all of it ended up crammed into a line's description or a spreadsheet on someone's desk, unqueryable and impossible to cost. Made-to-Order Decoration brings that world into SKU.io as structured data — a decoration spec you attach to any order line, registries of methods and placements you control, and a pro-forma cost estimate that shows you the margin before you accept the order.

If you build what you sell, planning has meant exporting to a spreadsheet and working the math by hand — which finished goods to build, which components that build will burn through, what's already on order, and what you still need to buy before you run short. SKU's old demand suggestions only ever looked at the finished product one level deep; they never opened up the recipe underneath. Material Requirements Planning replaces that with a full multi-level engine: one run explodes every bill of materials, nets each part against everything you have and everything that's coming, and hands you dated planned orders to make, buy, and transfer — all in one place.

If you sell supplements, food, cosmetics, pet products, or anything else with a shelf life, you need to know exactly which batch is on the shelf, when it expires, and whether you're shipping the soonest-to-expire stock first. Until now SKU could only capture that detail inside manufacturing. Lot & Expiry Tracking brings batch numbers and expiration dates to the entire platform — capture them when you receive, pick the right lots automatically, and see what's expiring (and what it's worth) before it becomes a problem.

Sending an FBA replenishment through a 3PL or supplier has always meant a scramble of emails — FNSKU labels in one attachment, box-content rules in another, prep instructions pasted into a note, and a separate back-and-forth just to confirm anything actually shipped. FBA Inbound for 3PLs & Suppliers replaces all of that with one clean handoff. When an inbound plan is sourced from a 3PL warehouse or a supplier, SKU.io packages everything the recipient needs into a single branded portal and emails them the link. And when a line is a kit your 3PL still has to assemble, SKU.io spells out exactly what to build and allocates the components so you can't oversell them.