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.

Your gross margin says a product is profitable. But after the ad spend, the affiliate payouts, the warehouse rent, and the software subscriptions — is it? Those indirect costs live in invoices and spreadsheets, never connected to the products that caused them. Cost Allocation closes that gap: record any indirect cost in SKU.io, spread it across the products, brands, suppliers, or sales channels it belongs to, and see true contribution margin — revenue minus COGS minus the overhead each product actually carries. It's a profitability layer, not a bookkeeping one: allocations never create accounting transactions, so there's no risk of double-counting against your real books.

"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.

Landed cost bills used to live scattered across the documents they belonged to. A freight invoice was tucked inside its purchase order, a customs bill inside another, an insurance premium inside an inbound shipment — and the only way to answer "which bills haven't been applied to my product costs yet?" was to open every document one by one. Landed Cost Bills is a new register that brings every bill together in a single searchable table, with live totals and an allocation status on every row, so a bill that hasn't reached your landed costs can't go unnoticed.

Customer returns used to mean stitching together a refund here, an inventory adjustment there, and a fresh judgment call on every item about whether it could go back on the shelf. There was no single place to see what was coming back, decide what should happen to it, or measure how much value you were recovering. Returns Management brings the whole flow together: authorize returns as RMAs, receive them at a scan-driven station, let your own rules decide each item's fate, and track recovery in a dedicated dashboard — with marketplace returns pulled in and matched to orders automatically.

Until now, SKU.io access control was all-or-nothing: everyone on your team could see every page and press every button, whether they needed to or not. Your warehouse staff could open accounting reports; a seasonal hire could delete a purchase order. User Roles & Permissions changes that. You build roles from a catalog of 280 fine-grained permissions — covering every area of the app, from products and orders down to individual actions like receiving a transfer or exporting a report — assign those roles to your users, and SKU.io enforces them everywhere: navigation menus, pages, action buttons, and the API itself.

When a supplier issues a credit memo — a short shipment, transit damage, a price adjustment — someone has to key it into SKU line by line, and the PDF itself ends up buried in an inbox or a shared drive. Vendor Credit OCR & Document Attachments ends both problems: attach the credit memo straight to the vendor credit for a permanent audit trail, or upload it and let AI read it for you. SKU extracts the supplier, credit number, date, line items, and totals, matches each line to your products, and pre-fills a vendor credit you review and confirm — turning five to ten minutes of data entry into under two. And credit memos that arrive by email need no upload at all: the Document Inbox now recognizes them automatically and routes them straight to the credit memo review queue.

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.