The delivery landed this morning and the cartons are on the dock. The customer's order is packed. But the receipt hasn't been keyed in yet, so SKU.io says you have zero on hand — and it refuses to ship. Until now, the only way out was to fix the paperwork first while the customer waited, or to let a sales channel ship it behind SKU.io's back and quietly lose track of the stock. Inventory debt replaces that with a deliberate choice: ship it now, record exactly what you owe and what it will roughly cost, and let the next receipt settle the difference — automatically, oldest debt first — with your books correct at every step in between.

A supplier sends you a credit note for goods you are keeping — they overcharged you, or they gave you a volume allowance after the fact. The credit should lower what you owe them and lower what those goods cost you. Until now a vendor credit could only do the first part: the stock stayed on your books at a price you never paid, and the only way to fix its cost was to edit the original purchase order or bill — which erased the credit note from your records. Vendor credit cost impact closes that gap. Every line on a credit now states what it does to the goods, a Reason for credit picks the right behaviour for you, and a Cost Impact panel shows the real numbers — which receipts change, how many units are still on hand versus already sold, and what moves on the books — before you click Authorize.

If you sell on Amazon both ways — Fulfilled by Amazon and merchant-fulfilled, where you ship the order yourself — you already know the two rarely want the same price. You carry the shipping on an MFN order, the Buy Box behaves differently, and until now the only way to price those listings apart was to pin them one at a time. The Amazon MFN pricing lane fixes that at the channel level: your merchant-fulfilled listings follow their own sequence of price levels, checked before the channel's FBA levels and falling through to them whenever a product has no MFN price. The channel's Pricing page now says which lane priced every listing, and a new Set Pricing action on the listings table lets you pin — or reset — a whole selection of listings in one go, with a preview of every price that would change.

An email lands from a marketplace: your listing is suspended pending documentation for batch OO-2607-B. Or an auditor picks a batch at random and asks what you tested it for. If your Certificates of Analysis live in an inbox and a shared drive, the next hour is spent searching — and the honest answer to "did anyone check this batch met spec?" is often "probably".

Lot compliance puts that evidence where it belongs: on the batch. File a Certificate of Analysis against the lot it covers, record your own identity check, and enter the lab's numbers so SKU.io judges them against a standard you set. A result outside your limit doesn't just get flagged — it takes the stock off sale.

Plenty of products aren't made in one place. You send ingredients to a co-packer who cooks and blends them, truck the result to a second vendor for filling and pasteurizing, and land the finished cases at a 3PL — three vendors, two hand-offs, one product, and you own the goods the entire way. Until now, modelling that meant inventing the whole structure by hand: a work-in-progress SKU per hand-off, a recipe per stage, lot-tracking flags on every node, contractors, and a production order for each leg — roughly 25 minutes of setup, with several places to get the cost model quietly wrong.

Multi-stage co-manufacturing turns that into one guided flow. Tell SKU.io who does what and what they charge, and it builds the intermediate products, the per-stage recipes, and the vendor terms in a single transaction — then keeps them honest every time you run it.

Every channel has a standard set of product fields, and then it has yours. The care instructions you added as a Shopify metafield. The country_of_manufacture and warranty_months attributes your Magento store has carried for years. That data is real, it's maintained, and until now SKU.io imported none of it — it read the fields every channel has and dropped everything else on the floor, leaving you to re-enter it by hand or accept a catalog that knows less than your storefront does. Channel attributes closes that gap. SKU.io now discovers the attributes your channel actually sends, shows you how many products carry each one and what the values look like, and lets you point them at any SKU product field — either once, when a product is first created, or on every sync, with drift detection watching for changes.

Importing a product from a channel has always been a one-time snapshot. Someone retitles a listing in Seller Central, swaps in a better photo, corrects a weight from pounds to grams — and SKU.io never hears about it. Months later your catalog and your channels have quietly drifted apart, and nobody can say which side is right. The usual workaround is a spreadsheet and a lot of squinting. Living Catalog replaces it: SKU.io now watches the content on your mapped listings, records exactly which fields changed on the channel side, and hands you a review queue instead of a mystery. Nothing is overwritten behind your back — you decide, per field, whether your catalog or the channel is the source of truth.

The same physical part often lives under two SKUs: the official part number customers search for, and the identical equivalent you actually keep on the shelf. Until now those orders just stalled — the listed SKU sat backordered while the interchangeable item was in stock a few feet away, and "fixing" it meant editing order lines by hand. Product substitutions links equivalent SKUs so those orders flow: swap a stalled line to the stocked substitute in one click, or select the whole backlog and release it at once. The customer still sees exactly what they ordered — the invoice and packing slip keep the original SKU — while the pick list tells your warehouse which part to actually pull.

Your demand-planning forecast has always turned recent sales into a reorder quantity — but it treated every product as if it sold at one steady pace. A SKU that has tripled over the last quarter was still planned off its flat average, so you under-bought your fastest movers and over-bought the ones winding down. And when you wanted to plan for a promotion you'd run before, you had to eyeball last year's numbers and mentally scale them up. Trend-aware forecasting changes both: the baseline can now follow a product's trend instead of a flat mean, every recommendation shows exactly how it was built, and a promotion you measured once becomes a reusable lift that automatically scales with how much your business has grown.

Your suppliers rarely reach every one of your warehouses in the same number of days. The same vendor might land stock at your main warehouse in two weeks but take six by sea to a warehouse in another region — yet SKU.io applied a single lead time to every destination, so one of those reorder recommendations was always built on the wrong number. Per-warehouse lead times let you set a default lead time on a supplier and then override it for individual warehouses, and demand planning automatically uses the right one for each destination you forecast.