sbskubase

vs. your forecasting spreadsheet

Your reorder math is costing you money.

If your forecasting lives in a Google Sheet — ShipStation export pasted in, six-month trailing average computed, reorder when cover drops below six months — you're carrying more inventory than you need to and you're still missing seasonality. skubase fixes both, in under ten minutes.

14-day trial. No card. Prices locked at renewal.

14-day free trial · No credit card · Prices locked at renewal

Why the spreadsheet is wrong

Five things your sheet can't do — and skubase does by default.

A 6-month rule of thumb is a tax on your working capital.

Holding 6 months of cover for an A-item with steady demand is statistically wasteful — that's a 95th-percentile-plus stockout rule applied to SKUs that only need 30–60 days. The cash gap is real, and it compounds across every reorder cycle.

Trailing averages miss seasonality and trend.

A 6-month moving average is half-blind on every Q4 ramp. skubase fits a Holt double-exponential model with a weekly seasonality factor, so a back-to-school SKU isn't reordered like a steady-state one.

All SKUs are not equal.

Your A-items deserve a 99% service level; your C-items don't. skubase segments by ABC × XYZ and sets safety stock per class — the math the spreadsheet can't do without becoming a part-time job.

Your suppliers are unmeasured.

If your spreadsheet doesn't track which vendors miss promised lead times, you're carrying their failures as your stockouts. skubase scores every vendor on on-time, fill rate, and lead-time stability.

Dead stock is a cash recovery problem your sheet ignores.

The Sheet shows you what you have. It does not propose a markdown plan, a bundle, a wholesale list, or a write-off. skubase does — with the dollar impact attached.

Side by side

The math, made visible.

MetricYour spreadsheetskubase
Forecasting modelTrailing 6-month moving averageHolt double-exponential + weekly seasonality + stockout probability
Safety stockSame buffer for every SKUService-level segmented by ABC × XYZ class
Reorder triggerCover < 6 monthsDays-until-stockout < lead time + safety, ranked by $ impact
Supplier accuracyNot trackedOn-time %, fill rate, lead-time stability, tiered
Bundle/kit logicManual decompositionAuto-decomposes at reorder time
Dead stock actionNoneMarkdown / bundle / wholesale / write-off plans
Time to update30–60 minutes per weekZero — recomputes when shipments land
AuditabilityWhoever last touched itEvery recommended quantity explains itself

How it works

Three steps. No consultant.

1

Drop in your ShipStation export

We accept the standard Orders or Shipments CSV — SKU, quantity, ship date are all we need. ShipStation aggregates Shopify, Amazon, eBay, Walmart, and most other channels, so the import covers everywhere you sell.

2

See your real velocity

Per-SKU 30 / 90 / 180-day shipped units. The number you've been eyeballing in the spreadsheet, computed correctly.

3

Get ranked actions

Skubase ranks every SKU into urgent reorders, overstock to draw down, and dead stock to liquidate. Work the queue; close the spreadsheet.

Stop reordering by averages. Start reordering by math.

The spreadsheet was a heroic fix. skubase is the permanent one.

14-day trial. No card. Prices locked at renewal.