36.1 Products in AIUNIFY Funnels

AIUNIFY Funnels includes an Ecommerce workspace that lets you create products or services that can be sold through supported Landing Page payment components.

The authenticated Ecommerce navigation contains two primary areas:

Products Create and maintain the products or services that can be used by supported Landing Page checkout components.
Orders Review and manage orders generated through Landing Page checkout activity.

36.2 What a Product Record Represents

A Product record provides the commercial information AIUNIFY Funnels needs when a Landing Page checkout is submitted.

The user-facing product workflow manages these core values:

Name The name of the product or service being sold.
Gross Price The amount charged for the product or service.
Currency The three-character currency selected for the product.
Description Optional descriptive information about the product or service.

36.3 Products Can Represent Products or Services

The Products interface explicitly describes this workspace as a place where you can add products or services that can be sold directly from Landing Pages.

This means a Product record does not have to represent a physical item. Depending on your business, it can represent:

  1. A physical product.
  2. A professional service.
  3. A consultation.
  4. A digital offer.
  5. Another one-time item that fits the supported Landing Page checkout workflow.

36.4 Opening Products

Select Products from the Ecommerce section of the authenticated AIUNIFY Funnels navigation.

The Products workspace requires an authenticated user session.

36.5 Your Product Listing

The normal Products listing is loaded for the currently authenticated user.

The application orders the listing by the Product's most recent update date in descending order and paginates the results in groups of 10.

36.6 Product Search

The Products controller supports a search value that is matched against Product names.

Use a recognizable portion of the Product name when locating an existing record.

36.7 Products Workspace Actions

The confirmed Products interface contains the following operations:

Create product Opens the form for creating a new Product record.
Edit Opens an existing Product record for modification.
Delete Removes the selected Product record after confirmation.

If no records exist, the interface displays:

No products found

36.8 Product Currencies

The Product form loads its Currency choices from the application's configured product-currency list.

The selected currency is saved directly with the Product and later copied into an Order when that Product is purchased through a Landing Page.

36.9 Product Price Is Used During Checkout

When a checkout request identifies a valid Product, AIUNIFY Funnels takes the Product's saved price and uses it as the Order total.

This means you should verify the Gross Price before directing customers to a live Landing Page checkout.

36.10 Product Name Is Copied into the Order

At checkout, AIUNIFY Funnels copies the Product's current name into the Order's product_name value.

The Order therefore retains a Product-name snapshot from the time that Order was created.

36.11 Product Currency Is Copied into the Order

The selected Product currency is also copied into the new Order.

Payment processing then uses the Order's saved currency and total when working with the supported payment gateway.

36.12 Product Records and Order Records Are Different

Products define what can be sold. Orders record individual checkout attempts or transactions.

An Order stores information such as:

  1. Landing Page.
  2. Product name.
  3. Gateway.
  4. Total.
  5. Currency.
  6. Customer-submitted fields.
  7. Payment status.
  8. Order status.
  9. Browser, OS, and Device information.

36.13 Product Publishing Fields in the Data Model

The Product data model includes internal is_publish and is_trash fields.

However, the confirmed standard user create/edit workflow focuses on Name, Gross Price, Currency, and Description. Do not assume that internal model fields represent additional user controls unless they are actually presented in your deployed interface.

36.14 Products Are Used by Supported Builder Checkout Components

The application exposes an authenticated Product lookup that returns Product IDs and names belonging to the signed-in user.

This supports Builder functionality that needs to associate a Landing Page commerce component with an available Product.

36.15 Changing a Product

Changing a Product's Name, Gross Price, Currency, or Description affects the current Product record used for future checkout activity.

Because Orders store transaction values separately, always review the Order itself when investigating a historical customer transaction.

36.16 Before Using a Product on a Live Landing Page

  1. Confirm the Product Name.
  2. Confirm the Gross Price.
  3. Confirm the Currency.
  4. Add a useful Description where appropriate.
  5. Save the Product.
  6. Configure the appropriate payment credentials in Account Settings.
  7. Associate the intended Product with the supported Landing Page checkout component.
  8. Confirm the Landing Page's payment-success action.
  9. Perform a controlled checkout test before accepting real customer payments.

Operating principle: Products define the offer being sold through a Landing Page; verify the name, price, and currency before launch because those values become part of each resulting Order.

Write Your Comment