No long-term contracts. No surprises.
Create your SkuBrain Free account, without a credit card. Then simply pick the plan that suits you.
Frequently asked questions
You charge for SKUs. What is a SKU?
SKU (typically pronounced “skew”) is short for stock keeping unit and refers to a distinct item (product or service) that you sell.
For inventory management purposes, a SKU can also be a unique identifier code that gets associated with each product. This might be used to create barcodes or simply a concise way to refer to each product in accounts or order management systems. SkuBrain uses these kinds of SKUs (identifiers) for forecasting and inventory replenishment reports etc. as well, but for the purposes of licensing just think of a SKU as a unique product or service that you sell.
How do you count the number of SKUs?
To work out how many SKUs you manage, we simply count the number of unique SKU identifiers in your sales history. If you’re using a third party inventory management system that we integrate with (such as Brightpearl, Shopify or Vend), essentially you’ll have one SKU for each product that you have configured in your inventory management system. If you’re using CSV files to upload your sales data to SkuBrain, the SKU is one of the columns in the CSV files that you upload when importing sales history or building inventory replenishment reports.
What happens if I go over my SKU limit?
If you have more SKUs than your plan supports, you’ll still be able to login to SkuBrain and view and manage demand forecasts and stock plans. However, you won’t be able to create any new forecasts until you’ve upgraded to a plan with sufficient SKUs.
It is also possible to reset your data in SkuBrain. This would delete all of the sales history that you have stored in SkuBrain, which would bring you back down to zero SKUs (and thus within the limits of whatever plan you’re on). However this would also delete any demand forecasts or replenishment plans that you had stored in SkuBrain… so you’d typically only do it if there was some issue with the sales history data that you had stored in SkuBrain.