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.

If you build what you sell, planning has meant exporting to a spreadsheet and working the math by hand — which finished goods to build, which components that build will burn through, what's already on order, and what you still need to buy before you run short. SKU's old demand suggestions only ever looked at the finished product one level deep; they never opened up the recipe underneath. Material Requirements Planning replaces that with a full multi-level engine: one run explodes every bill of materials, nets each part against everything you have and everything that's coming, and hands you dated planned orders to make, buy, and transfer — all in one place.

You've placed the order, the goods are on their way, and in many cases you've already paid a deposit up front — but the supplier's tax invoice never landed in your inbox. Those missing invoices quietly pile up: your books don't reconcile, you can't reclaim the VAT/GST on money you've already spent, and chasing them means digging through purchase orders one by one to work out who still owes you paperwork. Request Missing Invoices from Suppliers turns that scramble into a one-click ask. SKU now surfaces every purchase order still waiting on its invoice in a dedicated worklist, and lets you email the supplier a polished request — for a single order, or for all of their outstanding orders at once.

When a supplier asks for a deposit or prepayment, the proforma invoice usually lands in someone's inbox — and everything after that happens over email: forward it to whoever pays, re-key the wire details into the bank, then remember to send proof back. Details get lost, nobody can say who approved a five-figure wire or against which PO, and swapped bank details in an intercepted email thread are the classic way overseas payments get stolen. Vendor Deposit Payments pulls the whole flow into SKU — record the supplier's proforma invoice against a purchase order, request payment from a designated payer with the wire instructions attached, capture the payment proof, and email the supplier a remittance advice — with every step on the record.

Landed cost bills used to live scattered across the documents they belonged to. A freight invoice was tucked inside its purchase order, a customs bill inside another, an insurance premium inside an inbound shipment — and the only way to answer "which bills haven't been applied to my product costs yet?" was to open every document one by one. Landed Cost Bills is a new register that brings every bill together in a single searchable table, with live totals and an allocation status on every row, so a bill that hasn't reached your landed costs can't go unnoticed.

When a supplier issues a credit memo — a short shipment, transit damage, a price adjustment — someone has to key it into SKU line by line, and the PDF itself ends up buried in an inbox or a shared drive. Vendor Credit OCR & Document Attachments ends both problems: attach the credit memo straight to the vendor credit for a permanent audit trail, or upload it and let AI read it for you. SKU extracts the supplier, credit number, date, line items, and totals, matches each line to your products, and pre-fills a vendor credit you review and confirm — turning five to ten minutes of data entry into under two. And credit memos that arrive by email need no upload at all: the Document Inbox now recognizes them automatically and routes them straight to the credit memo review queue.

If you've ever compared a product's average cost on the Products list against the Inventory Valuation report and gotten two different numbers, you've met one of the oldest annoyances in inventory software: a stored "average cost" field that slowly drifts away from what your inventory is actually worth. Costs got written to that field by different workflows over the years, and rounding, timing, and edge cases let it wander. With this release, average cost is now derived directly from your FIFO inventory layers — the same ledger that values your stock — and every screen, report, export, and filter in SKU.io reads from that single source. The number you see on the Products list, the Inventory Planning Report, the Inventory Valuation report, a CSV export, or an answer from the AI assistant is now the same number, and it always reconciles: average cost × on-hand quantity = stock value, to the cent.

Fixing one field on a record used to mean a full detour: open the purchase order, change the supplier or the date, save, then click back to the list. Do that across a dozen rows and it's a dozen round-trips. Now your data tables have a new grid view — flip a switch and the list becomes a spreadsheet-style grid where you edit values directly in the cells. Your changes save as you go, and you never leave the list.

If you import from one supplier but distribute across several locations — an inspection sample to HQ, the bulk to a 3PL, more again to a second 3PL — you've been forced to fight the system. SKU treated the PO's destination warehouse as the single truth, so the only way to record reality was to split one commercial order into multiple POs and reconcile the duplicates against your vendor's invoices and deposits by hand. Multi-warehouse receiving changes that. The inbound shipment is now the authoritative unit of "where the goods land," and each shipment on a PO can be sent to a different warehouse — while the PO itself stays a single commercial document.

If you buy from more than a handful of suppliers, "how is supplier X doing?" is a question that costs you 20–40 minutes of exporting purchase orders and sales orders into a spreadsheet — and "which supplier grew the most this year, and which one is quietly slipping?" usually never gets asked at all. The data already lives in SKU: every PO, every receipt, every sale and its margin. It's just scattered. Supplier Analytics pulls it together into one decision-making surface: a macro dashboard that ranks your entire supplier base, a weighted performance scorecard on every supplier, and a per-supplier breakdown of which products are driving — or dragging — the relationship.