@jamesratcliffe what about work order lines? I'd like to be able to add a WorkOrderLine (I believe this is the correct abstraction) to a work order using the API. Is there any way to do this, or any alternative that you'd recommend?
I was taking a look at the docs for Sale, and it doesn't look like there is a way to add a SaleLine to a Sale either?
In the access scopes page there is a scope for employee:workbench that describes an ability to "View, create, update, and archive work orders." I found this misleading, but maybe this refers to something else?
Yes, that is a bit confusing, but the scope technically does grant write access. Right now that access is useless because there's no endpoint that lets you create, update or archive work orders, but when they're added, tokens with this scope will already be able to use those endpoints.
Adrian SamuelModerator, Lightspeed StaffPosts: 654moderator
@mVanier, none yet. Product managers are aware, there has been conversation on it, however any such updates would stand behind our major updates to our costing and inventory modules which we've publicly spoken about. Since workorders reserve inventory internally, all these things have to be factored into a logical development flow.
To your knowledge, is there another way to import workorders in bulk (ex. csv file, xml, etc.)? Or is the only way to create workorders is through the user interface?
I did the Booxi demo and the workorders are not created within booxi but actually through opening Lightspeed not through the API.
The 2 options then are creating a sale or a work order. The only advantage I see is that the client name is on a pick list and if you are creating a sale the noninventory item that is associated with the appointment is populated into the sale.
This still shows that the customer and noninventory item were added somehow through the API.
Can you point me to how one can open a lightspeed session with those parameters?
Please consider this as another upvote for the request to add Workorder Put/Post to the API.
We need the ability to create Workorders, and not having that in the API is going to create a lot of workarounds and manual data entry for our company.
Are there any updates on this request? Is it on a road map anywhere?
Since the loss of GSX in OnSite and the changes to work orders in Retail, this is becoming a critical need for us to be able to consider moving to Retail.
Given that the drop dead date for OnSite is a little less than a year away, this could be a significant pain point that may prevent us moving to Retail. We can understand that it is a small subset of users that needed GSX integration and OnSite like Work orders, and that Lightspeed may not be able to support this directly in new products. I would expect that extensions like this to the API would benefit a rather large number of users and allow users like us to implement custom integrations to keep our businesses running smoothly.
Seeing that in a few months will make the 3rd anniversary of the original post, I certainly wouldn't put too much faith in this actually being delivered. Although having a comprehensive API that mirror functionality available in the web client would seem logical enough...
Not being able to connect an external service booking system directly to work orders is such a severe oversight of LSR. If they don't allow API access then they should provide equivalent functionality within their UI to do this, but they don't. I don't know how other service based businesses are getting around this, but it's an extremely frustrating part of using LSR.
Not being able to connect an external service booking system directly to work orders is such a severe oversight of LSR. If they don't allow API access then they should provide equivalent functionality within their UI to do this, but they don't. I don't know how
Creating workorders through the web interface is tedious. Would really love an api endpoint for creating a new workorder. With appointments becoming the covid norm, it's essential to allow us to create integrations with third party appointment booking systems to generate new workorders associated with appointments. Under the current setup, we are copy ans pasting customer appointment registration from one browser tab to another. It's not a sustainable workflow. Thanks!
When is this going to get fixed?? Whether it be workorders, layaways or special orders, lets get going!!! It's ridiculous, you can find tonnes of threads where people are asking for this! If LS did it correctly the right way no one would need the API to do these things but when you need to build a manager for workorders because LS can't manage Labor units associated with a labor item, then you need a 3rd party solution.. Offer the needed tools or get out of the way and let us have access to it!
@Adrian Samuel@jamesratcliffe what do we need to do to convince the dev team that this is important. You have apps like booxi that say they are "fully integrated" but lack this simple feature.
matbar20
Member Posts: 5
48 comments
Lightspeed HQ
I was taking a look at the docs for Sale, and it doesn't look like there is a way to add a SaleLine to a Sale either?
You can add a SaleLine to a Sale with the Sale.SaleLine endpoint:
http://developers.lightspeedhq.com/retail/endpoints/Sale-SaleLine/
You can also update the Sale with the SaleLine(s) nested in the payload.
Lightspeed HQ
In the access scopes page there is a scope for employee:workbench that describes an ability to "View, create, update, and archive work orders." I found this misleading, but maybe this refers to something else?
Lightspeed HQ
If there are enough requests for a specific feature, the Product team may re-consider and re-prioritize to make room for that feature on the roadmap.
Lightspeed HQ
Hi guys, any news on this feature? It almost been a year since the last update.
We too would need those end-points for one of our projects. Any estimate on when we could expect to see those coming out?
Adrian Samuel
Software Developer
Lightspeed HQ
To your knowledge, is there another way to import workorders in bulk (ex. csv file, xml, etc.)? Or is the only way to create workorders is through the user interface?
It is not possible to import workorders. You will have to create them using the UI.
@Alex Lugo
Thanks for the information on work order creation via API. I see that Booxi is able to create WOs via their integration:
http://help.booxi.com/english/integration-setup/how-to-integrate-lightspeed-retail-with-booxi
Can you share more on how that is done?
I did the Booxi demo and the workorders are not created within booxi but actually through opening Lightspeed not through the API.
The 2 options then are creating a sale or a work order. The only advantage I see is that the client name is on a pick list and if you are creating a sale the noninventory item that is associated with the appointment is populated into the sale.
This still shows that the customer and noninventory item were added somehow through the API.
Can you point me to how one can open a lightspeed session with those parameters?
Please consider this as another upvote for the request to add Workorder Put/Post to the API.
We need the ability to create Workorders, and not having that in the API is going to create a lot of workarounds and manual data entry for our company.
thanks,
Pat
Please consider this as another formal request to get Workorder Put/Post available in the API.
Workorders are a key component for our business and not having that in the API is making our users to create data manually in multiple systems.
Thanks,
Raf
Are there any updates on this request? Is it on a road map anywhere?
Since the loss of GSX in OnSite and the changes to work orders in Retail, this is becoming a critical need for us to be able to consider moving to Retail.
Given that the drop dead date for OnSite is a little less than a year away, this could be a significant pain point that may prevent us moving to Retail. We can understand that it is a small subset of users that needed GSX integration and OnSite like Work orders, and that Lightspeed may not be able to support this directly in new products. I would expect that extensions like this to the API would benefit a rather large number of users and allow users like us to implement custom integrations to keep our businesses running smoothly.
Thanks
it will be amazing GSX integration!
Creating work orders is definitely important.
Another upvote for this!
Please consider this as another upvote for the request to add Workorder Put/Post to the API.
Seeing that in a few months will make the 3rd anniversary of the original post, I certainly wouldn't put too much faith in this actually being delivered. Although having a comprehensive API that mirror functionality available in the web client would seem logical enough...
Not being able to connect an external service booking system directly to work orders is such a severe oversight of LSR. If they don't allow API access then they should provide equivalent functionality within their UI to do this, but they don't. I don't know how other service based businesses are getting around this, but it's an extremely frustrating part of using LSR.
Not being able to connect an external service booking system directly to work orders is such a severe oversight of LSR. If they don't allow API access then they should provide equivalent functionality within their UI to do this, but they don't. I don't know how
Upvote for this discussion. Really looking forward to the availability to create work orders through the API! Please develop...
Creating workorders through the web interface is tedious. Would really love an api endpoint for creating a new workorder. With appointments becoming the covid norm, it's essential to allow us to create integrations with third party appointment booking systems to generate new workorders associated with appointments. Under the current setup, we are copy ans pasting customer appointment registration from one browser tab to another. It's not a sustainable workflow. Thanks!
When is this going to get fixed?? Whether it be workorders, layaways or special orders, lets get going!!! It's ridiculous, you can find tonnes of threads where people are asking for this! If LS did it correctly the right way no one would need the API to do these things but when you need to build a manager for workorders because LS can't manage Labor units associated with a labor item, then you need a 3rd party solution.. Offer the needed tools or get out of the way and let us have access to it!
Let's go already!!!
@Adrian Samuel @jamesratcliffe what do we need to do to convince the dev team that this is important. You have apps like booxi that say they are "fully integrated" but lack this simple feature.
Hi,
As the request has already been filed, we will remind the Product team that there is significant demand for this feature.
Would really love this ability. This would be so helpful.
@Ali_Masoumie Is there any status update yet?
Also very interested