Create and manage bike service work orders in Lightspeed Retail (R-Series)
domain: developers.lightspeedhq.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with OAuth2 and locate the Workorder endpoint under the account's API root
Create a new Workorder record referencing the customer and the item(s) being serviced
Add work order line entries for labor and parts tied to the work order
Update the work order's status field as the bike moves through service stages
Retrieve a work order by ID, or list with filters, to check status or print a ticket
Close the work order once complete and confirm the associated sale record if the shop invoices through POS
Known gotchas
Work order status values and required fields are account/version-specific — confirm the current status options in the endpoint reference before writing status-change logic
Archiving a work order does not automatically remove or void its linked sale — handle both records
Pulling the full work order list on every poll burns through the rate-limit bucket; filter and paginate instead
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?