Ecommerce Budgeting Forecasting

Name: Ecommerce Budgeting Forecasting
Author: finsilabs

finsilabs/awesome-ecommerce-skills

69 installs
41 repo stars
Updated March 13, 2026
finsilabs/awesome-ecommerce-skills

Build rolling operating budgets for marketing and inventory spend with variance analysis, scenario modeling, and utilization alerts.

About

Guides connecting platform data to an accounting system and building a 12-month rolling budget with budget-vs-actuals variance reporting. A developer uses it to build the operating plan, allocate marketing budget, or replace spreadsheet budgeting.

Rolling forward-view budget with monthly variance analysis
Focus on marketing spend and inventory open-to-buy budget categories

Ecommerce Budgeting Forecasting by the numbers

69 all-time installs (skills.sh)
Ranked #556 of 1,106 Finance & Trading skills by installs in the Skillselion catalog
Data as of Aug 3, 2026 (Skillselion catalog sync)

npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill ecommerce-budgeting-forecasting

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/finsilabs/awesome-ecommerce-skills/ecommerce-budgeting-forecasting.svg)](https://skillselion.com/skills/finsilabs/awesome-ecommerce-skills/ecommerce-budgeting-forecasting)

Installs	69
repo stars	★ 41
Last updated	March 13, 2026
Repository	finsilabs/awesome-ecommerce-skills ↗

What it does

Build rolling operating budgets for marketing and inventory spend with variance analysis, scenario modeling, and utilization alerts.

Files

SKILL.mdMarkdownGitHub ↗

Ecommerce Budgeting & Forecasting

Overview

A rolling operating budget is the financial backbone of any well-run ecommerce business. Unlike a static annual budget, a rolling budget is continuously updated — typically a 12-month forward view that advances one month with each passing period. Combined with variance analysis comparing actuals to plan, it gives operators the visibility to make confident resource allocation decisions.

For ecommerce, the most operationally sensitive budget categories are marketing spend (which drives immediate revenue) and inventory purchases (which requires significant lead time). This skill guides you through building and maintaining these budgets using your platform's data and a connected accounting system.

When to Use This Skill

When building the annual operating plan for an ecommerce business
When allocating a monthly marketing budget across channels with accountability
When managing an inventory open-to-buy budget and tracking against it
When replacing a spreadsheet-based budget process with an automated system
When producing variance reports (budget vs. actuals) by the 3rd business day of each month
When presenting a rolling forecast to your board or investors

Core Instructions

Step 1: Connect your platform data to your accounting system

Budgeting starts with accurate actuals. Connect your ecommerce platform to an accounting system to get the foundational data:

---

Shopify

1. Connect to QuickBooks Online: Go to the Shopify App Store and install QuickBooks Online by OneSaas or Bench — syncs Shopify orders, payouts, refunds, and fees into QuickBooks chart of accounts automatically 2. Connect to Xero: Install Xero Bridge by Amaka from the Shopify App Store — maps Shopify sales, refunds, shipping, and taxes to Xero accounts 3. Built-in Shopify Finances: Even without a separate accounting system, go to Analytics → Finances summary for monthly revenue, COGS (if costs entered per product), and gross profit — exportable to CSV for manual budget tracking

For dedicated ecommerce financial tracking:

Finaloop (Shopify App Store): Automated bookkeeping app designed for Shopify merchants; generates P&L, balance sheet, and cash flow statements automatically
A2X (Shopify App Store): Reconciles Shopify payouts to your accounting system with accurate period-matched journal entries

---

WooCommerce

1. Connect to QuickBooks: Use the WooCommerce Payments + QuickBooks integration or the Zapier WooCommerce → QuickBooks connection 2. Connect to Xero: Use the WooCommerce Xero extension ($79/yr) from WooCommerce.com — syncs orders, refunds, and customer invoices 3. Export for manual budgeting: Go to WooCommerce → Analytics → Revenue and export monthly revenue data to CSV; use this as your actuals baseline for budget vs. actuals comparison

---

BigCommerce

1. Connect to QuickBooks: BigCommerce App Marketplace → QuickBooks Online by Webgility — automates order sync and accounting entry posting 2. Connect to Xero: BigCommerce App Marketplace → Xero by Amaka or Synder 3. Use BigCommerce Analytics: Go to Analytics → Store Overview for monthly revenue actuals; export to CSV for budget tracking

---

Step 2: Build the revenue budget

The revenue budget is the foundation — all other budget lines are derived from or constrained by revenue projections.

Method: Growth from prior year with seasonality adjustment

1. Pull last 12 months of monthly revenue from your platform (by channel if multi-channel) 2. Calculate seasonal indices: Divide each month's revenue by the annual average monthly revenue

Example: If average monthly revenue is $100K and December is $200K, December's seasonal index is 2.0

3. Apply growth assumptions by channel:

Your website: 20% YoY growth (based on marketing investment plan)
Amazon: 10% YoY growth
Wholesale: 5% YoY growth

4. Multiply annual budget by seasonal index for each month

Example spreadsheet structure:

Channel     | Annual Target | Jan Index | Jan Budget | Feb Index | Feb Budget | ...
Website     | $1,200,000    | 0.07      | $84,000    | 0.06      | $72,000    | ...
Amazon      | $600,000      | 0.06      | $36,000    | 0.05      | $30,000    | ...
Wholesale   | $200,000      | 0.10      | $20,000    | 0.08      | $16,000    | ...

Tools for revenue forecasting:

Google Sheets / Excel: Build manually with SEASONALITY formulas or exponential smoothing
Shopify Analytics + Google Looker Studio: Connect Shopify data to Looker Studio for visual trend analysis to inform growth assumptions
Float (floatapp.com) or Pulse (pulseapp.com): Connect to accounting system; build revenue forecast by category

Step 3: Build the marketing budget

Marketing budgets work best as a combination of variable spend (% of revenue) and fixed spend (brand/content).

Variable marketing spend (performance channels): Set as a % of channel revenue. Typical ecommerce targets:

Google Shopping/Search: 6–10% of website revenue
Meta (Facebook/Instagram): 8–15% of website revenue
TikTok Ads: 5–12% of website revenue
Amazon Sponsored Products: 8–12% of Amazon revenue (TACOS)
Affiliate: 4–6% of attributed website revenue

Fixed marketing spend:

Email/SMS platform (Klaviyo, Postscript): Fixed monthly subscription cost
Influencer/creator partnerships: Fixed monthly budget with seasonal multipliers (November: 2x, December: 1.5x, January: 0.5x)
Content creation/agency retainer: Fixed monthly

Budget rule: Tie performance marketing budgets to revenue milestones. If revenue is tracking 20% above plan, the marketing team can spend more; if below plan, cut variable spend first before touching fixed costs.

Step 4: Build the inventory open-to-buy budget

Open-to-buy (OTB) is the dollar amount of new inventory you are authorized to purchase in each period.

Formula: OTB = Planned Sales (at cost) + Planned End-of-Month Inventory - Beginning-of-Month Inventory

Inputs needed:

Sales forecast (in units or at cost) by product category
Current inventory on hand (from your platform's inventory report)
Target weeks of cover (typically 8–12 weeks for standard products)
Supplier lead time (typically 6–12 weeks for imports)

Tools by platform:

Shopify: Use Inventory Planner (Shopify App Store) — automatically calculates OTB by product based on your sales forecast and current stock levels
WooCommerce: Use ATUM Inventory Management (free plugin) — calculates OTB and reorder points; integrates with WooCommerce inventory
BigCommerce: Use SkuVault or Brightpearl (App Marketplace) for OTB planning and purchase order management

Step 5: Track budget vs. actuals monthly

Set up a monthly variance report that compares actuals (from your accounting system) to budget. This should be available by the 3rd business day of each month.

Structure:

Account         | Budget    | Actual    | Variance ($) | Variance (%) | Status
Website Revenue | $84,000   | $91,000   | +$7,000      | +8.3%        | Favorable
Amazon Revenue  | $36,000   | $31,000   | -$5,000      | -13.9%       | Unfavorable ⚠
Meta Ads Spend  | $12,600   | $14,200   | +$1,600      | +12.7%       | Watch ⚠
Payroll         | $45,000   | $45,000   | $0           | 0.0%         | On Budget

Materiality thresholds for variance flags:

Flag variances > 10% AND > $5,000 in absolute dollars for management attention
Flag variances > 20% for any line item regardless of dollar amount
Require written commentary from budget owners on any flagged variance within 3 business days

Tools for budget vs. actuals:

QuickBooks Online: Run Reports → Profit & Loss vs. Budget — automatically compares actuals to your entered budget
Xero: Run Reports → Budget Variance — same functionality
Google Looker Studio + Sheets: Build a dashboard that reads actuals from your accounting system and budget from a Google Sheet; refresh monthly

Step 6: Update the rolling forecast monthly

Each month, replace prior-month budget with actuals and reforecast the remaining months:

1. Lock the closed month: Replace budget figures with actuals for the closed month 2. Revise forward months if actuals deviate materially from plan:

If revenue is running 15% above plan, revise marketing and inventory budgets upward for the next 3 months
If revenue is running 10% below plan, revise marketing (variable spend) downward; leave fixed costs unchanged unless runway is at risk

3. Maintain both the original annual plan and the rolling forecast as separate versions — this lets you measure forecasting accuracy over time

Best Practices

Build the budget bottom-up — revenue should flow from channel-level projections, not a top-down "we want to grow 30%" target; bottom-up plans are more accurate and create ownership at the team level
Account for seasonality in monthly splits — splitting an annual revenue budget evenly by 12 ignores seasonal peaks; use historical seasonal indices to allocate monthly budgets
Review OTB weekly — inventory decisions have 6–12 week lead times; a weekly review prevents stockouts and overbuys
Use zero-based budgets for overhead — for overhead categories, require each line item to be justified from zero rather than rolling forward last year's spend; this surfaces zombie subscriptions
Automate variance report distribution — on the 3rd business day after month close, auto-generate and distribute the budget vs. actuals report to department heads; remove the manual overhead of report production
Build variance commentary into the process — require budget owners to submit written explanations for any material variance within 3 business days of month close

Common Pitfalls

Problem	Solution
Budget built in isolation by finance only	Include marketing, operations, and merchandising in the budget process; they know planned campaigns and upcoming product launches that affect revenue projections
Monthly splits done evenly (annual ÷ 12)	Use historical seasonal indices to allocate monthly budgets; a $12M annual budget is not $1M per month if you do $3M in November and December
All variances treated as equally important	Use both absolute dollar and percentage thresholds; focus management attention on material items only
Re-forecasting every week	Update monthly with a mid-month flash if there is a significant business event; weekly re-forecasting creates a moving target
Missing one-time outflows in the budget	Annual insurance renewals, software true-ups, trade show expenses, and tax payments are predictable; include them explicitly with their calendar dates
Marketing overspend discovered at month-end	Set weekly pacing alerts in your ad platforms (Meta, Google) to flag when spending is tracking above monthly budget pace

Related Skills

@cash-flow-forecasting
@financial-reporting-dashboard
@marketing-spend-analysis
@profit-margin-analysis

{
  "context": "Tests whether the agent correctly implements the marketing budget computation rules including the six line items (paid_search_google, paid_social_meta, amazon_sponsored, email_sms_platform, influencer_content, affiliate), correct rates for each, min/max floor/cap enforcement, seasonal multipliers, and the account code naming convention.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "paid_search rate",
      "max_score": 8,
      "description": "paid_search_google budget is computed as 8% of website channel revenue (rate=0.08)"
    },
    {
      "name": "paid_social rate",
      "max_score": 8,
      "description": "paid_social_meta budget is computed as 12% of website channel revenue (rate=0.12)"
    },
    {
      "name": "amazon_sponsored rate",
      "max_score": 8,
      "description": "amazon_sponsored budget is computed as 10% of amazon channel revenue (rate=0.10)"
    },
    {
      "name": "affiliate rate",
      "max_score": 8,
      "description": "affiliate budget is computed as 4% of website channel revenue (rate=0.04)"
    },
    {
      "name": "email_sms fixed amount",
      "max_score": 8,
      "description": "email_sms_platform budget is a fixed $2,500 per month"
    },
    {
      "name": "influencer base amount",
      "max_score": 8,
      "description": "influencer_content base fixed monthly amount is $15,000"
    },
    {
      "name": "influencer seasonal Nov",
      "max_score": 8,
      "description": "influencer_content for November applies a 2.0x seasonal multiplier (resulting in $30,000 for the sample Nov output)"
    },
    {
      "name": "paid_search min/max cap",
      "max_score": 8,
      "description": "paid_search_google enforces a minimum of $5,000 and maximum of $150,000 per month"
    },
    {
      "name": "paid_social min/max cap",
      "max_score": 8,
      "description": "paid_social_meta enforces a minimum of $3,000 and maximum of $200,000 per month"
    },
    {
      "name": "Account code format",
      "max_score": 12,
      "description": "Each line item's account_code follows the pattern MKT-{LINE_ITEM_UPPER_WITH_DASHES}, e.g. MKT-PAID-SEARCH-GOOGLE, MKT-EMAIL-SMS-PLATFORM"
    },
    {
      "name": "version field value",
      "max_score": 8,
      "description": "Budget rows include a version field set to 'annual_plan' (not a custom name like 'budget_2026')"
    },
    {
      "name": "All six line items present",
      "max_score": 8,
      "description": "sample_output.json contains exactly six line items: paid_search_google, paid_social_meta, amazon_sponsored, email_sms_platform, influencer_content, affiliate"
    }
  ]
}

{
  "context": "Tests whether the agent implements the growth-from-base revenue budget method using trailing 12-month actuals, applies seasonality weights (not flat 1/12 splits), uses the correct account code and version naming convention, correctly locks actuals in rolling forecast updates, and separates the annual plan version from the rolling forecast version.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Trailing 12-month baseline",
      "max_score": 8,
      "description": "Revenue budget baseline is computed from the prior year's actuals (base_year = budget_year - 1), not from a top-down target"
    },
    {
      "name": "Per-channel growth rates",
      "max_score": 8,
      "description": "Each channel's annual budget applies its own growth rate multiplier to the baseline (e.g. website gets 20%, amazon gets 10%)"
    },
    {
      "name": "Seasonality weighting applied",
      "max_score": 10,
      "description": "Monthly budget amounts differ across months based on seasonality weights — November and December amounts are noticeably higher than January and February"
    },
    {
      "name": "No flat monthly split",
      "max_score": 8,
      "description": "Monthly budget amounts are NOT uniform (i.e., not simply annual_total / 12 for every month)"
    },
    {
      "name": "REV-NET account code",
      "max_score": 10,
      "description": "Revenue budget rows use account_code 'REV-NET' (not 'REVENUE', 'REV', or other variant)"
    },
    {
      "name": "Annual plan version naming",
      "max_score": 10,
      "description": "Initial budget rows have version set to 'annual_plan_{budget_year}' (e.g. 'annual_plan_2026')"
    },
    {
      "name": "Rolling forecast version",
      "max_score": 10,
      "description": "The rolling forecast output uses a different version value from the annual plan (e.g. 'rolling_forecast'), not overwriting the original"
    },
    {
      "name": "Actuals locked for past periods",
      "max_score": 12,
      "description": "For periods up to and including current_period (2026-03), the forecast uses the actual_amount from actuals_to_date, not the original budget amount"
    },
    {
      "name": "Growth revision applied to future only",
      "max_score": 10,
      "description": "The -5% growth_rate_revision is applied only to periods after current_period (2026-04 onwards), not to locked past periods"
    },
    {
      "name": "period_id format",
      "max_score": 8,
      "description": "period_id values use the YYYY-MM format (e.g. '2026-01'), matching VARCHAR(7) convention"
    },
    {
      "name": "Both functions present",
      "max_score": 6,
      "description": "revenue_budget.py contains both build_revenue_budget() and update_rolling_forecast() functions"
    }
  ]
}

Annual Revenue Budget and Mid-Year Forecast Update

Problem/Feature Description

A DTC ecommerce brand is preparing for its 2026 planning cycle. The VP of Finance needs to produce the annual revenue budget from historical data, and also wants a system for updating the forecast quarterly as actuals come in — without losing the original plan as a reference. The brand sells across three channels: website (DTC), Amazon, and wholesale. The planning team has noted that revenue is highly seasonal (Q4 is by far the largest quarter), and past attempts at flat monthly splits caused confusing variances every November.

The VP also wants the mid-year forecast update process to be rigorous: once a month has closed, its actuals should be locked in and only forward periods should be revised. A growth rate revision (positive or negative) can be applied to all future unlocked periods. The board expects to always be able to compare the current forecast to the original annual plan.

Output Specification

Produce a Python script revenue_budget.py that implements two functions:

1. build_revenue_budget(historical_monthly_revenue, growth_assumptions, seasonality_weights, budget_year) — builds a monthly revenue budget DataFrame for budget_year from the provided historical data, applying per-channel growth assumptions and distributing the annual totals across months using the seasonality weights. Each output row must include period_id, channel, category, version, budget_amount, and account_code.

2. update_rolling_forecast(original_budget, actuals_to_date, current_period, growth_rate_revision) — updates the budget by locking actuals for periods up to and including current_period, and applying growth_rate_revision to all future unlocked periods. The function must preserve the original version and set a new version for the forecast output.

Also produce sample_output.json demonstrating both functions using the following inputs:

Historical revenue (2025 actuals):

website channel, apparel category: Jan–Dec 2025 with these monthly values (USD):

Jan: 120000, Feb: 110000, Mar: 130000, Apr: 125000, May: 140000, Jun: 135000, Jul: 145000, Aug: 150000, Sep: 160000, Oct: 180000, Nov: 300000, Dec: 280000

Growth assumptions: website: 20%, amazon: 10%

Seasonality weights: Jan: 0.07, Feb: 0.06, Mar: 0.07, Apr: 0.07, May: 0.08, Jun: 0.07, Jul: 0.08, Aug: 0.08, Sep: 0.08, Oct: 0.09, Nov: 0.15, Dec: 0.10

For the forecast update: Actuals are available through 2026-03. Apply a -5% revision to forward periods.

The sample_output.json should show:

Part 1: The full 12-month annual budget for the website/apparel channel
Part 2: The rolling forecast after applying the March 2026 actuals lock and -5% revision

Note: Clean up any large intermediate files. The final outputs should only be revenue_budget.py and sample_output.json.

{
  "context": "Tests whether the agent implements the correct variance classification thresholds (dual absolute+percentage for 'material', percentage-only for 'notable'), the correct budget utilization alert thresholds (pace_ratio > 1.20 triggers overspend, pace_ratio < 0.50 at mid-month triggers underspend), severity assignment logic, and alert sorting.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Material variance threshold",
      "max_score": 10,
      "description": "variance_flag = 'material' when BOTH percentage > 10% AND absolute value > $10,000"
    },
    {
      "name": "Notable variance threshold",
      "max_score": 10,
      "description": "variance_flag = 'notable' when percentage > 5% (and not already classified as material)"
    },
    {
      "name": "Within tolerance label",
      "max_score": 8,
      "description": "variance_flag = 'within_tolerance' for all other rows (not 'ok', 'normal', or other label)"
    },
    {
      "name": "Variance absolute calculation",
      "max_score": 8,
      "description": "variance_absolute is computed as actual_amount MINUS budget_amount (actuals minus budget, not budget minus actuals)"
    },
    {
      "name": "Overspend alert trigger",
      "max_score": 10,
      "description": "An overspend alert is generated when pace_ratio > 1.20 (where pace_ratio = actual_utilization_pct / expected_utilization_pct)"
    },
    {
      "name": "Underspend alert trigger",
      "max_score": 10,
      "description": "An underspend alert is generated when pace_ratio < 0.50 AND expected_utilization_pct > 0.50 (i.e., after mid-month only)"
    },
    {
      "name": "Warning vs critical severity",
      "max_score": 10,
      "description": "Overspend severity is 'warning' when pace_ratio is between 1.20 and 1.40, and 'critical' when pace_ratio >= 1.40"
    },
    {
      "name": "Info severity for underspend",
      "max_score": 8,
      "description": "Underspend alert severity is 'info' (not 'warning' or 'low')"
    },
    {
      "name": "Alert sort order",
      "max_score": 10,
      "description": "Returned alert list is sorted with 'critical' alerts first, before 'warning' and 'info'"
    },
    {
      "name": "Paid Social flagged in sample",
      "max_score": 8,
      "description": "sample_alerts.json contains an alert for Paid Social (pace_ratio = (85/50)/(20/30) = 2.55, which is critical)"
    },
    {
      "name": "Influencer flagged in sample",
      "max_score": 8,
      "description": "sample_alerts.json contains an underspend alert for Influencer (pace_ratio = (5/30)/(20/30) = 0.25, below 0.50 threshold at mid-month)"
    }
  ]
}

Budget vs. Actuals Monitoring System

Problem/Feature Description

The CFO of an ecommerce company is tired of getting surprised at the end of each month when actuals come in. By then it's too late to course-correct. She wants two things: (1) a SQL query that she can run against the financial database each month to flag which budget lines have meaningful gaps versus actuals, prioritizing the lines that deserve real management attention rather than burying them in a sea of noise; and (2) a Python function that fires alerts mid-month when any department is burning through budget too fast or suspiciously underspending.

The company has a budget_entries table and a financial_facts table in its data warehouse. The ops team runs the monthly close on approximately the 2nd of the following month. The CFO wants the report ready by the 3rd business day. She also wants the in-month alerting tool to tell her at-a-glance which items are most urgent.

Output Specification

Produce two artifacts:

1. variance_report.sql — A SQL query that compares budget to actuals and adds a variance_flag column classifying each line as one of three categories based on the size of the gap. Include variance_absolute (actuals minus budget) and variance_pct columns. Assume the tables available are budget_entries, financial_facts (with columns fiscal_period, account_code, amount, statement_type), and budget_accounts (with account_code, account_name, category). Use a parameterized version filter :active_budget_version.

2. budget_alerts.py — A Python function generate_budget_alerts(budget_vs_actuals, current_day_of_month, days_in_month) that takes a DataFrame of budget vs. actuals rows and returns a list of alert dictionaries. Each alert should have account, severity, and message fields. The returned list should be ordered by urgency.

Also produce sample_alerts.json showing output from the alert function for this scenario: it is day 20 of a 30-day month, and the following accounts have these actuals vs. budgets:

Paid Search: actual $95,000 vs budget $100,000
Paid Social: actual $85,000 vs budget $50,000
Email Platform: actual $2,500 vs budget $2,500
Influencer: actual $5,000 vs budget $30,000

{
  "name": "finsi/ecommerce-budgeting-forecasting",
  "version": "0.1.0",
  "summary": "Build rolling operating budgets for marketing spend, inventory purchases, and operations with variance analysis, scenario modeling, and budget utilization alerts",
  "skills": {
    "ecommerce-budgeting-forecasting": {
      "path": "SKILL.md"
    }
  }
}