23 posts tagged with "Reporting"

Seasonal buyers plan months ahead and manage month by month, and the budget usually lives in a spreadsheet nobody else can see. It goes stale the moment a purchase order lands. Open-to-buy planning brings that budget into SKU.io. Create a season, plan what each category or brand should sell, mark down and hold at month end, and SKU.io works out how much you still need to buy. Purchase orders count against the budget as they're placed. Once the season starts, plan sits beside actual so you can see a category drifting before it's over budget.

If you sell apparel, you don't buy a style: you buy a size run. Order every size evenly and you sell out of the middle sizes while the ends sit on the shelf. A style's stock is spread across dozens of variants, so spotting the gaps means scrolling a long list. Sizes and colours puts the size run front and centre. Derive a size curve from how a style really sold. See its stock as a grid of sizes and colours and reorder the gaps in one go. Compare sizes across every vendor in one report.

When you start on SKU.io you have a reason: fewer oversells, fewer hours lost to purchase orders and stock counts, a faster month-end close. Six months later it's hard to say how far you've come, because nobody wrote down where you started. Success plan fixes that. Pick up to three goals, record where you're starting from, and SKU.io measures the ones it can see in your own orders and stock every month. For the rest, it asks you two quick questions at day 30, 90 and 180 and at year-end.

Every support ticket tells you something: a screen that confuses people, a setting nobody understands, an integration that keeps tripping up. Spread across a year of conversations, though, the pattern is hard to see, and you usually have to ask us for a summary. Support Insights lets you build that summary yourself. Pick a date range and SKU.io produces a report that crosses three things: what your team asks us about, which parts of SKU.io you actually use, and how our servers performed over the same period. The result is a short, ranked list of findings that says where the pain is and whether it's on our side or yours.

The report builder covers most questions in a few clicks. But sometimes you need to rank products against each other, compare one period with another, or combine data in a way the builder can't express. Until now, those reports meant waiting on someone to build them for you. SQL reports let the people on your team who know SQL write the report themselves, as a query, right inside SKU.io. The query runs read-only against your own data, and the result is a normal saved report you can share, schedule and export.

You rolled out SKU.io to your team, but did it stick? Is the purchasing team actually receiving POs in SKU.io, or still working from a spreadsheet? Which features are you paying for and never touching, and which ones could save you hours if someone switched them on? Until now there was no single place to answer that. The new Feature Adoption report maps every SKU.io feature by area, shows which ones your team uses and who uses them, and points out what you haven't tried yet. When a feature will never fit your business, you can hide it so the report stops suggesting it.

If you pay sales reps on commission, you have probably been doing the math somewhere else. Rates live in a spreadsheet, someone exports orders at the end of the month, and the two get reconciled by hand — every month, for every rep. It works right up until a rate changes mid-month, or someone asks which territory is actually carrying the number.

Sales rep commissions brings all of it into SKU.io. Give each rep a commission rate, group reps into territories or teams, and run the numbers over any date range you like. The orders are already here, so the calculation is just there — nothing to export, nothing to reconcile.

Your home dashboard used to be one fixed layout — the same handful of cards for everyone, whether you live in sales, purchasing, or the warehouse. Now it's yours to shape. Customizable dashboards let you add any of 100+ widgets — KPIs, trend charts, gauges, leaderboards and live activity — then drag, resize and arrange them exactly how you want. Keep separate dashboards for different jobs (an Overview, a Sales view, an Operations view) and switch between them with one click. Everything is drawn from your live data, so the moment a widget lands on your board it's already showing real numbers.

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.

Which material actually makes you money? Which collection is quietly dragging your margin down? If you track those things as product attributes, the answer has always been in SKU — but the Profitability Report couldn't see it. It grouped by Brand, SKU, Supplier, Sales Channel, Product Type, and Sub Sales Channel, and that was it. Anything else meant exporting to a spreadsheet and pivoting by hand. Group by Attribute fixes that. The Profitability Report now offers a seventh grouping: pick any custom product attribute you've defined — Material, Collection, Season, Fit, anything — and the report builds one row per value, with the same revenue, cost, profit, and margin math as every other dimension.