SKU cost formula, inputs, units, and assumptions
Last updated: 2026-07-28
Written and reviewed by Seller Profit Guard Editorial Team.
A reusable SKU cost record separates material, purchased components, labor, packaging, fulfillment, transaction extras, allocated variable overhead, and expected loss. Every value needs a currency, unit basis, source, effective date, and owner. Sum only compatible per-unit or per-order amounts; unknown costs must never be converted to zero.
What is the complete per-SKU cost formula?
For one sellable SKU, direct unit cost equals material and purchased-component consumption plus production or provider cost plus measured labor plus packaging plus SKU-attributable fulfillment plus other variable cost. Add explicit allocation and expected-loss layers only when the decision requires them, and keep those layers visible. Marketplace fees belong in the order profit calculation unless the library deliberately stores a source-dated per-order planning assumption.
Normalize every component to the same decision grain. A material purchased by the roll becomes cost per used length plus credible waste. A batch becomes cost per good unit, not per unit started. Labor minutes become minutes divided by sixty multiplied by the loaded hourly rate. Packaging packs become component cost per order. Shipping can be a current label receipt, route-specific planning case, or excluded from the reusable product cost with a clear flag.
| Layer | Formula basis | Required metadata |
|---|---|---|
| Material | Used quantity × unit cost + waste | Unit, source, date |
| Labor | Minutes ÷ 60 × loaded hourly rate | Task, rate, timing sample |
| Packaging | Components per order × component cost | Pack size and quantity |
| Fulfillment | Label, handling, insurance, provider | Route and evidence type |
| Allocation | Documented shared cost ÷ relevant driver | Period and denominator |
| Expected loss | Incident rate × unrecovered loss | Cohort and sample |
How should units and quantity basis be normalized?
Store purchase unit, purchase quantity, usable quantity, consumption unit, consumption per SKU, conversion factor, waste basis, and resulting cost. Do not type a pack price directly into a per-unit field. For weight or length, document whether the usage is measured before or after trim, cure, shrinkage, or spoilage.
Test each conversion with a hand calculation and a boundary case. A 50-sheet pack costing $20 is $0.40 per sheet before waste. If a product uses 1.5 sheets and expected waste is 8% of consumption, document whether the applied usage is 1.62 sheets or a batch-yield method. The choice must be consistent and must not add waste twice.
Which assumptions must stay outside observed cost?
Future shipping, expected returns, planned discounts, estimated labor improvement, and forecast order volume are scenarios rather than settled product cost. Store them in labeled fields or run them in the downstream calculator. Do not overwrite a current measured record with an optimistic future state.
General overhead such as rent, software, utilities, and owner compensation can be important, but allocation is a policy choice. Record the driver, period, denominator, included costs, and decision purpose. Keep contribution before overhead distinguishable from a target that reserves overhead or owner pay.
- Observed invoice cost
- Measured consumption
- Measured labor
- Explicit allocation
- Estimated risk
- Unknown pending evidence
SKU cost formula questions
Should Etsy fees live in the SKU library? Usually keep actual marketplace movements in the order calculation; store only clearly scoped planning assumptions when needed.
Is owner labor free? No. Measure time and choose an explicit rate appropriate to the seller's decision.
Can shipping be one average? Only for a documented cohort; heavy, international, expedited, or free-shipping cases need separate treatment.
What if a component is shared across products? Allocate measured consumption to each SKU and verify total usage returns to purchase or batch evidence.
When is a record reusable? When SKU, units, sources, formulas, dates, and version remain stable and traceable.
How should currency conversion be stored?
Preserve source currency, conversion source, rate date, converted currency, and original amount. Do not overwrite invoice currency with a current rate. For planning, run a dated rate scenario and show the effect separately.
If procurement and sale currencies differ, cost conversion and marketplace settlement are different layers. Apply each conversion once, retain rounding policy, and stress credible currency movement without claiming a forecast.
Treat quantity basis as part of the formula, not a footnote. A roll price needs usable length after setup waste; a sheet price needs pieces per sheet and reject rate; a batch needs sellable output; labor needs task minutes, paid-time scope, and rate basis. Write the dimensional equation beside a dummy calculation so another operator can cancel units and reproduce the amount.
Before approving an input map, change one variable at a time and predict which subtotal should move. A packaging quantity change must not alter material cost. A currency change must not alter physical consumption. If unrelated layers move, the import map or formula dependency is wrong. Preserve these invariance tests as fixtures for later versions.
Which evidence supports this SKU cost formula?
A reusable cost record needs seller-owned evidence. Material and purchased-component costs come from invoices, bills of materials, measured usage, scrap, and yield. Labor comes from timed tasks and an explicit loaded hourly rate. Packaging comes from component quantities and purchase cost. Fulfillment comes from label receipts, carrier adjustments, outsourced fulfillment bills, handling, insurance, and documented subsidies. Etsy exports can carry seller-added SKUs and transaction context, but they do not supply the seller's private production economics.
Record source type, supplier or internal process, currency, quantity basis, unit conversion, effective date, operator, and evidence location without copying private invoices into public reports. A checksum or file identifier can protect lineage, but it does not prove the unit basis is correct. Recalculate pack, sheet, roll, batch, hour, minute, weight, and quantity conversions with a public dummy example before importing a large cost library.
Keep observed, allocated, and estimated values distinguishable. A current invoice is observed evidence; a monthly subscription divided by forecast orders is an allocation; expected scrap, return loss, or future shipping is an estimate. Store the formula and review trigger with every non-observed amount. Unknown remains unknown until measured; zero requires evidence that the cost is genuinely absent.
- Use one stable SKU for every cost-distinct sellable variation.
- Store currency, unit, quantity basis, source, and effective date.
- Separate materials, labor, packaging, fulfillment, overhead allocation, and risk.
- Retain prior versions so historical sales can use the cost effective at the time.
- Escalate tax, accounting, legal, employment, and platform-policy questions to the appropriate professional or official source.
Privacy and commercial sensitivity for SKU cost formula
A cost library does not need buyer names, delivery addresses, private messages, payment credentials, marketplace passwords, or raw order history. It may contain supplier pricing, labor rates, production time, margins, sourcing notes, and fulfillment terms that are commercially sensitive. Keep the working library in controlled seller storage and use redacted identifiers or public dummy values for documentation and support.
Seller Profit Guard stores the free browser workflow locally by design. A downloaded cost library or profit report is still a private business record. Do not paste real supplier invoices, buyer data, order rows, or SKU economics into public communities, email drafts, or AI prompts. Share the column map, formula, units, and a made-up reproduction case when troubleshooting.
- Do not publish raw supplier, buyer, address, or order data.
- Use controlled identifiers rather than invoice images in reports.
- Separate public calculation examples from private operating records.
- Back up the cost library before bulk edits or imports.
- Treat exported cost and margin files as confidential.
How to apply this SKU cost formula in the SKU Cost Library
Open the SKU Cost Library and add one representative SKU manually before importing a file. Confirm material, packaging, labor minutes, labor rate, shipping, transaction extra, other cost, target margin, notes, currency, source date, and unit basis. Save locally, reload, and export the record. Then import the public template or a controlled working copy and review missing, duplicate, invalid, and suspicious values before accepting the batch.
Use the saved library in Profit Guard with a representative order export or the public dummy sample. Inspect missing-cost warnings and variation joins before interpreting contribution. Run a base case and a page-specific stress case, then record the cost version, result, seller decision, owner, and next review date. A reusable record is valuable only when its units, source, effective date, and SKU join remain traceable.
- Preserve the source evidence and current library backup.
- Validate the SKU, currency, units, quantity basis, and effective date.
- Calculate each cost layer independently before summing.
- Import and resolve duplicate, missing, or invalid rows.
- Test one handmade and one variation-sensitive scenario.
- Record the version, decision, rollback, and next review.
Related resources
- Open the SKU Cost Library: Create, import, validate, and reuse browser-local SKU cost assumptions.
- Calculate SKU-level Etsy profit: Apply material, labor, packaging, shipping, and fee records to sold SKUs.
- Review Etsy variation SKU risk: Find blank, duplicated, inconsistent, or cost-distinct variation SKUs.
- Read the Etsy SKU naming guide: Design stable identifiers for listings, variations, inventory, and historical joins.
- Review local-first CSV privacy: Keep buyer, address, order, supplier, and private margin data out of public artifacts.
Sources and further reading
- Etsy Help: How to Use SKU for Your Inventory: Official Etsy guidance on adding SKUs and using seller-defined identifiers to track inventory.
- Etsy Help: How to Add Variations for Your Listings: Official variation workflow, including variation-level price, quantity, processing profile, and SKU controls.
- Etsy Help: Download Sold Transaction Spreadsheets: Official sold-transaction export workflow; order data can include seller-added SKU numbers.
- Etsy Help: How to Calculate Shipping Costs: Official shipping-cost estimator context; final label cost can differ from a planning estimate.
- Seller Profit Guard calculation methodology: Cost-layer definitions, editable assumptions, evidence hierarchy, contribution scope, and local-first privacy boundary.
Related Seller Profit Guard tools
- Open the SKU Cost Library: Create, import, validate, and reuse browser-local SKU cost assumptions.
- Calculate SKU-level Etsy profit: Apply material, labor, packaging, shipping, and fee records to sold SKUs.
- Review Etsy variation SKU risk: Find blank, duplicated, inconsistent, or cost-distinct variation SKUs.
- Read the Etsy SKU naming guide: Design stable identifiers for listings, variations, inventory, and historical joins.
- Review local-first CSV privacy: Keep buyer, address, order, supplier, and private margin data out of public artifacts.
- Etsy SKU Cost Example: A $18.35 Handmade Item: Continue the SKU evidence, version, and decision workflow.
- Etsy Variation Costs: Stop Averaging Every Option: Continue the SKU evidence, version, and decision workflow.
- SKU Costing Mistakes: 12 Errors That Hide Margin: Continue the SKU evidence, version, and decision workflow.
- SKU Cost Data Sources: Invoice to Time Study: Continue the SKU evidence, version, and decision workflow.
- SKU Cost Confidence: When a Record Is Ready: Continue the SKU evidence, version, and decision workflow.
Next step: Open the SKU Cost Library.
This is operational planning help, not tax, accounting, legal, financial, or platform-policy advice. Review the Terms and disclaimer, and verify current platform rules and fee assumptions before changing prices.