A fluid power manufacturer opening a direct commerce channel had no storefront, no organic history, and one hard requirement: the Acumatica PIM stays the source of truth. Five months later a 22k-SKU Next.js + Saleor build was live — AIO-ready from the first deploy, and earning its first AI Overview citations within 12 weeks of launch.
22k
SKUs on a greenfield Next.js + Saleor build
5 mo
Kickoff to launch
12 wk
To first AI Overview citation after launch
1
Source of truth — the Acumatica PIM, wired straight through
The situation
A manufacturer selling through an OEM channel decided to open a direct commerce channel — net-new, with no existing storefront and no organic history to inherit. The catalog was 22k SKUs, the pricing was multi-currency across multiple tax regions, and the product data lived where it belonged: in the Acumatica PIM, which was not going to be replaced.
The constraint
Greenfield domains start with nothing engines trust. Every citation heuristic that favors incumbents — history, links, behavioral signals — worked against this launch. And the PIM-as-source-of-truth requirement meant no copy-paste catalog: if product data forked from Acumatica, the project failed on its own terms regardless of traffic.
What we ran
The PIM stays canonical. Product data flows from Acumatica into Saleor, so the catalog never forks — 22k SKUs with one source of truth.
Server-rendered storefront with multi-currency and multi-tax-region handling from day one.
Schema graph, direct-answer category structure, and machine-parseable spec tables shipped with the first deploy.
This is what a Website Development engagement at this scale looks like in practice.
Why it worked
A greenfield domain can’t win citations on authority, so it has to win on legibility. The engines’ first crawl saw the catalog exactly the way they want it: structured specs, answer-shaped category pages, a complete schema graph. That is why the first citations arrived in weeks, not quarters — there was no remediation phase, because nothing shipped broken.
What happened
The build went live at month five, 22k SKUs, PIM wired straight through.
The first AI Overview citations on tracked category queries arrived inside 12 weeks of launch — on a domain that had existed for less than half a year and had no link history to lean on.
The number that mattered
0 wk
Time to first AI Overview citation, post-launch
Greenfield build · zero pre-launch organic history
Measurement notes
A metric without a source is an assertion. Every number on this page is listed below with how it was counted.
Anonymity. Client name withheld under NDA — most industrial distributors prefer the case study without the logo. The vertical, scale, timeline, and every number are as measured; only identifying details are removed. Reference calls available on request.
More case studies
Industrial hydraulics distributor~8,500 SKUs
Anonymized · NDA+43.5%
Qualified leads per month, on the August baseline
Aug 2024 – Jan 2025 · client CRM
An ~8,500-SKU industrial hydraulics distributor came in with qualified inbounds flat at 1,840 a month and AI Overviews citing its manufacturers instead of its own category pages. Six months of catalog and AI-search engineering later, January closed at 2,640 — +43.5% on the August baseline, with paid budget held flat.
Industrial hydraulics distributor~8,500 SKUs
Anonymized · NDA8,500
SKUs replatformed in six months
Magento 1 → Next.js + Shopify Hydrogen
The same hydraulics distributor’s commerce stack was end-of-life: Magento 1, legacy schema invisible to AI Overviews, and 600ms-plus INP killing add-to-cart on mobile category browsing. A six-month full replatform moved all 8,500 SKUs onto a headless Next.js + Shopify Hydrogen storefront with a complete schema graph live from the first deploy.
Your catalog, same standard
Held to the same standard as the studies above: we measure where you stand today — organic and AI-search visibility across your top categories — and show you the baseline before we propose a thing.