... Configurable payment options and charges per vendor: ...
Hi Dennis: Will this be handled by Payment Director and something alike for shipping (configurable shipping methods/charges by) by Shipping Director? In this case it wouldn't mind that each vendor would have to provide their API Keys/Passwords/etc
Hi Dennis: Will this be handled by Payment Director and something alike for shipping (configurable shipping methods/charges by) by Shipping Director? In this case it wouldn't mind that each vendor would have to provide their API Keys/Passwords/etc
I've not had much time to look at 3.0 yet. I think per vendor payment options is doable; the only concern being what hezyz mentioned about "annoying for the end user.". But, I think that would only be the case if vendors used methods like PayPal which require a customer going to another site to complete the transaction. If vendors used methods like Authorize.NET, then it should not be a problem.
For shipping, I'd like to get a sense of what to expect with
a.m. wrote:
... Here are some things still to be done (after 3.00 release):
1. Configurable shipping options and rates (managed by a vendor).....
1. Configurable shipping options and rates (managed by a vendor).....
Shipping Director is a "Rate Calculation Method". Having a UI similar to Amazon's ability to select different methods for different packages requires UI changes, and the ability to process the returned form, and a place to store the vendor to shipping selection information and ability for vendor/admin to see and manage it. This may require core nopC support.