The AI queue is where AI proposals wait for a human decision. When an AI assistant proposes a change through MCP, nothing changes in Elovate or your webshop yet. The proposal is stored in the AI queue until an administrator approves or declines it.
What a proposal contains
The item: a product, category, attribute, page, block or blog post.
The store view: the default value (all store views) or one specific store view.
Current and proposed value side by side, always complete, never shortened.
A reason the reviewer can judge, for example “meta description was missing” or “description mentioned the wrong material”.
A proposal replaces the whole field. If something below the text should stay, such as an FAQ or a table, it must be part of the proposed value. Check this when you review.
Reviewing a proposal
Open the AI queue in Elovate.
Compare the current and proposed value and read the reason.
Approve to apply the change in Elovate and send it to the webshop. The sync log shows “AI proposal” as the origin.
Decline if the change is not right. Add a reason, so the assistant can make a better proposal next time.
Approving is only possible in Elovate, never through MCP.
Statuses
Status | Meaning |
Pending | Waiting for an administrator. The author can still update or withdraw it. |
Approved | Applied in Elovate and sent to the webshop. |
Declined | Rejected, with the reviewer's reason. |
Outdated | The item changed after the proposal was made. The proposal does not overwrite the newer content; it can be updated to compare with the current value, or withdrawn. |
Reverted | Was approved, but an administrator put the old values back. |
Withdrawn | Taken back by its author. |
Failed | Applying the change failed. An administrator can retry. |
New pages, blocks and blog posts
The assistant can also propose a new page, block or blog post. It is only created after approval, and it is created inactive by default, so you can check it in the webshop before making it visible. If the webshop refuses the new item, the administrator sees that in the AI queue and the content is not lost.
Good to know
There can be only one open proposal per field. A second one is refused until the first is approved, declined, updated or withdrawn.
SKU, price, stock, status, visibility and IDs can never be proposed.
A URL key can only be proposed for a store view that does not have its own URL key yet.