Most guides on projected cost vs actual cost stop at the definition and never show you the math. That is a problem, because the definition is the easy part. The hard part — and the part that decides whether your store makes money — is measuring the gap precisely and knowing which line item caused it.
This guide fixes that. You get exact formulas, a worked per-order example, and the profit angle the generic articles always skip.
What is projected cost vs actual cost?
Projected cost (also called estimated or budgeted cost) is what you forecast you will spend on a product, order, campaign, or period — built from your history and your assumptions. According to Chron's small-business budgeting coverage, projected costs are based on prior sales numbers and anticipated increases in expenses. Actual cost is what you genuinely spent once the period closes. As UpCounsel explains, it differs from budgeted or forecasted costs in that it represents recorded figures, not estimates — it is the real, invoiced total once every fee, surcharge, and refund has settled.
The distinction sounds obvious, but the two numbers are produced by completely different processes. Your projection is a plan built weeks in advance. Your actual is a pile of real transactions — ad platform charges, supplier invoices, carrier surcharges, chargebacks — that only fully resolves after the fact.
That timing gap is exactly why "projected vs actual" is a discipline and not a one-time calculation. You project forward, you reconcile backward, and the difference tells you how good your assumptions were. As eBillity notes, estimated vs actual costs are used in accounting so companies can predict gains and losses and make better decisions.
A key nuance that competitors' articles miss: for print-on-demand sellers, actual cost is especially hard to pin down because supplier costs from Printify or Printful only enter your records through completed orders — catalog costs are not automatically synced into your reporting. That means your "actual" can still be an approximation unless you reconcile at the order level.
How to calculate the cost variance
The core metric is the cost variance — the difference between what you spent and what you planned to spend.
- Cost variance = Actual cost − Projected cost
- Variance % = (Actual cost − Projected cost) ÷ Projected cost × 100
A positive variance means you overspent (bad). A negative variance means you came in under budget (usually good, sometimes a sign your projection was too conservative).
Project managers formalize the same idea through earned value management, where the Cost Performance Index (CPI) = earned value ÷ actual cost, and a CPI above 1.0 means you are getting more value than you paid for. For an ecommerce store, the plain variance and variance % are usually enough — the discipline matters more than the acronym.
Businesses use actual costs to analyze cost variances, track profitability, and improve future budgeting, according to UpCounsel's breakdown of actual cost in accounting and business. Some companies adopt hybrid approaches, blending projected (standard) costing for planning with actual costing for reporting — a useful pattern for POD sellers who need to quote margins before orders land.
A worked example: projected vs actual for one store
Say you run a print-on-demand apparel store — call it Summit POD — doing a thousand orders a month. Here is what you projected at the start of the month versus what actually happened.
| Line item | Projected | Actual | Variance |
|---|---|---|---|
| COGS (blank + print) | $16,000 | $17,200 | +$1,200 |
| Shipping | $5,000 | $5,900 | +$900 |
| Payment processing | $1,600 | $1,600 | $0 |
| Pick/pack labor | $1,400 | $1,500 | +$100 |
| Ad spend | $10,000 | $11,000 | +$1,000 |
| Total variable cost | $34,000 | $37,200 | +$3,200 |
Run the variance math: actual $37,200 − projected $34,000 = +$3,200 overspent. As a percentage: $3,200 ÷ $34,000 = +9.4% over budget.
Now watch what that does to profit. You projected revenue of $40,000, so projected profit before fixed costs was $40,000 − $34,000 = $6,000. Actual revenue also missed — say it came in at $39,000 because a few campaigns underdelivered. Actual profit before fixed costs = $39,000 − $37,200 = $1,800.
Your cost variance alone (+$3,200) plus your revenue miss (−$1,000) turned a projected $6,000 into an actual $1,800. That leverage is the whole reason projected vs actual matters more in a thin-margin business than in a fat one.
Why projected and actual costs drift apart
The gap is rarely one big mistake. It is usually four or five small drifts that compound. As Marcus Lemonis's business resource explains, in some cases costs rise or certain items are more expensive than expected, while in other cases companies require fewer resources than originally projected. Understanding which direction you're drifting — and why — is the whole game.
Ad costs move with the auction. You budget a CPM and a ROAS; the auction hands you something else. Rising ad frequency is a classic culprit — the more times the same person sees your ad, the more you pay for diminishing returns. Read how increasing average order value with AI can offset rising ad costs without needing to cut spend.
Shipping surcharges hide in the fine print. Dimensional weight, residential fees, and peak-season surcharges routinely push actual shipping above the flat number you projected. This is one of the most common reasons actuals exceed projections for POD sellers.
Returns and refunds land late. You book revenue on day one, but a refund three weeks later quietly raises your effective cost per net order — and your projection almost never accounted for it. Our average checkout completion rate benchmark gives you a realistic baseline for what share of initiated checkouts should actually convert, so your revenue projection starts from a defensible number.
Abandoned carts break your revenue side. Projected revenue assumes a conversion rate that abandonment erodes. A small miss on that assumption cascades into a large miss on revenue, which makes even an on-budget cost base look unprofitable. Setting up a Klaviyo browse abandonment flow is one of the highest-leverage ways to recover projected revenue before the gap opens.
COGS creeps. Supplier price changes, a shift in product mix toward pricier items, or a print upcharge you forgot to model all widen the gap. For POD sellers using Printify or Printful, supplier costs only enter your warehouse data through completed orders — catalog costs are not synced in real time — so your COGS projection can quietly become stale between reconciliation cycles.
Poor attribution inflates effective ad cost. If your Google Ads campaigns are missing ValueTrack tokens, store-side attribution returns NULL for the Google channel, meaning your projected ROAS and actual ROAS diverge silently. You think the campaign is profitable; the actual cost per acquired order is higher than you see.
The per-order angle the generic guides skip
Here is the insight most SERP competitors miss: a monthly projected-vs-actual report tells you that you missed. It does not tell you which order lost money. And in ecommerce, profit lives at the order level.
Two orders with identical $40 revenue can have wildly different actual costs — one shipped a light tee across town, the other shipped a heavy hoodie across the country with a return. Averaged into a monthly total, they cancel out and you learn nothing. Measured per order, you can see exactly which products, SKUs, or ship-to zones are dragging your actuals above your projection.
This is why the net profit margin benchmark is a useful sanity check alongside your variance report: if your actuals are consistently pushing you below the benchmark range for POD stores, the problem is almost always a systematic gap between projected and actual cost at the SKU or shipping-zone level.
The per-order view also connects to CRO. CRO techniques for ecommerce raise revenue per visitor, which means fewer orders need to absorb your fixed and semi-fixed cost base — a structurally tighter projected-vs-actual spread.
How projected cost fits into standard vs actual costing
A subtopic the top-ranking results cover that this page was previously missing: the formal distinction between standard costing and actual costing.
Standard costing assigns a predetermined cost to each unit produced — essentially a formalized projected cost — and then compares it to actuals at period end. It is widely used in manufacturing because it simplifies inventory valuation and makes variance analysis repeatable. According to UpCounsel's accounting coverage, actual costing provides a precise view of production expenses, though it may be harder to predict than standard costing.
For POD sellers, you are implicitly doing standard costing every time you plug a fixed Printify base cost into your margin model. The problem is that your "standard" often goes stale: supplier price changes, shipping zone upgrades, and seasonal surcharges create a growing wedge between your standard (projected) cost and the actual cost landing in your invoices. Reconciling that wedge at least monthly — not quarterly — is what separates stores with tight margins from those constantly surprised by their bank balance.
Turning the variance into action
A variance number is only useful if it changes what you do next. Three moves:
Tighten the projection. Feed last period's actuals back into next period's forecast. If shipping ran over three months running, your projection was wrong, not your carrier. As eBillity recommends, using detailed reports to look at time and costs spent on similar past periods before building estimates is the fastest way to shrink systematic error.
Isolate the driver. Sort the variance by line item and by SKU. Fixing the one product that runs dramatically over on COGS beats shaving a small amount off everything. The supplier reconciliation thinking in this dropshipping data guide applies equally to tightening your COGS projections.
Reprice or re-margin. If actual costs are structurally higher than projected, the answer is often a price change, not a cost cut. The net profit margin benchmark tells you what target margin a healthy POD store should be defending so you know how much room you have before a reprice is unavoidable.
The bottleneck for most stores is not the math — it is that the actual costs are scattered across Shopify, Meta Ads, Google Ads, Printify, and Printful, and nobody stitches them into a true per-order number. That is precisely what PodVector is built for: it reads live data across all five platforms and computes your true per-order profit, so your "actual" is a real figure and not a guess.
Victor, PodVector's AI employee, reads that live data, identifies where projected and actual costs are diverging, and proposes the move — for example, repricing your worst-margin SKUs to a target margin, or raising your free-shipping threshold — as an approval card showing old and new values. You approve or reject; Victor executes the Shopify-side write. He is not a dashboard, and he does not touch your ad account. See how the full PodVector platform fits into a POD growth stack, or explore how Shopify AI capabilities extend beyond cost tracking. Start free and see your real per-order profit.
FAQs
What is the difference between projected cost and actual cost?
Projected cost is your forecast — what you expect to spend, built from history and assumptions before the period starts. Actual cost is the real, invoiced total once the period closes and every fee, surcharge, and refund has settled. As UpCounsel defines it, actual cost differs from budgeted or forecasted costs in that it represents recorded figures, not estimates. The difference between them is the cost variance.
How do you calculate cost variance?
Subtract projected cost from actual cost: variance = actual − projected. Express it as a percentage with (variance ÷ projected) × 100. A positive result means you overspent; a negative result means you came in under budget. In the worked example above, actual $37,200 minus projected $34,000 gives a +$3,200 (+9.4%) overspend.
What is standard costing vs actual costing?
Standard costing assigns a fixed predetermined cost per unit — effectively a formalized projected cost — and compares it to actuals at period end. Actual costing records what you truly spent. According to UpCounsel, actual costing provides a precise view of production expenses but may be harder to predict than standard costing. For POD sellers, your Printify or Printful base cost in your margin model is your standard cost; what hits your invoice after shipping zones, surcharges, and price changes is your actual cost.
Why is my actual cost always higher than my projected cost?
Usually because projections omit the costs that land late or vary with conditions — shipping surcharges, refunds, chargebacks, ad-auction inflation, and product-mix shifts. For POD stores specifically, supplier costs only enter your data through completed orders, so catalog-level cost changes can go undetected until reconciliation. Feeding real actuals back into your next forecast closes most of the gap over a few cycles.
Should I track projected vs actual per order or per month?
Both, but the per-order view is where the money is. A monthly total tells you that you missed; the per-order view tells you which SKUs, products, or shipping zones caused the miss. Averages hide the orders that lose money, so decisions based only on monthly totals tend to be too blunt to fix anything.
Does a favorable variance always mean I did well?
No. Coming in under budget can mean genuine efficiency — or it can mean you padded the projection, underspent on growth, or simply booked fewer orders than planned. As Marcus Lemonis's business resource notes, calculating both numbers before and after transactions is essential to understanding your business. Always read a cost variance alongside revenue and profit, never in isolation, or an under-budget month can quietly disguise a shrinking business.