If you buy or sell in more than one currency, keeping exchange rates accurate used to be a manual chore — someone had to remember to update the conversion for each currency, and a rate that quietly went stale skewed your margins, costs, and reports. Automatic Daily Exchange Rates takes that job off your plate: SKU.io now pulls fresh rates every day and keeps every currency current, converted to your base currency automatically — whatever that base currency is.

If you sell on eBay, you know the pain of month-end reconciliation. An eBay Managed Payments payout is a single net deposit that quietly bundles your gross sales, refunds, final value fees, ad fees, shipping-label costs, and adjustments — so the number that lands in your bank is none of your revenue figures. Matching it back to your books by hand takes hours, and coding the whole deposit to one income account quietly misstates your revenue, fees, and tax.

eBay Payout Accounting fixes that. SKU now pulls your eBay Managed Payments payouts, breaks each one into its real components, and posts a single deposit-matched summary to your accounting — one entry that reconciles to your bank deposit to the cent.

You could always see a customer's orders — but never, in one place, how much they owed you, how overdue it was, or how to go about collecting it. Chasing payment meant exporting to a spreadsheet, hand-building a statement, and sending it from your inbox, all outside SKU.io. The customer page is now an accounts-receivable command center — it opens on money owed, breaks the balance down by how overdue it is, produces a real statement of account, and lets you email that statement or a payment request without leaving the page.

When a customer checks out with an offline payment method — a bank transfer, a purchase order, a "pay on delivery" — the order lands in SKU.io unpaid, yet until now it behaved exactly like an order you'd already been paid for: it allocated your stock immediately and could sail straight through to fulfillment. So a wire that might never arrive could quietly tie up inventory for weeks, and there was no way to say "hold this until the money's in." The new Unpaid Orders settings let you decide, per sales channel, exactly how an unpaid order is handled — bring it in as a held reserve with an automatic expiry, park it as a draft for review, or treat it as open and let it ship — with per-payment-method overrides and control over when it reaches your accounting software.

You went to the trouble of entering your marketing spend, 3PL fees, software subscriptions and Amazon storage costs, and allocating them to the right products and brands — but your Profitability Report acted like none of it existed. It stopped at gross profit, so a brand that looked healthy on paper could be underwater once its share of overhead landed. The Profitability Report now includes the cost entries you allocate — every marketing campaign, fee and overhead cost folds into the report as a distinct, auditable cost line, and the bottom line becomes a full margin ladder: Revenue → Gross Profit → Contribution Margin → Operating Profit.

If you sell on more than one channel, your Xero or QuickBooks profit and loss report probably can't tell you which channel actually makes money — Amazon revenue, Shopify revenue and your wholesale orders all land in the same sales and cost-of-goods accounts. Until now the only way to split them out was to create a separate account for every channel, which bloats your chart of accounts and makes month-end a chore. SKU.io now supports Tracking Categories — map each of your sales channels to a Xero tracking category option (or a QuickBooks class), and every invoice, credit and cost-of-goods journal we post carries that tag. Run your provider's normal P&L-by-tracking-category report and your numbers are already split by channel — no extra accounts required.

The number Shopify deposits into your bank account is never your sales number. Every payout bundles sales, refunds, processing fees, and adjustments into a single net amount — so at month end someone has to reconstruct each deposit from dozens of individual invoices, or worse, book the whole thing to one income account and quietly misstate revenue, tax, and fees. SKU.io now syncs your Shopify Payments payouts and can post one summarized accounting entry per payout — sales, refunds, fees, and adjustments each routed to the right ledger account, with the net matching your bank deposit to the cent. When the deposit appears in your bank feed, it reconciles in one click.

You close the books for a month, reconcile everything to QuickBooks or Xero, and move on — and then a customer return, a late supplier bill, or a marketplace settlement shows up dated back in that closed period. Do you let it silently change a month you've already reported? Block it and lose the transaction entirely? Neither is a good answer. SKU.io now has first-class accounting lock dates — set the date your books are closed through, and any activity that arrives afterward dated on or before it is automatically posted to the first open day instead, with its original date preserved and clearly flagged. Your closed periods stay closed, and nothing falls through the cracks.

Sell something on Monday, ship it on Friday, and your books tell a small lie all week: the revenue is already sitting in your P&L, but the cost of goods doesn't arrive until the shipment goes out. Inside one month it makes your daily margins jumpy; across a month-end it's worse — one period gets revenue with no cost, the next gets cost with no revenue. And if you take pre-orders or run backorders, "revenue you haven't earned yet" can sit in your income statement for weeks. Fulfillment-based revenue recognition is a new accounting policy that fixes this the way accountants say it should be fixed: invoiced sales park in a Deferred Revenue liability, and revenue is only recognized when the goods actually ship — released on the very same entry, and the very same date, as their cost.

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.