Which material actually makes you money? Which collection is quietly dragging your margin down? If you track those things as product attributes, the answer has always been in SKU — but the Profitability Report couldn't see it. It grouped by Brand, SKU, Supplier, Sales Channel, Product Type, and Sub Sales Channel, and that was it. Anything else meant exporting to a spreadsheet and pivoting by hand. Group by Attribute fixes that. The Profitability Report now offers a seventh grouping: pick any custom product attribute you've defined — Material, Collection, Season, Fit, anything — and the report builds one row per value, with the same revenue, cost, profit, and margin math as every other dimension.

If you plan how much to buy from each supplier every month, that plan probably lives in a spreadsheet — and reconciling it means exporting purchase orders, pivoting them by supplier and month, and eyeballing the result against your budget. By the time you spot an overrun, the money is already spent. Purchasing Targets brings the whole loop into SKU: set a monthly purchase target per supplier, and a live report compares it against your actual purchase orders — with variance, mid-month pacing, and exactly how much room you have left to buy.

Real business relationships are never one person. Your supplier has a sales rep who quotes, an AR specialist who chases invoices, and a shipping coordinator who books freight — but until now, SKU.io gave you a single "contact name" field and left the rest to sticky notes and inbox archaeology. Contacts replaces that flat field with a full contact book on every supplier, customer, and warehouse: unlimited people, each with a role, email, phone, title, and notes, one of them starred as the primary. Contacts show up right in your supplier, customer, and warehouse lists, flow through import and export like any other data in SKU.io, and their personal details are encrypted at rest.

If you buy or sell across a border, the Incoterm is one of the most consequential fields on the order — it decides who pays the freight, who insures the goods, who clears customs, and the exact moment risk stops being yours. Until now, SKU.io treated it as little more than a note: a free-text code on purchase orders, nothing at all on sales orders, and no explanation of what any of it meant. Incoterms changes that. The 11 official ICC Incoterms® 2020 rules now ship built into every account with plain-English education, a term on an order is a complete value — code, named place, and edition — that's locked into history, and every screen that touches a term can explain exactly who is responsible for what.

A tracking number on its own doesn't tell you anything. To find out whether an order actually reached the customer — or whether a supplier shipment is anywhere near your dock — you had to copy the number, open the carrier's website, and check shipments one at a time. Failed deliveries and stalled packages stayed invisible until a customer complained or a receipt came up overdue. 17TRACK Delivery Tracking changes that: connect your own 17TRACK account and SKU.io registers every new tracking number automatically, pulls live carrier status for it, and shows a delivery-status chip beside the tracking number everywhere it appears — across outbound fulfillments, purchase order inbound shipments, warehouse transfers, customer returns, and shipments back to vendors.

Granular permissions let you decide exactly who can approve a purchase order — but until now, everyone else hit a dead end. A purchasing clerk could build the perfect draft PO and then… nothing. No button, no handoff, no trail. The request lived in a Slack message, the decision lived in someone's head, and the draft sat unnoticed. Purchase Order Approval Requests closes that gap: anyone who can edit a purchase order can now submit it for approval in one click, everyone with approval rights is notified instantly, and the decision — approve, or reject with a reason — lands right back on the order where the whole team can see it.

Every merchant that sells online lives with returns, and the awkward ones are the blemished and open-box items: a watch comes back with a scratched bezel, you can't sell it as new, so it drifts into a corner and quietly loses value until someone finally gets around to listing it somewhere. That "someone" was a job — a person opening each product, writing a listing, setting a price, and babysitting it. Automatic eBay listing for blemished SKUs hands that whole job to SKU.io. The moment a return is received and marked as a new blemished SKU, SKU.io can publish it to eBay as an auction — with the item's condition written into the listing — and then keep relisting it, stepping the price down on a schedule you choose, until it sells.

You set Net 30 on a purchase order, the supplier's invoice arrives — and then nothing. The due date was something you typed in by hand (or didn't), it rendered as plain grey text, and nothing in SKU.io ever told you a payment was about to slip. Late fees, missed early-pay discounts, and a scramble at month-end were the result. Invoice Due Dates & Payment Scheduling closes that loop end to end: due dates now derive themselves from your payment terms, every invoice and bill wears a live overdue / due-soon status, a proper payables aging report shows who you owe by bucket, you can pay a supplier's whole statement in one recorded payment, and the correct due date flows through to Xero and QuickBooks Online so your accounting reports finally agree with SKU.io.

Until now, refunding a customer meant leaving SKU.io. Your CS rep would look up the order here — what shipped, what came back, what's already been credited — then open Shopify admin, or Seller Hub, or Seller Center, re-key the same line items and amounts into that channel's refund form, and hope nothing got transposed along the way. Every channel meant another login, another tab, another place a decimal could slip. Channel Refunds ends the round trip: pick the lines, quantities, and amounts right on the SKU.io sales order and the refund goes out to the channel itself — the customer gets their money back through the original payment method, and the matching sales credit lands in your books automatically, linked to the request that created it.

AI agents are getting genuinely useful — but pointing one at a platform with thousands of API endpoints is a slow, error-prone start. The agent has to rediscover which endpoint does what, what fields it needs, and how the pieces fit, every single time. So teams end up rebuilding the same integration glue over and over. Agentic Skills fixes that. It's a new open-source library of ready-made skills — curated playbooks that tell an AI agent exactly how to accomplish a real business task in SKU: which endpoints to call, in what order, with which fields, plus the e-commerce context to get it right. Point your agent at a skill and it just works.