← Back to blog

WooCommerce Payment Gateway Fees: How to Calculate Real Order Profit

A practical guide to calculating WooCommerce payment processing fees, net payout and real order profit—including fixed fees, effective rates, COGS, small-order economics and verification.

Online card payment illustrating WooCommerce payment gateway fee and profit calculations

Payment fees are easy to underestimate in WooCommerce because the number shown in the order total is not necessarily the amount that reaches the merchant account. A processor may deduct a percentage of the transaction, a fixed charge, and—depending on the account, customer and payment method—additional costs such as international-card or currency-conversion fees.

That distinction matters when you are pricing low-value products, deciding whether free shipping is sustainable, comparing gateways, or estimating the margin left after a promotion. The useful question is not simply “What percentage does my gateway charge?” It is: what does this order earn after the payment cost and the costs of fulfilling the sale?

The free WooCommerce Payment Fee & Profit Calculator on WPToolix models that decision locally in your browser. This guide explains the calculation behind it, where simplified calculators go wrong, and how to verify the result against real WooCommerce and processor data.

Start by separating revenue, payout and profit

These three numbers answer different questions.

  • Order amount is the amount you are modeling as charged to the customer.
  • Net payout is the modeled amount remaining after the payment-processing fee.
  • Profit goes further and subtracts cost of goods plus any additional costs you choose to include.

WooCommerce’s Cost of Goods documentation describes COGS as the direct costs associated with products sold and uses that information to calculate product and order profit margins. That is why a payment-fee calculation by itself is not a profit calculation.

The basic percentage-plus-fixed payment fee formula

For a processor that charges a percentage plus a fixed amount, a useful baseline is:

processing fee = order amount × percentage rate + fixed fee

If an order is 100.00, the rate is 2.9%, and the fixed charge is 0.30:

100 × 0.029 + 0.30 = 3.20

The modeled payout is therefore 96.80 before any other costs.

This structure is not unusual. Current Stripe US standard pricing, for example, lists a percentage plus a fixed charge for domestic online card transactions, while its pricing page separately lists potential additions for international cards and currency conversion. WooPayments likewise documents that its exact fees vary with factors including merchant country, customer country, currency and payment method. The important workflow lesson is to enter the rate that applies to your account rather than copying a rate from a generic example.

Why small orders have a higher effective fee rate

A fixed transaction charge has disproportionate impact as the order value falls. Suppose the modeled fee is 2.9% + 0.30.

  • On 100.00, the fee is 3.20, or 3.20% of the order.
  • On 20.00, the fee is 0.88, or 4.40%.
  • On 5.00, the fee is 0.45, or 9.00%.

The advertised percentage has not changed. The effective fee rate changed because the fixed component is spread across a smaller transaction.

This is one reason minimum-order rules, bundles and product pricing can matter for stores with inexpensive items. You do not need to change the store merely because the effective rate is high, but you should see the economics before making the decision.

Calculate order profit after the gateway fee

A practical planning model is:

profit = order amount − payment fee − COGS − other absorbed costs

Imagine the 100.00 order above has 40.00 of product cost and 5.00 of packaging or shipping cost paid by the merchant:

100 − 3.20 − 40 − 5 = 51.80 estimated profit

The corresponding margin on the modeled order amount is:

51.80 ÷ 100 × 100 = 51.8%

This is deliberately a decision model rather than an accounting statement. Taxes, shipping income, fulfillment costs, refunds and other components can be treated differently depending on your business and reporting method. WooCommerce’s Cost of Goods extension documentation, for example, provides settings that determine whether checkout fees, shipping and taxes are included or excluded from its profit reports.

Do not confuse markup with margin

This mistake can make a profitable-looking pricing spreadsheet misleading.

If a product costs 60 and sells for 100 before other costs, the gross difference is 40. The margin is 40% because the profit is divided by the selling price. The markup is about 66.7% because the same 40 is divided by the 60 cost.

When evaluating WooCommerce orders, state explicitly which metric you are using. The WPToolix calculator reports margin against the modeled customer charge.

How much should you charge to preserve a target profit?

If you are solving for a customer charge rather than starting with one, the percentage fee creates a small algebra problem: increasing the price also increases the percentage-based processor fee.

For the calculator’s simplified model:

required charge = (target profit + COGS + other costs + fixed fee) ÷ (1 − percentage rate)

That is more accurate than taking your desired pre-fee price and simply adding the headline percentage. WooCommerce’s documentation for its Payment Gateway Based Fees extension illustrates the same underlying distinction between adding a percentage to an amount and calculating a fee so that a desired amount remains after commission.

Customer payment fees are a separate decision

WooCommerce extensions can apply fixed or percentage fees based on the selected payment gateway, and current WooCommerce Marketplace documentation includes gateway-fee rules based on cart/order values and other conditions.

That technical capability does not mean every merchant should pass card costs directly to customers. Surcharge rules can depend on location, card network, processor agreement, tax treatment and other requirements. There is also a conversion question: an extra checkout charge may recover a fee while making the checkout less attractive.

Use a profit calculator first to understand the cost. Treat the decision to surcharge as a separate legal, contractual and customer-experience question.

A practical WooCommerce gateway comparison workflow

  1. Collect your real rates. Use the pricing or contract for each payment method and merchant region.
  2. Choose representative order values. Test a small order, your approximate average order value, and a high-value order.
  3. Include the fixed fee. It can materially change small-order economics.
  4. Add product cost. Use COGS that reflects the direct product cost you actually track.
  5. Add costs relevant to the decision. Packaging or merchant-paid fulfillment may matter even when they are reported differently in accounting.
  6. Run special cases separately. International cards, currency conversion or alternative payment methods may have different rates.
  7. Compare against actual settlements. A calculator is most useful when you periodically check whether its assumptions still match processor reports.

How to verify the calculation on a real store

Do not stop after the formula looks correct. Pick several completed orders and reconcile them.

1. Start with a simple domestic transaction

Choose an order without a refund, dispute, currency conversion or unusual payment method. Record the amount used by the processor to calculate its fee.

2. Compare the processor fee

Check the transaction or balance report from the payment provider. Confirm whether the percentage, fixed component and fee base match your assumptions.

3. Reconcile the payout

Subtract the documented transaction fee and compare the result with the provider’s settlement information. If it differs, investigate additional fees rather than forcing the calculator to match.

4. Add WooCommerce product cost

If you track COGS, verify that the stored cost belongs to the quantity and variation actually sold. A correct gateway calculation paired with stale product cost still produces a misleading profit estimate.

5. Test an edge case

Repeat the exercise with a low-value order or a transaction that uses a different payment method. This often exposes fixed-fee effects or rate differences that are invisible at average order value.

Common reasons your calculated fee does not match the settlement

  • The transaction was international.
  • Currency conversion applied.
  • The payment method has a different base rate.
  • The merchant has custom or volume pricing.
  • The processor calculated its fee from a different amount than you assumed.
  • A refund, dispute or other adjustment is included in the report.
  • Taxes or shipping were included differently in your profit model.
  • You compared a single transaction with a payout that bundles multiple transactions.

The right response is to identify the missing component, not to invent a “correction factor.”

Where this fits with other WooCommerce tools

Payment economics is only one part of maintaining clean product data. Before a large catalog import, the WooCommerce CSV Import Doctor can flag common structural problems. If the catalog contains variable products, use the WooCommerce Variation & SKU Generator to plan combinations and identifiers before creating rows.

For payment decisions, open the WooCommerce Payment Fee & Profit Calculator, enter your actual processor terms and test several realistic order values rather than relying on a single headline percentage.

Final checklist

  • Use the rate for your merchant account and payment method.
  • Model both percentage and fixed transaction fees.
  • Keep payout and profit as separate concepts.
  • Include COGS when evaluating profitability.
  • State clearly which other costs are included.
  • Test low, typical and high order values.
  • Model international and conversion cases separately when relevant.
  • Verify estimates against real settlement reports.
  • Review surcharge compliance separately before adding customer-facing payment fees.

A fee calculator cannot replace your processor statement or accounting records. What it can do is make the assumptions visible. That is often enough to catch pricing decisions that looked reasonable when the fixed transaction cost, COGS or small-order effective rate was hidden.