Details
-
Type: New Feature
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 5.5.0-b1
-
Component/s: None
-
Labels:None
Description
Some users have asked for the ability to set an override price to the package price when the service is added so that they can make changes to the package pricing without affecting services that use that pricing.
The designed solution to the pricing change problem is to simply create a new package for the new pricing model, and retire the old package (make inactive or restricted).
The solution would be to simply record the package pricing as the override price when the service is added if the package is set to do so.
However, this opens another can of worms.
- Reporting: How can staff tell when they're losing money on a particular service (e.g. .com domain orders for $5, now costs $8 to resell, is a loss of $3)?
- Updating: How can staff mass update a number of services. Perhaps all at once, or selectively in bulk?
Issue Links
- blocks
-
CORE-4467 Domain Manager: Add option to set override price on added domains
- Closed
I'm not sure how reporting would be an issue. The ability to update the price enmasse for services that have a price override set does not currently exist, and could potentially be done at a later time if necessary. Admins who set the package to set a price override on provisioning, unless they don't understand how it works, will be unlikely to need to change the price in the future because they are the ones who expect the customer to be "locked in" to the same price they signed up with.