Inventory & Ops · Blog post · source Jul 2, 2026
One Inventory View Across FBA, AWD and a 3PL Built with Claude Code
See units on hand and sell-through across FBA, AWD and a 3PL in one place
“A 90-minute weekly manual reconciliation became a refresh that completes in a few minutes”
Per source Reported by an agency about its own client work, not independently verified.
Copy-paste prompt
Here's the raw JSON from the FBA /fba/inventory/v1/summaries endpoint (pasted below). Write an ingest script that upserts sellerSku, asin, and the fulfillable/inbound quantities into a fba_inventory table, paginating on nextToken, capped at 20 pages. Never overwrite the cost column on the product table — COGS is entered manually and must survive a refresh.
This prompt is quoted or closely adapted from the original source. Replace anything in [brackets].
What they did
A consultant built a client's inventory portal with Claude Code over a weekend. The brand sells across Amazon FBA, Amazon's AWD, a third-party warehouse and a Shopify store, and each names the same SKU differently. One Node.js script per source (SP-API for FBA, AWD, finances, returns and sales-and-traffic; the 3PL's API; Shopify) loads Postgres, run in dependency order by one orchestrator. For each source he pasted the real API response into Claude Code and stated the table and constraints, such as never overwriting hand-entered COGS.
How it went
Every source ran cleanly but totals were still wrong because SKUs didn't join, until he measured join coverage and built a SKU-to-ASIN crosswalk with normalization and a list of orphans. A 90-minute weekly manual reconciliation became a refresh that completes in a few minutes, and he estimates Claude Code turned a week of work into two evenings plus a few dollars of usage.
We only report what the source says. Results are self-reported unless noted.
Worth knowing
An agency build log. No model runs at refresh time: the AI built the pipeline and the pipeline is deterministic, which is what you want for inventory numbers.