Billable weight calculator
Know what weight a carrier will bill before you print the label: a 5 lb box measuring 20 × 15 × 10 inches with divisor 139 bills at about 21.58 lb, on its dimensional weight. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Actual weight
- 5
- Length
- 20
- Width
- 15
- Height
- 10
- Dim divisor
- 139
- Volume
- 3,000
- Dimensional weight
- 21.582733813
- Billable weight
- 21.582733813
- Charged by
- dimensional
Carriers bill parcels on billable weight—also called chargeable weight—not only on what the scale reads. When a box is large but light, dimensional (volumetric) weight can exceed the actual weight, and you pay on the larger figure. This billable weight calculator accepts actual scale weight, package length, width, and height, plus your carrier’s dimensional-weight divisor, then returns dimensional weight, the billable result, and whether rating should follow actual or dimensional rules. Optional round-up matches whole-unit ceiling policies common in rate cards. Units stay caller-consistent: use inches and pounds with divisors such as 139 or 166, or centimetres and kilograms with 5000, without silent conversion.
What billable weight means and how dimensional weight is computed
Billable weight—also called chargeable weight—is the weight figure a carrier uses when rating a shipment. It is not always the number on the warehouse scale. For many parcel and LTL programs the billable amount is the greater of two quantities: the actual weight of the packed goods and the dimensional weight derived from the outer carton size.
Dimensional weight exists because aircraft and truck capacity is limited by cube as much as by mass; a large, fluffy package can consume as much network space as a denser box of the same exterior dimensions. The standard formula is dimensional weight equals length times width times height divided by a published dim divisor.
That divisor is not universal: United States domestic parcel programs often use 139 when dimensions are in inches and weight is in pounds; some international lanes use 166 with the same inch-and-pound convention; metric programs frequently use 5000 when dimensions are in centimetres and weight is in kilograms. Your contract, rate card, or carrier portal is the source of truth for which divisor applies—never assume a single global constant. Once dimensional weight is known, billable weight is simply the maximum of actual weight and dimensional weight.
When the two values are equal, rating follows the actual scale weight. When dimensional weight is larger, the shipment is cube-constrained and charged on volume.
Where a billable weight calculator earns its keep
Ecommerce operations teams use a billable weight calculator before they print labels so oversized light cartons are flagged and packing is tightened before the carrier invoice arrives. Marketplaces and multi-carrier rate shops need a deterministic oracle that applies the same max-of-actual-and-dimensional rule across UPS, FedEx, USPS, DHL, and regional integrators once the correct divisor is supplied per service. Finance and logistics analysts reconcile carrier invoices against order history by replaying dimensions and weights through the same formula instead of reverse-engineering a spreadsheet.
Failed validation does not consume balance.
What you can do with it
Checkout and rate shopping
Estimate chargeable weight for multi-carrier quotes by applying each service’s dim divisor to the same L×W×H and actual weight.
Invoice reconciliation
Replay order dimensions through the billable weight formula to explain why a carrier billed dimensional weight instead of the warehouse scale reading.
FAQ
Do I need matching units for weight and dimensions?
Yes. Keep one system: inches with pounds and an inch-based divisor, or centimetres with kilograms and a metric divisor. The calculator never converts units silently.
How is dimensional weight calculated?
Multiply length, width and height, then divide by your carrier’s divisor. A 20 × 15 × 10 box has a volume of 3,000; divided by 139 that gives about 21.58, well above a scale weight of 5.
Which dimensional weight divisor should I use?
Use the one in your contract or rate card. Many domestic programs in the United States use 139 with inches and pounds, some international lanes use 166, and metric programs often use 5000 with centimetres and kilograms.
Can billable weight be rounded up to the next whole pound or kilogram?
Yes. Turn on the round-up option and the result rises to the next whole unit after actual and dimensional weight are compared, as many rate cards do. Leave it off to keep full precision.
Why does my package bill at more than its scale weight?
Because the box is large for what it weighs. Carriers charge the greater of actual and dimensional weight, so a light, bulky carton is billed on its size. When both are equal, the actual weight is used.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/ecom/billable-weight \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"actual_weight":5,"length":20,"width":15,"height":10,"dim_divisor":139}'const res = await fetch("https://api.kit.forhosting.com/ecom/billable-weight", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"actual_weight": 5,
"length": 20,
"width": 15,
"height": 10,
"dim_divisor": 139
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/ecom/billable-weight",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"actual_weight": 5,
"length": 20,
"width": 15,
"height": 10,
"dim_divisor": 139
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/ecom/billable-weight", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"actual_weight":5,"length":20,"width":15,"height":10,"dim_divisor":139}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"actual_weight":5,"length":20,"width":15,"height":10,"dim_divisor":139}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/ecom/billable-weight", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"actual_weight": 5,
"length": 20,
"width": 15,
"height": 10,
"dim_divisor": 139
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "ecom.billable_weight",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
What billable weight means and how dimensional weight is computed
Many carriers then round billable weight up to the next whole pound or kilogram before looking up the rate; this calculator exposes that step as an optional round_up flag so automation can match the rate engine you already use.
Input contract, response fields, and validation behaviour
A short formula string restates the rule for display next to the result. Example: actual weight five, dimensions twenty by fifteen by ten, divisor one hundred thirty-nine yields volume three thousand, dimensional weight about twenty-one point five eight, and billable weight on the dimensional side. POST a JSON body with five required positive finite numbers: actual_weight (scale weight of the finished package), length, width, and height of the outer dimensions in a single consistent length unit, and dim_divisor from your carrier’s dimensional-weight rule. Optionally send round_up as a boolean; when omitted it defaults to false and the billable figure keeps full precision after the max comparison. Each numeric field may arrive as a JSON number or as a numeric string; missing fields, empty strings, non-finite values, zeros, and negatives fail with invalid_input naming the field, and those failures are not billed. On success the body echoes the inputs, reports volume as length times width times height, dimensional_weight as volume divided by dim_divisor, and billable_weight as the maximum of actual_weight and dimensional_weight—with an optional ceiling when round_up is true. The charged_by field is either actual or dimensional so UIs can highlight which side won without re-comparing floats. Pair the response with your own unit labels; this endpoint does not convert inches to centimetres or pounds to kilograms—mixing systems with the wrong divisor is a data-quality problem outside the pure math. Keep requests small, pin rounded outputs in tests, and reuse the same module in browser and API so free previews match prepaid automation.
Where a billable weight calculator earns its keep
Warehouse management and packing-station software can call the API on every carton scan to show staff whether the scale or the tape measure is about to set the cost. Document your dim_divisor source in runbooks, store length and weight units next to each SKU or carton profile, and you get reproducible chargeable weight for checkout estimates, SLA audits, and edge workers without standing up a full rating engine of your own.
Integration use cases
Pre-label packing checks
Scan carton dimensions and scale weight at the pack bench; show billable weight and charged_by so staff can downsize fluffy boxes before labels are bought.
Technical questions
How is billable weight calculated?
Billable (chargeable) weight is max(actual_weight, dimensional_weight), where dimensional_weight = (length × width × height) / dim_divisor. Optional round_up ceilings the result to whole units.
What dim_divisor should I use?
Use the divisor from your carrier contract or rate card. Common values include 139 (US domestic in·lb), 166 (some international in·lb), and 5000 (cm·kg). This tool does not pick a carrier for you.
When is charged_by dimensional versus actual?
charged_by is dimensional when dimensional weight is strictly greater than actual weight; otherwise it is actual (including when the two values are equal).
What does the billable weight calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.