money-billUpcharges

Upcharges allow you to increase the price of a product based on specific customizations selected by the user.

Overview

The Upcharge system relies on a relationship between the Base Product (the item being customized) and a secondary Upcharge Product (a SKU within your e-commerce platform that represents the fee).

  1. Configuration: Upcharge logic is handled within the VU product libraries/configuration. You define which increments or selections trigger a price increase.

  2. Visual Feedback: When a customer selects a premium option in the VU Customizer, the displayed price of the product updates dynamically to reflect the total cost.

  3. Cart Behavior: When the customer clicks "Add to Cart," VU actually sends two items to the cart:

    • The Base Product (at its standard price).

    • The Upcharge Product (representing the extra cost).

How Upcharges Work

The Upcharge system functions by associating the Base Product with a secondary Upcharge Product (a separate SKU/Item).

  1. Product Setup:

    • You must have a "Base Product" (the main item).

    • You must also create specific "Upcharge Products" (dummy SKUs) in your e-commerce platform (e.g., Shopify, BigCommerce) to represent the cost of the add-on (e.g., "+$5.00 Premium Finish").

  2. Logic Configuration:

    • Inside the VU Admin (using JS libraries/configuration), you define which customer selections trigger the upcharge.

  3. The User Experience:

    • As the customer interacts with the VU Customizer and selects a premium option, the Displayed Price updates visually in real-time to reflect the total cost (Base + Upcharge).

Visual Merging (Front-End Implementation)

By default, the shopping cart will display the Base Product and the Upcharge Product as two separate line items.

If you prefer these to appear as a single item to the customer, this requires a visual adjustment within your e-commerce theme files. Your developer can group the items visually in the cart template so the customer perceives them as one unified product, even though they remain separate SKUs on the backend for inventory and accounting purposes.

Last updated