Drop-shipping should be the easiest kind of fulfillment — your supplier ships straight to the customer and you never touch the stock. In practice, an out-of-stock order would quietly backorder against your own warehouse instead of routing to the supplier, and when it didn't drop-ship there was no single place to see why. Drop-ship automation brings the whole flow together: a Drop-ship Status panel that shows exactly why an order will (or won't) route to a supplier, automatic routing of eligible out-of-stock orders, a purchase order created and sent on your behalf, and a clear view of whether that PO actually reached the supplier. No more guessing, no more silent backorders.

If you sell regulated, high-value, or warranty-backed goods — electronics, medical devices, cosmetics, anything with a recall or authenticity requirement — "how many do we have" was never enough. You needed to know which one, and where it went. Until now SKU.io tracked quantities but not the individual units behind them. Serial Number Tracking closes that gap — and now follows each unit end to end: opt in per product, capture a serial as stock arrives, choose the exact units when you fulfill, print them on your pick lists and packing slips, and trace any serial's full history.

Customizing your PDF documents — invoices, purchase orders, packing slips, quotes, credit notes — used to mean wrestling a word-processor-style editor that had its own ideas about your layout. Simple requests like "make the items table span the full page" were surprisingly hard, and anyone comfortable with HTML had to fight the editor's constant reformatting. The new PDF Template Editor replaces all of that with a proper split-pane workspace: your template's HTML on one side, a live PDF preview on the other, and a built-in Template AI assistant that can make layout changes for you from a plain-English instruction — "make the items table full width", "add a Supplier SKU column", "match a clean Stripe-style invoice". Every AI edit is validated, shown as a reviewable diff, and never saved until you say so.

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.

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.

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.

Plenty of 3PLs run their entire warehouse on Odoo — receiving, picking, packing, and shipping all live in their Odoo instance, not in a purpose-built WMS. If that's your fulfillment partner, keeping SKU.io in step has meant emailing spreadsheets of orders, waiting for someone on their side to key them in, and then chasing tracking numbers and stock counts by hand. The new Odoo 3PL integration treats that Odoo-powered warehouse as a first-class fulfillment provider inside SKU.io: connect once, and outbound orders flow straight to the 3PL, tracking and shipping details come back on their own, and the warehouse's live stock-on-hand syncs into SKU.io — with the 3PL kept as the source of truth for what's physically on the shelf.

Sending an FBA replenishment through a 3PL or supplier has always meant a scramble of emails — FNSKU labels in one attachment, box-content rules in another, prep instructions pasted into a note, and a separate back-and-forth just to confirm anything actually shipped. FBA Inbound for 3PLs & Suppliers replaces all of that with one clean handoff. When an inbound plan is sourced from a 3PL warehouse or a supplier, SKU.io packages everything the recipient needs into a single branded portal and emails them the link. And when a line is a kit your 3PL still has to assemble, SKU.io spells out exactly what to build and allocates the components so you can't oversell them.

If you fulfill through Walmart Fulfillment Services (WFS), the stock Walmart holds for you has always been a blind spot in SKU — you had to jump back into Seller Center to see quantities, plan replenishment, and put together an inbound shipment. Walmart Fulfillment Services support closes that gap: turn it on for your Walmart integration and SKU gives you a live view of your WFS inventory, a guided workflow to build and send inbound shipments, and end-to-end tracking of those shipments into Walmart's fulfillment centers.