Inventory count API issue

andyandy Member Posts: 20
edited January 2019 in Apps & Integrations
Our e-commerce platform gets stock levels from inventory in lightspeed via the API. We just pull through the changes since the last time it checked to keep it simple. 

The problem comes when we adjust inventory levels in Lightspeed via an inventory count. Doing so doesn’t appear to update the time stamp of the items that it adjusts. Therefore the API can’t see the changes and everything quickly gets out of sync.

Can anyone at Lightspeed let me know if this is a bug, something we’ll need to workaround, or are we missing something?
Post edited by andy on
Tags:

11 comments

  • andyandy Member Posts: 20
  • gregaricangregarican Member Posts: 504 
    Quick question. If you look in the front end web client, do you see the activity in the Inventory Change Logs for an item that was adjusted?
  • Adrian SamuelAdrian Samuel Moderator, Lightspeed Staff Posts: 625 moderator
    @andy I've done some testing and I note that the timeStamp changes intermittently. You can make a count and a given item might have an update in the timeStamp, or it unfortunately simply might not. It might be better for you to check the ItemShops relation against a previous stock level that you persist a DB record.

    Adrian Samuel

    Integrations & Solutions Developer - Strategic Solutions

    Lightspeed HQ

  • gregaricangregarican Member Posts: 504 
    Not to interject here, but wouldn't this be considered a defect that would require fixing? Reason I'm asking is that I have a fair amount of API routines that rely on timeStamp values being consistently defined. If there is some inconsistency present then this is a concern. Retooling a fair amount of custom code isn't as desirable as patching the bug really :smiley:
  • andyandy Member Posts: 20
    @Adrian Samuel Sounds like a pretty major flaw. Do you think it’s only related to the Inventory Counts tool? What’s the process from here? 
  • Adrian SamuelAdrian Samuel Moderator, Lightspeed Staff Posts: 625 moderator
    @andy I really couldn't say, it might be that DB time stamp updates run a time routine and if I waited a bit longer it would have updated. It really requires end to end testing to see what's really happening.

    I'll file a bug for our developers to look into this.

    Adrian Samuel

    Integrations & Solutions Developer - Strategic Solutions

    Lightspeed HQ

  • NiguNigu Member Posts: 6

    Hey @Adrian Samuel

    I've also faced with this issue.

    It happens if you change Inventory could inline in Inventory Details:

    You will see "Working" and "Saved Changes" notification, but you can find that Total Remaining still incorrect and does not match sum of Remaining input values. Also Item.timeStamp is not changed too - so you can't get this quantity change by timeStamp filtering. History tab also will show old information.

    You can add "0" into Quantity input in Add Inventory box and press "Add Inventory" which will do nothing but update Item timeStamp, Inventory Details and History tab. But it's definitely not a best solution, so hope it will be fixed soon.

  • andyandy Member Posts: 20

    @Adrian Samuel Did anything ever come of this?

    We are still having issues with inventory levels not updating. Most recently, some items that were sold online with sales pushed through the API appear to have updated correctly, but, some of the same item sold in store on the same day don't appear to have updated the timestamp, leading to the API seeing incorrect information and us selling things we no longer have.

  • andyandy Member Posts: 20
    edited January 2
  • gregaricangregarican Member Posts: 504 

    This thread is approaching its first birthday. It would be reassuring to know that this has been identified as a defect and is on the dev roadmap for being patched. But the lack of feedback leads me to believe otherwise.

  • andyandy Member Posts: 20

    Sigh.

Sign In or Register to comment.