Retailer Data Partnership
LastList turns a household's shopping list into a store by store plan: what to buy, where it is in stock, and what it costs. Shoppers finish in your channel, whether that is pickup, delivery, or a trip to the store.
That is the entire request. One credentialed, rate-limited, read-only feed or API.
- No checkout or cart integration
- No change to fulfillment
- No commission, revenue share, or affiliate fee
- No new consumer surface for your team to build or maintain
- No exclusivity
Shoppers arrive at your channel with a complete, accurate basket instead of a half-remembered list.
Today we can show a shopper that your store is nearby. We cannot show them a single product inside it, so the basket gets built somewhere else. You already publish catalog and price data to third-party consumer surfaces. This is the same category of integration, for list building rather than delivery.
How the Data Is Handled
Commitments we are prepared to put in writing
- Display only. Shown to an individual shopper in the context of their own list.
- You set the price. We display the price you publish, exactly as you publish it. We are not asking for shelf price or zone pricing.
- No bulk export. No redistribution, no resale, no syndication to third parties.
- No price archive. No historical pricing database is retained or derived.
- Rate limited. Volume caps you set, with credentials you can revoke at any time.
- Attribution. Shoppers are handed off to your channel, tracked and reportable.
- Superseding terms. The agreement governs this access, replacing the site terms of use for the licensed purpose.
A Known Quantity
LastList runs live product-API integrations with Walmart and Kroger, including the full Kroger banner family: Ralphs, Fred Meyer, King Soopers, Smith's, Fry's, QFC, Dillons, Harris Teeter, Mariano's, Pick 'n Save, Metro Market and Food 4 Less. We also integrate Best Buy and eBay, and we are an Instacart Developer Platform partner.
We hold production API access with two of the three largest grocers in the United States. We are asking to extend coverage, not to pilot an unproven idea.
- Web at lastlistapp.com
- Apple App Store, as a native application
- Google Play, as a native application
- Microsoft Store
- Amazon Alexa Skill Store
We are early and not claiming scale. That is precisely why the ask carries no revenue share. We want read access to build the product properly, not a commercial commitment either side would have to justify.
We consume whatever you already produce. A partner feed, an existing internal API, or a nightly file drop all work.
Typical fields: product identifier or UPC, title, brand, size or pack, category, store identifier, published price, and an availability flag if you have one. Availability is welcome but not required.
We have done this four times. Engineering effort on your side is normally scoping and access provisioning rather than new development.