Skip to content
For grocery stores

Make the most of what you sell.

Xpired is a shopper beta that helps people use what they buy before it goes to waste. We want to scope a small Pittsburgh pilot with one or two stores: staff log and confirm items with the same app, and we measure together whether anything changes.

Xpired beta inventory screen listing bananas, romaine lettuce, baby spinach, blueberries, roma tomatoes and whole milk, each with a planning window such as about 1 day left, below the notice that estimated use-by windows are not food-safety or edibility checks, in an app that does not evaluate freshness or food safety
The shopper beta's inventory list, as it runs today. The pilot concept starts from this capture-and-confirm flow.
Talk to us about a pilot See what the app does today
  • Beta. Nothing is for sale yet.
  • A person confirms every item.
  • No shrink or revenue result is claimed.

Merchant features are planned concepts. Nothing on this page is a forecast, quote, or offer. What a pilot would and would not include

Suggestions for you to check before you add them.

LOG

Log what is on the shelf.

In the pilot concept, staff photograph items and confirm what the app suggests. Nothing is saved until a person confirms it.

IN FRAME · SUGGESTIONS FOR YOU TO CHECK.

When it does not know, it says so directly.

REVIEW

Give every item a planning date.

A date from typical storage guidance, or an honest no default. A store lead reviews the list and decides what happens next. The app does not decide for you.

IN FRAME · NO DEFAULT STORAGE TIME.

NOT BUILT Track what changed

A work-items view that summarizes pilot activity is a planned concept. It is not built and it is not part of the beta.

PLANNED

Reports, exports, analytics, integrations, and pricing tools are planned concepts too. None are generally available, and no production integration is claimed.

What a pilot includes

  • Staff inventory logging and date-label confirmation with the beta app.
  • A written scope first. Stores, audience, timing, responsibilities, commercial terms, and success measures require written agreement.
  • Baselines you provide: current workflow, shrink, labor, revenue, and how each one is measured.
  • Human review before any store action. Model output is supplemental, and the store keeps every decision and its legal responsibility.
  • Data handling as described in our Privacy Policy.

What a pilot does not include

  • Image-based freshness scoring, automated markdowns, analytics, integrations, and business outcomes are planned concepts, not currently generally available.
  • Any promised shrink, savings, revenue, labor, margin, compliance, or environmental result. No margin outcome or production dynamic-pricing feature is promised.
  • A price, quote, or forecast. The separate scenario tool does hypothetical arithmetic only.
  • Legal advice. AB 660 applicability depends on your products, dates, and counsel.
“Estimated use-by windows are not food-safety or edibility checks. Inspect each item before use.”
Printed on the beta's inventory screen.

Labeling provisions now in effect

California AB 660 date labels

For covered foods manufactured on or after July 1, 2026, AB 660 standardizes certain quality- and safety-date terms and generally prohibits consumer-readable "sell by" labels. It does not mandate markdown pricing, waste reports, or a particular recordkeeping system.

  • Confirm scope
  • Use permitted terms
  • Keep AI supplemental

This material distinguishes the current shopper beta from planned merchant workflow concepts and is not legal advice or a delivery commitment. AB 660 applicability depends on the product, manufacturing date, labeling responsibility, statutory exceptions, and other law. Consult qualified counsel or the appropriate California agency. Read the official statute.

Ready to scope a pilot?

Request a product discussion. Response times vary; no response-time SLA is offered.

Prefer email? LawHuaExpired@gmail.com