Sending content to your shop
This is the only step that changes what your customers see. Everything before it happens in a private copy — nothing reaches your Shopware store until you press the button on this page.
Sending replaces the text that is in your shop today, and it cannot be undone from here. The old text only survives in your own shop’s version history, if it keeps one. Always use Review on a row first — see Review & approval.
Who can send content
Two conditions have to be met at the same time:
- You are an Owner, Manager or Editor of the shop — Auditors never qualify.
- Your membership carries the May push content to the shop permission.
If either is missing, the buttons described below simply do not appear for you. Ask an Owner or Manager to grant the permission on Settings › Members — you cannot grant it to yourself. Details in Team & roles.
Sending, step by step
- In the shop sidebar, open All jobs and press View on the finished run.
- Tick the items you are happy with. Only rows with the status Completed that have not been sent yet offer a checkbox.
- Press Send to my shop… in the toolbar above the table. The button shows how many items you ticked.
- You land on a confirmation page. Read it (see below) and press Yes, send to my shop.
The three dots in Send to my shop… are a promise: that button never writes anything, it only takes you to the confirmation page.
The confirmation page
Its heading counts your selection: “Send N items to your shop?”, followed by “This writes the generated content into ‘your shop’ straight away.”
What will change in your shop
The first card lists, in plain words, everything that is about to happen:
- Which fields are overwritten — “The text currently in the product description is replaced”, or the name of the custom field you configured. Picture jobs do not overwrite a field, so this line is absent for them.
- The no-undo warning — “This cannot be undone from here — the old text is only still available in your shop’s own history, if it keeps one.”
- What it costs — “It costs N credits (M per item). Your shop can spend X right now.” You always see the total before you commit. See Credits.
- Approval — if your shop requires approval before publishing, the line “Items that have not been approved yet are skipped.” is added.
The “Gets written into” column
Below the card, every selected item is listed with Product, Language, Module and Gets written into. That last column is the one to read carefully — it names the exact destination:
| What it says | What happens |
|---|---|
| The product description | The generated text replaces the description of that product, in that language. |
| The custom field “…” | The text goes into the named custom field instead. Your existing description stays untouched. |
| The picture library of your shop | The generated pictures are uploaded to your media library and attached where they belong. |
| N accepted suggestion(s) | A FAQ suggestions item creates one help-center entry per suggestion you accepted, on the category or the product listed underneath. Suggestions you rejected or have not decided on are not sent. |
| Not sent | A FAQ suggestions item that still needs something from you: a suggestion nobody has decided on yet, or nothing accepted at all. It is listed so you can see it, but it is not sent and costs nothing. |
Where a text ends up is decided when the job is created — in the shop Configuration or in the template you picked, under Write result to. Changing that setting afterwards does not move an existing job’s destination.
What happens to accepted FAQ suggestions
How the suggestions come about, and how you review them, is on FAQ suggestions. This section is only about what the push does inside your shop.
A new entry is created as active, inherited by everything below its category, and with the display options (“show on category pages” / “show on product pages”) the run was configured with. Its order inside your help center is simply the order you reviewed the suggestions in — the first suggestion of an item becomes position 1, the second position 2, and so on. If you want them somewhere else in the list, reorder them in your shop’s FAQ Manager afterwards; we never renumber entries you already had.
A suggestion marked as an improvement does not create anything: it rewrites the question and the answer of the existing entry it names, in the run’s language, and leaves everything else about that entry (its assignments, its order, its badge) alone. If you deleted that entry in your shop in the meantime, the item fails with “The FAQ entry this suggestion improves no longer exists in your shop” — open the run, press The old entry is gone — send as a new entry on that card and send again. Entries that were already written stay as they are; sending again never creates a second copy of them.
If there are not enough credits
The page shows a red card, Not enough credits to send this, naming what the batch costs and what you can spend. The confirm button is not rendered at all — only Cancel. Go back and select fewer items, or ask whoever runs the platform for a top-up.
The whole batch is priced as one. Nothing is sent halfway: a partly published selection would leave you with a mix of old and new text and no way to tell which is which.
Watching it happen
After you confirm you return to the job page, which refreshes itself while the work is running. The Push column of each row shows one of five states:
| Badge | Meaning |
|---|---|
| Not pushed | Still only here. Nothing in your shop has changed. |
| Push queued | Accepted and waiting its turn. |
| Sending to your shop | Being written right now. The row offers no checkbox while this lasts, so it cannot be sent twice. |
| Pushed | Done. The date, the time and who sent it are shown underneath. |
| Push failed | Something went wrong. Your shop was not changed — see below. |
No email is sent when content is published. The job page is the record.
Every item is charged only once
The push credit is charged the moment an item is successfully written, and an item that already says Pushed can never be sent again: the checkbox disappears and the system treats a repeat as a no-op. Duplicate attempts — a double click, a reloaded page, a retry after a network hiccup — never cost you twice.
If you press Send to my shop… while some of the selection is still on its way, you are told “N item(s) are already being sent to your shop and were not queued again.” — the rest goes through normally.
Regenerating an item resets it to Not reviewed and Not pushed, because the old result no longer describes what would be published. That new version is a new publication and costs the push credit again. See the item costs in Credits.
What exactly happens to a text
The text is written into the product or category you generated it for, in the language of that item, and nothing else on that record is touched. If a colleague is editing the same product in the Shopware admin at that moment, only the one field involved is affected.
Custom fields that are not translatable
A custom field in Shopware can be marked as not translatable — it then holds a single value for the whole shop. If you publish into such a field, only the text in your shop’s main language is written; the other languages are quietly skipped. Otherwise every language would overwrite the previous one and the last one to arrive would win at random.
The app tells you this while you configure the target: “This field is not translatable — a value generated for one language would be overwritten by the others, so only the shop’s default-language text is written.” If you need one text per language, use the product description or a translatable custom field.
What exactly happens to pictures
- Every picture you ticked in the Review window is uploaded into your shop’s media library — into the target folder if the task has one configured, otherwise into your shop’s default location.
- Product pictures are then attached to the product. The first one becomes the cover only if the product has no cover yet — a cover you chose yourself is never displaced.
- Category pictures become the category’s cover image, because a category has exactly one. Images an earlier attempt at the same item had already uploaded are tidied up afterwards.
- Alt texts are not attached to a product at all. They are written onto the picture itself in your media library, per language, so every place that picture is used benefits.
Pictures already carried into your shop are remembered, so a retry never uploads the same file twice.
When a push fails
A failed item shows Push failed plus a sentence in plain language telling you what to do — for example that your shop cannot be reached, that it refused the access data, that it is answering too slowly, or that the custom field you selected no longer exists. Under it there is a Technical details disclosure with the raw message, which is what support will ask for.
Nothing was half-written: a failed push leaves your shop as it was.
- Read the sentence and fix the cause. Connection problems are fixed on Settings › Connection — try Test connection there. Missing fields are fixed in the template.
- Back on the job page, tick the failed rows again. Failed items are always selectable.
- Press Send to my shop… and confirm.
A failed push is not charged, so retrying costs you the push credit once, not twice. If you send too often in a short time you get “Too many push attempts. Please wait a minute and try again.” — that is a rate limit, not an error.
The first time you publish into a shop, do it with a single product. Look at it in your Shopware admin and in the storefront, then send the rest. That costs one credit and saves an afternoon of undoing.
Common failure messages and what to do about them are collected in the FAQ.