Release Notes — Page 4

If your accountant reports revenue by product line, every product needs the right sales and cost accounts — and until now that meant setting them on each product, one at a time, and remembering to do it for every new product too. Miss one and its sales land in the wrong line of your P&L. Account rules fix that at the source: write a few rules such as "Apparel posts sales to 4010 Apparel Sales", and every matching product follows them — today's catalog and every product you add tomorrow. A live preview shows what a rule will change before you save it, and an account map shows where your whole catalog posts.

Every online store we have run sat on a CMS: an admin login, a stack of plugins and a theme, each one something to patch, defend and pay for. Stores are built differently now. A coding agent can write any design you can describe, so the store doesn't need a screen for a person to click through. It needs a standard, an API, and the freedom to look like anything. So we built one. Storefront is our open-source store kit, with no CMS in the middle, and starting today SKU.io connects to a Storefront store as a sales channel. Orders flow in, and stock, tracking and products flow back out, with no plugins and no keys to copy.

You already ask an AI assistant to draft emails and summarise documents. But when the question is "how much of this do we have, and is more on the way?", it has nothing to go on, so you end up copying numbers out of SKU.io by hand. The new MCP Server connects SKU.io to the assistant you already use: Claude, ChatGPT, Cursor or any other assistant that supports MCP connectors. Add one link, sign in to SKU.io, and the assistant answers from your live products, stock, orders and purchase orders. If you allow it, it can also do the routine work, such as drafting a purchase order or recording a supplier invoice.

When you start on SKU.io you have a reason: fewer oversells, fewer hours lost to purchase orders and stock counts, a faster month-end close. Six months later it's hard to say how far you've come, because nobody wrote down where you started. Success plan fixes that. Pick up to three goals, record where you're starting from, and SKU.io measures the ones it can see in your own orders and stock every month. For the rest, it asks you two quick questions at day 30, 90 and 180 and at year-end.

Some jobs happen one record at a time: add the standard note to an order, flag it for the warehouse, update a supplier in your accounting system. Until now, a workflow could only start on its own, from a schedule or an event, so these jobs stayed manual. Record automations let you run a workflow by hand on the record you're looking at. Open a supplier, product, sales order, purchase order or customer, click the lightning bolt at the top of the page, and pick what to run. A workflow can even hand the job to a script or an AI agent on your own computer, and report the result back on the record.

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.

If your team automates with n8n, connecting it to SKU.io used to mean building every step by hand: an HTTP request for each call, a token pasted into headers, and a webhook wired up separately for each event. SKU.io now has its own node in n8n. Search for SKU in the nodes panel, install it, connect your account once, and your workflows can start the moment something happens in SKU.io and create or find SKU.io records from any other step. The node carries n8n's verified badge, so it installs on n8n Cloud as well as on your own n8n server.

If you sell through Amazon, Walmart and TikTok fulfillment, restocking them is a weekly juggling act. Each network has its own replenishment screen, they all draw on the same stock in your warehouses, and none of them knows what the others asked for, or what you need to keep for the orders you ship yourself. Send Planner puts it into one plan. It works out how much of your stock should go to each network and from which warehouse, keeps enough back for your own orders, shares stock fairly when there isn't enough, and then creates the shipment drafts in each network for you.

When you're stuck on a screen, the answer usually lives in a guide on another tab. You search for it, read it, then switch back and try to remember which button it said to click. In-app guides bring that help to you. Open the guide on any SKU.io screen and it slides in beside the page, with the summary, the video walkthrough and the numbered steps for exactly what you're looking at. You can follow along without leaving your work.

Most teams have a rule for spending money: the purchasing manager signs off on everyday orders, the owner signs off on the big ones, and someone checks every deposit and bill before it's paid. Until now that rule lived in people's heads and inboxes. Approval policies put it in SKU.io. You set tiers by amount and choose who approves each one, and every purchase order, vendor deposit and bill payment is routed to the right people automatically. Approvers work from one Approvals queue, and email alerts mean a request never sits unnoticed.