Ecommerce
Complete catalog browsing, product detail and selection without exposing raw stock.
Ecommerce
Prepare
Enable ecommerce and prepare public products, variants, options, and market assignment in the target environment. A Publishable Key is enough for the catalog; keep Secret Keys and privileged order/inventory work on your server. New customer accounts use Customers, separately from public browsing.
These examples use the published SDK 0.65.1, Next.js 16.3.8 App Router, React 19.2.4, and Node 24.15.0. Install the SDK in your own app with npm install @01.software/sdk@0.65.1. The examples use force-dynamic; SDK calls run on requests, not at build time. This assumes no cacheComponents or static export. Compile and controlled local transport checks do not certify hosted availability or remote workspace admission.
Implement catalog to selection
Copy the complete Product listing page, then the Product detail page and read error boundary. Open /products, follow a card and then a swatch/selection link, and verify the selected product/variant remains the same after reload. Both recipes run with the public package and do not require the later split reference pages.
Normal, empty, and failure results
Verify an empty catalog, one published product, direct unlisted detail, and absent/non-public detail. Listing emptiness is success; detail absence uses a standard 404. Async route params are awaited. Test stable-ID selection roundtrips, stale selection, credential/feature errors and workspace denial without falling back to raw collection reads. Network/server failures need a read retry UI; do not render them as zero stock or zero products.
Public DTOs omit raw inventory. Catalog availability can be stale; stock checks do not reserve, and final order creation rechecks stock and sellability. Displaying a catalog does not establish payment readiness.
Next Actions
Continue with the existing SDK cart, checkout, and PaymentSession guidance. Preserve the operation’s typed reason and retry/idempotency behavior; do not blindly repeat writes or start payment from a catalog click. Checkout/payment implementation is outside this task. Use Commerce Operations, Integrations & Keys, and Deploy for product ownership, provider setup and launch.