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.

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.