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.

If you sell on Amazon FBA, storage fees quietly eat into your margins — and until now they were invisible at the product level. Amazon charges them per product, per month, but the only way to see what each product was really costing you was to download a TSV, aggregate hundreds of FNSKUs across fulfillment centers, map them to your products, and hand-enter the totals. Every month. So in practice, nobody did. Amazon storage fee cost allocation changes that: SKU.io now pulls Amazon's two storage fee reports automatically and turns them into per-product cost entries — no spreadsheets, no manual entry.

"If I sell this at $X on Amazon, what do I actually keep?" Until now, answering that meant a spreadsheet — one that doesn't know your real landed costs, your channel's fee schedule, or what actually happened the last hundred times you sold the item. Product Pro Forma is a live, per-channel profitability calculator built into SKU.io. Pick any product (or sketch a hypothetical one you're thinking of sourcing), and it models the full unit economics — selling price, COGS with cost-category breakdown, shipping, marketplace fees, payment fees — for each of your connected sales channels. Every input recalculates the results instantly, and for products you already sell, the estimate sits right next to your actual realized profitability so you can see exactly where your assumptions drift from reality.

Keeping your catalog, inventory, and orders in sync has always meant repetitive busywork: downloading a supplier's price file, massaging the columns, importing it, and doing it all again next week — or asking for custom development every time a partner sends data a slightly different way. Workflows changes that. It's a visual automation builder inside SKU.io where you chain a trigger to a series of actions on a drag-and-drop canvas: when a file lands on an FTP server, when a schedule fires, or when something happens in SKU itself, your workflow picks the data up, transforms it, and writes it into your account — no spreadsheets, no waiting on engineering.

Chasing payment on an order has always meant leaving SKU.io — copying an amount into a separate payment tool, emailing a link by hand, then circling back to mark the order paid once the money landed. It's slow, easy to forget, and the two systems never quite agree.

Stripe Payments closes that loop. Connect your Stripe account once, and you can send a customer a secure, hosted invoice directly from any sales order. Your customer pays with a card through Stripe's checkout, and SKU.io records the payment against the order automatically — no manual reconciliation, no copy-paste, no guesswork.

If you've connected a script, a custom integration, or an automation tool to SKU with a personal access token, that token has been a black box: is it still being used? Is it failing? Is it slow? And — the question that really matters — is it being used from somewhere it shouldn't be? API Usage Log answers all of that. Every API request made with a personal access token is now recorded automatically, and each token gets its own analytics dashboard and a searchable, filterable log of every single request.