Costing & Pricing
BOGO Is Not 50% Off: Calculate the Real Cost of Buy-One-Get-One Promotions
Compare BOGO, percentage discounts, gifts, bundles, and full-price offers using contribution, packaging, fulfillment, inventory, and repeat behavior.
Buy one, get one free sounds like a fifty-percent discount, but the business experiences more than a price reduction. It produces two units, picks two units, may need a larger package, pays fees on the transaction, and removes twice the inventory from future full-price availability. If the product is heavy or fragile, shipment economics can change again.
BOGO can be useful for trial, seasonal exit, pair usage, or increasing household adoption. It becomes dangerous when it is chosen because the headline feels stronger than the math.
Compare promotions at the order level. Include the physical work and ask what customer behavior the offer is supposed to change.
The quick answer
The outcome is a promotion chosen for a specific job, with complete order economics, capacity guardrails, clear terms, and a post-campaign review. Begin with Rebuild the last three promotions at order level using actual product, packaging, fees, shipping, labor, refunds, and subsequent customer orders. The first operating priorities are define the behavior goal and model the complete order; the working system then has to support check inventory and capacity, write qualification clearly, measure incrementality and repeat. Keep the scope narrow enough that the decision can be tested with real evidence instead of debated through general opinions.
What this looks like in a real maker business
A soap maker runs BOGO on a $12 bar that costs $3.20 to make. The offer appears profitable because $12 exceeds $6.40. But two wrappers, added pick time, marketplace fee, shipping subsidy, and lost full-price stock reduce contribution sharply. A curated three-bar discovery bundle at a smaller effective discount creates a higher order value, better trial, and cleaner inventory planning.
The practical playbook
Define the behavior goal
Trial, frequency, cart size, seasonal sell-through, referral, and new-customer acquisition are different jobs. If the promotion has no named behavior, success collapses into revenue.
Put it to work: Write the target customer, desired action, and post-promotion behavior.
Model the complete order
Include both product costs, packaging, variable labor, fees, shipping change, returns, and tax assumptions. Compare with the contribution from the likely full-price order.
Put it to work: Use the bundle margin calculator for each structure.
Check inventory and capacity
A successful BOGO can consume two production cycles for one order count. Confirm materials, shelf life, bottleneck hours, and the full-price opportunities displaced.
Put it to work: Model the maximum response the business can fulfill without shortening required process time.
Write qualification clearly
Define equal-or-lesser value, eligible variants, automatic or coded application, limit, dates, channels, shipping, returns, and what happens when stock ends.
Put it to work: Ask someone unfamiliar to explain the offer after reading it once.
Measure incrementality and repeat
Compare new customers, contribution, product trial, repeat purchase, and normal-period demand. A promotion may pull future orders forward rather than create additional demand.
Put it to work: Review the cohort after the normal replenishment window, not only at campaign close.
What can go wrong
Promotion, pricing, advertising, tax, returns, and platform requirements vary. Do not use inflated regular prices, fake deadlines, hidden exclusions, or unclear “free” claims. Preserve the offer customers actually saw.
A useful safeguard is to keep the original source record beside the interpretation. If an order, count, supplier date, batch result, customer message, or payment changes, update the decision and preserve why it changed. This prevents a confident dashboard from drifting away from the physical business.
The number that keeps this honest
Track contribution per promoted order and contribution per unit removed from inventory. Then measure qualified repeat behavior after the offer.
Use the number as a decision signal, not a performance weapon. Review the definition, compare similar periods, and pair it with quality and customer evidence. A metric becomes dangerous when people improve the displayed result by moving work, cost, or failure outside the measurement.
A simple 30-day implementation
Week 1: establish the baseline
Gather the records described above and keep uncertainty visible. Use actual orders, batches, counts, supplier confirmations, and payment records wherever possible. Mark estimates instead of polishing them into false facts. Choose one product, channel, or workflow narrow enough to finish in a week. A completed small baseline teaches more than a company-wide workbook nobody trusts.
Week 2: change one operating rule
Translate the first two playbook steps into a rule with an owner, trigger, input, decision, and expected output. Save the previous method. Explain the change to everyone whose work or promise is affected. If the rule touches safety, compliance, employment, tax, contracts, or regulated claims, pause for qualified guidance before using a general article as authority.
Week 3: run the rule in real work
Use the rule through a normal cycle. Record exceptions when they happen; do not repair the record after the fact. Keep customer commitments and required controls intact. One exception may be ordinary variation. Repeated exceptions usually mean the threshold, instruction, source data, authority, or capacity assumption needs revision.
Week 4: review the evidence
Compare the baseline with the metric in this guide. Ask what improved, what moved somewhere else, and what new burden appeared. Keep the rule, revise it, or remove it. Write the decision, owner, and next review date. That short history becomes operating memory and prevents the same debate from restarting whenever the founder is tired.
When connected software becomes useful
Spreadsheets and checklists are excellent for learning a method. They become fragile when the same product, formula, material, batch, order, customer, and cost must be updated in several places. Duplicate entry creates version disagreement; delayed entry makes reports look precise while the floor works from different facts.
Connected software should not automate confusion. It should preserve the current product version, show available and committed inventory, connect production with actual material and yield, carry costs into channel decisions, record who changed what, and make exceptions visible. Start with the decision that currently requires the most reconciliation. Add the next workflow only after the first source of truth is dependable.
Questions to ask before you scale the change
- Can a trained person explain the rule and the reason behind it?
- Is the required source data available at the moment the decision is made?
- Does the rule protect product quality, customer expectations, and applicable obligations?
- What evidence would prove the change is helping rather than moving cost elsewhere?
- Who owns an exception, and how quickly must they respond?
- Can the business export the records and reconstruct what happened later?
Growth becomes calmer when decisions leave a trail. The objective is not more administration. It is fewer avoidable surprises and a business that can repeat what works.
Related tools and reading
The bottom line
The outcome is a promotion chosen for a specific job, with complete order economics, capacity guardrails, clear terms, and a post-campaign review. Choose one product or workflow, establish the baseline, and make one observable change. Review the result after a real cycle. Clear evidence, a responsible owner, and a next review date will outperform a dramatic overhaul that the business cannot sustain.
Explore all free tools for makers, browse the Batch Scale resource center, or see how Batch Scale connects costing, inventory, production, orders, and customers.