The Bulk Sync API allows you to update inventory and pricing for multiple products across multiple locations in a single request. This is ideal for syncing data from external systems like ERPs, POS systems, or inventory management tools.
Endpoint
POST
/mulopimfwc/v1/inventory/bulk-sync
Headers
| Key | Value |
|---|---|
| Content-Type | application/json |
| X-API-Key | your-api-key-here |
🔐 The
X-API-Keyis required for authentication. Requests without a valid API key will be rejected. Please set up the API first by following the documentation.
Request Body
The request body must contain an items array. Each item represents a product-location inventory update.
Supported Identifiers
You can identify products and locations using either:
sku+location_slug- OR
product_id+location_id
Request Body Example
{
"items": [
{
"sku": "PROD-001",
"location_slug": "main-store",
"stock": 100,
"regular_price": "29.99",
"sale_price": "24.99"
},
{
"product_id": 123,
"location_id": 5,
"stock": 50,
"regular_price": "19.99"
}
]
}
Field Description
| Field | Type | Required | Description |
|---|---|---|---|
| sku | string | Optional | Product SKU (required if product_id is not provided) |
| product_id | integer | Optional | WooCommerce Product ID |
| location_slug | string | Optional | Location slug (required if location_id is not provided) |
| location_id | integer | Optional | Location ID |
| stock | integer | Yes | Stock quantity for the product at the location |
| regular_price | string | Optional | Regular product price |
| sale_price | string | Optional | Sale price (must be less than regular price) |
Response Example
{
"success": true,
"message": "Processed 2 items. 2 succeeded, 0 failed.",
"results": {
"success": 2,
"failed": 0,
"errors": []
}
}
Response Fields
| Field | Description |
|---|---|
| success | Indicates whether the API request was processed |
| message | Summary of the bulk sync operation |
| results.success | Number of items successfully updated |
| results.failed | Number of items that failed |
| results.errors | Detailed error messages for failed items (if any) |
Error Handling
- If an item fails validation (missing identifiers, invalid price, etc.), it will be counted under
failed. - Successful items are processed independently, meaning one failure does not stop the entire sync.