# BillingRunResellerOutcome

A model the API reference uses in a request or a response. The operation pages link every field typed as this model here.

Classifies how a single reseller fared within an admin billing-run batch. Lives in
Domain.Shared so the Domain aggregate (`MerchantBillingRunBatch`'s embedded
outcome) and the Application.Contracts DTOs can both reference it without a layer violation.

## Values

| Value | Description |
| --- | --- |
| `Completed` | A run executed for the reseller (may include per-merchant failures within it). |
| `SkippedNoBillableMerchants` | No merchants were assigned to a price plan for the period: no run was created. |
| `SkippedAlreadyRun` | A completed (non-dry) run already exists for this reseller and period. |
| `SkippedRunInProgress` | A run is already in progress for this reseller. |
| `Failed` | The reseller's run failed before completion (or failed to enqueue). |
| `Scheduled` | The reseller's run was accepted and queued as a background job. Merchants are billed asynchronously; the run's final status (Completed, PartiallyCompleted or Failed) appears on the run once processing finishes. An all-resellers batch reports progress through the batch status instead. |
| `SkippedMerchantBillingDisabled` | The reseller has the "Merchant Billing" master switch (ResellerFeatures.MerchantBilling) turned off, so no run was created and no invoices were generated for its merchants. |

## See also

- [All documentation](https://devportal.demo.winkpg.io/llms.txt): the machine-readable index of every public page on this site.