Catalog
- Catalog Structure
- Catalog Product Type
- Variant Model
- Product Discovery Model
WebShop Application Type
Build a WebShop that helps people find the right product and finish with confidence.
A commerce product succeeds when merchandising, checkout, fulfillment, and post-purchase service work like one connected system. If any part breaks, conversion drops and trust disappears after the sale.
For teams who want a storefront that does real commercial work, not a catalog that merely looks polished. The essential question is whether the shop can move customers from intent to delivery with as little friction and ambiguity as possible.
- Reduce drop-off during product discovery and checkout.
- Support the catalog logic your merchandising team actually runs.
- Make fulfillment and returns part of the buying promise.
Open in Workspace
Audience: Merchants, DTC brands, retail operators, and commerce teams.
Supported Decisions
What the workspace can actually scope
These decision areas and option sets come from the application-type specs used by the workspace.
Merchandising
- Inventory Visibility
- Pricing Pattern
- Assortment Strategy
Cart & Checkout
- Cart Persistence
- Order Capture Model
- Purchase Mode
Fulfillment
- Fulfillment Model
- Order Splitting
- Delivery Commitment Style
Post-Purchase
- Returns Model
- Order Tracking Depth
Planning Signals
What to keep visible while scoping
These notices are generated from the same priority and mapping files used by the workspace.
High-priority choices
-
Recommended Pricing Pattern
Pricing pattern changes catalog modeling, promotion rules, checkout totals, and merchandising operations.
-
Required Order Capture Model
Order capture model determines checkout, payment, and downstream fulfillment flow.
-
Recommended Purchase Mode
Purchase mode changes identity, cart persistence, and abandonment handling.
Related scope notices
-
Notice Order Capture ModelWhen: Quote-to-Order
Quote-to-order commerce often needs CRM opportunity and quote workflow coverage.
-
Notice Purchase ModeWhen: Account Required
Account-required checkout should align with the core registration model.
-
Notice Fulfillment ModelWhen: Digital Delivery
Digital delivery should align with the core file-handling capability.
-
Notice Returns ModelWhen: Self-Service Returns Portal
Self-service returns still need admin-side exception-resolution workflow support.
Start with catalog reality, not storefront aesthetics
A WebShop has to reflect the actual shape of the catalog. Physical goods, digital goods, services, and mixed catalogs create different buying questions. Variant complexity changes everything from filtering to merchandising to fulfillment. A simple product grid works for some stores, but not for a catalog where color, size, bundle logic, or configuration rules determine whether the customer can make a correct decision.
- Align catalog structure with real product types and variant depth.
- Explain whether the buying journey is browse-led, search-led, or guided.
- Use merchandising rules that make pricing, stock, and promotions legible.
Make checkout feel inevitable, not fragile
Cart persistence, guest checkout, account requirements, and order capture style all change how forgiving the store feels. Commerce teams often over-focus on button design while under-designing the purchase model itself. If the store serves repeat consumers, guest and account checkout may coexist. If the store sells high-consideration products or quote-led products, standard self-serve checkout may not be the right default.
- Clarify whether purchase is guest, account-based, express, assisted, or quote-led.
- Show how saved carts and cross-device continuity affect conversion.
- Treat the checkout model as a strategic operating choice, not just a UI pattern.
Fulfillment is part of the product promise
Customers do not experience the transaction as complete at payment. They experience it as complete when delivery, pickup, or digital access happens the way the store implied it would. That means the fulfillment model has to be visible in the page narrative. Shipping, pickup, digital delivery, or mixed fulfillment all create different expectations around timing, stock visibility, and order splitting.
- Surface inventory and availability with the level of precision your operation can actually support.
- Connect fulfillment choices to order splitting, carrier handoff, and delivery expectations.
- Use the page to set honest expectations before the customer pays.
Post-purchase trust decides whether revenue repeats
Tracking depth, returns workflow, and exchange handling determine whether the shop feels trustworthy after the sale. A store with only vague status updates asks customers to do the support work themselves. A store with milestone visibility, carrier-linked tracking, and exception handling shows that the operation is built for real-world delivery complexity.
- Design the order tracking experience for reassurance, not just status display.
- Choose returns and exchange flows that fit the margin profile and product category.
- Frame post-purchase service as a growth lever for repeat purchase and brand trust.
Decision Criteria
What To Evaluate First
Use these questions to decide which supported options deserve attention before a project is scoped.
- Does the catalog model fit your real product types, variants, and merchandising complexity?
- Is the checkout flow designed around how your customers actually commit to purchase?
- Can fulfillment promises, stock visibility, and delivery windows be supported operationally?
- Will tracking, returns, and exchanges increase confidence before and after the sale?
Call To Action
A WebShop is only as strong as the path from discovery to delivery.
If the catalog, checkout, fulfillment, and post-purchase journey are aligned, the store feels decisive and trustworthy. If they are disconnected, the brand absorbs friction at every step.