Listing Cost Library audit checklist and change log
Last updated: 2026-07-28
Written and reviewed by Seller Profit Guard Editorial Team.
A defensible SKU cost-library audit records identity, units, source evidence, formulas, required layers, effective dates, imports, downstream joins, privacy, approvals, and rollback. Every checked item links to evidence. Completion requires material unknowns and collisions to be resolved or formally held; clean boxes alone are not proof.
What belongs in the identity and unit checklist?
Verify every active SKU is nonblank, unique after approved normalization, attached to the intended product or variation, and protected from historical reuse. Record listing and variation mapping, old-to-new aliases, active dates, currency, purchase unit, usable quantity, consumption unit, conversion, and quantity basis.
Hand-check representative pack, weight, length, batch, hour, minute, item, order, and bundle conversions. Confirm imported decimals and delimiters, block conflicting duplicate rows, and preserve the pre-import backup.
| Control | Required evidence | Failure response |
|---|---|---|
| Identity | Unique SKU and mapping | Resolve collision |
| Units | Conversion hand-check | Correct denominator |
| Layers | Included/excluded scope | Measure or hold |
| Source | Lineage and date | Refresh evidence |
| Version | Effective interval | Repair history |
| Join | Dummy and representative match | Fix mapping |
What belongs in the source and formula checklist?
For materials, labor, packaging, fulfillment, allocation, and risk, record source, currency, unit, formula, effective date, owner, and review trigger. Recalculate each subtotal and the final total. Verify waste, yield, quantity, and labor are not counted twice.
Classify every layer as observed, measured, allocated, estimated, stale, or unknown. Confirm zeros have evidence and negatives use explicit credit or recovery treatment. Check that marketplace and order costs are not hidden inside a production layer and then subtracted again downstream.
How should changes and approvals be logged?
Record timestamp, SKU set, old and new values, source change, unit change, formula change, reason, affected periods, fixtures, expected results, operator, reviewer, approval, rollback, and follow-up. Preserve the prior library and report fingerprints.
Review a bounded sample of unchanged and changed records, plus missing, duplicate, stale, and variation-sensitive cases. Approval states the exact scope and does not certify profit, tax, accounting, employment, legal, or marketplace compliance.
- Every check links to evidence.
- Every change creates a version.
- Every import has a backup.
- Every exception has an owner.
- Every approval states scope and rollback.
How do you design an audit sample that can find defects?
Define the population before choosing rows: active SKU versions, versions used by the review period, imported source records, or sold-item joins. Record population size, selection rule, exclusions, and review date. Include a deterministic random sample for broad coverage and a risk sample for newly added, high-value, high-volume, multi-currency, renamed, bundled, stale, manually overridden, or variation-sensitive records. Do not choose only familiar bestsellers or records that already passed a dashboard.
Trace each selected item in both directions. Starting from the SKU record, reproduce source quantity, conversion, layer subtotal, effective interval, and total, then confirm a dummy or private controlled transaction selects that version. Starting from a transaction reference, find the one valid SKU version and reconstruct its layers. Record population and sample error counts separately; a passing sample provides bounded assurance for that procedure and date, not proof that every untested row is correct.
Add deliberate negative fixtures outside private data: a blank identifier, a normalization collision, a pack-versus-each error, overlapping version dates, missing labor, stale shipping evidence, and an unmatched variation. The validator must reject or classify each fixture as expected. If a previously detected defect no longer triggers, investigate the control before celebrating a cleaner report.
| Sample stratum | Why inspect it | Reperformance |
|---|---|---|
| Random active records | Broad library coverage | Source through total |
| Changed versions | Update and interval risk | Old/new selection |
| Variation extremes | Averages can conceal loss | Option-specific join |
| Negative fixtures | Validator sensitivity | Expected rejection |
| Historical orders | Current-cost rewrite risk | Date-effective match |
What should the final audit evidence package contain?
Keep a compact manifest containing audit scope, population counts, sampling method, reviewed control version, library fingerprints before and after review, source-register summary, exception register, fixture results, recalculation worksheet, version-overlap test, join-test summary, reviewer questions, dispositions, approval boundary, and rollback location. Reference private evidence by controlled identifier or path; do not copy invoices, buyer details, supplier terms, or raw order exports into a public SEO report.
Separate findings from management actions. A finding states the observed condition, affected population, evidence, and control objective. The response names an owner, correction, validation method, due date, and residual uncertainty. The reviewer then marks the finding open, remediated, accepted within a stated operational boundary, or outside scope. A blank status, deleted row, or reduced warning count is not a disposition.
Finish with a reconciliation of counts and material changes. Explain why active records, unique SKUs, versions, unknown layers, exceptions, and fingerprints changed from the opening snapshot. Retain unanswered reviewer questions independently from the operator queue. This makes the audit reproducible even when the person approving it did not perform the import or cost measurement.
- Scope and population are explicit.
- Sampling is reproducible and risk-aware.
- Fixtures prove controls can still fail.
- Findings remain distinct from corrective actions.
- Private evidence stays referenced, not republished.
- Closing counts reconcile with the opening snapshot.
SKU cost audit questions
Can the checklist replace an accountant? No. It is an operational data control.
Should historical costs be changed after an audit? Correct errors through a logged version or correction; preserve prior evidence.
How are inactive SKUs handled? Archive with dates and mappings needed for historical orders.
What blocks approval? Ambiguous identity, invalid units, material unknowns, broken versions, failed joins, or missing rollback.
What proves completion? Reproduced totals, passing controls, resolved or formally held exceptions, and preserved evidence.
What negative evidence should an auditor inspect?
Challenge sudden zero warnings, missing cost categories, reduced row counts, identical costs across unlike variations, unchanged labor after workflow changes, and all records sharing one source date. A clean result can reflect a weakened control.
Compare the current package with the prior approved state and explain material changes. Keep reviewer questions separate from operator exceptions so approval pressure cannot silently close either list.
Define audit criteria before inspecting results: approved identity rules, unit dictionary, required layers, evidence classes, refresh intervals, effective-date policy, import tolerances, fixture expectations, join logic, and approval roles. Freeze the criteria version in the evidence package. Changing a tolerance after seeing failures is a control change that needs its own reason, test, and approval.
Use reviewer independence proportionate to risk. The operator can self-check ordinary additions, while bulk imports, mapping changes, formula changes, corrections to historical intervals, and overrides of material unknowns deserve a second reviewer. Independence does not mean copying private data into a new system; provide controlled access to the source reference and retain only the minimum audit result.
Which evidence supports this SKU cost audit?
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 audit
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 audit 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.
- SKU Cost Formula: 8 Inputs Etsy Sellers Need: Continue the SKU evidence, version, and decision workflow.
- 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.
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.