Seller Profit Guard

Listing Cost Library worked example for a handmade product

Last updated: 2026-07-28

Written and reviewed by Seller Profit Guard Editorial Team.

This illustrative handmade SKU totals $18.35 before marketplace fees: $6.40 materials, $7.50 labor, $1.45 packaging, $2.20 fulfillment preparation, and $0.80 allocation. The example shows units, intermediate arithmetic, and evidence labels. Replace every value with current invoices, measured time, and seller-specific records.

Listing Cost Library worked example for a handmade product evidence workflow from source and units through SKU version and seller decision
A reusable cost record keeps identity, units, source, version, and decision connected.

What handmade product is the example costing?

Assume one personalized desk accessory uses a wood blank, finish, hardware, protective material, and a printed insert. The seller assigns SKU DESK-WAL-PERS-01 and records one production batch, timed personalization, and a standard domestic packaging configuration. The example excludes Etsy fees and final shipping label cost so those remain order-specific downstream layers.

Illustrative materials are $4.80 for the blank and hardware, $0.95 for measured finish and consumables, and $0.65 for expected batch waste, totaling $6.40. Fifteen labor minutes at a $30 loaded hourly rate equal $7.50. Packaging components total $1.45; fulfillment preparation is $2.20; a documented monthly tool allocation adds $0.80.

Handmade SKU cost waterfall totaling 18 dollars and 35 cents before marketplace fees
The example preserves intermediate arithmetic instead of storing only a total.
LayerIllustrative calculationAmount
MaterialsBlank/hardware 4.80 + finish 0.95 + waste 0.65$6.40
Labor15 minutes ÷ 60 × $30/hour$7.50
PackagingBox, protection, tape, insert$1.45
PreparationHandling and fulfillment preparation$2.20
AllocationDocumented per-order tool allocation$0.80
TotalSum before marketplace fee and label$18.35

How are the example values entered and tested?

Enter the SKU, each cost layer, labor minutes and rate, source notes, currency, and effective date. Save locally, reload, and export. Recalculate labor separately: 15 ÷ 60 × 30 equals 7.50. Add the five displayed amounts to confirm 18.35. A unit test should reject negative cost, nonnumeric minutes, blank SKU, and a duplicate SKU with conflicting values.

Import the record into a fresh browser profile or test library and confirm the exported values round-trip without changing units or decimals. Link the SKU to a public dummy order and verify the downstream calculator subtracts the total once per unit and flags a deliberately misspelled SKU.

Evidence matrix for the handmade example showing invoice time study packaging count and allocation
Each example value has a different evidence type and review trigger.

What decisions can the $18.35 record support?

It supports a product-cost input for pricing and contribution scenarios within the documented scope. It does not prove profit because order revenue, Etsy fees, advertising, actual label cost, refunds, tax, overhead outside the allocation, and owner objectives remain separate.

Stress the record with higher material price, longer personalization time, heavier packaging, or rework. Change one driver at a time and show the delta. If the seller plans a $42 sale price, the remaining amount before marketplace fees, shipping label, ads, risk, and target is $23.65—not final profit.

Handmade SKU example questions

Why exclude the shipping label? It can vary by destination, weight, package, and service; model actual or route-specific cost downstream.

Why include fulfillment preparation? It is a measured seller cost distinct from carrier label price.

Can the $0.80 allocation be removed? Yes if the decision reports contribution before that allocation; label the scope.

How is waste measured? Use batch input versus good output or measured consumption, and avoid adding the same waste twice.

Does the example reflect a customer? No. It is synthetic and contains no seller, buyer, order, or invoice data.

How does the example respond to a supplier price change?

If the blank rises from $4.80 to $5.40, create a new effective-dated record. The illustrative total becomes $18.95 while the prior $18.35 version remains attached to earlier production or sales under the seller's policy.

Re-run the downstream price case and attribute the $0.60 change to material. Do not edit labor, packaging, or allocation to preserve a preferred total. Record source, date, affected inventory, decision, and rollback.

Reperform the example without copying its total. Start with the five independent source facts, convert each to a per-sellable-unit amount, and add them only after the units agree. Then change quantity from one item to two and state which layers multiply, which remain per order, and which require a separate bundle record. This exposes formulas that accidentally treat every cost as per item.

Use the example as a regression fixture with expected intermediate values, not merely a marketing illustration. Save the inputs, rounded layer outputs, total, effective date, and selected SKU version. After code or import changes, compare every intermediate result. A matching final total can still hide offsetting errors, so subtotal equality matters.

Listing Cost Library worked example for a handmade product page-specific cost comparison and control boundary
The comparison isolates the page's decision without presenting a planning estimate as observed cost.

Which evidence supports this handmade SKU example?

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.

Privacy and commercial sensitivity for handmade SKU example

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.

How to apply this handmade SKU example 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.

  1. Preserve the source evidence and current library backup.
  2. Validate the SKU, currency, units, quantity basis, and effective date.
  3. Calculate each cost layer independently before summing.
  4. Import and resolve duplicate, missing, or invalid rows.
  5. Test one handmade and one variation-sensitive scenario.
  6. Record the version, decision, rollback, and next review.

Related resources

Sources and further reading

Related Seller Profit Guard tools

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.