Skip to main content

Introduction

This section provides a quick guide to the structure of Webround Commerce entities, illustrating their function and the logic behind their existence. The goal is not to delve into the technical details of APIs or specific data types, but to provide a descriptive overview of their role and how they are strategically positioned within the business flow. Understanding these entities allows for a clear vision of how the entire operational cycle is managed, from catalog to sale.

The Heart of the Catalog

In Webround Commerce, catalog management follows a precise hierarchy that reflects sales and warehouse logic. The structure is based on three levels: Product, Variant, and SKU.

The hierarchy follows this flow: Product (Template) -> Variant (Declination) -> SKU (Purchase Option)

Product: The General Template​

The Product acts as a general template. It identifies the merchandise in a generalized way (e.g., "Icon T-shirt") and defines common characteristics. It is at this level (along with the variant) that weight and dimensions for shipping are managed.

Options (e.g., "Size") are defined on the Product. These options specify the purchase choices available for that product. By defining a "Size" option with values "S, M, L, XL", we establish the matrix that will generate the final purchase points. It is possible to link multiple options in parallel to reconstruct complex choice matrices.

Variant: The Declination​

The Variant represents the specific declination of the product based on a primary commercial distinction, such as color.

  • Example: If the product is the "Icon T-shirt", the variants will be "White T-shirt", "Black T-shirt", "Green T-shirt".

Think of a shop window: what you see on display (the model in a specific color) is the variant.

SKU: The Purchase Option​

The SKU (Stock Keeping Unit) represents the final purchase option and derives directly from the variant crossed with the options defined on the product.

If the Variant is "White T-shirt" and the "XL" Size option is defined on the Product, the SKU will be the specific unit the customer adds to the cart. Unlike the higher levels, SKUs have a purely operational and managerial purpose:

  • Prices: The specific cost for that particular purchase option.
  • Inventory: The actual physical availability in warehouses.

In Summary: The T-shirt Example​

  1. Product: The "T-shirt" template where we define the "Size" option (S, M, L, XL).
  2. Variant: We create a variant for each color (White, Black, Green).
  3. SKU: For each variant (color), the system generates the purchase options based on the sizes. The "White T-shirt - XL Size" SKU is the object that manages the price and stock.

This structure allows for the rapid configuration of complex catalogs: by defining options only once on the product, they are used to automatically identify SKUs starting from every single created variant.

Limitless Flexibility​

The strength of this architecture lies in its adaptability. Webround Commerce catalogs virtually extend to any type of business: whether you run a clothing store, a perfumery, a wine shop, a restaurant, a dealership, or offer online consulting services, the Product -> Variant -> SKU structure is able to mold itself to your needs.

Thanks to this highly specializable and flexible hierarchy, Webround Commerce does not impose a rigid model, but provides the tools to precisely map every operational flow, ensuring that every single entity exactly reflects the reality of your physical or digital catalog.

Extensibility

Thanks to APIs, Webhooks, and other entities present in the management system, it is simple to adapt Webround Commerce for the generalized management of customers, products for sale, and warehouse management, even if you do not create a website or conduct online sales through it.

You can extend this tool as you wish, creating integrations of any kind. Save on the management overhead of your business thanks to Webround Commerce.