Commerce
Catalog, one-time payments, inventory, orders, fulfillment, and their NestJS application boundaries.
Commerce packages keep product terms, payment state, stock promises, order state, and fulfillment progress separate while providing an orchestration layer that composes them into one-off purchase flows.
Portable domains
| Package | Plan | Responsibility |
|---|---|---|
@playstack/catalog | Products, variants, immutable offers, and provider-aware quotes. | |
@playstack/payments | One-off checkout, capture, refund, dispute, and reconciliation projections. | |
@playstack/inventory | Locations, balances, reservations, and immutable stock adjustments. | |
@playstack/fulfillment | Encrypted fulfillment requests and provider-neutral delivery progress. | |
@playstack/commerce | Order snapshots and transactional orchestration across the other domains. |
NestJS boundaries
| Package | Plan | Responsibility |
|---|---|---|
@playstack/nest-catalog | Authorized catalog administration. | |
@playstack/nest-payments | Refund, reconciliation, and verified payment-event services. | |
@playstack/nest-inventory | Inventory administration and reservation-expiry workers. | |
@playstack/nest-fulfillment | Fulfillment administration and queue-neutral workers. | |
@playstack/nest-commerce | Checkout, order-access, and payment-projection services. |
Subscriptions remain in @playstack/billing. Product applications can use subscriptions and one-time commerce together without forcing either payment model into the other.