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.

If your fulfillment lives in a third-party warehouse, your operational truth lives in someone else's system. Orders get shipped in the WMS, inventory moves in the WMS, returns land in the WMS — and SKU.io only finds out if someone re-keys it, or if you commissioned a bespoke integration for that one provider. Switch 3PLs, add a second warehouse, or work with a partner running a different platform, and you start over. The new Trackstar integration removes that per-provider tax. Trackstar is a unified API that sits in front of dozens of warehouse systems — ShipBob, ShipHero, Extensiv and more — so a single connection in SKU.io keeps your orders, inventory, products, inbound shipments, returns, shipping methods and bills in sync no matter which WMS is actually doing the work.

As you grow, "which shelf is that on?" becomes the question that slows your whole warehouse down. Stock lands wherever there's room, pickers wander the floor hunting for it, and the only real map lives in someone's head. Warehouse Locations gives that map a home in SKU.io: divide any warehouse into typed, barcoded bins — receiving docks, pick faces, bulk reserve, returns, shipping — and every unit of stock now has an exact address. From there, SKU.io does the thinking for you: it suggests where to put stock away on receipt, generates a guided pick route that walks staff bin-by-bin, keeps your pick faces topped up from reserve, and lets you move a whole pallet in one step. Best of all, you turn it on in place on a live warehouse — no re-creating warehouses, no stopping to count.

Still running a Magento 1 (or OpenMage) storefront? It hasn't had an official update in years, but plenty of stores still sell on it every day — and keeping it in step with the rest of your operation has meant re-keying every order by hand and hoping your published stock levels haven't drifted since the last time someone checked. Magento 1 is now a first-class sales channel in SKU — connect your store once and orders import automatically, your catalog syncs in, and a side-by-side inventory view shows exactly where your real stock and your storefront disagree so you can push the correct numbers back with one click. It lives right alongside Shopify, Amazon, and every other channel, using the same screens you already know.

If you ship through Shippit, you know the drill: every order gets re-keyed into the Shippit merchant portal by hand, labels get printed over there, and then someone copies the tracking number back into SKU.io — order by order, all day. Meanwhile your fulfillments stay open, your sales channels never hear that the parcel shipped, and the real courier cost lives only in Shippit, so your margins are a guess. The new Shippit integration closes that loop end to end. Connect your Shippit account once, and orders routed to Shippit are created there automatically, a courier is allocated and the label generated on Shippit's side, and the moment it's despatched the tracking number, carrier, and shipping cost flow straight back into SKU.io — no re-keying, no copy-paste, no blind spots.

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.

Selling in person used to mean running a separate point-of-sale system — Square, Shopify POS, Lightspeed — and then reconciling every one of those sales back into SKU.io at the end of the day. Your on-hand counts, customer history, and financials were always a step behind, and closing the books meant matching two systems by hand. SKU.io Point of Sale removes the second system entirely: a fast, touch-friendly register lives right inside SKU.io. Ring up a sale at the counter and it instantly becomes a paid, fulfilled sales order — inventory decrements on the spot, so your numbers are correct the moment the customer walks out.