Change Store Status
Stores
Change Store Status
This endpoint controls the operational status of a store across delivery service partners. You can open or close the store on all platforms simultaneously, or manage individual platforms (UberEats, DoorDash, GrubHub) separately. This is essential for managing store hours, temporary closures, and platform-specific operations.
PUT
Change Store Status
This endpoint provides granular control over store availability across delivery platforms. You can manage store status globally or per platform, with optional scheduling for automatic status changes.Documentation Index
Fetch the complete documentation index at: https://developer.lulacommerce.com/llms.txt
Use this file to discover all available pages before exploring further.
Path Parameters
The unique identifier of the store to update status for
Request Body Fields
Request Body Fields
Delivery Service Provider to control. Options:
"All"- Controls all platforms simultaneously"UberEats"- Controls only UberEats"DoorDash"- Controls only DoorDash"GrubHub"- Controls only GrubHub
Store operational status:
true- Opens the store (ONLINE)false- Closes the store (OFFLINE)
When the status change should automatically revert. ISO 8601 format with timezone.Example: “2024-11-15T23:59:00-07:00”
If omitted, the status change is permanent until manually changed
When the status change should take effect (for scheduled changes).Example: “2024-11-15T00:00:00-05:00”
Common Operations
Open All Platforms
Opens the store on all delivery platforms simultaneously.Close All Platforms
Closes the store on all delivery platforms simultaneously.Platform-Specific Control
Open UberEats Only
Close DoorDash Only
Pause GrubHub
Scheduled Operations
Schedule Store Pause
Response Types
Successful Status Change
Indicates whether the status change was successful
Detailed status information after the change (included for “All” operations)
Simple Success Response
For single platform operations or basic operations:Detailed Response Example
For “All” platform operations with full status:Best Practices
Status Management Recommendations
Status Management Recommendations
Use “All” for consistent customer experience across platforms
Use individual platform controls when specific integrations have issues
This allows you to maintain operations on working platforms
Use end_time for temporary closures (breaks, maintenance, etc.)
For immediate closures, use “All” with is_active: false
This immediately stops new orders across all platforms
Real-time Effect: Status changes take effect immediately on all specified platforms. Existing orders in progress are not affected.
Platform Dependencies: Some platforms may have additional requirements or delays in reflecting status changes. The response indicates the success of the API call, not necessarily the immediate platform reflection.

