datawebotKroger grocery data: UPCs, local prices & order changes
A Kroger guide to UPC and product IDs, store-scoped prices, fulfillment types, digital coupons, substitutions and current API/site terms.
Kroger product IDs and package items should stay distinct
Kroger's Public product-details documentation accepts a productId or UPC as the requested product identifier. The separate Partner API response example also shows productId, UPC, itemId and size fields. These labels describe different levels of a grocery record: preserve each value as the source returns it, and do not join packages by title alone.
Scroll to compare →
| Record level | Kroger documentation | Useful comparison rule |
|---|---|---|
| Product lookup | The Public product-details request accepts productId or UPC. | Keep both identifiers when returned; store UPC values as text so leading zeroes survive. |
| Product identity | The Partner API response example includes productId and UPC for the product. | Keep the source's product-level identifiers separate from a display title or brand label. |
| Item option | The Partner response example shows itemId and size within product item data. | Retain package size and item-level ID as separate fields when the response includes them. |
| Name matching | A product name is a human-readable label, not the productId or UPC. | Do not use title similarity alone to merge package sizes, flavors, counts or other item options. |
| Evidence | Public and Partner API references describe different access tiers and may expose different operations or response details. | Record which documentation or supplied authorized response supports each field; mark absent values unknown. |
A Kroger price observation needs a store and fulfillment context
Kroger's product-list documentation describes filter.locationId as the store used to limit results and lists four fulfillment values. The Partner product-details reference says a locationId is needed to return product price, availability and aisle location. Save the source's store and fulfillment context beside every value; a returned availability signal does not reserve an item or promise exact shelf stock.
Scroll to compare →
| Context | Kroger field or label | What to preserve |
|---|---|---|
| Store | filter.locationId selects the location used to scope results. | Keep the returned locationId with the store label or address context supplied by the source. |
| In store | ais means Available In Store. | Distinguish the fulfillment label from a current inventory quantity or reservation. |
| Curbside | csp means Curbside Pickup. | Keep curbside availability separate from an in-store or home-delivery result. |
| Delivery or shipping | dth means Delivery To Home; sth means Ship To Home. | Preserve each source-supported mode separately; do not collapse delivery and parcel shipping. |
| Aisle and availability | The Partner product-details reference associates locationId with returned price, availability and aisle details. | Treat aisle location and inventory labels as store-specific, time-sensitive source signals, not guarantees. |
Keep regular price, promotion, coupon and receipt amount distinct
The Kroger Partner product response example separates regular and promo price fields. Kroger's digital-coupon help describes a different offer layer: coupons are loaded to a Shopper's Card and apply to qualifying purchases. A catalog price, coupon eligibility and final receipt line are not interchangeable amounts.
Scroll to compare →
| Price layer | Kroger's published context | How to record it |
|---|---|---|
| Regular amount | The Partner response example names a regular price field. | Store the amount, currency, selected store, item option and observation time. |
| Promotional amount | The same response example names a separate promo price field. | Keep it distinct from the regular amount and retain any source label or qualification. |
| Digital coupon | Kroger says digital coupons are loaded to a Shopper's Card and redeem on qualifying items; the deduction appears on the receipt. | Record the offer condition and coupon state only when supplied by an authorized source; never infer eligibility from a promotion price. |
| Final item charge | Kroger says the final price can change after order placement, and the receipt shows the exact item price. | Use the receipt or final order record for realized spend, not an earlier catalog offer. |
| Customer account context | Coupon loading and card details relate to a customer's account. | Do not include card numbers, credentials, customer identities or account history in a public product record. |
Substitutions and weighted products belong to a fulfilled order event
A selected catalog item is only the start of a Pickup or Delivery order. Kroger says totals are estimates that can change because of coupons, substitutions, taxes, weighted items or price updates. If a shopper accepts a substitute, Kroger charges the substituted item's price. Keep the requested item and what was actually picked as linked but distinct order-line facts.
Scroll to compare →
| Order stage | Kroger-published rule | Separate event fields |
|---|---|---|
| Requested item | The order begins with a selected product and package option. | Retain requested productId or UPC, item option, store, fulfillment mode and selected quantity when supplied. |
| Substitution | Customers may allow or reject a substitution; an accepted replacement is charged at its own price. | Link original and replacement identifiers, the decision state, replacement price and time. |
| Weighted item | Produce, deli, meat and seafood may be selected by weight or count; fulfilled amount can differ from the estimate. | Keep estimated weight/amount separate from picked quantity and final line charge. |
| Estimate | Kroger identifies coupons, substitutions, taxes, weighted items and price updates as reasons a checkout total may change. | Label the total as an estimate and preserve its calculation time and displayed conditions. |
| Receipt | The final item price appears on the receipt after the fulfilled order amount is determined. | Use the receipt or authorized order record for realized spend; do not backfill it from the product listing. |
| AI-generated product summary | Kroger Terms §7.2 say AI-generated product information, including ingredients, nutrition or availability, may be inaccurate or not current. | If an AI summary conflicts with product labeling, packaging or the applicable product/transaction page, use that source-of-record information and retain its provenance. |
Separate Kroger's documented APIs from its consumer-site terms
Kroger publishes distinct Public API and Partner API documentation, while its Website & App Terms govern access to the Kroger Sites. The Terms last updated September 9, 2026 prohibit automated means such as bots, crawlers, scrapers and data-mining tools from accessing, collecting, extracting or monitoring site information (§5.3). Section 8 discusses third-party agents used to interact with Kroger on a customer's behalf; it does not grant general permission to collect the storefront catalog.
Scroll to compare →
| Route or rule set | What the first-party material says | Keep the boundary clear |
|---|---|---|
| Public APIs | Kroger's Public API workspace documents product and location requests using OAuth 2.0. | Follow the applicable API documentation and terms; API documentation is a different access route from the consumer storefront. |
| Partner APIs | Kroger maintains a separate Partner API workspace with its own product-response reference. | Do not describe Partner fields or access as automatically available to every Public API client. |
| Consumer Websites and Apps | Terms §5.3 prohibit bots, crawlers, scrapers and data-mining tools from accessing, collecting, extracting or monitoring Kroger Site information. | Do not treat public page visibility or a product URL as authorization to automate collection or reuse content. |
| Third-party agents | Terms §§8.1–8.2 make customers responsible for an agent they choose and allow Kroger to limit or block agent access or require authentication or authorization evidence. | Do not interpret customer-agent language as overriding the separate site-use restriction or as a general catalog feed. |
| Terms version | The Website & App Terms show Last Updated September 9, 2026 and apply to the Kroger Sites; other Kroger agreements are separate. | Check the current terms applicable to the intended product or API route before relying on this dated summary. |
Content reviewed 2026-10-04.