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.

Need to tell a batch of customers their orders are delayed, back in stock, or shipping Monday? Until now that meant opening each sales order and sending one email at a time — and a customer with five orders received five separate emails. Bulk Customer Emails changes that. Select any set of sales orders and SKU emails their customers in a single action, automatically grouping every order for the same customer into one message, skipping anyone without an address, and recording each send to the order's history.

Pricing tiers used to be entirely manual: every product needed a fixed price typed in for every tier. With ten tiers across thousands of products, that's tens of thousands of prices to maintain — and the moment a base price moved, you were updating Wholesale, Distributor, and Employee one product at a time. Relative Pricing Tiers let a tier calculate its own prices from a formula instead. Pick what the tier is based on, set the adjustment, and SKU keeps every product's price in that tier current for you.

Filing a state sales-tax return used to mean leaving SKU.io, exporting orders, and rebuilding the numbers in a spreadsheet — channel by channel, because each marketplace only shows you its own slice. Sales Tax Reporting brings the whole picture into one place: tax collected by destination state, the split between what you owe and what your marketplaces already remitted for you, and a live view of where you're approaching economic-nexus thresholds.

If you've ever compared a product's average cost on the Products list against the Inventory Valuation report and gotten two different numbers, you've met one of the oldest annoyances in inventory software: a stored "average cost" field that slowly drifts away from what your inventory is actually worth. Costs got written to that field by different workflows over the years, and rounding, timing, and edge cases let it wander. With this release, average cost is now derived directly from your FIFO inventory layers — the same ledger that values your stock — and every screen, report, export, and filter in SKU.io reads from that single source. The number you see on the Products list, the Inventory Planning Report, the Inventory Valuation report, a CSV export, or an answer from the AI assistant is now the same number, and it always reconciles: average cost × on-hand quantity = stock value, to the cent.

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.