Builder Settings
Currency
Set the global display currency used across pricing interfaces so menu, cart, and order screens remain consistent for builders, testers, and end users.
A single setting influences multiple commerce-related components.
Price displays use this currency context throughout user flows.
Set once before heavy pricing content work to avoid QA drift.
Global pricing display behavior
Sets default display context
Defines which currency code is used when rendering app-level price values.
Aligns commerce interfaces
Ensures menu cards, cart summaries, and order views present coherent price context.
Supports QA consistency
Teams can validate pricing and formatting behavior against a single selected currency.
Prepares payment alignment
Currency selection can be coordinated with Stripe transaction strategy in later setup stages.
Set currency in three steps
Configuration flow
- Open App Settings & Deploy → Currency.
- Select the required currency code.
- Save changes.
Validation checklist
- Preview menu and cart after currency change.
- Confirm order summary displays match expected currency context.
- Align Stripe/payment setup afterward if needed.
Common mistakes to avoid
Changing currency late
Late currency changes can invalidate screenshots and QA expectations across pricing-heavy screens.
Skipping preview pass
Always re-check menu, cart, and order pages after changing currency to confirm display consistency.
Ignoring payment alignment
Coordinate display currency choices with payment provider setup to avoid operational confusion.