RevenueFlow.Catalog
0.1.0-alpha.7.2
dotnet add package RevenueFlow.Catalog --version 0.1.0-alpha.7.2
NuGet\Install-Package RevenueFlow.Catalog -Version 0.1.0-alpha.7.2
<PackageReference Include="RevenueFlow.Catalog" Version="0.1.0-alpha.7.2" />
<PackageVersion Include="RevenueFlow.Catalog" Version="0.1.0-alpha.7.2" />
<PackageReference Include="RevenueFlow.Catalog" />
paket add RevenueFlow.Catalog --version 0.1.0-alpha.7.2
#r "nuget: RevenueFlow.Catalog, 0.1.0-alpha.7.2"
#:package RevenueFlow.Catalog@0.1.0-alpha.7.2
#addin nuget:?package=RevenueFlow.Catalog&version=0.1.0-alpha.7.2&prerelease
#tool nuget:?package=RevenueFlow.Catalog&version=0.1.0-alpha.7.2&prerelease
RevenueFlow.Catalog
Optional CatalogProvisioningService freezes Core provider plans alongside offer publication and coordinates durable single-owner native mutations, dependency ordering, read-only uncertain-outcome recovery and atomic provider links/history/outboxes. Supply it to CatalogService and register the optional RevenueCatalogProvisioningWorker from the hosting package, or pump scoped pages yourself. Native IDs and readiness are separate from local purchase/fulfillment evidence. See the repository's docs/catalog-provisioning.md for setup, bounds and platform-specific behavior.
CatalogService implements ICatalogService over any conforming IRevenueDocumentQueryStore. Publishing stores immutable product, price, fulfillment and named offer revisions with CAS publication heads, command receipts, history and selected event consumers in one transaction. An existing revision can never acquire different terms. Archival hides current discovery while preserving historical exact reads and captured purchase terms.
Offerings contain ordered packages of exact equivalent offer references. The scoped default pointer pins an explicit offering revision; publishing another revision does not silently replace a selected default. Set the pointer explicitly to roll it forward. Provider mapping revisions bind full scope, provider, account and test/live mode; their indexed current projection permits one SKU per exact offer and binding. New acquisitions may use current mappings; webhook reconciliation must use already pinned terms. CaptureAsync captures terms, never payment evidence. Catalog JSON documents are limited by the shared store's 64 KiB bound.
ImportProviderPageAsync consumes Core's IProviderCatalogReader and durably stages one bounded fact page with its next opaque cursor. Missing provider prices remain unknown. Import never creates benefits, publishes offers or proves payment; applications explicitly map imported facts and approve fulfillment revisions. Retry the same command after an unknown commit outcome; a committed replay performs no provider I/O. Continue using a new command and the retained next cursor to import additional pages.
Typed list pages use the shared store's live GUID cursor order. Offer revision pages use a dedicated scoped entity kind, so unrelated products cannot consume a filtered page. Live reads and default discovery are configuration views; applications pin exact revisions when preparing acquisition intent.
Catalog behavior in the RevenueFlow.Catalog namespace. InMemoryCatalogRegistry is a thread-safe, process-local development example. It is not durable, does not coordinate separate processes and cannot participate in commerce database transactions.
Register a CatalogOffer, then retrieve it by full scope and exact product, price and fulfillment IDs and versions. Registration atomically rejects replacing a previously registered product, price or fulfillment revision with changed contents. A failed registration publishes none of its new definitions. Matching repeated registration is idempotent. Lookup does not choose a latest revision or authorize purchases.
The development registry's provider mappings require an already registered exact offer. Its lookup includes full scope and provider account, and its registrations cannot be rebound. Use the durable service's explicit versioned mapping lifecycle when changing current provider terms. Provider payload authenticity and account ownership remain application/provider-adapter responsibilities.
Construct a PurchaseSnapshot from an immutable offer before persisting purchase terms in the commerce transaction. Catalog definitions and snapshots are JSON round-trippable with System.Text.Json and constructor validation. Long-lived snapshot retention and schema version migration belong to a production commerce store.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- RevenueFlow.Catalog.Abstractions (>= 0.1.0-alpha.7.2)
- RevenueFlow.Events.Abstractions (>= 0.1.0-alpha.7.2)
- RevenueFlow.Stores.Abstractions (>= 0.1.0-alpha.7.2)
NuGet packages (2)
Showing the top 2 NuGet packages that depend on RevenueFlow.Catalog:
| Package | Downloads |
|---|---|
|
RevenueFlow
RevenueFlow commerce composition with internal administrative issuance. External providers and stores are explicit opt-ins. |
|
|
RevenueFlow.Hosting.Worker
Explicit background worker for bounded RevenueFlow event dispatch. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 0.1.0-alpha.7.2 | 60 | 11/10/2026 |