A Store structured around the decisions your shoppers are making, tagged by campaign, and tested against detail-page conversion six weeks after launch.
About this service
A Store earns its build when tagged campaign traffic converts better on it than the same campaigns pointed at a detail page. That is the single test we hold a build to: sales per visit by source tag, six weeks after launch, against a detail-page control running the same keywords and the same budget. Across our last four builds the Store won three times, by 11 to 34 percent, and lost once, on a single-title brand that had no business having a Store and was told so in week one.
Pages follow buying questions, not product lines:
A reader deciding which book in a nine-title series to start with, or a traveller choosing between cabin-size and hold luggage, is settling one question. That question gets one page, built to answer it, with the comparison visible without scrolling on a 390 px viewport. Depth stops at two levels. Past that, Store Insights shows visits arriving and nothing happening afterwards, which is what a navigation problem looks like once it reaches the data.
Source tags, and what skipping them costs:
Every campaign pointing at the Store gets its own source tag before launch, because untagged traffic collapses into one undifferentiated row and takes the six-week test down with it. Tagged off-Amazon traffic also qualifies orders for the Brand Referral Bonus, returning around 10 percent of qualifying sales as a credit against referral fees. That is a real line in the P&L, and it is forfeited by default whenever a link is pasted in without a tag.
Assets, specs and the moderation buffer:
Hero imagery at 3000 px wide. Product photography at 1600 px on the longest side so hover zoom fires. Shoppable image tiles where the range is visual rather than technical, and video under 30 seconds with the product in frame inside the first three. We write the copy and direct the shot list; your studio shoots, or we brief one. Submissions usually clear moderation inside a business day and occasionally take three, so launch dates carry that buffer rather than pretend it away.
What we refuse to build:
Brand story pages no campaign will ever point at. Autoplay video across the header. A page per SKU. A founder letter. Each one exists because a template offered a slot, and each adds a click between a paid visitor and the thing they arrived for. If a page has no campaign behind it and no question in front of it, it does not enter the build.
Not included:
A+ content and detail page modules. Photography and video production. Sponsored Brands and DSP management, which is separate work. Localisation beyond the English-language stores. We build on amazon.co.uk, amazon.ie, amazon.com and amazon.de where the catalogue supports it, and we will say plainly when a second marketplace does not yet carry the traffic to justify a second build.
Who should not buy this:
Brands with no paid budget aimed at the Store. With nothing to send, a Store is decoration with a reporting tab attached. Equally unsuitable at one or two ASINs, where a strong detail page and its comparison module will beat anything we could build, and we would rather say that on the first call than take the fee.
How the four weeks run:
Week one, structure and the buying questions, agreed in writing. Week two, copy and asset specification. Week three, build and internal review. Week four, moderation, tagged campaign setup and launch. The six-week test then runs on its own, and we report the result whether or not it flatters the build.