Plan at SKU, channel and month. Niblin turns your history into a driver-based starting point, sends each department its guidance, and walks every plan through approval to one signed-off budget.
See how Niblin models it
Driver-based
Each channel starts from its own drivers: orders, units, price, discounts, returns, fees and ad spend, all at SKU, channel and month. Planners edit the drivers, and the P&L follows.

Departments
Finance sets top-down guidance such as a revenue growth target and an opex cap. Each department head plans their own lines against it and explains any gap with a note.

Approvals
Every department plan moves through its own approval chain, from owner to finance to CFO, with send-back notes and delegation. The budget calendar sets the due dates and stops a step that is not ready.

Versions
Once signed off, the original budget is locked as the comparator for the year. Approved requests for extra budget, reallocations, new hires and capex land as tracked changes beside it, and a re-budget becomes a revision version.

Link Shopify, Amazon, your ad platforms and QuickBooks, Xero or Zoho Books so history and actuals come in from the source.
Finance sets the budget targets and the guidance each department plans against.
Channels plan on drivers, departments plan their lines, and each plan moves through its approval chain.
The CFO signs off one budget, which becomes the baseline for variance all year.
Spreadsheets are flexible and every finance team knows them. The strain shows when one budget has to hold SKU, channel and department detail through several rounds of review and approval.
| Spreadsheet model | Niblin | |
|---|---|---|
| Starting point | Spreadsheet modelLast year's file, copied and adjusted | NiblinDriver-based baseline from your history |
| Channel detail | Spreadsheet modelTabs per channel, linked by hand | NiblinDTC, Amazon and wholesale on their own cost structures |
| Department input | Spreadsheet modelTemplates emailed out and merged back | NiblinDepartment plans against guidance, with notes on overages |
| Approvals | Spreadsheet modelEmail threads and version names | NiblinRole-based approval chains on a budget calendar |
| Changes after sign-off | Spreadsheet modelOverwrite the file or save a copy | NiblinRevision versions beside the original budget |
| Closed months | Spreadsheet modelPasted actuals that can drift | NiblinActuals, read-only once a month closes |
Revenue and channel costs are budgeted at SKU, channel and month, built from drivers such as orders, price, discounts, returns, fees and ad spend. Department costs are planned by department and month. You can roll up to category, channel, entity and company without keeping a second model.
Wholesale, retail and distributor accounts are planned as channels in their own right, with their own fee waterfall, deductions, payment terms and seasonality. They sit beside DTC and Amazon in one budget instead of a single wholesale line in a spreadsheet.
Yes. Department heads can download a template, plan in Excel and upload it back. Niblin shows a preview of what will change and lists anything it skipped, such as a closed month or a locked plan, before the upload applies.
The approved budget stays fixed as the comparator. Approved requests for extra budget, reallocations, new hires and capex are tracked as changes beside it, giving you an original and a revised budget. A full re-budget is saved as a revision version.
The FP&A analyst or finance lead runs the cycle, department heads plan their own lines, and the CFO or founder signs off. Your analyst stops being the data plumber and spends the budget season on the assumptions instead of stitching exports together.
Learn the method
Related solutions
Driver-based budgets at SKU, channel and month, with department plans and approvals in one place.
See how Niblin models it