What does a tightly scoped reseller pilot look like?

A marketplace curator scopes a generated retail pilot around customer account ACC-2187, which is being transferred from one purchasing department to another. Request CHG-0412 names the new department contact and asks that open-order communications follow the transfer.

The pilot includes the customer account, department relationships, open orders and communication-routing rules. A downstream evaluator must identify which orders still require contact updates and which completed orders retain their historical contact information. The state change ends when the permitted routing updates are recorded and the unresolved exceptions are listed.

Payment credentials, credit reassessment and changes to the legal purchasing entity sit outside this pilot. If a task requires one of those processes, it should expose the boundary through an explicit unsupported-action result rather than silently assuming completion.

The reseller asks to inspect the task wording, schema, accepted outcomes and catalogue description together. The useful acceptance decision is whether this bounded package supports the promised downstream use. Expansion can then target a missing dependency or exception that buyers actually need, rather than adding unrelated records simply to make the sample look more substantial.