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.

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.

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.

Faire joins SKU as a first-class sales channel — connect your account and orders, products, and inventory stay in sync.

The VeraCore fulfillment integration now has a complete, dedicated management workspace.

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.