Effective price after subsidy calculator
A 25% subsidy on a list price of 100 leaves the buyer paying 75. Enter the price and a percentage or a fixed amount per unit to see the out-of-pocket price, the discount and whether the item ends up fully covered. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Base price
- 100
- Subsidy type
- percent
- Subsidy value
- 25
- Subsidy amount
- 25
- Subsidy applied
- 25
- Effective price
- 75
- Discount received
- 25
Subsidies change what a buyer actually pays, not just the sticker number on the shelf. Whether the support is a flat voucher per unit, an employer contribution, an insurance co-pay reduction, or a government percentage rebate, the question people type into search is the same: what is the effective price after subsidy? This calculator takes a positive base price, a subsidy type (percent or per unit), and a non-negative subsidy value, then returns the absolute subsidy amount, the amount actually applied (never more than the base), the effective buyer price, the discount received, and the equivalent discount percent.
What effective price after subsidy means
In applied microeconomics and everyday consumer math, the effective price is the out-of-pocket amount the buyer remits after a third party covers part of the list price. A subsidy can be specified as a percentage of the base—for example twenty-five percent off a textbook under a student program—or as a fixed per-unit amount, such as a two-dollar food voucher per item or a fixed employer HSA contribution toward a benefit. Both forms reduce the cash the buyer hands over; they differ only in how the absolute subsidy is derived.
The effective price is then base minus the applied subsidy. The applied amount is the lesser of the computed subsidy and the base price itself: a voucher larger than the list price does not create a cash refund in this model; the buyer pays zero and the residual voucher is unused. That floor matches how most retail and program rules treat over-subsidy at the register and keeps automation clients from inventing negative prices.
Where the price after subsidy matters
Public-policy and development teams model consumer-facing prices after energy, transit, education, or health subsidies and need a deterministic oracle that matches the published program formula byte for byte. Retail and marketplace backends often store list price and a subsidy flag separately; a tiny parse call at checkout or in a quote engine avoids re-implementing percent-versus-per-unit branches in every client language. Benefits and insurance products quote member cost after plan-level co-pay subsidies; product managers and support tools need the same numbers the member will see on the bill.
Failed validation does not consume balance. Keep requests small, pin the rounded fields in tests, and you get reproducible buyer net prices for dashboards, chatbots, and edge workers without standing up a full pricing engine of your own.
What you can do with it
Program and policy cost sharing
Convert list price plus a percent or per-unit public subsidy into the out-of-pocket effective price households actually face.
Checkout and quote engines
Apply employer, voucher, or insurance per-unit subsidies at quote time and return net price plus discount received for the receipt line.
Teaching and auto-grading
Grade homework on consumer price after subsidy with a deterministic oracle that rejects invalid percent ranges and negative bases.
FAQ
Does the calculator handle tax or currency conversion?
No. It is unit-agnostic pure arithmetic on the three inputs. Apply tax or FX in your own pipeline before or after this call.
What does a 25% subsidy on a price of 100 leave me paying?
You pay 75. The subsidy covers 25 of the list price, which the calculator also shows as a discount of 25% so you can compare it with other support schemes.
What is the difference between a percent and a per-unit subsidy?
A percent subsidy takes a share of the list price, so it grows with the price. A per-unit subsidy is a fixed amount for each item, like a voucher, whatever the price is. Both lower what the buyer hands over.
What happens if the subsidy is larger than the price?
The subsidy is capped at the price, so the buyer pays zero and the item is marked as fully covered. The unused part of the voucher is not turned into a refund or a negative price.
How can I compare a percentage subsidy with a fixed voucher?
Look at the equivalent discount percent. The calculator restates any applied subsidy as a share of the original price, so a percentage scheme and a per-unit voucher can be compared on the same scale.
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/econ/effective-price-after-subsidy \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"base_price":100,"subsidy_type":"percent","subsidy_value":25}'const res = await fetch("https://api.kit.forhosting.com/econ/effective-price-after-subsidy", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"base_price": 100,
"subsidy_type": "percent",
"subsidy_value": 25
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/econ/effective-price-after-subsidy",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"base_price": 100,
"subsidy_type": "percent",
"subsidy_value": 25
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/econ/effective-price-after-subsidy", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"base_price":100,"subsidy_type":"percent","subsidy_value":25}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"base_price":100,"subsidy_type":"percent","subsidy_value":25}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/econ/effective-price-after-subsidy", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"base_price": 100,
"subsidy_type": "percent",
"subsidy_value": 25
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "econ.effective_price_after_subsidy",
"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
When the subsidy covers the full base, effective price is zero and fully_subsidized is true.
What effective price after subsidy means
For a percentage subsidy the absolute amount is base_price times subsidy_value over one hundred. For a per-unit subsidy the absolute amount is simply the subsidy_value in the same currency units as the base. Reporting both the raw subsidy_amount and the subsidy_applied makes the capping rule transparent when auditors compare program rules to receipt totals. The discount_percent field restates the applied subsidy as a share of the original base so analysts can compare percent and per-unit schemes on a common scale without rewriting formulas by hand.
Input contract, response shape, and validation
POST a JSON object with three required fields. base_price must be a finite positive number strictly greater than zero; zero or negative bases fail with invalid_input because a non-positive sticker price is not a meaningful subsidy base. subsidy_type must be percent or per_unit; common aliases such as percentage, pct, absolute, fixed, and amount are normalized to those two canonical values. subsidy_value must be a finite non-negative number. When subsidy_type is percent, subsidy_value must also lie in the closed interval from zero to one hundred; values above one hundred are rejected rather than clamped, so a data-entry error of one hundred twenty percent cannot silently invent free goods plus an extra twenty percent. Missing fields, empty strings, non-finite numbers, and unknown subsidy types all throw invalid_input and are not billed. On success the response echoes base_price, subsidy_type, and subsidy_value (rounded for stable goldens), then subsidy_amount, subsidy_applied, effective_price, discount_received (equal to subsidy_applied), discount_percent, fully_subsidized, and a short formula string. Example: base_price one hundred, subsidy_type percent, subsidy_value twenty-five yields subsidy_amount twenty-five, effective_price seventy-five, and discount_percent twenty-five. Example: base_price forty, subsidy_type per_unit, subsidy_value ten yields effective_price thirty and discount_percent twenty-five. Pair the numeric fields with your own currency formatting; this endpoint is unit-agnostic and does not convert currencies or attach tax.
Where an effective-price-after-subsidy API earns its keep
Classroom and MOOC problem sets on price controls and transfers use effective price after subsidy as a standard homework prompt; an API with clear invalid_input on bad percent ranges grades those items without silent empty successes.
Technical questions
How do I calculate effective price after a subsidy?
Send base_price (positive), subsidy_type (percent or per_unit), and subsidy_value. The API returns effective_price = base_price minus the applied subsidy, plus discount_received and discount_percent.
What is the difference between percent and per_unit?
Percent takes subsidy_value as 0–100 of the base; per_unit takes subsidy_value as an absolute amount in the same units as base_price. Both report an absolute subsidy_amount before capping.
What if the subsidy is larger than the base price?
For per_unit, the applied subsidy is capped at base_price so effective_price is zero and fully_subsidized is true. Percent values above 100 are rejected as invalid_input.
What does the effective price after subsidy calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.