Running an Amazon affiliate site is a conversion game played in small margins: the product box has to look trustworthy, prices have to stay current or your Amazon compliance breaks, and every outbound link needs your tracking ID attached. AAWP is the plugin that handles all three in one place — product boxes, bestseller and new-release lists, comparison tables, and geotargeted links that route each visitor to their local Amazon store. The 5.x line is the generation that matters right now: Amazon’s Creators API support landed in 5.0 just as the legacy PA-API stack started its deprecation cycle, so a current build is effectively a requirement, not an upgrade.
What follows is a practical review of the 5.1.0 build — what the plugin actually does, where it beats its direct competitors, and the configuration decisions that determine whether your lists refresh cleanly or quietly rot.
Competitive Features
- Dual API support, with a migration path. AAWP speaks both the legacy PA-API 5.0 and Amazon’s Creators API. Since 5.0, the Creators API is fully supported, and the plugin kept shipping SDK updates within days of Amazon releasing them — 5.1.0 already bundles the 1.3.0 Creators API PHP SDK.
- Click tracking that survived a security audit. Version 5.0.9 fixed an unauthenticated SQL injection in the click-tracking module the same month it appeared in the changelog. That’s a meaningful signal: the module is actively maintained, not abandoned middleware.
- Migration tooling for your competitors’ users. Built-in Lasso migration (5.0.6) and Amalinks Pro migration (4.3.3) mean switching platforms doesn’t require rebuilding every product placement by hand.
- Geotargeting without another plugin. Visitors from supported countries are routed to their local Amazon storefront automatically, with the tracking ID preserved — the feature that alone replaces a separate geo-redirection stack on most affiliate sites.
- Cache architecture tuned for API quotas. Product data is cached and renewed on schedule rather than per-visit, which is the only sane design under Amazon’s request limits. The automatic cache renewal even preserves list positions for bestseller and new-release lists, fixed in 5.1.0.
- Schema markup included. Product schema output ships in the plugin (4.2.0), so review-style pages get structured data without a separate SEO schema plugin fighting over the same markup.
Key Features
- Product boxes. The core unit of AAWP output: title, thumbnail, star rating, price line, buy button — all rendered from live API data with your disclaimer text attached. Templates are configurable, and filters exist for adjusting the price line and image cropping.
- Bestseller and new-release lists. Pull category bestsellers directly from the API and renew them automatically. The 5.1.0 fix for list positions matters here: without it, renewed lists could shuffle products out of order.
- Comparison tables. Multi-product tables with a “highlight” field for your recommended pick. The editor integration covers both Gutenberg (as a block,
apiVersion 3since 5.0.8) and the classic editor’s TinyMCE. - Filtering by ASIN and stock status.
filterby asinin lists (5.0.6) and an “out of stock” filter in the Products Overview table (5.0.3) give you control over which products render — useful when a niche’s bestseller list includes items you’ve already reviewed as poor buys. - Books-specific data. 5.0.10 added pages count and publication date as product data attributes, which book-niche affiliates previously had to hardcode manually.
- AAWP API connection tooling. A reconnect button, scheduled connection tests, and quota information surfaced in the admin — the plugin treats the API as the fragile external dependency it is.
- Uninstall data handling. Data deletion on uninstall was improved in 4.2.9, relevant if you manage client sites and need clean removals.
Comparison with Competitors
AAWP vs WPLister (for eBay sellers diversifying)
The realistic competitor set for AAWP inside this catalog is the eBay-side equivalent, because the two cover the same workflow — marketplace data into WordPress content — for different networks.
| Aspect | AAWP | WPLister Pro |
|---|---|---|
| Target marketplace | Amazon (10 storefronts incl. Ireland) | eBay |
| API generation | PA-API 5.0 + Creators API | eBay APIs |
| Product output | Boxes, lists, comparison tables | Listing templates and listings display |
| Geotargeting | Built-in | Not the core feature |
| Click tracking | Built-in with export | Present, different scope |
| Changelog cadence | Days-to-weeks after Amazon changes | Steady, smaller surface |
If your traffic is Amazon-native, the eBay listing integration is the wrong tool no matter how good it is at its own job; the reverse holds equally. Where AAWP is clearly ahead is the geo-routing and compliance-sensitive price freshness — eBay listings don’t have the same “prices must be current or you’re out of compliance” pressure.
AAWP vs FS Poster (social automation layer)
This comparison looks odd until you consider what affiliate site owners actually stack: content generation on one side, distribution on the other. AAWP generates the Amazon-facing content; the social auto-posting scheduler pushes it to networks. They are complementary rather than substitutes, and neither replaces the other.
| Aspect | AAWP | FS Poster |
|---|---|---|
| Core job | Marketplace product display | Multi-network auto-posting |
| Depends on external API | Amazon PA-API/Creators API | Social network APIs |
| Content type produced | Product boxes, lists, tables | Scheduled shares of your content |
| Overlap | Near zero | Near zero |
The verdict here is “both”: a content plugin and a distribution plugin solve different halves of the affiliate pipeline.
Recommended Stack: AAWP covers the Amazon product layer, but the underlying site still needs the same foundations as any content business — a solid email capture setup converts the traffic that Amazon’s commission model doesn’t retain. That’s the slot the email marketing automation plugin fills, keeping your audience list on your own infrastructure instead of losing it to the marketplace.
Official Changelog
The registry lists a single version line for this plugin, so the changelog below covers the current release.
Version 5.1.0
Release Date: September 3, 2026
- Updated Creators API PHP SDK to 1.3.0
- Added Minn Admin compatibility
- AAWP API scheduled test connection now runs conditionally
- Fixed availability status incorrectly set to “out_of_stock” when availability sits on a non-first offer listing
- Fixed automatic cache renewal not refreshing bestseller/new-releases list positions
- Fixed invalid products never marked “invalid” under the Creators API
- WordPress 7.1 compatibility, minimum PHP version raised to 8.1, Freemius WP SDK updated to 2.13.4
Frequently Asked Questions
Does AAWP work without an Amazon API connection?
Partially. The plugin’s own AAWP API (its hosted service) requires a valid API key since 4.4.0, and the core product-data features are built around Amazon’s PA-API 5.0 or the Creators API. Without any API connection you’re limited to static output — which defeats the purpose, since auto-updating prices and stock status are the main reasons to run the plugin at all.
What changed with the Amazon Creators API transition?
Version 5.0.0 added full Creators API support in January 2026, and subsequent releases have kept the SDK current (1.3.0 as of 5.1.0). The practical meaning: sites on the 5.x line are already aligned with Amazon’s newer API stack, while builds stuck on 4.x are running on the deprecated PA-API path.
Is the click-tracking module safe?
The known vulnerability — an unauthenticated SQL injection via click tracking — was disclosed and fixed within the 5.0.9 release in July 2026. Running anything older than 5.0.9 means running that vulnerability, which on a public-facing affiliate site is not a defensible position.
Can I migrate from Lasso or Amalinks Pro?
Yes. Lasso migration shipped in 5.0.6 and Amalinks Pro migration in 4.3.3. Both convert existing product placements rather than requiring a manual rebuild, which matters if you have hundreds of boxes across a mature site.
Which WordPress and PHP versions does it support?
The 5.1.0 build is compatible with WordPress 7.1 and requires PHP 8.1 or newer — the minimum was bumped in that same release. Older PHP stacks need to stay on older plugin branches, which also means missing the Creators API fixes.
Does the GPL version receive updates?
The GPL build distributed here is the full plugin source under its original license. What it does not include is the vendor’s license key for their update feed, so updates arrive when you pull a newer GPL release rather than automatically through your admin dashboard.
Leave a Reply