Changelog

We've just released a couple of enhancements to Custom Fields.

We are now providing a simple API for both reading and writing serial numbers.

With the introduction of two new Workflow events, you can new register rules to be triggered when a sale is created and when it is updated.

This update contains new functionality for updating a third party billing subscription as well as a tutorial for its basic use. This functionality is currently in BETA and we'd love for you to try it out, so that anything you build with Lightspeed Retail (X-Series) is as easy to buy as possible. This new functionality will allow you to manage subscriptions for Apps you build using our Core APIs, or extensions you build using Workflows. If you'd like to use this new API, please contact [email protected] and we can help get you onboard.

This update contains specifications for third party billing APIs as well as a tutorial for their basic use. These are new APIs currently in BETA and we'd love for you to try them out so you that anything you build with Lightspeed Retail (X-Series) is as easy to buy as possible. These APIs will allow you to manage subscriptions for Apps you build using our Core APIs, or extensions you build using Workflows. If you'd use these APIs, please contact [email protected] and we can help get you onboard

With this update, you can now mark custom fields as editable in the UI. We are slowly working towards making custom fields editable in our UI. If you want your custom field to be editable in the UI, simply set editable_in_ui to true when creating it.

In Lightspeed Retail (X-Series), you are now able to add multiple barcodes that can be scanned alongside the SKU (Stock Keeping Unit). These can be captured on Standard and Variant products, and used for scanning/selling and inventory management without sacrificing the ability to identify products internally using a SKU.

With this update, you can now mark custom fields as visible in the UI. We are slowly working towards showing custom fields in our UI. If you want your custom field to be visible in the UI, simply set visible_in_ui to true when creating it.

This update provides a new 2.0 Webhooks API for managing webhooks. The primary difference between this API and its v0.9 counterpart, is that this API accepts JSON, instead of encoded form data.

Note: Currently we recommend that you continue to use the v2.0 API for production.