Skip to main content

2. Commerce Hub: Use Cases

Use Case #1: Publishing New Products

Your e-commerce team wants to onboard a new line of items to the Marketplace. They click Commerce Hub → Offerings, then + Add to open the “Add product” form. They select the target Project, enter Name, SKU, Price, choose a Category, upload a Main Image, and toggle Active. Upon saving, the new product appears in the table (with Total count updated) and is immediately searchable and filterable by Name, SKU, Category, and Status—ready for customers to browse and purchase.

Use Case #2: Reusing Marketplace Settings via Project-Scoped Configurations

A second business unit needs the same Order Statuses, Category hierarchy, and Payment Methods you built for Project A. From Commerce Hub → Configurations, they select their Project in the “Settings by project” bar, click Clone from project, choose Project A in the modal, and hit Clone. Instantly, all statuses, labels, and configuration entries appear for the new Project. They can then tweak colors or labels in-place without rebuilding from scratch.

Use Case #3: Building & Managing Categories for Discovery

Your merchandising team wants to group products by “Electronics,” “Accessories,” and “Clearance.” They go to Commerce Hub → Categories, click + Add, pick the Project, enter the Label and URL slug, and optionally nest it under an existing parent. In the table view they can expand each row to see how many products already use that category, edit or delete categories, and drag-and-drop to reorder. Search and filtering on the Category name let them locate and manage any node in a large tree.

Use Case #4: Enabling Multiple Payment Methods & Integrations

Your finance team needs to offer PayPal, Stripe, and an in-house “Manual” option. Under Commerce Hub → Payment methods, they click + Add, choose the Project, pick Type (e.g. “Stripe”), select Integration, set the Merchant ID, and define Currencies, Rules, and Credentials via the JSON editor. Toggling the Status switch immediately enables or disables that payment option on the storefront. The table shows Name, Type, Integration, and Project columns—so teams can audit and adjust live methods in seconds.

Use Case #5: Reviewing & Fulfilling Customer Orders

Customer support needs to monitor incoming orders. They open Commerce Hub → Orders, where the table lists Order ID, Date, Project, Customer, Cost, and Status—together with Total count, Search box, and a Filter drawer for date ranges, customer name, price slider, and status selectors. Clicking the expand-row arrow on any order reveals full order details on the right. From there, they can update the Status dropdown (e.g. “Shipped”), add internal notes, or trigger notifications—ensuring every order is tracked, processed, and closed in one unified interface.