Doozly
Nearly every guide to building an Amazon affiliate store opens the same way: install WooCommerce. Before you do, two things are worth knowing. WooCommerce is a shop — cart, checkout, orders, tax rules — and an affiliate store never takes a payment. And the price you are about to type into each product is something Amazon’s own policies do not allow you to type in.
Two different things share the name
Worth separating before anything else, because the advice for each is unrelated.
An Amazon Storefront is Amazon’s own page, at amazon.com/shop/yourname. Amazon hosts it, you curate it, and it belongs to the Influencer Programme rather than to plain Associates. You do not build it and you cannot rank it — it is a page on Amazon’s domain, and Amazon decides what it looks like.
An Amazon affiliate store is your own website, presenting a set of Amazon products with your links attached. You own it, it is the thing that can rank in Google, and it is what the rest of this page is about.
The confusion matters commercially: a storefront lives on Amazon’s traffic, a site of your own lives on search traffic you built. They are not competing options so much as different businesses.
The WooCommerce question
The standard recipe is WooCommerce with the External/Affiliate product type, which replaces the Add to cart button with a link out. It works. The question is what else comes with it.
Installing WooCommerce adds a cart, a checkout, customer accounts, order and session tables, tax and shipping settings, payment gateway plumbing, a REST API and its own set of pages — to a site whose entire job is to send people somewhere else to pay. None of that machinery ever runs, but it is all installed, all updated, and all attack surface.
That is not an argument that WooCommerce is bad. It is an argument about fit, and there are cases where it fits:
- You also sell something of your own. A course, a template, a physical product. Then you already need a shop and the affiliate items ride along.
- You genuinely need catalogue features. Filtering by attribute across hundreds of products, faceted search, sorting by price. If your site is a catalogue rather than a set of articles, a catalogue engine earns its place.
- You already know it. Familiarity is a real cost saving and worth more than architectural tidiness.
What does not justify it is the thing most people install it for: showing a product with a picture, a price and a button. That is a paragraph and a link.
| WooCommerce build | Posts and a shortcode | |
|---|---|---|
| What gets installed | A shop engine, its database tables and its own pages | Nothing beyond the product box |
| What you maintain | Shop updates, gateway plumbing, an extra REST surface | The posts themselves |
| Where a product lives | Its own product page | Inside the article that recommends it |
| What a search engine finds there | A title, an image, a price | The reasoning that led to the product |
| Moving to another theme | Product templates to rebuild | Posts move as posts |
| Worth it when | You also sell your own goods, or need catalogue filtering | You are recommending things |
The price you type in is a compliance problem
This is the part that no build-a-store tutorial mentions, and it is not a technicality. From the Associates Programme Policies:
Because prices for and availability of Products that you have listed on your Site may change, your Site may only show prices and availability if: (a) we serve the link in which that price and availability data are displayed, or (b) you obtain Product pricing and availability data via Creators API or PA API…
Read that against the standard tutorial, which has you copy a price off the product page and paste it into a WooCommerce field. A hand-typed price is neither of the two permitted sources. It is also wrong within days — Amazon prices move constantly — and a store of three hundred products maintained this way is a store of three hundred stale prices.
There is a second clause, and it catches even people who do use the API:
You will include a date/time stamp adjacent to your display of pricing or availability information on your application if you obtain Product Advertising Content from Data Feeds, or if you call Creators API, PA API or refresh the Product Advertising Content displayed on your application less frequently than hourly.
So the honest options are three: show no price at all, show one that Amazon itself serves, or pull it from the API and stamp it with the time you fetched it. Refreshing nightly is perfectly legitimate — it just obliges you to say when.
It is worth being straight about how this plays out, because the gap between the rule and the practice is wide. Practically every affiliate plugin on the market has a plain text field for the price, ours included, and a great many sites use it. Amazon is not known for pursuing publishers over a hand-typed figure. The rule is still the rule, and it is your account rather than the plugin’s that carries the risk — but the more reliable reason to avoid a typed price is the unglamorous one: it is wrong within days, and a wrong price is the fastest way to lose a reader who checks.
The awkward part. Amazon will not issue you a Creators API credential until your account has recent qualifying sales. So the compliant way to show prices is closed to exactly the people starting a store, and the way that is open to them is the non-compliant one.
The way out is not clever: launch without prices. A product card with a title, an image, a rating and a button converts perfectly well, breaks no rule, and never goes stale. Add prices once you have the credential. The sales requirement and what the Creators API is.
What a store actually needs
Strip the question back to jobs and the shopping list is short:
| The job | What does it |
|---|---|
| Organising products into sections | Your theme’s categories and menus. WordPress has done this since 2003. |
| Presenting one product | A product box: image, title, rating, button. |
| Keeping prices legitimate | Amazon’s API, with a timestamp — or no price at all. |
| Getting paid for the click | Your tag, and a different one for every country your readers are in. |
| Staying inside the rules | Disclosure above the first link, rel="sponsored" on it. |
| Taking money | Nothing. You never take any. |
Only the last row is what WooCommerce is for, and it is the one row an affiliate store crosses out.
The lighter way to build it
Ordinary posts and pages, organised with ordinary categories, with a shortcode wherever a product belongs. That is the whole architecture, and it is faster to build, faster to load and far easier to move to another theme later.
It is also better for search, for an unglamorous reason: a WooCommerce catalogue page is a grid of products with almost no text, and a page with almost no text does not rank. The affiliate stores that earn are article-shaped — a comparison, a guide, a recommendation — with products embedded where the reader has just been persuaded. The store is the sum of the articles, not a catalogue with articles bolted on.
What this plugin contributes to that: As an Amazon Associate we earn from qualifying purchases. renders the product box, holds a separate Associates tag for each of the twenty-two marketplaces, and fills the title, image, price and rating from Amazon once you connect a credential. The documentation covers every attribute; the piece on the button covers the link itself.
What it does not do, since that matters too: no cart, no faceted search, no filtering by attribute across a catalogue. If you need those, you needed a shop after all.
How to arrange it so it ranks
“Article-shaped” is easy to agree with and harder to build, so here is the shape concretely. The unit is not the product. The unit is a decision somebody arrives with.
Nobody searches for a product they have already chosen and then reads a review of it. They search sideways: best coffee grinder for small kitchens, quiet air purifier under $150, does this fit a 2019 model. Each of those is a page. The product appears inside it, at the point where the reader has been persuaded, and the same product can appear in four such pages without a word of it being duplicated.
Which leaves three kinds of page and no others:
- Guides — one per decision. These are what rank, and where every product box lives.
- Category hubs — a short piece of orientation and the links down to the guides. Written for a reader who is browsing, not for a search engine.
- One store page, if you want one at all — navigation, not a landing page. Do not expect it to rank and do not spend a week on it.
The counting question answers itself once the shape is right. Twenty guides that each settle a real decision are a store. Three hundred product pages are a database with a theme on it, and the reason those sites disappeared from search was never a penalty — it is that there was nothing on the page worth showing anybody.
It is also the shape that survives Amazon’s own review. Applications are rejected for thin content more often than for anything else, and a grid of imported titles is the definition of it.
Common questions
How should the pages be organised?
Around decisions rather than products. One guide per question a reader actually arrives with — best for a small kitchen, quiet models under $150, what fits a given model — with the product boxes inside those guides. Category hubs link down to the guides; a store page, if you have one, is navigation rather than something you expect to rank.
What is an Amazon affiliate store?
A website of your own that presents Amazon products with your affiliate links attached. You hold no stock and take no payment — the reader clicks through and buys on Amazon, and you earn a commission. It is not the same as an Amazon Storefront, which is a curated page hosted on Amazon under the Influencer Programme.
Do I need WooCommerce for an Amazon affiliate store?
No. WooCommerce is a shop engine — cart, checkout, orders, tax — and an affiliate store never takes a payment, so none of it runs. It makes sense if you also sell something of your own, or if you genuinely need catalogue filtering across hundreds of products. For showing products inside articles, posts, categories and a shortcode do the job.
Can I type Amazon prices into my site by hand?
No. Amazon’s Programme Policies allow a price to be shown only if Amazon serves the link containing it, or if you obtain the price through the Creators API or PA API. A price you copied and pasted is neither, and it is stale within days in any case.
When do I need a timestamp next to the price?
Whenever your price data is refreshed less frequently than hourly, or comes from a Data Feed. Amazon’s own example of an acceptable format is “Amazon.com Price: $32.77 (as of 01/07/2008 14:11 PST- Details)”. A nightly refresh is fine; it just has to say when it happened.
How many products does an affiliate store need?
Fewer than you think. A hundred thin product pages rank for nothing; twenty articles that genuinely help someone choose will outperform them. Amazon also expects a site to have real content, and thin catalogues are a common reason applications are rejected.
Can I build one before I am approved by Amazon?
Yes, and you have to: Amazon only reviews your application after three qualifying sales, so the site must exist and be publishing first. You get a working tag immediately at sign-up. Build without prices until you have the API credential.
Will my store earn from readers in other countries?
Only if you hold a tag for the store they land on. A tag belongs to one national programme, and a purchase on another Amazon store earns nothing rather than less. Most affiliate stores lose a substantial share of their audience this way without ever seeing it in a report.
The summary worth keeping: an affiliate store is a content site with products in it, not a shop with the payment removed. Skip the checkout you will never use, keep the prices legitimate or leave them out, and put a tag against every country your readers actually come from. Checked against Amazon’s published policies on August 20, 2026.
