Work Order Lifecycle
Understanding how work orders move through the system is key to building effective integrations.
Status Flow
1. Creation
Work orders start with a customer and vehicle link. Use POST /v1/work-orders to
initialize a ticket.
2. Adding Services
Once created, you can add services, labor, and parts. This updates the total cost automatically.
3. Updating Status
As technicians work, update the status to keep customers informed. Status changes trigger webhook events.
Inventory Management
Keep your stock levels accurate by syncing your inventory system with BigShop.
Real-time Updates
When parts are added to a work order, stock is reserved. When the work order is completed, stock is deducted.
Low Stock Alerts
Set reorder points for items. The API returns low_stock flags you can
filter by.
Webhook Integration
Webhooks allow your system to react immediately to changes in BigShop.
Example Payload: work_order.updated
{
"event": "work_order.updated",
"occurredAt": "2024-03-20T14:30:00Z",
"data": {
"workOrderId": "wo_987xyz",
"previousStatus": "pending",
"currentStatus": "in_progress",
"technicianId": "user_456"
}
}Best Practices
- Always verify the webhook signature (if enabled) to ensure authenticity.
- Respond with a
200 OKimmediately to prevent retries. - Process heavy logic asynchronously after receiving the event.