When you run a cable company, it makes sense to have the ability to explicitly and exhaustively define the streets and street-ranges in the town so that you can never have an invalid address entered for service. I've just finished the basic implementation of that for the better billing project, along with the other major contact types (phones, email, shipping address). It's all inheritance heavy, so that you can reference a "location", be it a constrained address or a free-form one from a mailing address.
Also did the basic credit-card storage tables (planning on using public-key encryption for that storage so that only the payment-processing machine will be able to access the plaintext information).
Beginning work on the billing process itself. Probably tomorrow I'll work on the tabular cost setup system and mocking up discount systems and tokens to move a customer to alternate billing tables. Should likely also work on the "bundle" support. I'm meeting a client tomorrow to discuss what they need in their new billing system.
Pingbacks are closed.