Changing a handful of values across a list used to mean either opening each record or trusting that every keystroke in the grid was the one you meant. Editable Mode is now a real spreadsheet, and nothing you type is saved until you've seen it. Make all your changes, open Review & save, check each old value against the new one, and save them together, or throw them all away.
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.
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.
Import duty is often one of the biggest costs on a product, and one of the last to show up. Your customs broker bills it weeks after the goods land, as one lump sum for the whole entry, so until then your margins look better than they really are. Then the bill arrives and you have to work out which products it belongs to. Tariffs & duty closes that gap. Keep a table of duty rates by HS code, country of origin and destination, and SKU.io estimates the duty on every purchase order line. The estimate follows the goods to the inbound shipment and the receipt, and can go into stock cost the day they arrive. When the broker's bill comes in, SKU.io shows you how close the estimate was.
When a vendor ships a dropship order straight to your customer, they usually ship on their own carrier account. You pay their markup, you don't control the carrier, and then you chase them for a tracking number and type it in by hand. Dropship vendor shipping labels fixes that. Switch it on for a supplier, and SKU.io buys a prepaid label on your own Shippo, ShipStation, Starshipit or EasyPost account and gets it to the vendor. The label's tracking flows back into the order by itself, so your customer and sales channel hear "shipped" at the right moment.
If you make some of what you sell, a reorder list only tells half the story. You also need to know what to build, when to start it, and which ingredients those builds will use, and that usually means juggling a purchase forecast, a manufacturing suggestion list and a spreadsheet to tie them together. Make, buy & move brings it into one plan. Demand Planning now works out, for every product at every warehouse, whether you make it from its recipe, buy it from a supplier, or move it in from another warehouse. Then it turns the plan into draft orders in one step.
Suppliers sell liquids by volume — a gallon of agave syrup, a drum of oil, a pint of extract. Recipes and stock counts use weight. Those are different kinds of measurement, and the number that connects them is different for every ingredient: a gallon of syrup and a gallon of oil do not weigh the same. Until now, the only way through was to invent a unit per ingredient and type the factor in yourself — a step that quietly goes wrong at receiving and turns into an argument with a supplier about what the purchase order should have said. Density conversions replace that with one number per product. Set the density, and every conversion between a volume unit and a weight unit is worked out for you, with its arithmetic shown on the row.
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.
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.