Bug Report - Square Online - Adding stock to item with unit cost of 0 - cost recorded incorrectly

[Cobbles]

We occasionally are sent free items of product we already sell from a different vendor.

I add a new vendor to the item and set the unit cost to 0, then add the stock, ensuring that I have chosen the new vendor and that the unit cost is 0.

However, if I look in the inventory history, the unit cost has been incorrectly recorded as the original, non-zero unit cost (but with the correct new vendor name).

Please fix this - it's not a one-off, it happens every time.

Steps to reproduce:

1) Open any existing item with a vendor and unit cost not zero.

2) Add a new vendor, and set the unit cost for that vendor to 0.

3) Add stock from that vendor.

4) Look in Inventory History - the stock has been added with the new vendor name but with the unit cost of the original vendor, not the 0 it should be.

[JTPets]

I use the purchase order tool to add new items in, it allows me to report the cost of goods with each order

[Cobbles]

Thanks for the reply @JTPets but I don't see the connection with my bug report?

[Cobbles]

Hello, is there anybody from Square reading bug reports?

It would be good to get a response.

[JTPets]

Are you able to grab any screens recoding or images to show the error? I can tag a few mods with a full report

[Cobbles]

Thanks. I've included very clear steps to reproduce in my OP.

[tranguyen]

Thanks for sharing the steps in your original post, @Cobbles.

Before I can open a ticket with our bugs team, there are just some additional pieces of information I'd like to get so that our team can investigate and try to replicate the issue on their end:

1. Is this happening when you're updating the stocks through the Square for Retail app, on your computer or using a Square device like the Terminal, the Register, etc? And if you are seeing the issue when you're on your computer, can you let me know the browser you are using? 
2. While you have provide the steps, to help make the investigation quicker, it'd be great if you can share a screenshot of an item that you've set up like you've outlined. Or even just share the name of an item that have that setup as an example.
3. Has this been happening only recently, or has it been like this since you first started using unit cost management? 

Once I have these information, I can open a ticket with our team to help us understand more whether this is a limitation with the current Square setup or a bug. 

[Cobbles]

Thanks for getting back to me @tranguyen 

1. I'm using Safari on a Mac to enter items.

2. Here are some example screenshots.

Item set up with 2 vendors. The Freebie vendor has zero unit cost

Add an item from the Freebie vendor - note that the unit cost is 0.

Inventory history for that added item shows incorrect unit cost of the other vendor, not 0 as it should be.

 

3. It's been happening for at least several months now, but I've only recently got round to reporting it.

Thanks.

[tranguyen]

The team is looking into this at the moment but they just want to quickly confirm the name of the item you included in the screenshot above @Cobbles! I couldn't see it in the pic so when you have a moment, if you could let me know which specific item this is, that'd be much appreciated. The team can use it as the starting point for some testing. 

[tranguyen]

Appreciate all the details @Cobbles! I've raised a ticket as I can also replicate the issue when I followed the steps you outlined with my own test account.

When I get an update from our team, I'll follow-up here so please keep an eye on this thread. 

[tranguyen · Accepted solution]

Thanks so much for bearing with me here @Cobbles!

The team have been able to roll out a fix for this issue. Going foward, when you add new inventory with a zero-value unit cost, it should work as expected.

However, for any existing adjustments where the stock price is incorrect, you'd need to manually adjust this still and it should reflect the zero-value unit cost.

Let me know if you are still seeing the same issue when creating new adjustment and I can definitely reach back out to our engineering team. 

[Cobbles]

@tranguyen Thanks, I can confirm that this bug is now fixed.

[tranguyen]

Glad to hear it's fixed @Cobbles !