Add "type" to the pricings table, possibly as ENUM ("new", "renew", "transfer"). By default, all pricing would be set to "new".

Add the following columns to the pricings table after price: price_renew, price_transfer defaulting to NULL

Renewing Services

When services renew, they should renew at the price set for "renew" unless it is null, in which case it should fallback to the price defined in pricings.price

This allows 2 things:

• Staff can set a different price for new vs renewing services. For example, 1 month free trial, or promotion period, and then renewal at a different price
• Domains often renew at a different price, so it solves the problem with domain renewal pricing

UI Changes

When creating/editing a Package we should add a way so that staff can manually set a different renew price if they choose, but for simplicity the field should not be shown by default. Possibly a link under the "Options" section called "More"? Clicking the link would show the Renew column after the Price column.

OR we can always have a column for renew price, but must click something to activate it for each term. Like a Checkbox.

[x] [input field] (Check the box to set different renew price)

Checkbox unchecked, input field disabled, input box has a placeholder with description of checking the box to set a price.

We do not need to show the transfer price because the core will not use it. The domain manager will set the price for price, price_renew, and price_transfer on its own. The UI changes here are solely to support the renew price for other services.