Architecture & Data Flow

The Wix eCommerce platform comprises multiple interconnected components. Together, these components enable sophisticated purchase flows for customers, as well as powerful sales and order management capabilities for business owners. This architecture provides flexibility and adaptability, allowing you to extend, customize, or replace elements of the purchase flow in accordance with your specific needs.

These are the platform’s main components:

Catalog (SPI)

Different businesses sell different types of products and services, so Wix provides a flexible interface for connecting externally managed catalogs with the Wix eCommerce platform through the Catalog SPI (Velo). A catalog can contain anything sellable, including physical products, services, gift cards, pricing plans, and singular, custom items created for individual transactions like specialized project work. Business solutions with varied offerings, such as Wix Bookings, Wix Stores, and Wix Restaurants, provide the Wix eCommerce platform with access to their catalogs via the Catalog SPI. This enables robust integration of the platform’s Cart and Checkout functionalities with diverse business types.


Once customers have found catalog items they want to purchase, they can add these items to their cart. A cart holds information about a potential transaction, including details about selected items, prices, and discounts, as well as the potential buyer. Site visitors can see their cart on the cart page. Developers can access and manage customer carts with the Cart API (REST, SDK, Velo) and the Current Cart API (Velo, SDK). Some purchasing flows bypass the cart entirely and proceed directly to checkout.


Checkout is the page where a buyer finalizes a purchase. A buyer can reach the checkout page from their cart, or directly – for example, by clicking a button on a catalog or product page. Each checkout holds information about the items to be purchased, price and tax summaries, shipping and billing information, any applied discounts, and more. The checkout experience can be customized, extended, and replaced to suit the needs of the business. Out of the box, the checkout page is tailored to the geographical location of the customer. Developers can access and manage checkout details and trigger checkout-related events with the Checkout API (REST, SDK, Velo).

Customization SPIs

You might need to integrate additional logic into your Cart or Checkout functionality. The eCommerce platform provides SPIs that enable you to integrate custom additional fees (REST, Velo), external shipping rates (REST, Velo), custom cart or checkout validations (REST, Velo), and custom discount triggers (Velo). Cart and Checkout determine the total cost of a purchase based on these customizations.


The Discounts component offers flexibility in pricing strategies. With the Discount Rules API (REST, SDK, Velo), or directly in a site’s dashboard, you can create and manage complex discount rules that are applied to cart or checkout items automatically. These rules are informed by:

  • Scopes (REST API, REST SPI), which define groups of catalog items that are eligible to qualify for discounts.
  • Custom triggers (REST, Velo), which determine the conditions under which discounts apply.


The Payments component facilitates payment processing for buyers. It’s integrated into the site’s checkout page for customer-initiated payments, and the dashboard, where business staff can process customer payments. Payments can also be triggered after an order has been made for unpaid, changed, or partially paid orders. Wix offers several options for handling payments, including Wix Payments for credit cards and other popular payment methods, Wix Pricing Plans for memberships, and for gift cards. Additional payment integration options can be found in the Wix App Market, and developers can create custom payment platform integrations using the Order Transactions API.

Thank You Page

Once a transaction is completed, the customer is redirected to a Thank You Page. This page acknowledges the successful payment and thanks the customer for their purchase.


Once a customer has committed to a purchase, an order is created. An order holds information about purchased items, price and tax summaries, shipping and billing information, any applied discounts, and the status of payment and fulfillment. In the dashboard, business staff can create new orders, view and edit existing orders, track fulfillment, and manage the payments cycle. The Orders API (REST, SDK, Velo) enables apps or site owners to customize management of the order lifecycle, including viewing, editing, approving, canceling, and charging.


The Fulfillment component is the process's concluding step, ensuring customers receive their purchases. It accommodates all types of goods or services, from physical and digital products to service provisions, ensuring a comprehensive fulfillment solution. A fulfillment object contains information about an order’s shipping provider, tracking details, and line items. Fulfillment details can be accessed and managed using the Order Fulfillments API (REST, SDK, Velo), allowing a high degree of customization.


The Notifications component plays a vital role in keeping site owners up-to-date with critical events throughout the buying process. This service sends alerts to site owners when specific events take place, such as a successful or failed payment, the creation of an order, or fulfillment events. Notifications keep site owners informed and help them stay on top of orders, ensuring a smooth buying experience for their customers.

Was this helpful?