OFBiz › OFBiz - Dev

[jira] [Created] (OFBIZ-4725) Currently the system ecommerce is B2C add functions to enable B2B

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

5 messages Options

Nicolas Malin (Jira)

[jira] [Created] (OFBIZ-4725) Currently the system ecommerce is B2C add functions to enable B2B

Currently the system ecommerce is B2C add functions to enable B2B
-----------------------------------------------------------------

Key: OFBIZ-4725
URL: https://issues.apache.org/jira/browse/OFBIZ-4725
Project: OFBiz
Issue Type: Improvement
Components: order, specialpurpose/ecommerce
Affects Versions: SVN trunk
Reporter: Hans Bakker

Currently the ecommerce and order component is facilitating B2C (business to consumer) We suggest to add functions to allow also B2B Business to Business where a contact person uses the ecommerce on behalf of the company he works for, i.e. not entering quotes/orders for himself but entering orders for the company he works for. This relationship is already establsihed on the party component in the profile contact/related-account box.

These are functions which need change:

1. Registration : add the related company field and create a relationship between person and company.
2. Profile page: display an information of the related company: already shown
3. Checkout: if person who login has the related company, an order what person created will be an order of the related company.
4. Order History: adjust to be an order list for the related company.
5. Request entry : adjust to be the request list for the related company.
6. Quote entry: adjust to be the quote list for the related company.
7. Message : adjust to be the message list for the related company.
8. Shopping Lists : adjust to be the shopping list for the related company and adjust create a shopping list for the related company.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Nicolas Malin (Jira)

[jira] [Commented] (OFBIZ-4725) Currently the system ecommerce is B2C add functions to enable B2B

[ https://issues.apache.org/jira/browse/OFBIZ-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225708#comment-13225708 ]

Anne Jessel commented on OFBIZ-4725:
------------------------------------

I don't think points 4 through 8 are right. One person in a company shouldn't be able to see everything ever ordered by anyone else in the company. An employee working in the Australian branch shouldn't be able to see what the French branch have been ordering.

I think the order/quote/request related functions should only display the items relevant to the employee. The company details should be used for shipping and invoicing contacts, but not for display of historical items.

Does that make sense?

> Currently the system ecommerce is B2C add functions to enable B2B
> -----------------------------------------------------------------
>
> Key: OFBIZ-4725
> URL: https://issues.apache.org/jira/browse/OFBIZ-4725
> Project: OFBiz
> Issue Type: Improvement
> Components: order, specialpurpose/ecommerce
> Affects Versions: SVN trunk
> Reporter: Hans Bakker
>
> Currently the ecommerce and order component is facilitating B2C (business to consumer) We suggest to add functions to allow also B2B Business to Business where a contact person uses the ecommerce on behalf of the company he works for, i.e. not entering quotes/orders for himself but entering orders for the company he works for. This relationship is already establsihed on the party component in the profile contact/related-account box.
> These are functions which need change:
> 1. Registration : add the related company field and create a relationship between person and company.
> 2. Profile page: display an information of the related company: already shown
> 3. Checkout: if person who login has the related company, an order what person created will be an order of the related company.
> 4. Order History: adjust to be an order list for the related company.
> 5. Request entry : adjust to be the request list for the related company.
> 6. Quote entry: adjust to be the quote list for the related company.
> 7. Message : adjust to be the message list for the related company.
> 8. Shopping Lists : adjust to be the shopping list for the related company and adjust create a shopping list for the related company.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

Nicolas Malin (Jira)

[jira] [Commented] (OFBIZ-4725) Currently the system ecommerce is B2C add functions to enable B2B

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225835#comment-13225835 ]

Jacopo Cappellato commented on OFBIZ-4725:
------------------------------------------

In most common B2B scenarios the point #1 will have to consider at least few different use cases:

* the company running OFBiz doesn't allow customer companies (and their employees) to self register; the party for the customer company is manually created by backend users and then parties and userlogins for employees accounts are also created and sent to the users

* the company running OFBiz allows customer companies to self register; the user that registers the company will also get a user account (as primary contact); if additional employees are needed the primary contact will have some kind of dashboard from where she could invite other users

* allow users to self register as employees of an existing company; an admin will have to validate/activate their registration (after making sure that she is actually an employee of the company)

In general the system should never allow the user to self register and pretend to be an employee of company ABC to avoid security risks: I could register and see/place orders of that company.

I also agree with Anne that very few companies will be happy to show all the order information to all their employees; especially if the employee is a sales rep, she should only see the orders placed by her (in the most simplistic scenario) and/or the orders placed by sales rep under her (if a sales hierarchy is in place); and administrator will have to see the orders for the whole company (or division if he is only associated to a sub-division).

Nicolas Malin (Jira)

[jira] [Commented] (OFBIZ-4725) Currently the system ecommerce is B2C add functions to enable B2B

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242036#comment-13242036 ]

Hans Bakker commented on OFBIZ-4725:
------------------------------------

Pre-register.

most companies will only allow pre-registered users. What we can do is to allow registration, but create an approval function for it (Jacopo suggestion). Use the party status id for this. The company in registration is a simple text field which later in the approval process cab be linked to an existing account or a new account(partygroup) to be created.

See all company items.
4-8 will only list the items which were added by the related contact.(Anne and Jacopo)

Thanks you for the suggestions, if no further comments we wil start the implementation.

regards,
Hans

Nicolas Malin (Jira)

[jira] [Commented] (OFBIZ-4725) Currently the system ecommerce is B2C add functions to enable B2B

In reply to this post by Nicolas Malin (Jira)

[ https://issues.apache.org/jira/browse/OFBIZ-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242099#comment-13242099 ]

Pierre Smits commented on OFBIZ-4725:
-------------------------------------

I agree with Hans on this. A simple sanity check is whether the server or ISP name and the TLD of the email address matches the one registered with company. From there on, the backend person can additionally approve or reject.

Also I think that the self registered company and contacts should appear in the SFA module. If the registered company is not approved by the backend user it should be earmarked as prospect, not as customer. When the backend approver changes the status to customer all orders can be processed.

Regards,

Pierre