Change articles in batch: one approval for up to 25 articles

Thirty article descriptions are out of date. On a handful of articles the unit is no longer right, on others a care note is missing. Deciding what to change is quick. Organizing it used to be anything but: every single article had its own preview and its own approval. With thirty articles, that means thirty previews, thirty clicks and thirty moments that pull you away from your actual work. (The numbers are an example.)

Problem

People rarely change master data one record at a time. You tidy up a product group, standardize descriptions or apply a change to several articles as one connected piece of work. Until now, the approval flow only handled single cases: one preview, one approval, one execution per article, no matter how closely related the task was.

Solution

With wals.pro AI 4 weclapp, you bundle up to 25 articles into a single preview. You see all proposed changes at a glance, give one approval, and one execution writes all the records. 25 preview-and-approval pairs become one. There is no new tool and no new interface: the existing preview-and-approval flow now carries several articles at once.

• You ask for the change. For example: “Revise the descriptions of the articles in the Accessories product group following this pattern.” The AI assistant assembles the changes for up to 25 articles.
• You review the preview. For each article you see what changes, with the current value next to it.
• You approve once. The approval applies to exactly these changes. If even a single change is swapped, added or edited afterwards, the execution refuses it.

Fewer clicks, same control

Fewer approvals do not mean less checking. Every article in the batch still goes through its own checks: its own version check, its own permission check, its own audit log entry. The approval bundles the click, not the diligence.

If anything has changed on one of the articles between your preview and the execution, for example because someone else edited it in the meantime, wals.pro AI writes nothing at all, not even the first article, and reports the discrepancy. Better to preview again than to overwrite an article that is out of date.

Result

You get back the way of working you had anyway: connected master data maintenance in one go. One preview for the whole series, one approval, one execution. Control stays complete: checked per article, logged per article.

What it is not

• The batch changes existing articles; it does not create new ones. The article number cannot be changed in a batch.
• It covers the usual article fields. Fields such as price lists, tags or manufacturer are still edited per article in their own preview.
• The upper limit is 25 articles per approval. Depending on your plan, it may be lower.
• There is no rollback. If the execution is interrupted partway through, articles that have already been written stay written. The result tells you for each article whether it was written.

How bulk changes work step by step is described in the help article Change several records in one step. You can find out what else wals.pro AI 4 weclapp can do on the product page. Connect wals.pro AI to your weclapp at ai.wals.pro or book an appointment at wals.pro/termin.