Skip to main content

Price Increases

When the Rabisu (upstream) cost rises, it does not automatically reflect on your customer's sell price — you decide. Product webhooks carry a notification only; current data is fetched with GET /products/{id}.

Pending decisions

When a cost increase is detected, a pending decision is created (without touching the sell price). You see them under Addon Modules > Rabisu > Increases & Decisions. Two sources:

  • Base product cost increased (product.price_changed).
  • Config option cost increased (the purchase price of an existing sub-option — RAM/CPU/disk — went up).

Decision options

For each pending decision:

  • Pass-through: Recompute the catalog sell price with the current cost + markup. If the policy is enabled, existing services are repriced too.
  • Absorb: Keep the sell price fixed and reduce your margin (the decision is closed).

Reprice policy

A layered reprice policy (product > group > global, default OFF) controls for which products existing services get repriced. If the policy is off, only the catalog price is updated; existing customers are not affected.

Existing-service repricing

When a reprice is applied:

  • Increases only, only active/suspended services are affected (no threshold).
  • Repricing uses the WHMCS-native UpdateClientProduct autorecalc=true — base product
    • config option charges are computed together by WHMCS's own logic.
  • The new amount takes effect on the next renewal + a notification email is sent to the customer.

Dry-run preview

The "Increase Preview" button reports, read-only, which existing services would be repriced at the current catalog price and the total periodic revenue difference. Nothing changes — you see the impact before deciding.