Many new stores price from one number: supplier cost. That is the fastest way to misread profit. The real pricing floor is not COGS alone. It is COGS, packaging, warehousing, fulfillment, payment fees, platform fees, discounts, refunds, duties or tax boundaries, support, and ad payback combined into contribution profit. A product that looks like it has 60% gross margin can still lose money per order if several layers are missing.
This article does not give a fee table because platform plans, payment providers, rates, and markets change. Treat it as a pricing cost stack: where each cost comes from, what teams usually miss, and when to move into the Ecomwith pricing calculator for scenario testing. The goal is not one perfect price. It is knowing the floor you cannot sell below, the discount that destroys margin, and the ROAS your ads must clear.
Product cost is not the pricing floor
COGS is product cost, not order cost. Suppose a supplier charges $18 and you plan to sell at $49. The margin looks healthy. But add $5 for packaging and fulfillment, $3 for payment and platform fees, $6 average shipping subsidy, $5 discount, $3 refund loss, and $2 support and exceptions. Contribution profit can fall to roughly $7. That leaves very little room for paid acquisition.
Separate three profit layers. Product gross margin is price minus COGS. Contribution profit deducts costs that move with each order. Operating profit also deducts fixed costs, software, people, and inventory financing. Pricing must at least protect contribution profit; otherwise, every new order can amplify cash pressure.
Cost layers to include before setting price
The first layer is product and packaging: purchase price, samples, defects, packaging material, and inspection. The second is fulfillment: warehousing, pick-pack, domestic freight, international freight, exceptions, and reshipments. The third is transaction cost: payment fee, platform transaction fee, currency loss, refund processing, and dispute cost. The fourth is promotion: discount, gift, free shipping subsidy, affiliate commission, and creator samples.
The fifth layer is refund and support: return shipping, unsellable returns, support time, and chargeback risk. The sixth is ad payback: how much you can spend on a first order and how much repeat purchase, email, accessories, or subscription revenue is proven later. The seventh is cash timing: inventory deposits, ad prepay, payout delay, and supplier terms. Profit lives not only inside an order, but also in when cash leaves and returns.
A simple SKU example
Assume a $59 price, $22 COGS, $6 packaging and fulfillment, $3 payment and platform fees, $7 average shipping subsidy, $4 blended discount, $3 refund loss, and $2 support or exception cost. Contribution profit is $12, and contribution margin is about 20.3%. If you judge only the first order, break-even ROAS is roughly 493%. If an ad platform reports 300% ROAS, the store may be losing money on first-order economics even as orders rise.
Now imagine a bundle raises AOV to $79 while extra COGS and fulfillment add only $12. Contribution profit may rise to $26, contribution margin to about 32.9%, and break-even ROAS may drop near 304%. Pricing is not an isolated setting. AOV, bundle structure, shipping threshold, discount design, inventory mix, and refund rate all change what ads can afford.
How refunds and discounts change the answer
Refunds are not only a support problem; they are a pricing variable. A product with an 8% refund rate and a product with a 2% refund rate can have identical price and COGS but completely different ad tolerance. Refunds may also include return shipping, unsellable inventory, support time, and disputes. Pricing models should include expected refund loss before the month-end report arrives.
Discounts are not only a conversion lever. Ten percent off, free shipping, buy X get Y, bundle pricing, automatic discounts, and discount codes affect AOV, margin, buyer expectation, and repeat quality differently. Before launching a promotion, ask whether the goal is first-order conversion, inventory movement, AOV lift, or list growth. Without a clear job, the store often trades profit for low-quality orders.
When to use the pricing calculator
Use the pricing calculator when you can list price, COGS, payment cost, fulfillment, shipping subsidy, discount, refund rate, and ad cost. Run at least three scenarios: normal price, promotion price, and bundle price. For each scenario, review contribution profit, contribution margin, acceptable CPA, break-even ROAS, and cash recovery timing. Do not stop at gross margin percentage.
If the calculator shows thin profit, inspect four directions before reacting: price may be too low, bundle or AOV may need work, fulfillment or shipping may need redesign, or ads may need a smaller test. Cutting ad budget is not the only answer. Healthy pricing is the shared result of page promise, promotion, logistics, inventory, and acquisition economics.
Pricing cost stack
| Cost layer | Where to get it | Common mistake | Calculator input |
|---|---|---|---|
| COGS | Supplier quote, purchase order, BOM | Using purchase cost only and missing packaging or defects | Product cost |
| Fulfillment | 3PL bill, warehouse fees, freight table | Using standard freight only and missing reships or free-shipping subsidy | Fulfillment and shipping cost |
| Payment fees | Shopify, gateway, payout statement | Using a rough percent and missing cross-border or refund costs | Payment and transaction fee |
| Discounts | Discount rules, order reports, affiliate commissions | Reading conversion lift without margin dilution | Discount and commission |
| Refunds | Refund rate, support logs, return cost | Treating refunds as a month-end issue, not pricing input | Refund and support loss |
Turn this into a repeatable operating loop
Do not treat this article as a one-time reading task. Turn the decisions around Product cost is not the pricing floor / Cost layers to include before setting price / A simple SKU example into a small operating loop that your team can run before a launch, after a platform change, or when performance data starts to look inconsistent. The practical output should be a dated note, a checklist status, and a short owner comment, not a vague memory that someone "looked at it." That habit gives future reviews something concrete to compare against.
The table on Pricing cost stack starts with COGS / Fulfillment / Payment fees. Use those rows as the minimum evidence set. If one row cannot be verified, mark the page, campaign, feed, event, or policy as not ready and write down the exact missing proof. This protects the team from a common ecommerce failure mode: a visible metric moves, everyone reacts, but no one knows whether the store, tracking, content, or offer was actually in a valid state.
After you apply the checklist, connect the result to the linked Ecomwith tool, tutorial, or answer page. The blog should help you make the first decision; the next route should help you calculate, audit, document, or repair the issue. That is also what makes the page useful for search and AI discovery: it states the operating question, shows the evidence, and then points to the next page where the reader can act with more context.