ARR vs CARR vs Revenue: Backlog and Bookings for Manufacturers
ARR vs CARR vs revenue, explained for manufacturers: how bookings, backlog and contracted revenue differ from recognized revenue, and how to use each one.
Nauman Poonja, CPA · Updated · 7 min read · Editorial standards 
ARR, CARR and revenue are software metrics. They answer a simple question: how much revenue is locked in, how much is signed but not started, and how much did we actually earn?
Manufacturers ask the same question every week. They just use different words: bookings, backlog and recognized revenue. If you sell parts, equipment or contract manufacturing, those are the numbers that tell you what's coming and how solid it is.
This post explains ARR and CARR briefly, then shows how the same thinking applies to a $3M to $30M manufacturer: what counts as contracted revenue, what doesn't, and how to use backlog without fooling yourself. All examples are illustrative.
What Are ARR and CARR?
ARR stands for annual recurring revenue. It's the yearly value of active subscriptions. If a software company has 200 customers each paying $500 a month, ARR is $1.2M (200 times $500 times 12). It leaves out one-time fees like setup or training.
CARR is contracted ARR. It adds subscriptions that are signed but haven't started yet, and usually subtracts customers who have given notice they're leaving. So CARR is a forward-looking version of ARR.
Neither one is a GAAP number. Revenue on the income statement is what was actually earned in the period under the revenue standard, ASC 606. A company can sign a big contract in December and recognize almost none of it that year.
That's the useful lesson for a manufacturer. There's a difference between what's signed, what's started and what's earned. Each tells you something different.
The Manufacturer Version: Bookings, Backlog and Revenue
Here's how I'd translate the three software numbers for a plant.
| Software metric | Manufacturer equivalent | What it tells you |
|---|---|---|
| New ARR signed | Bookings (orders received) | How much new business came in this period |
| CARR | Backlog (open orders not yet shipped) | How much work is committed but not yet earned |
| ARR | Recurring service or supply contracts, if you have them | The part of revenue that repeats on its own |
| GAAP revenue | Recognized revenue | What you actually earned this period |
Bookings
Bookings are the value of firm orders received in a period. A purchase order for $180k of brackets received in March is a March booking, even if it ships in June.
Backlog
Backlog is the value of orders you've received but not yet shipped or earned. It's your manufacturing version of CARR. It tells you how much work is lined up.
Recognized revenue
Recognized revenue is what shows up on your P&L. For most manufacturers, that happens when control of the product transfers to the customer, often at shipment or delivery. For some custom work, it happens over time as you build. Our ASC 606 guide for manufacturers covers when each applies.
Contracted vs Uncontracted Revenue
This is where manufacturers most often overstate what they have. Not everything a customer tells you is a commitment.
| Type | Example | How firm it is |
|---|---|---|
| Firm purchase order | PO with part, quantity, price and date | Contracted. Count it in backlog. |
| Release against a blanket order | Customer releases 2,000 units for next month | Contracted for the released quantity |
| Blanket order balance | Annual blanket for 24,000 units, 6,000 released | Usually soft. Depends on the terms. |
| Customer forecast | EDI forecast or a planning spreadsheet | Not contracted. Useful for planning only. |
| Quote outstanding | Quote sent, no PO | Pipeline, not backlog |
I'd report backlog in two lines: firm and soft. Firm is POs and releases. Soft is blanket balances and forecasts. If you mix them, the backlog number will look better than it is, and your cash plan will be built on hope.
Read the blanket order terms. Some customers can cut or cancel unreleased quantity with little notice. Others commit to buy finished goods and raw material you've bought for them. That difference matters a lot if the program ends.
A Worked Example: Tracking Backlog for a Quarter
Here's an illustrative job shop for one quarter.
| Line | Amount |
|---|---|
| Opening firm backlog | $3.2M |
| Plus bookings this quarter | $2.9M |
| Less revenue recognized (shipped) | ($2.6M) |
| Less cancellations and changes | ($0.1M) |
| Ending firm backlog | $3.4M |
The math: $3.2M plus $2.9M minus $2.6M minus $0.1M is $3.4M. If that doesn't tie, something is off in how orders or shipments are recorded.
Two ratios come out of this.
Book-to-bill ratio is bookings divided by revenue. Here it's $2.9M divided by $2.6M, about 1.12. Above 1.0 means orders are coming in faster than you're shipping, so backlog is growing. Below 1.0 for several quarters means backlog is shrinking.
Backlog in months is backlog divided by average monthly revenue. Monthly revenue was $2.6M divided by 3, about $867k. So $3.4M of backlog is about 3.9 months of work.
Neither ratio is good or bad by itself. A shop with 3.9 months of backlog and full capacity may need to push lead times or add a shift. One with three weeks of backlog and idle machines needs sales.
Why Backlog Isn't Revenue and Isn't Profit
Backlog is a promise of future revenue. It isn't revenue until you deliver. And it isn't profit until you deliver at the cost you quoted.
Three things can go wrong between booking and shipping.
- Margin erosion. If you quoted in spring and material went up by fall, the backlog is worth less than it looks. I'd keep an estimated margin on backlog, not just a dollar value.
- Capacity. If you can't ship it on time, it slides, and so does your cash. Compare backlog hours to available hours, not just dollars. Your capacity utilization tells you if the work can actually get out the door.
- Cancellations. Customers change programs. Know your cancellation terms and what you can recover for material already bought.
So I'd look at backlog three ways: dollars, estimated gross margin and production hours. The dollar number alone is the least useful of the three.
Where ARR Does Apply to Manufacturers
Some manufacturers do have recurring revenue. Common examples are maintenance and service contracts on equipment you sold, software or monitoring subscriptions that come with a machine, consumables on a replenishment agreement, and extended warranties sold separately.
For those lines, ARR is a fine metric. Track it separately from product sales. It behaves differently, it's often higher margin, and buyers tend to value steady contracted revenue more than one-time sales.
Just don't call your whole business recurring because customers reorder. Repeat orders are good. They aren't contracts. If a customer can stop ordering next month without penalty, I wouldn't count it as ARR. Our post on customer retention for manufacturers shows a better way to measure how much of that repeat business sticks.
Reading a Software Vendor's ARR When You Buy
You'll also hear ARR when you buy software. ERP, MES and quality systems are usually sold as subscriptions. The vendor's sales team cares about their ARR, which affects how they price your deal.
A few practical points from the buyer's side:
- Multi-year commitments help the vendor's contracted revenue, so that's where you usually have room to ask for a discount or a price cap on renewal.
- Read the renewal clause. Many subscriptions renew automatically with an increase. Put the renewal date in your calendar 90 days ahead.
- Count the total cost over the term: subscription, implementation, add-on modules and internal time. The first-year price is rarely the full picture.
Our post on ERP selection for manufacturers goes deeper on the buying decision.
How to Use Bookings and Backlog in Planning
Backlog is one of the best inputs you have for a forecast. Firm backlog covers the next few weeks or months with real orders, so you're not guessing.
Here's how I'd use it:
- Schedule firm backlog by expected ship week.
- Apply your normal payment terms to turn ship dates into collection dates. That feeds your 13-week cash flow forecast.
- Layer soft backlog and pipeline on top, with a probability you can defend.
- Compare backlog hours to capacity by department.
- Review book-to-bill monthly. Two or three months below 1.0 is an early warning on revenue.
I think every manufacturer over a few million in revenue should have a one-page monthly report with bookings, backlog (firm and soft), book-to-bill and backlog months. It takes an hour if the order data is clean.
Common Mistakes with Backlog and Bookings
- Counting forecasts as backlog. Keep firm and soft separate.
- Not removing cancelled or changed orders. Backlog should roll forward and tie every month.
- Booking revenue when the order comes in. Revenue is recognized when you deliver, not when you're promised.
- Ignoring margin in backlog. Old quotes at old costs can turn a full backlog into a thin year.
- Treating repeat customers as recurring revenue. Without a contract, it's a habit, not a commitment.
How Accounovation Helps
We work as the finance team for established manufacturers between about $3M and $30M in revenue. We set up a monthly bookings and backlog report that ties to your ERP, split firm from soft, and connect it to your budgeting and forecasting.
If you also sell service contracts or subscriptions, we separate that revenue in the books and recognize it correctly. That's part of our manufacturing accounting and fractional CFO work. Happy to jump on a call if helpful.
Frequently Asked Questions
What is the difference between ARR and CARR?
ARR is the annual value of active recurring contracts. CARR adds contracts that are signed but haven't started, and usually removes customers who have given notice.
What is the manufacturing equivalent of CARR?
Backlog. It's the value of firm orders received but not yet shipped or earned, so it shows committed future revenue.
Is backlog the same as revenue?
No. Backlog is future revenue you've been promised. Revenue is recognized only when you deliver, usually when control of the product passes to the customer.
What is a good book-to-bill ratio?
Above 1.0 means backlog is growing and below 1.0 means it's shrinking. One quarter tells you little. The trend over several quarters, compared to your capacity, is what matters.
Should blanket orders be counted in backlog?
Count released quantities as firm. I'd show the unreleased balance separately as soft backlog unless the terms commit the customer to buy it.
More on: KPIs & Financial Reporting · Budgeting & Forecasting
