Setting your customer pricing

Customer-facing prices and wholesale costs are controlled from /dashboard/reseller/plans. Each platform plan gets one row with four fields:

• Retail monthly — what your customer pays you per month. Blank = inherit the platform's monthly price.

• Retail annual — same, for annual cycles. Blank = inherit.

• Wholesale monthly — what you pay VICIfast per server-month. Blank = your tier's wholesale markdown applies to the effective retail.

• Wholesale annual — same, annual.

Tier-based default

Your tier has a wholesaleMarkdownBps setting (basis points; 2000 = 20% off). If you don't set an explicit wholesale price, wholesale is computed as retail × (1 − bps / 10000). So if your tier is at 20% markdown and the platform plan is $100/mo, leaving everything blank means you pay $80 and your customer pays $100.

Per-plan overrides

Use overrides for negotiated deals or cohort pricing. Common patterns:

• Higher retail — premium positioning. Wholesale stays at your tier's default; the spread is yours.

• Lower retail, same wholesale — promotional discount that you eat.

• Wholesale of 0 — trial-credit pattern. VICIfast doesn't charge you; the customer still pays you at retail. Pair this with a long trial for a "free for the first 30 days" promotion.

Drift safety

The cart-finalize flow re-resolves prices at debit time. If you change an override mid-checkout, the customer pays what their cart showed (the order's stored totalCents) — but the wholesale we debit you reflects the new override. You will never debit a customer more than they were quoted.

Wholesale-cannot-exceed-retail invariant

The form rejects saves where wholesale > retail. The dual-debit engine also refuses orders that would violate this at run time, so any drift between your config and the platform tier is fail-safe.