Data requirements

A smaller, documented input makes the service safer and easier to audit.

The normal starting point is a stable, buyer-normalized inventory export. Nothing operational should be sent through the public website.

Accepted profile

Fields the working schema is designed around.

The field list is a planning profile, not a request to email data. The exact schema and secure exchange are agreed in writing after fit review.

Explicit exclusions

No autonomous purchasing, stockout or savings guarantee, ERP write, supplier commitment, or replacement for a qualified inventory planner.

Credentials, unrestricted system access, and unrequested free text are never part of the published plan.

Data lifecycle

01
Agree
Write down the permitted fields, purpose, owner, transfer, retention, and deletion rule.
02
Prepare
The buyer exports and normalizes only the agreed minimum input.
03
Validate
Schema failures and unknown values are rejected without inference.
04
Deliver
Portable outputs carry definitions, exceptions, and confirmation states.
05
Delete
Working data follows the written retention rule; the buyer keeps the final pack.

Field glossary

Period index: A relative time bucket supplied without exact dates.
Quantity band: A buyer-normalized quantity range rather than a raw transaction.
Exception rule: A buyer-authored condition used to surface a row for review.
History sufficiency: Whether the submitted period coverage meets the agreed rule.
Data-quality code: A neutral structural issue such as missing or invalid input.
Planner queue: Items needing qualified human review; not purchase recommendations.

A useful first conversation

Describe it in general terms. We will tell you which plan fits, what we would need, and where we would draw the line.