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.

If you ship through Shippit, you know the drill: every order gets re-keyed into the Shippit merchant portal by hand, labels get printed over there, and then someone copies the tracking number back into SKU.io — order by order, all day. Meanwhile your fulfillments stay open, your sales channels never hear that the parcel shipped, and the real courier cost lives only in Shippit, so your margins are a guess. The new Shippit integration closes that loop end to end. Connect your Shippit account once, and orders routed to Shippit are created there automatically, a courier is allocated and the label generated on Shippit's side, and the moment it's despatched the tracking number, carrier, and shipping cost flow straight back into SKU.io — no re-keying, no copy-paste, no blind spots.

Until now, each integration had a single "Enable Automatic Sync" switch buried in its General settings — and it did more than the label said. Turning it off to pause order imports during a cleanup also stopped tracking numbers from reaching your sales channel, which meant customers stopped getting shipping notifications and marketplace seller metrics quietly degraded. Granular Sync Controls replaces that one overloaded switch with a dedicated Sync tab on every integration, where each direction of data flow gets its own toggle: import orders, import products, submit tracking, push inventory, push prices — each one independent.

Plenty of 3PLs run their entire warehouse on Odoo — receiving, picking, packing, and shipping all live in their Odoo instance, not in a purpose-built WMS. If that's your fulfillment partner, keeping SKU.io in step has meant emailing spreadsheets of orders, waiting for someone on their side to key them in, and then chasing tracking numbers and stock counts by hand. The new Odoo 3PL integration treats that Odoo-powered warehouse as a first-class fulfillment provider inside SKU.io: connect once, and outbound orders flow straight to the 3PL, tracking and shipping details come back on their own, and the warehouse's live stock-on-hand syncs into SKU.io — with the 3PL kept as the source of truth for what's physically on the shelf.

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.

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.

If you fulfill through Walmart Fulfillment Services (WFS), the stock Walmart holds for you has always been a blind spot in SKU — you had to jump back into Seller Center to see quantities, plan replenishment, and put together an inbound shipment. Walmart Fulfillment Services support closes that gap: turn it on for your Walmart integration and SKU gives you a live view of your WFS inventory, a guided workflow to build and send inbound shipments, and end-to-end tracking of those shipments into Walmart's fulfillment centers.

Advertising is usually an Amazon seller's biggest variable cost after the product itself — but until now it lived in a separate tab, invisible to your profitability inside SKU.io. A product could look healthy on margin while quietly losing money once ad spend was counted, and the only way to see the truth was exporting ad reports and inventory reports and joining them by hand in a spreadsheet. Amazon Ads cost attribution closes that gap: connect your Amazon Advertising account and SKU.io automatically pulls your Sponsored Products spend, attributes it to the exact SKU it was spent on, and turns it into real product-level costs — so your contribution margin and ACoS finally include the cost of the ads that drove the sales.

Building an FBA shipment used to mean bouncing between SKU.io, a spreadsheet, and Seller Central — figure out what to send, create a plan in SKU.io, then leave to do packing, placement, carriers, and labels by hand. The most error-prone steps happened outside your system of record, and a multi-SKU shipment could eat an afternoon.

Now you can run the entire Amazon FBA inbound workflow inside SKU.io — from "what should I send?" all the way to "tracking numbers submitted, labels printed." Smart item selection, box content, placement-fee comparison, carrier booking, label printing, and receiving reconciliation are all in one guided flow.