E-mail notifications per-product
public
group: e-Commerce Module
davenotik@drupal.org - Wed, 2006-09-06 19:23
Hi. :)
I want to have store summaries e-mailed to an e-mail address other than the one in admin/settings (which is inherited on admin/store/settings). The person in charge of the store isn't necessarily the main administrator of the website.
In fact, the person in charge of one product isn't necessarily the one in charge of another. It'd be great to be able to specify where notifications are sent on a per-product basis.
This workable now, in the works, ...?
Thanks so much.
--Dave
Use cases?
Letting visitors and customers subscribe to products (news, support, ...) sounds reasonable to me.
Having a different shop admin (email) than site admin, too. Could be added to shop settings.
But I don't understand why you'd want to have a separate email for each product...?! I'm administering some online stores and I never had such a demand.
Daniel F. Kudwien
unleashed mind
Depends on who the "product manager(s)" is(are)
I can see where, depending on the size of a business/organization and/or the number of products/services being offered, an admin might want to "assign" the different products/services to different product/service managers.
In many medium and large size businesses/organizations, there are many different product/service managers.
So, e.g., the Toyota Camry product emails would go to the Toyota Camry product manager, the Toyota Corolla product emails would go to the Toyota Corolla product manager, etc. Ditto for services-related (consulting, law firms, etc.) businesses/organizations.
Walt Esquivel, MBA; MA; President, Wellness Corps; Captain, USMC (Veteran)
$50 Hosting Discount Helps Projects Needing Financing
Categories
I don't see products here, rather seem to be divisions. So we're actually speaking of a separated email per product category. So there could be one customer service department selling all paid services and another department selling some retail goods, both independently from each other. I can see, what's next: product access permissions per division/department/user role avoiding that dep A edits products of dep B.
Daniel F. Kudwien
unleashed mind
I see your point and here's another explanation...
You can call them divisions, yes, but the bottom line I'm trying to explain is that a product manager "can be thought of as a mini-CEO of the product and has overall responsibility for the success of a product." In my business life, I've been a product manager for various different products (and services also; services are often included under the heading of "products").
As such, I can see the case for business scenario where "the boss" wants different product managers to receive the different products' emails, respectively, so that each product manager can act accordingly to the product he/she owns. In other words, Product A's emails go to Product Manager A, Product B's emails go to Product Manager B, and so on.
Walt Esquivel, MBA; MA; President, Wellness Corps; Captain, USMC (Veteran)
$50 Hosting Discount Helps Projects Needing Financing
Level of assignment
So you mean it's required to assign the product manager already at product level?
My idea was to lift up the level to a category, since I could argue that you'd rather assign different product managers per category than per product. I'd bet that there aren't much product managers dealing with just one product out of one category. Of course we have to deal with taxonomy, so there aren't real categories involved and products can be assigned to more than one category. So assigning a product manager per category won't really work. Any other idea to minimize the product configuration? I'm a bit afraid of having to select a product manager for each and every product in a store. For 10 products - okay. But stores with, say 1.000+ products, won't feel comfortable with that.
Daniel F. Kudwien
unleashed mind
I didn't mean to make things too complicated
Hi Daniel,
I'm not sure what the original poster (davenotik) had in mind and I was only trying to show a few examples as to where I thought one might want product emails sent to different product managers.
As to the actual practicality of my comments, yes, I think making the code be able to send Product A's emails to the Product A Product Manager and Product B's emails to the Product B Product Manager might make things a bit more complex than what is practically needed.
I highly doubt 99% of Drupal administrators need the complexity I described in my post above. My comments are more academic than practical. I concur with your suggestion that "you'd rather assign different product managers per category than per product" and I also concur that "there aren't much product managers dealing with just one product out of one category."
Thank you for your comments!
Walt Esquivel, MBA; MA; President, Wellness Corps; Captain, USMC (Veteran)
$50 Hosting Discount Helps Projects Needing Financing
An Idea
I have a similar need. I'm creating a site to process orders for multiple suppliers. Customers will order and pay for products on my site, and the orders will be forwarded to the suppliers.
The stores module allows site members to submit and manage their own products. Maybe an order notification feature could be added. Are there any other modules that might be useful?
Update
Now that I've discussed options with sime, neclimdul, and gordon, I think we'll need the following features:
davenotik may want settings to allow e-mail notifications based on other transaction events.
Me to...
I have a need for this as well, but more instantaneous. We sell physical stuff from our website (CD's, Vinyl, merch) which we ship from our office, but we use 7Digital for our digital distribution, and I would like to create a new store that gives one interface for the user, but they purchase either physical or digital items and payment can be assigned to the correct API (either Worldpay for us, or 7Digital's own payment system).
The user can then instantly get their downloads, but physical orders are then processed by us.
Tane Piper
Digital Spaghetti