Open JeffPyeBrook opened 10 years ago
I think this is worth thinking about. I think low-touch in core, maybe even as part of an abstract in a new class as we're re-thinking the shipping API (Maybe 4.0, 4.1?) and then extending in plugins would make great sense.
I have a plan for this and will start working on it. The new indicium capable shipping module I have would be a good test of the new features and backwards compatibility.
Add the ability of shoppers to select shipping add-ons like delivery confirmation, hold for delivery and insurance at checkout.
Add support in core where shipping is selected. The shipping plugins and modules would have the option to include it, the same way they have the option to include tracking support now.
One way to implement it would be to create a new default shipping module class.
Just like the getForm method that is used to present options to the admin we could have a getShippingOptions method that if defined would show a form controlled by the shipping module plugin. There would also be a saveShippingOptions method that would be called to store the data. The module would be responsible for all the storage.
That would make it a pretty light touch on core.
Thinking about options like these:![screenclip](https://f.cloud.github.com/assets/3098792/2304606/80298e84-a22a-11e3-9365-27fbe8d3b655.png)