Shopware 6 API：更新已有商品时不传入库存或价格信息报错，求解决方案

I totally get your frustration here—Shopware 6's upsert behavior is a noticeable shift from Shopware 5, especially when you're trying to decouple product core data updates from inventory management handled by an external ERP. Let's break down the best solutions to avoid that annoying 400 error without having to fetch and re-send the existing stock value every time:

1. Use Partial Updates (PATCH Request) Instead of Upsert #

Shopware 6 fully supports partial updates via PATCH requests for individual entities, which is exactly what you need here. Unlike the upsert (PUT) endpoint that enforces all required fields (even for existing products), a PATCH request only updates the fields you explicitly send, leaving all other fields (including stock) untouched.

Example PATCH Request #

• Endpoint: PATCH /api/product/206c59a3339383101655aae7598e328c (replace with your product ID)
• Payload: Only include the fields you want to update—no need for stock, productNumber, or other fields you don't want to modify:

{
  "language": "default",
  "taxId": "6460303d84264f36858d1fe9e8c2f60f",
  "name": "SLT 95 Nano Crystal",
  "active": true,
  "visibilities": [
    {
      "id": "d43840cff1b2bcc741a9a83ebb5b3c16",
      "salesChannelId": "e8d8fd2337dd42e0a86b47ea68739824",
      "visibility": 30
    }
  ],
  "categories": [
    {
      "id": "66ca2d80dc532d4d6659b4430e6954a8"
    }
  ],
  "description": "A not so much very short text. Another short text.",
  "price": [
    {
      "net": 9999.99,
      "gross": 9999.99,
      "linked": true,
      "currencyId": "b7d2554b0ce847cd82f3ac9bd1c0dfca"
    }
  ],
  "crossSellings": [
    {
      "id": "b3e3171397d30794171877fed2329d96",
      "name": "Similar Products",
      "assignedProducts": [],
      "type": "productList",
      "active": true,
      "sortBy": "name",
      "sortDirection": "ASC",
      "limit": 24,
      "position": 1
    }
  ]
}

This will update only the specified fields and keep your existing stock value intact, no validation errors included.

2. Decouple Inventory Management from Product Updates #

Shopware 6 is built with modularity in mind, so it's best practice to handle inventory updates separately from product core data changes. Instead of updating stock via the product entity, use the dedicated inventory endpoints:

• Update stock for a product: POST /api/product/{productId}/stock
• Manage stock entries directly via the product_stock entity API

This aligns perfectly with your ERP workflow—your ERP can handle inventory updates independently, while your product update process only touches core fields like name, price, or categories. No more conflicts or mandatory field issues.

3. Modify Validation Rules (Advanced, Use with Caution) #

If you absolutely need to use upsert (e.g., for bulk updates), you can customize the validation constraints for the stock field via a custom plugin. The idea is to remove the "required" validation when updating an existing product (i.e., when the product ID exists).

Here's a quick outline of how to do this:

• Create a custom plugin that subscribes to the EntityDefinitionValidationEvent
• In the event listener, check if the entity is a ProductDefinition and if the operation is an update (check for existing ID)
• Remove the NotBlank constraint for the stock field in update scenarios

Note: This approach requires plugin development and can affect other parts of Shopware (like product creation), so test thoroughly before deploying to production.

Why Your Temporary Workaround Isn't Ideal #

Fetching the current stock value and re-sending it does work, but it introduces a race condition: if another system (like your ERP) updates the stock between your fetch and upsert requests, you'll overwrite the latest value with stale data. The PATCH or decoupled inventory approach avoids this entirely.

内容的提问来源于stack exchange，提问作者Rämbozämb