-
Notifications
You must be signed in to change notification settings - Fork 629
Description
Is your feature request related to a problem? Please describe.
Carriers in the US often have rate sheets with 2 or 3 separate prices, usually an intrastate, interstate, and "unknown" rate depending on the area code of the source and destination numbers. I've not been able to come up with a set up that uses the existing structure of rate cacher without defining multiple carrier entries for each actual carrier, adding a rate sheet to each of those, and trying to keep track of what carrierid is for what carrier with what rate pricing.
Describe the solution you'd like
I'd like the option to be able to define multiple ratesheets per carrier entry and then be able to select which ratesheet to choose from in the assorted script functions.
Implementation
- Component: Rate Cacher
- Type: Various parameters
Describe alternatives you've considered
None, but if there's a good proposal, I'll try it out.
Additional context
I've contemplated ways of adding this feature myself and I can if my plan makes sense to the development team. Biggest change will be in the carrier_cell struct. We can either just add a couple of additional members for the extra ratesheets, like what the account_cell struct has for wholesale vs retail. That will work, but it does impose an artificial limit on the number of ratesheets per carrier. Or we can change the existing members to arrays. The script functions will have to be modifed accordingly.