Skip to main content
PUT
https://api-staging.luladelivery.store
/
stores
/
{store_id}
Update Store
curl --request PUT \
  --url https://api-staging.luladelivery.store/stores/{store_id}
{
  "success": true
}
This endpoint allows you to update various aspects of a store’s configuration including name, contact details, point of contact, and addresses. Address updates support both modifying existing addresses and adding new ones.

​
Path Parameters

​
store_id
string
required
The unique identifier of the store to update

​
Query Parameters

​
company_id
string
required
The company ID that owns this store for authorization purposes
​
name
string
Updated store name. Example: “bulk ingest test #1”
​
email
string
Updated store contact email address. Example: “[email protected]”
​
phone_number
string
Updated store contact phone number. Example: “+12679397993”
​
point_of_contact
number
Updated point of contact user ID. Example: 1000418
​
addresses
array
Updated address information. Can include existing addresses (with IDs) and new addresses (without IDs)

​
Request Example

{
    "name": "bulk ingest test #1",
    "email": "[email protected]",
    "phone_number": "+12679397993",
    "point_of_contact": 1000418,
    "addresses": [
        {
            "id": "b6197e9c-8e68-47fe-8dd7-e057d07197ea",
            "line_1": "102 W. Mission Ave.",
            "city": "Escondido",
            "state": "CA",
            "zip": "92025",
            "address_type": 0
        },
        {
            "id": null,
            "line_1": "102 W. Mission Ave.",
            "city": "Escondido",
            "state": "CA",
            "zip": "92025",
            "address_type": 1
        }
    ]
}

​
Response

​
success
boolean
Indicates whether the update operation was successful

​
Response Example

{
    "success": true
}

​
Address Update Behavior

​
Existing Address
behavior
When id is provided: Updates the existing address with new information
Only the provided fields will be updated
​
New Address
behavior
When id is null: Creates a new address record and associates it with the store
New addresses will be assigned unique IDs automatically
​
Address Removal
behavior
To remove an address: Don’t include it in the addresses array
Removing the primary store address may affect operations

​
Update Impact

​
Store Information
updated
Basic store details like name, email, and phone number
​
Contact Assignment
updated
Point of contact can be reassigned to different users
​
Address Records
updated
Existing addresses are modified, new addresses are created
​
Partner Integrations
preserved
Delivery service partner configurations remain unchanged
​
Store Status
preserved
Store operational status and settings are maintained

​
Best Practices

​
Partial Updates
best-practice
Only include fields you want to change
Omitted fields will retain their current values
​
Address Management
best-practice
Always include existing address IDs when updating addresses
Forgetting to include an address ID may create duplicates
​
Contact Validation
best-practice
Verify that the new point_of_contact user exists and has appropriate permissions
Invalid user IDs will result in update failure
​
Business Hours
best-practice
Perform updates during low-activity periods to minimize operational impact
Store updates don’t affect ongoing orders

​
Error Scenarios

​
Store Not Found
error
The specified store_id doesn’t existStatus Code: 404
​
Company Mismatch
error
The store doesn’t belong to the specified company_idStatus Code: 403
​
Invalid Contact
error
The point_of_contact user ID doesn’t existStatus Code: 400
​
Address Validation
error
Address information is incomplete or invalidStatus Code: 400
Operational Continuity: Store updates are designed to maintain operational continuity. Existing orders, inventory, and partner integrations continue functioning normally during and after updates.
Audit Trail: All store updates are logged for compliance and troubleshooting purposes. Update timestamps and user information are automatically recorded.