Tracking WooCommerce cost of goods gives store owners a clearer view of how product costs relate to selling prices and order values. Instead of relying only on revenue, you can record the direct cost assigned to a product, review that cost in the order editor and use the resulting information to support product and order profitability analysis.
WooCommerce includes a Cost of Goods Sold feature for this workflow. You can enable it in the settings, assign costs to simple products or variations, inspect line-item costs and maintain catalog data through the built-in product CSV tools. However, COGS should be treated as direct product-cost tracking, not as a complete accounting or net-profit system. The following process explains what the feature records, how to configure it and which limitations matter when interpreting the results.
What WooCommerce Cost of Goods Sold Tracks
WooCommerce Cost of Goods Sold records a cost associated with a product sold in the store. Once product costs are populated, the order editor can use them to show the cost of individual line items and the total product cost displayed for an order. This helps store owners compare the amount charged with the direct cost assigned to the products in that order.
For a catalog with different products, this information can support product-level comparisons. It can also help identify how the cost of a particular product contributes to an order-level result. The feature is therefore useful when you need a consistent place to maintain product cost data rather than relying only on selling prices.
Direct product costs versus net profit
The scope of COGS is important. The documented feature concerns direct product costs, so the displayed values should support gross-profit analysis rather than be presented as complete net-profit figures. The available information does not establish that the product cost field includes shipping, payment-processing fees, advertising, labor, taxes, storage, returns handling or other overhead.
Consequently, a store owner should not treat a COGS total as a substitute for accounting advice or a complete financial statement. Broader profitability may require additional cost categories and separate financial review. Use the WooCommerce values to understand product costs and order-level gross-profit relationships, while keeping that boundary clear.
How to Enable COGS in WooCommerce
The built-in Cost of Goods Sold feature must be enabled before cost fields become available in the product editing screens. The documented configuration path is located in the WordPress administration area under WooCommerce settings.
Activation checklist
- Open WooCommerce in the WordPress admin and select Settings.
- Open the Advanced section, then select Features.
- Select the Cost of Goods Sold option.
- Save the changes.
- Open a product editor and confirm that the cost field is available.
After activation, check the product editing screens before relying on order cost figures. This simple confirmation helps establish that the feature is active and that the intended cost data source is being used.
If another COGS plugin or solution is already active, identify which system should be authoritative before enabling or configuring a second one. Running overlapping COGS systems can produce two cost totals, making later order review harder to interpret.
Assigning Costs to Simple Products
For a simple product, the cost is entered directly in the product editor. Open the relevant product, go to the General tab and locate the Cost of Goods field. Enter the product cost used for direct-cost tracking, then save the product.
This value becomes important when WooCommerce calculates the cost associated with an order line. The field should represent the direct product cost you intend to track in the store. Do not assume that it automatically includes other categories of business expenditure, because the documented feature does not establish that broader scope.
Verifying the product-level value
Review the field after entering it, especially before checking order-level results. If no value is set for a simple product, the cost defaults to zero. An empty field can therefore be interpreted by the system as a zero cost, even when the store owner has simply not finished configuring the catalog.
A practical check is to open several products after activation and confirm that the intended values are populated. When reviewing later orders, use the configured product cost consistently and investigate any unexpected zero before drawing conclusions about product profitability.
Handling Variable Product Costs
Variable products require an additional check because different variations can have different direct costs. WooCommerce allows a cost to be entered at the variable-product level. That product-level cost is inherited by the variations as a default value.
This is useful when the variations share the same direct cost. For example, if the relevant variations have one common product cost, the shared product-level value can provide the default rather than requiring the same value to be entered repeatedly.
Default values and variation overrides
When variation costs differ, configure individual variation values to override the inherited default. The workflow is therefore based on two levels:
- Use the variable-product cost as the default when the variations share the same direct cost.
- Enter an individual variation cost when that variation has a different direct cost.
- Review the variation data after manual or bulk changes before interpreting order costs.
The important distinction is between an inherited value and an override. One product-level value should not automatically be treated as accurate for every variation after variation-specific costs have been configured. Check the individual variations whenever costs differ by size, color or another variation attribute.
This review is especially important before analyzing orders containing multiple variations. The cost used for a line item depends on the product or variation data assigned to that item, so the catalog should reflect the intended values before the order data is evaluated.
Reading COGS in WooCommerce Orders
Once product costs are configured, open an order in the WooCommerce order editor to review how those values are displayed. WooCommerce adds a Cost column for each line item. This makes it possible to inspect product cost at the same level as the products and quantities included in the order.
The line-item cost is calculated from the individual product cost multiplied by the ordered quantity. This means that the displayed value reflects both the configured cost for the product or variation and the number of units purchased. Reviewing the quantity alongside the cost can help explain why an order line contributes a particular amount to the total.
Line-item cost, Cost Total and refunds
WooCommerce also displays a Cost Total beside the order total. This provides an order-level view of the product costs shown for the order. You can use the line-item values and Cost Total together when supporting a gross-profit analysis, while remembering that the result does not establish complete net profit.
Refunds require separate attention. For refunded orders, the order editor displays the combined cost of refunded items. A tooltip also shows the per-unit product cost. Inspecting both pieces of information helps clarify how the refunded quantity relates to the displayed cost.
Do not assume that changing a current product cost will recalculate historical order COGS values. WooCommerce documentation states that existing order COGS values do not change when the product price is later updated. Historical order review should therefore be interpreted using the stored order values rather than an expectation of automatic retroactive recalculation.
Importing and Exporting Product Costs with CSV
WooCommerce supports COGS values through its built-in product CSV import and export tools. This is useful for stores maintaining a larger catalog or needing to move product cost data in bulk. The tools are available from Products and All Products, where you can choose Import or Export.
Exports can include selected columns or all product columns. Imports can add products or update existing products. WooCommerce also supports matching existing products by ID or SKU, which is important when the purpose of the import is to update existing catalog data rather than create additional products.
The feature supports COGS values, but the reviewed information does not verify a specific COGS column name or provide a complete COGS-specific CSV example. Avoid assuming an unverified file structure. Use the export workflow and the fields provided by the relevant WooCommerce installation as the basis for preparing changes.
A controlled bulk-update workflow
- Back up the store before making a bulk catalog change.
- Export the relevant product data from Products > All Products.
- Prepare a small test update rather than changing the entire catalog immediately.
- Confirm that existing products and variations will be matched consistently by ID or SKU.
- Run the test on staging or a test site when possible.
- Inspect several edited products after the import completes.
- Proceed with a larger update only after the test produces the expected results.
This controlled process reduces the risk of changing the wrong products or variations. For larger catalogs, smaller batches can make review easier. After importing, verify that the cost values appear correctly in the product editor and that the relevant product or variation matches the intended record.
Important COGS Limitations and Compatibility Checks
WooCommerce COGS can provide useful direct-cost information, but several boundaries affect how the data should be used. Understanding them before building a reporting workflow helps prevent incorrect conclusions about product margins, order profitability or historical figures.
First, the documented feature is not currently integrated with WooCommerce Analytics. Do not expect native COGS dashboards or Analytics-based profit reports based on this feature. Order-editor values can still support direct review and gross-profit analysis, but the absence of Analytics integration is an important reporting limitation.
Second, product and order data should not be confused. Updating a current product price does not change existing order COGS values. Historical orders therefore should not be treated as if they will automatically recalculate after a later catalog change.
What the feature does not provide
The feature does not establish a complete net-profit system. The reviewed documentation supports tracking direct product costs, but it does not confirm that the field includes shipping, payment-processing fees, advertising, labor, taxes, storage, returns handling or other overhead. Those categories may require separate review.
It also does not provide a documented WooCommerce Analytics integration for COGS. If you need broader financial reporting, treat the order-editor cost values as one part of the information required for that analysis, not as the entire result.
Finally, avoid running another COGS plugin alongside the built-in feature without deciding which source is authoritative. Two active cost systems can produce two totals. A clear setup sequence is to enable the intended feature, assign costs to simple products and variations, review order costs, and maintain the catalog carefully through controlled updates.
WooCommerce Cost of Goods Sold offers a practical way to record direct product costs, review line-item and order-level costs, and maintain catalog values through CSV import and export. For simple products, enter the cost in the General tab; for variable products, use a shared default or variation-specific overrides. In orders, review the Cost column, Cost Total and refund details. Keep the limitations in view: COGS is not currently integrated with WooCommerce Analytics, later product-price changes do not recalculate existing order values, and the feature is not complete net-profit accounting. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.