# E-commerce pilot scoping worksheet

This worksheet is a proposed discussion aid, not a contract. A human reviews the request before ProxyLane confirms feasibility, scope, price or any delivery terms.

## Scoping questions

- What product URLs or source list should be considered?
- Which variants must match exactly: size, colour, pack, unit, model or another attribute?
- Which fields are required beyond `product_url`, `variant`, `price`, `currency`, `availability`, `observed_at`, `region` and `match_status`?
- Which geographies and currencies are in scope?
- What refresh interval should the pilot assess?
- What output format should the team review: JSON, CSV or another agreed format?
- What expected volume should the pilot cover?
- Which source conditions should produce `accepted`, `review` or `unknown`?
- How should missing prices, unknown stock and failed fetches be represented?
- Who performs the human review, and what decision may follow an accepted record?

## Acceptance worksheet

| Check | Agreed rule | Result | Reviewer / date |
| --- | --- | --- | --- |
| Source list |  |  |  |
| Variant and unit matching |  |  |  |
| Required fields |  |  |  |
| Geography and currency |  |  |  |
| Refresh interval |  |  |  |
| Output format |  |  |  |
| Expected volume |  |  |  |
| Unknown stock handling |  |  |  |
| Failed fetch handling |  |  |  |
| Human review rule |  |  |  |

## Proposed output decision

Pilot status: ____________________

Open feasibility questions: ____________________________________________

Agreed acceptance decision: ____________________________________________

The request should include the vertical, source list, required fields, geography, refresh interval, output format, expected volume and acceptance rules. Use the contact page to draft the email; no message is sent automatically.