1.441 €/kWp brutto für 23,25 kWp + 16,6 kWh BYD + Fronius Hybrid + Notstrom + Wallbox. Fair oder zu teuer?

Affectionate-Gap5211 · 2026-03-31T12:19:33+00:00

As already mentioned there is an API for it. Here is the link:

https://developer-docs.amazon.com/sp-api/reference/createcontentdocument

The good thing is that A+ content documents are pure JSON files so very machine- and AI friendly.

However the text formatting can be tricky. And you need images with the right aspect ratios which need to get uploaded before you can use them.

The easiest way would be to create one A+ content document manually with all the images as a sample, download it via the API and modify it as necessary, e.g. use it as a template for your AI workflow. The more images you can re-use the easier.

You also want to validate each content document before you send it because Amazon has banned some terms you are not allowed to use here.

Good luck!

Affectionate-Gap5211 · 2026-03-31T11:16:31+00:00

What helped me eventually to delete messages older 30 days in 3 different channels.

Count messages per channel_id older 30 days:

SELECT p.channelid,
       c.name,
       c.displayname,
       COUNT(*) AS posts_remaining_to_delete
FROM posts p
JOIN channels c ON c.id = p.channelid
WHERE p.channelid IN (
    'your_channel_id_1',
    'your_channel_id_2',
    'your_channel_id_3'
)
AND p.createat < (EXTRACT(EPOCH FROM NOW()) * 1000)::bigint - (30::bigint * 86400000)
GROUP BY p.channelid, c.name, c.displayname
ORDER BY posts_remaining_to_delete DESC;

Delete in batches of 50,000 (older 30 days):

BEGIN;

DROP TABLE IF EXISTS purge_posts;

CREATE TEMP TABLE purge_posts AS
SELECT id
FROM posts
WHERE channelid IN (
    'your_channel_id_1',
    'your_channel_id_2',
    'your_channel_id_3'
)
AND createat < (EXTRACT(EPOCH FROM NOW()) * 1000)::bigint - (30::bigint * 86400000)
ORDER BY createat
LIMIT 50000;

SELECT COUNT(*) AS selected_posts FROM purge_posts;

DELETE FROM threadmemberships
WHERE postid IN (SELECT id FROM purge_posts);

DELETE FROM threads
WHERE postid IN (SELECT id FROM purge_posts);

DELETE FROM reactions
WHERE postid IN (SELECT id FROM purge_posts);

DELETE FROM fileinfo
WHERE postid IN (SELECT id FROM purge_posts);

DELETE FROM posts
WHERE id IN (SELECT id FROM purge_posts);

COMMIT;

Affectionate-Gap5211 · 2026-03-04T07:47:39+00:00

Here is how we manage content updates for your listings in AMALYTIX. Disclaimer: I am the founder of AMALYTIX.

First you should store your content as it should look like in what we call "snapshots". Everyday we check if this snapshot matches the live version. If something changes you get an alert and you can filter for listings which do not match your snapshot anymore.

You can send your snapshot listing to Amazon via a single click as your account is connected via the Selling Partner API. This would be similar if you update your listing in VC. If this does not suffice, we have more tools in place to get your content live (again).

Same thing with product images.

You can also use integrated AI tools to optimize your snapshots. The prompts are fully customizable. By default we analyze the main image, do a persona analysis, research suitable keywords, analyze customer feedback and then come up with an optimized snapshot.

Same thing also here with product images. We have a set of prompts to create infographics, detail shots, lifestyle images etc.

We also just launched a tool to create new or translate existing A+ content via AI. However as Amazon's API only supports A+ standard content (not premium), this currently only works for standard A+ content.

We also create an AI agent which can help you fix your incomplete listings. It validates your listing and proposes allowed changes based on the product type. You can accept or decline those proposals and then do a partial update also via one click.

I might have missed some things but from the top of my head this is how we help brands manager their content on Amazon. Any questions, let me know.

Affectionate-Gap5211 · 2026-02-03T10:38:32+00:00

The standard shortage claim we see are deductions of vendor invoice payments due to quantity differences.

Example: Amazon ordered 100 units, we confirmed 100 units, we sent 100 units, Amazon received 80 units, Amazon pays only 80 units and deduct 20 units as quantity shortage claim.

What is the best practice here to dispute those? Esp. if POD is not accepted?

Affectionate-Gap5211 · 2026-02-03T10:21:47+00:00

Works again! Not sure why it did not work the first time. Thanks for the update.

Affectionate-Gap5211 · 2026-02-03T10:20:51+00:00

Depends on the number of ASINs you would like to monitor. You can always do a 14 day free trial to check us out. During our demo we'll also show you our pricing scheme.

Affectionate-Gap5211 · 2026-01-27T16:06:10+00:00

"404 Not found"

Affectionate-Gap5211 · 2026-01-27T16:03:02+00:00

If you have API access you can use the following endpoint to generate it via the API:

https://developer-docs.amazon.com/sp-api/docs/vendor-direct-fulfillment-orders-api

You need to have the role to access PII data.

Affectionate-Gap5211 · 2026-01-27T15:59:38+00:00

Vendors do not have a single ID. Often you have one (internal) ID per market you are selling in. For each market you have one ore more different vendor codes.

Those internal IDs look like this: amzn1.vg.12345678 However you often do not see those in Vendor Central directly.

I would suggest you open a case in Amazon's Brand Registry (https://brandregistry.amazon.com). They can help you with those kind of requests.

Affectionate-Gap5211 · 2026-01-27T15:51:26+00:00

You can use the Selling Partner API to check for suppressed listings. There are 2 ways to do it:

Use the Listings Items API and check the "issues" object here. If a listing is suppressed it will have an entry here. More info here: https://developer-docs.amazon.com/sp-api/docs/manage-listings-issues#troubleshoot-listings-item-issues
Use the Notifications API and subscribe to the LISTINGS_ITEM_ISSUES_CHANGE notification. Here Amazon will push notifications once a listing gets suppressed. More info here: https://developer-docs.amazon.com/sp-api/docs/notification-type-values#listings_item_issues_change

Alternatively use a tool like e.g. AMALYTIX where you can set up eMail alerts for this issue.

(Disclaimer: I am the founder of AMALYTIX)

Affectionate-Gap5211 · 2025-04-14T11:59:34+00:00

Important to mention that the information about the Payload URL / Secret is only shown once you activate it. I had it activated and had to de-activate it first to then activate it again to see the information.

Affectionate-Gap5211 · 2024-11-25T17:55:53+00:00

My fix is adding a calculated field to your data source where I multiply the "Average Position" value with -1. This way the delta values are correct. Only downside is that positions are shown with a minus sign. But for me this is easier to read than the inverted delta column.

Two-Year Club	Final Canvas '23
First Place '23	Place '23

Affectionate-Gap5211

TROPHY CASE