If you run a print on demand store on Shopify, you already know the cost of a customized order is not the same as the cost of a plain one. You are probably reconciling your Shopify COGS manually in a spreadsheet or at month end, because Shopify's product cost field holds one number and your orders carry many. This article is about a better way to do what you are already doing

The base cost field was not built for POD 

A base T-shirt costs 10 dollars. One customization adds 2 dollars. Another adds 0.75 dollars. The Shopify product record stays at 10 dollars, but three orders of that same T-shirt can cost 10, 12, or 12.75 dollars to fulfill. Multiply that across a catalog and a month of orders, and the manual reconciliation is the only thing standing between the reported numbers and the real ones.

Why manual POD cost tracking breaks as you grow 

Doing it by hand works until it does not. Order volume climbs, customization options multiply, new SKUs get added, and the spreadsheet starts lagging behind the orders it is meant to describe. Profit per order is only accurate once the reconciliation catches up. Pricing decisions on individual customizations wait on the same cycle. The information needed to automate this is already in each order, which makes the manual work doubly frustrating.

How to speed up COGS tracking with shopify signals 

Shopify gives you two signals that identify what customization an order carries.

Order tags travel with the order and mark the customization option chosen. Line item properties sit on the specific line and hold the per-item details, such as the text or design the customer configured.

Once customization is identifiable through tags or line item properties, the method is: assign a cost to each customization option, then apply that cost automatically to any order whose tags or properties match. Base product cost stays on the product. Customization cost sits on the order. Profit on each order is calculated against the full cost of fulfilling it, with no spreadsheet in the middle.

How this looks in practice

• Order with Customization A: 10 dollar base + 2 dollar customization cost.

• Order with Customization B: 10 dollar base + 0.75 dollar customization cost.

• Order with both: 10 dollar base + 2.75 dollar customization cost.

The product record never changes. The order carries its own cost line for the customization, matched to the tag or line item property that triggered it.

Automate shopify POD cost tracking with Bloom 

Custom orders often look like your best orders on the top line and your worst on the bottom line, once you factor in the hidden costs. With Bloom’s tag and property based cost rules, you get a dedicated view for custom orders and can track true margins instead of estimates. 

Start with a simple rule in Cost Settings 

In Bloom’s cost settings, you can create rules that assign custom costs based on order tags or line item properties. Say your workflow tags a customized order with Cus-A. You just map Cus-A to its associated cost in Bloom. The same approach works for line item properties like “Embroidery: Yes” or “Print type: Foil.”

The Cost flows into every order automatically 

Once a rule is in place, Bloom pulls that customization cost into every matching order’s calculation, right alongside base COGS, shipping, transaction fees, and ad spend. You don’t have to reconcile orders one by one.

Get a clear profit view on every custom order 

In your order profit reports, you can add a dedicated Customization Costs column. This shows exactly how much each add-on contributed to the cost of each order, sitting next to revenue and net profit. You get the actual margin on every custom order instead of an averaged estimate.

Filter and group your custom orders into one view 

Because the rules are tied to tags, you can filter your reports using those same signals. Want to see every order tagged Cus-A for the last 30 days, with total revenue, total customization cost, and total profit? One filter does it. 

Conclusion

The information you need is already in Shopify. Order tags and line item properties tell you which customizations belong to which order. Once costs are attached to those, the monthly reconciliation stops being something you have to carve out time for.

Bloom is built to do that inside the Shopify setup you already run. Base cost stays on the product, customization costs follow the tags and line item properties they come from, and the profit per order lands at a figure that matches reality rather than approximating it.

Frequently asked questions

How do you track customization costs on Shopify POD orders?

Use the signals Shopify already produces: order tags and line item properties. Assign a cost to each customization option, tied to its tag or property, and have those costs applied automatically to any order that matches.

Can order tags and line item properties be used to assign POD costs?

Yes. Order tags identify customizations at the order level and line item properties identify them at the line level. Both can carry assigned costs that get applied automatically to matching orders.

What is the best way to manage Shopify COGS for personalized products?

Keep the base cost on the product and keep the customization cost on the order. Use tags and line item properties as the trigger. Apply the costs automatically so profit per order is correct in real time instead of after a reconciliation pass.

Why does Shopify’s base cost field fall short for print on demand stores?

Because it holds one number per product, and a customized order can carry several different costs on top of the base. A plain T-shirt and the same T-shirt with two add-ons share the same product record but have different fulfillment costs, which is why manual reconciliation becomes the fallback.

Can you see profit on individual custom orders without a monthly reconciliation?

Yes. Once customization costs are tied to order tags or line item properties and applied automatically, each order’s profit is calculated in real time against the full cost of fulfilling it, so you no longer need to wait for a month-end spreadsheet pass to see true margin per order.