Skip to content
For Grocery Retailers

Explore inventory &
date-label pilots

Scope a pilot around staff inventory discipline and date-label workflow support. Image-based freshness scoring, automated markdowns, analytics, integrations, and business outcomes are planned concepts — not currently generally available.

Seeking Store Partners
Current TestFlight Beta
AB 660 Overview + Planned Concepts
Produce worker; merchant dashboard and analytics are planned concepts
Beta

Current product status

Build-bound

Produce coverage

Human

Review before store action

Planned

Analytics and integrations

BENEFITS

What a pilot can evaluate

These are pilot hypotheses, not measured customer outcomes or generally available automation.

Test Inventory Discipline

Evaluate whether structured staff check-ins and date-label discipline can inform shrink decisions. No shrink reduction or revenue outcome is promised.

Study Review Consistency

Compare a scoped image-scoring workflow with existing checks. Labor effects must be measured in the participating store.

Explore Planned Workflows

Evaluate future date-label workflow concepts after legal and operational review. These tools are not generally available.

HOW IT WORKS

Illustrative pilot workflow

The steps below are pilot concepts, not current product capabilities. Image-based freshness scoring is not currently generally available; every step requires human review or remains planned.

1. Log

Staff capture item and date-label information during checks

2. Confirm

A staff lead confirms dates, quantities, and conditions before any action

3. Review

Store staff review work items and decide on markdowns, rotation, or donation

4. Track - planned

A future work-items dashboard could summarize authorized pilot activity; it is not a live feature

PILOT EVIDENCE BOUNDARY

Measure first; make no outcome assumption

Image-based freshness scoring is not currently generally available. Merchant automation, date-label workflows, reports, exports, analytics, integrations, pricing tools, and environmental reporting are pilot concepts - not currently generally available features.

Customer baseline

Agree what data is authorized and how current workflow, shrink, labor, and revenue are measured.

Human review

Treat model output as supplemental; stores retain decisions and legal responsibility.

No promised result

No shrink, savings, revenue, labor, margin, compliance, or environmental outcome is assumed.

Pilot Discussions

Explore a Scoped Store Pilot

Contact us to discuss whether a limited Pittsburgh pilot fits your store. Scope, timing, responsibilities, commercial terms, and success measures require written agreement.

What We Would Scope Together

Staff inventory logging and date-label confirmation workflows
A limited pilot audience and acquisition plan, if mutually agreed
Baseline metrics to test whether the workflow affects shrink or revenue
Optional discovery for planned date-label workflows; no compliance assurance
Commercial terms discussed and documented before any commitment

Pilot Status

Contact us for current partner availability and timing

Industry Average Shrink The Problem
$380B

ReFED reports $380B in U.S. surplus food in 2024, of which $325B was wasted. Xpired has not verified a store-level revenue or waste-reduction outcome.

Informational

Freshness estimates are not deployment-rated or safety-grade

Build-bound

Produce coverage requires signed-build verification

Build-dependent

Processing and network requirements vary by model path and beta build

Interested in becoming one of our first store partners? Let's talk.

Schedule a Conversation

PLATFORM

Illustrative merchant workflow

Planned concepts for discovery, from scanning to analytics. Availability and scope are not generally promised.

Date-Label Logging - planned

A future workflow could help staff record quality and safety dates during checks; current availability is not promised

Human Review - planned

A future workflow could require staff confirmation before any store action is suggested

Work-Items Dashboard - planned

A future dashboard could list reviewable work items from authorized pilot data; it is not live

Device-Based Concept

A scoped pilot may use compatible phones or tablets after technical review

Produce worker; merchant platform features are planned and require written scope

Manifest-bound SKUs

No deployed ID percentage claimed

Illustrative planning only

No validated merchant ROI result yet

Xpired has not established production shrink, labor, revenue, environmental, payback, or savings outcomes. Merchant pricing, automation, implementation scope, and subscriptions are not generally available.

A real pilot would first agree on customer-provided baselines, measurement methods, responsibilities, and written commercial terms. The separate scenario tool performs hypothetical arithmetic only; it is not a forecast, quote, offer, or outcome claim.

Open Illustrative Scenario Tool
Labeling Provisions Now in Effect

Review Your CA AB 660 Workflow

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

Review product coverage, manufacturing date, labeling responsibility, exceptions, and federal requirements.

Use Permitted Terms

Support the permitted "BEST" quality-date and "USE" safety-date terms after qualified review.

Keep AI Supplemental

If a future verified build returns a freshness estimate, it is supplemental. Merchant markdown automation is planned and not generally available; neither replaces required labels.

What AB 660 Addresses

  • Permitted quality- and safety-date terms
  • Consumer-readable "sell by" restrictions
  • Product, date, and responsibility scope
  • Statutory exceptions and federal preemption

Planned Xpired Concepts

  • Planned configurable, human-reviewed label workflows
  • Planned internal operational reports and exports
  • Planned timestamped internal activity history
  • Current supplemental shopper estimates; planned merchant pricing tools

Scope and schedule are confirmed after discovery. Let's talk about a partnership.

Schedule a Workflow Demo

Product overview only • No obligation • Not legal advice

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.

Produce worker; compliance dashboard and reporting are planned concepts
PLANNED WORKFLOW CONCEPTS

Explore future date-label operations

Configurable merchant workflows, internal records, and reporting exports are planned concepts, not generally available features. If developed and contracted, they would support - but never guarantee - legal compliance.

Planned human review of permitted AB 660 date terms
Planned timestamped internal activity history
Planned configurable operational reports
Planned ESG reporting exports

Ready to explore a scoped pilot?

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

Prefer email? LawHuaExpired@gmail.com