POST /items: modifiers_ids (item-to-modifier assignment) not persisted

[TastyWave]

Has anyone run into this? We can't get item-to-modifier assignment to stick via the API.

Steps to reproduce:

1. GET /v1.0/items/{item_id} → the modifier_ids field is an empty array.
Side note: the official docs at developer.loyverse.com name this field modifiers_ids, with an "s", in both the request and response schema — but the actual response returns modifier_ids, without the "s". Looks like a docs/implementation mismatch on its own.

2. POST /v1.0/items with a complete, valid item body (item_name, variants, etc.) and "modifiers_ids": ["<a valid modifier id on the account>"] set.

3. Response: 200 OK, updated_at is refreshed — so the request clearly reaches the API and is processed.

4. A subsequent GET on the same item still shows modifier_ids: []. The assignment is silently dropped.

Reproduced multiple times with both the documented field name (modifiers_ids) and the field name actually returned by GET (modifier_ids) — neither has any effect, and no error is returned either way.

Is assigning a modifier to an item via POST /items actually supported? If so, what are we missing? If it's a known limitation, it'd be great to get the docs corrected, since they currently suggest it should work.

Happy to share more request/response details if useful.

[Yasuaki]

Hello @TastyWave

Thank you for reporting the issue.

> 2. POST /v1.0/items with a complete, valid item body (item_name, variants, etc.) and "modifiers_ids": ["<a valid modifier id on the account>"] set.

Could you try "modifier_ids" instead of "modifiers_ids"?