If you've ever re-run the Inventory Valuation report "as of" a closed month and gotten a different number than last time, you know how unsettling that is — especially at month-end close. It happened because cost corrections (a late freight bill, a vendor invoice true-up, a write-down) silently rewrote history: the report always valued past inventory at today's cost. With Inventory Revaluations, every cost change is now a dated, auditable event. The valuation report values each period at the cost that was in effect on that date, so the same as-of date returns the same value — no matter what corrections land later.

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.

If you make or assemble what you sell, you've been stitching the production side together by hand — drawing down raw-material stock in one place, adding finished units in another, and working out what each batch actually cost in a spreadsheet. SKU now does all of it for you. Manufacturing lets you define a recipe once, run a manufacturing order to turn components into finished goods, and have SKU consume the raw materials, receive the finished product into stock, and post the accounting — automatically, every time you produce.

If you run Amazon in SKU.io, your day moves across a lot of pages — orders, FBA inventory, removal orders, reimbursements, settlements, reports. Until now those pages didn't all look or behave the same way, so a single workflow could feel like using two different products: different navigation, different tables, different filters. We've rebuilt the entire Amazon integration into one modern, consistent workspace. Every page now shares the same layout, the same powerful filtering and saved views, the same exports and bulk actions — and a single view across all your Amazon accounts.

Fixing one field on a record used to mean a full detour: open the purchase order, change the supplier or the date, save, then click back to the list. Do that across a dozen rows and it's a dozen round-trips. Now your data tables have a new grid view — flip a switch and the list becomes a spreadsheet-style grid where you edit values directly in the cells. Your changes save as you go, and you never leave the list.

If you sell on more than one channel, you already know the problem: to check a listing you had to find its product first, open it, and dig into the Listings tab — one product at a time. There was no way to ask "show me every Amazon listing" or "which channels are out of sync with my real stock?" without clicking through your whole catalog. The new Listings and Channel Inventory pages fix that. They give you a single table of every listing across every connected channel — and a dedicated view that shows, at a glance, exactly where each channel's stock has drifted from SKU.io and lets you correct it in bulk.

When a customer has a store credit on file and a sales order they haven't paid yet, the obvious thing to do is use one to settle the other. Until now that took several manual steps — recording a fake payment, remembering to mark the credit as used, and reconciling both sides by hand. Applying Store Credit to Sales Orders turns that into a two-click flow: open the order's Payments tab, pick the credits to apply, and SKU records the allocation, updates the order's balance, and keeps the credit's remaining balance in sync — all in one go.

If you import from one supplier but distribute across several locations — an inspection sample to HQ, the bulk to a 3PL, more again to a second 3PL — you've been forced to fight the system. SKU treated the PO's destination warehouse as the single truth, so the only way to record reality was to split one commercial order into multiple POs and reconcile the duplicates against your vendor's invoices and deposits by hand. Multi-warehouse receiving changes that. The inbound shipment is now the authoritative unit of "where the goods land," and each shipment on a PO can be sent to a different warehouse — while the PO itself stays a single commercial document.

If you manage more than a handful of SKUs, you already live the 80/20 problem: roughly 20% of your products drive 80% of your revenue — but the long tail quietly declining, the winner you should be reordering harder, the SKU that's thriving on Amazon while it collapses on your Shopify store — none of that is visible without exporting sales orders and reconciling them by hand. Product Analytics turns the sales, purchasing, COGS, and inventory data SKU already holds into a single decision-making surface: a macro dashboard that ranks every product, a weighted performance scorecard on each one, and a true per-channel breakdown of where the revenue is actually coming from.