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 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 buy from more than a handful of suppliers, "how is supplier X doing?" is a question that costs you 20–40 minutes of exporting purchase orders and sales orders into a spreadsheet — and "which supplier grew the most this year, and which one is quietly slipping?" usually never gets asked at all. The data already lives in SKU: every PO, every receipt, every sale and its margin. It's just scattered. Supplier Analytics pulls it together into one decision-making surface: a macro dashboard that ranks your entire supplier base, a weighted performance scorecard on every supplier, and a per-supplier breakdown of which products are driving — or dragging — the relationship.

If you import from overseas, order custom tooling, or pay any supplier a deposit before production starts, you already know the awkward gap: the cash leaves your account weeks before a bill exists, and SKU had nowhere to put it. Until now that money lived in a spreadsheet or got hacked in as a negative bill line — which quietly corrupts your costs. Vendor Deposits closes the gap. It's a new first-class document that lets you record a prepayment, pay it, track it against the purchase order, and automatically net it off the supplier's bill when it finally lands.

You can now turn PDF documents into SKU.io records automatically — no more manual line-by-line entry.

Finding a specific product or order used to mean clicking into the right list, waiting for it to load, then filtering or scrolling until it turned up — and reaching for the mouse for every hop between pages. Now SKU has a redesigned global search and a full set of keyboard shortcuts. Press ⌘K from anywhere to open a command palette that searches across your products, orders, and contacts at once — or jump straight to any page, and select and open rows in your data tables, all without leaving the keyboard.

When a supplier issues a credit — for returned goods, a pricing correction, a damaged shipment, or a volume rebate — where does it go? Until now, the honest answer was usually a spreadsheet, or a manual journal entry in QuickBooks that SKU never saw. There was no record tying the credit back to the original purchase order, no way to apply it against a future bill, and no clean reversal of inventory cost. Vendor Credits changes that: a supplier credit is now a proper document in SKU, with a full lifecycle, that you can apply to bills, reconcile, and sync to your accounting platform.

A new Inventory & Valuation section anchors every Amazon FBA integration, Stock Holds and Allocations become first-class workspaces, and the Profitability report gains FIFO-layer drilldowns.

The Settings area is rebuilt on the modern datatable stack, Stock Takes become a full Vue 3 workspace, a new Profitability report ships, and PDF templates can be set per store.

The COGS rebuild now runs in parallel batches with live progress, a new Purchase Invoices page joins Orders, and a wave of background-job reliability fixes land.