Products and commerce

Products describe what you sell (training courses and ticketed events). The public storefront turns those products into tenant-hosted offers at /courses and /events, while Commerce now tracks orders and payments from checkout through fulfillment.

Products — courses

Path: Products → Courses (/products/courses)

1. Open Course product management and check active vs retired counts.
2. Create a course product — course code, title, category, price, delivery mode (such as self-paced, cohort, hybrid, or workshop).
3. Use the table as your operating catalog: View opens a detail page; Edit updates catalog copy and pricing; ACTIVE / RETIRED adjust sellability.
4. Fill in the public fields on create or edit: slug, public description, badge, CTA label, featured, and SEO copy. Those values drive the public storefront detail pages and CMS merchandising sections.
5. Coordinate with Learning when you deliver training—products describe the offer; cohorts live under Learning.

Products — events and tickets

Path: Products → Events (/products/events)

1. Open Event management; note live and scheduled counts.
2. Create an event — event code, name, venue, start and end times, seat count, ticket type, price.
3. Review the schedule and inventory in the table; View opens a detail page; Edit updates venue, times, seats, and price.
4. Use the same public storefront fields so visitors see a polished event page at /events/[slug].
5. Pair with commerce and operations as money and delivery move forward.

Public storefront

Paths: /courses, /courses/[slug], /events, /events/[slug], /checkout/[id], /orders/[id]

These routes are tenant-hosted. In production they run on the workspace website hostname, such as tenant.platform.reuzio.com or a verified custom domain, not only on the platform root host.

1. Publish active courses and scheduled or live events with storefront-ready slugs and copy.
2. Visitors browse those offers on the tenant public website, open the detail page, and choose the checkout CTA.
3. Checkout creates a durable checkout session, then an order, then a linked payment.
4. Paid course orders fulfill into Learners and Enrollments. Event orders fulfill into Event registrations and reserve inventory.
5. CMS pages can also feature selected offers through Commerce sections JSON, so editorial pages and product discovery stay in one system.

Commerce — orders

Path: Commerce → Orders (/commerce/orders)

1. Open Orders to review confirmation codes, buyer identity, totals, and fulfillment state from the public storefront.
2. Use the detail page to confirm which items were sold, whether payment is recorded, and whether event registrations were issued.
3. Pair order review with Payments when a buyer needs support or finance needs a status check.

Commerce — payments

Path: Commerce → Payments (/commerce/payments)

1. Open Payment integration and review pending, succeeded, and refunded counts.
2. Add payment — transaction ID from your gateway, customer, amount, method (card, invoice, bank transfer, wallet, etc.).
3. View opens a payment detail page for the full record and quick status updates.
4. Storefront checkout also creates payment records automatically, so the payments area now mixes manual backoffice entries with public checkout results.
5. Monitor refunds and pending items regularly to catch revenue issues early.

Before you start

• Use stable codes for courses and events—they are reused in operations.
• Align customer naming with CRM and finance so records match.

Related

• Learning
• CRM
• Operations
• Manage offers, events, and payments