Level 7 · Which loyalty tier is she in?

and, or and the order of the branches

and is true only when both sides are true. or is true when at least one side is. Gold uses and and silver uses or, and that difference decides Dana’s tier:

spend >= 1000 and orders >= 5    # True and False  -> False
spend >= 500 or orders >= 10     # True or False   -> True

An if/elif/else chain stops at the first true branch, so the order matters. Put the most demanding tier first. If silver came first, a customer with $3,000 and 20 orders would match silver and the gold branch would never run.

if spend >= 1000 and orders >= 5:
    tier = "gold"
elif spend >= 500 or orders >= 10:
    tier = "silver"
else:
    tier = "bronze"

A customer with $200 spent and 12 orders lands in silver through the orders side of the or. A customer with $480 and 3 orders falls through to bronze.

When a rule mixes and and or in one line, add parentheses so the grouping is obvious to the next reader: (spend >= 1000 and orders >= 5) or vip. Python evaluates and before or, but nobody should have to remember that to review a business rule. Short, explicit conditions are also much easier to test one at a time when a customer asks why they ended up in the wrong tier.

Cleaning text before you show it

Names typed into a CRM arrive with stray spaces and random capitals. String methods return a new, cleaned string and can be chained:

"  dana WHITFIELD ".strip()           # 'dana WHITFIELD'
"  dana WHITFIELD ".strip().title()   # 'Dana Whitfield'

.title() capitalizes the first letter of each word and lowercases the rest. It’s fine for most names, but it isn’t perfect: “mcallister” becomes “Mcallister”, not “McAllister”. For a quick label that is usually acceptable; for a mailing you’d want a cleaner source.

Building the label

An f-string drops values into text. Anything inside the braces is evaluated, including method calls:

f"{name.strip().title()}: {tier}"     # 'Dana Whitfield: silver'

Common mistakes

• Swapping and and or between the tiers. The words in the policy (“and”, “or”) map directly to the Python keywords, so copy them across carefully.
• Using > where the rule says “at least”. $1,000 exactly is gold territory, so the test is >=.
• Putting silver before gold.
• Calling .title() but forgetting .strip(), which leaves spaces at the start of the label.