14 posts tagged with "Improved"

In July we added fulfillment-based revenue recognition: sales wait in Deferred Revenue and count as revenue when they ship, in the same entry as their cost of goods. It had one big gap. If your Amazon, eBay, Shopify or Walmart sales are accounted for through their payouts, as most multichannel stores' are, switching on would have counted that revenue twice: once at shipment and again on the payout. Those stores had to stay on order-date revenue. Now they don't. And before anyone switches, SKU.io shows you exactly what would change, month by month, using your own recent orders.

SKU.io's AI features can help with orders, inventory, purchasing and reports. They are much easier to switch on once you can say exactly what the AI is allowed to look at. Many teams are happy for AI to read their catalog and stock, but would rather it never sees a customer's name, email or address. AI data access controls let you decide what SKU.io's AI can see, who on your team can use it, and they keep a record of every AI action.

The emails SKU.io sends for you, such as order confirmations, shipping updates and purchase orders, are often the first thing a customer or supplier sees from your business. Until now, changing one meant hand-editing HTML in a small text box and hoping it looked right in an inbox. Email templates has been rebuilt around an AI assistant: describe the change in plain English, watch a live preview update with a real order, and save when you're happy. The assistant edits the words and the design together, and one change can be applied to every email that needs it.

Changing a handful of values across a list used to mean either opening each record or trusting that every keystroke in the grid was the one you meant. Editable Mode is now a real spreadsheet, and nothing you type is saved until you've seen it. Make all your changes, open Review & save, check each old value against the new one, and save them together, or throw them all away.

Your 3PL counts the stock on its shelves, and SKU.io keeps its own count of the same stock. When the two drift apart, you either sell stock that isn't there or hide stock you could be selling — and comparing them by hand is unreliable, because orders keep shipping while you look. 3PL inventory comparison checks the two against each other automatically, every day, warehouse by warehouse. It rewinds SKU.io to the exact moment the 3PL counted, so a shipment in flight never shows up as a false difference. Where the 3PL is right, you accept its count and SKU.io creates the stock takes for you.

Until now, each integration had a single "Enable Automatic Sync" switch buried in its General settings — and it did more than the label said. Turning it off to pause order imports during a cleanup also stopped tracking numbers from reaching your sales channel, which meant customers stopped getting shipping notifications and marketplace seller metrics quietly degraded. Granular Sync Controls replaces that one overloaded switch with a dedicated Sync tab on every integration, where each direction of data flow gets its own toggle: import orders, import products, submit tracking, push inventory, push prices — each one independent.

When the same customer places two or three orders to the same address within a few days, your warehouse shouldn't have to pick, pack, and dispatch each one separately — that's more labels, more trips to the packing bench, and more chances for something to drift out of sync. Merged fulfillment orders let you combine open orders that ship from the same warehouse to the same address into a single fulfillment order, so they're picked, packed, and dispatched together as one. Each sales order keeps its own line items and identity — nothing is destroyed or rewritten. And now, even when auto-dispatch has already sent your orders on to your carrier or 3PL, SKU can still combine them — safely reconciling with the carrier so your customer gets a single parcel instead of two.

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

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.