Item Costs Not Reflecting in Inventory History Since New Item Entry Page Introduced

I've added new items into my inventory using the newly redesigned Create Item page, and when I run a Cost of Goods Sold Report this morning this pops up to the top:

 

Some stock adjustments in your inventory history are missing unit costs. Add missing costs for accurate reports and margins.

 

Every item that I entered had a cost associated with it. I believe the new Create Item page has a bug and is not carrying through to all reports, namely the Inventory History Report. 

250 Views
Message 1 of 2
Report
1 REPLY 1
Square Champion

Hey there! 👋 Thanks for sharing this — I'm seeing the same issue after the recent update, so it definitely looks like there may be a glitch with the new Create Item page not linking costs to Inventory History correctly.

🧐 What’s Happening:

Even though you entered your costs during item creation, it sounds like they’re not being carried over to the Inventory History, which is what Square uses for COGS (Cost of Goods Sold) reports. That can cause reports to throw errors or show missing costs, which is super frustrating — especially when you're trying to stay on top of margins.

What You Can Try Right Now:

  1. Manually Add Missing Costs:

    • Head over to Inventory > History

    • Click on any adjustment labeled "Missing Cost"

    • Enter the cost manually (yes, I know it’s annoying — but it works as a temp fix)

  2. Double Check via CSV Export:

    • Export your item library as a CSV (from Item Library > Export)

    • Make sure the Unit Cost shows up correctly in the sheet

    • Re-upload if needed, which can bulk apply costs across items

  3. Report It to Square Directly:

    • Sounds like a bug Square needs to address. Use your Dashboard under Settings > Feedback (or even chat with support) to report it with a quick note like:

      “Cost not syncing from new Create Item page to Inventory History/COGS report.”

The more of us that report this, the quicker it gets escalated. You're not alone — and thank you for flagging it, because this definitely affects reporting accuracy!

Let us know if you figure out another workaround — we’re all ears. 💙

224 Views
Message 2 of 2
Report