WA Agency Amazon Spend - Orders, Categories, UNSPSC avatar

WA Agency Amazon Spend - Orders, Categories, UNSPSC

Pricing

$1.00 / 1,000 wa agency amazon spend records

Go to Apify Store
WA Agency Amazon Spend - Orders, Categories, UNSPSC

WA Agency Amazon Spend - Orders, Categories, UNSPSC

Washington agencies' Amazon Business purchases (944k line items, FY18-26): which agency bought what, from whom, for how much, under which UNSPSC commodity code. Filter by agency, product category, brand, UNSPSC, date, amount; aggregate spend by agency/category/brand.

Pricing

$1.00 / 1,000 wa agency amazon spend records

Rating

0.0

(0)

Developer

Wenhao Yang

Wenhao Yang

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

8 hours ago

Last modified

Categories

Share

WA Agency Amazon Spend (wa-amazon-spend)

Pull Washington state agencies' Amazon Business purchases - 944,699 line items / $81M across 9 fiscal years (FY18-FY26), from the state's free public open data.

This is the long tail of government procurement: every individual order an agency places through Amazon - the laptop, the LEGO set, the lab beaker, the printer toner - that nobody else tracks. It is the counterpart to WA Master Contracts: master contracts show the big negotiated vendors; this shows the day-to-day retail spend underneath.

Built for AI agents, developers, and market-intelligence / audit users who want to know what WA agencies are actually buying, from whom, at what price, under which UNSPSC commodity code.

What this data is

Each record is one line item - an agency's purchase of one product:

FieldMeaning
agencyNameThe buying agency (e.g. SOCIAL AND HEALTH SERVICES DEPT)
orderDate / paymentDateOrder / payment date
productCategory / productTitleAmazon's category + the product's full title
brand / manufacturer / sellerNameWho makes / sells it
unspsc8-digit UNSPSC commodity code (FY19+; FY18 predates the column)
quantity / itemSubtotal / shippingHandling / tax / netTotalWhat it cost
fiscalYearWhich FY dataset it came from

UNSPSC is the unique angle. Master contracts and agency contracts carry no product codes - Amazon spend does. So you can query "what agencies bought under commodity class 44 (office equipment)" directly.

Typical questions it answers

  • What is an agency buying from Amazon? agencyName=NATURAL RESOURCES -> every line item.
  • Who spends the most? Aggregate by agency -> total spend + order count.
  • What categories dominate? Aggregate by productCategory -> the tail of office/safety/IT spend.
  • Surge / anomaly monitoring - which agency's Amazon spend spiked this quarter? Aggregate by agency + dateFrom, compare against last quarter. Audit signals.
  • Specific products / vendors - keywords=["LEGO"], brand=HP, or an 8-digit unspsc=60141100.
  • Big-ticket orders - minNetTotal=1000 for orders over $1k.

Aggregate mode (server-side)

Turn on aggregate and it rolls up spend on the source - which means it works over the whole 944k-row corpus instantly, no matter how broad your filters:

Output fieldMeaning
keyThe agency / product category / brand / fiscal year
totalNetTotal net spend for that group
ordersNumber of line items

Group by agency (who spends most), productCategory (what dominates), brand, or fiscalYear.

Inputs (all optional)

InputWhat it does
keywordsMatch any keyword against product title / brand / seller
agencyNameSubstring match on the buying agency
productCategorySubstring match on Amazon's category
brandSubstring match on brand
unspsc8-digit UNSPSC code - accept 1/2/4/6/8 digits (exact at 8). FY18 auto-skipped
dateFrom / dateToOrder date range (YYYY-MM-DD)
minNetTotalOnly orders at or above a dollar amount
fiscalYearRestrict to one FY dataset (FY18-FY26), or all
aggregate + groupByRoll up by agency / productCategory / brand / fiscalYear -> totalNet + orders
maxResultsCap the number of records (default 200)

Low cost, server-side

From $0.001 per record - with a per-run charge cap so even a full-corpus aggregate can't surprise-bill.

This is nine fiscal years of Washington agencies' Amazon purchases - the state publishes each FY as a separate dataset, and the schemas drift across years: FY18 has no commodity-code column at all, and the same column that is numeric in FY19 is text in FY22. We merge all nine onto one query surface that knows each year's shape, so a filter over the whole 2018-2026 span works even where a naive query would hit a type mismatch. Filters, counts and roll-ups are pushed down to the source ($where / $group) - the ~944k-row / ~440MB corpus is never bulk-downloaded; an unfiltered run returns the most recent line items as a live monitoring feed.

Data source & freshness

  • Source: data.wa.gov - State Agency Amazon Spend (Socrata SODA API, free public, no login) - 9 fiscal-year datasets.
  • Update cadence: near-daily as orders are reported - the freshest state spend data on WA open data.
  • Coverage: agency purchases through Amazon Business only. FY18 has no UNSPSC column (schema predates it).