Offering different prices to different customer tiers sounds simple until it's time to actually apply it. Someone has to remember that VVIP customers get 50% off, regular VIPs get 20% off, and everyone else pays full price — and remember to apply the right discount every single time a sale happens. Miss it once, and a loyal customer gets overcharged, or worse, a discount gets applied to someone who shouldn't have it.

In this tutorial, we'll build a VIP Customer Pricing system — a setup where each customer has a tier, and every transaction automatically calculates the correct final price based on that tier. No manual discount lookups, no remembering percentages.

---

Step 1: Create the Customer Table

Start with a table called Customer. Add the fields Name, Email, and Tier (Single Select, with options Regular, VIP, and VVIP).

Customer table with Name, Email, and Tier columns, Tier set as a single select field

Add a few customers with different tiers:

• Hannah Brooks — Regular
• Leo Fischer — VIP
• Grace Okafor — VVIP

Customer table showing three records for Hannah Brooks, Leo Fischer, and Grace Okafor with different tier values

---

Step 2: Create the Transaction Table

Create a new table called Transaction. Add a One-to-Many field linking each transaction to a Customer, an Amount field (Currency, USD), and a Date field.

Transaction table with Customer link, Amount in USD, and Date columns

Add a few sample transactions before setting up any pricing logic:

• Hannah Brooks — $100.00 — 2026-08-20
• Leo Fischer — $100.00 — 2026-08-21
• Grace Okafor — $100.00 — 2026-08-22

Transaction table listing three purchase records for Hannah Brooks, Leo Fischer, and Grace Okafor each at one hundred dollars

---

Step 3: Pull in the Customer's Tier

Before we can apply a discount, the Transaction table needs to know which tier the customer belongs to. Add a new column on the Transaction table, set its data type to Lookup, and pull the Tier field from the linked Customer.

Adding a Lookup column on the Transaction table pulling the Tier field from the linked Customer record

Every transaction now shows the customer's tier directly, without opening their record separately.

Transaction table showing the Tier column filled in automatically for each transaction based on the linked customer

---

Step 4: Add the Discounted Price Logic

Now for the actual pricing rule. Add another new column on the Transaction table, and set its data type to Custom Logic.

Adding a new Custom Logic column on the Transaction table

Describe the rule in plain language: if the Tier is VVIP, apply a 50% discount to the Amount; if the Tier is VIP, apply a 20% discount; otherwise, charge the full Amount.

Describing the conditional discount logic based on Tier for VVIP fifty percent off, VIP twenty percent off, and full price otherwise

Confirm the clarification screen once the system shows its interpretation, then click Save.

Clarification screen confirming the conditional pricing logic based on customer tier

Transaction table showing the Final Price column filled in automatically with the correct discount applied per customer tier

---

Step 5: Watch It Apply Automatically

Let's test it with a new sale. Add a transaction for Grace Okafor — $60.00 — 2026-08-26.

Adding a new transaction for Grace Okafor for sixty dollars on 26 August 2026

As soon as it's saved, the Tier pulls in as VVIP and the Final Price calculates itself at $30.00 — the 50% discount applied instantly, with zero manual input.

Transaction table showing Grace Okafor's new transaction with Tier and Final Price filled in automatically

---

Step 6: Handle a Tier Upgrade

Say Hannah Brooks gets upgraded from Regular to VIP. Update her Tier field on the Customer table.

Updating Hannah Brooks's Tier field on the Customer table from Regular to VIP

Notice that her past transaction stays at $100.00 — it isn't recalculated retroactively, since it reflects the price at the time of that sale. Any new transaction she makes from now on, however, will correctly apply the VIP discount.

Transaction table showing Hannah Brooks's past transaction unchanged while a new transaction reflects her updated VIP tier

---

Recap

What you built:

1. A Customer table with a Tier field
2. A Transaction table linked to Customer
3. A Lookup field pulling the customer's Tier into each transaction
4. A Custom Logic field applying the correct discount automatically based on that tier

This same pattern — pulling in a related value and applying conditional logic — works well beyond pricing tiers. Shipping fees based on region, commission rates based on role, or service charges based on membership level can all be built the exact same way.