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.

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.

Advertising is usually an Amazon seller's biggest variable cost after the product itself — but until now it lived in a separate tab, invisible to your profitability inside SKU.io. A product could look healthy on margin while quietly losing money once ad spend was counted, and the only way to see the truth was exporting ad reports and inventory reports and joining them by hand in a spreadsheet. Amazon Ads cost attribution closes that gap: connect your Amazon Advertising account and SKU.io automatically pulls your Sponsored Products spend, attributes it to the exact SKU it was spent on, and turns it into real product-level costs — so your contribution margin and ACoS finally include the cost of the ads that drove the sales.

If you sell on Amazon FBA, storage fees quietly eat into your margins — and until now they were invisible at the product level. Amazon charges them per product, per month, but the only way to see what each product was really costing you was to download a TSV, aggregate hundreds of FNSKUs across fulfillment centers, map them to your products, and hand-enter the totals. Every month. So in practice, nobody did. Amazon storage fee cost allocation changes that: SKU.io now pulls Amazon's two storage fee reports automatically and turns them into per-product cost entries — no spreadsheets, no manual entry.

Your gross margin says a product is profitable. But after the ad spend, the affiliate payouts, the warehouse rent, and the software subscriptions — is it? Those indirect costs live in invoices and spreadsheets, never connected to the products that caused them. Cost Allocation closes that gap: record any indirect cost in SKU.io, spread it across the products, brands, suppliers, or sales channels it belongs to, and see true contribution margin — revenue minus COGS minus the overhead each product actually carries. It's a profitability layer, not a bookkeeping one: allocations never create accounting transactions, so there's no risk of double-counting against your real books.