Example: you are a travel agency with a VAT rate of 19% on the trip and a VAT rate of 5% on the processing of the file (commission on sale). You will, therefore, have the VOYAGE product and the DOSSIER TREATMENT product with different VAT rates and also a differentiated total of several VAT rates.
Search
Showing posts with label *** Practical case studies. Show all posts
Showing posts with label *** Practical case studies. Show all posts
2018/04/15
I sell items with several different VAT rates, can Simple ERP help me?
Simple ERP perfectly manages several different VAT rates within a single document.
Example: you are a travel agency with a VAT rate of 19% on the trip and a VAT rate of 5% on the processing of the file (commission on sale). You will, therefore, have the VOYAGE product and the DOSSIER TREATMENT product with different VAT rates and also a differentiated total of several VAT rates.
Example: you are a travel agency with a VAT rate of 19% on the trip and a VAT rate of 5% on the processing of the file (commission on sale). You will, therefore, have the VOYAGE product and the DOSSIER TREATMENT product with different VAT rates and also a differentiated total of several VAT rates.
Multi-issue companies: consider working in multi-warehouses and/or multi-products
If you work in multiple sender companies, you may want to view the stock and/or goods movement status by sender company one day.
Moreover, in general, a company owns its own stock, but if it has decided to work jointly with another company in the same Simple CRM / ERP.
There are two solutions: either multi-warehouse or multi-product. It is up to you to choose the solution that suits you best.
MULTI ENTREPOT
This is the simplest solution: create one warehouse per company, since warehouse filtering is possible via PRODUCT
MULTI PRODUITS
Another possibility is to create several products, i.e. one per issuing company.
Example: the companies "Papeterie de Paris" and "Papeterie de Lyon" share the same Simple CRM because they are part of the same group.
They will, therefore, create in the PRODUCT category "Bic and Pen", the products
Ballpoint pen - Bic /Paris
Ballpoint pen - Bic /Lyon
Ballpoint pen - Parker /Paris
Ball style - Parker /Lyon
So, to see the stock status of Paris products, just go to PRODUCT and enter /Paris in the Product name and apply the filter.
This solution is to be chosen if companies pool their stocks.
Moreover, in general, a company owns its own stock, but if it has decided to work jointly with another company in the same Simple CRM / ERP.
There are two solutions: either multi-warehouse or multi-product. It is up to you to choose the solution that suits you best.
MULTI ENTREPOT
This is the simplest solution: create one warehouse per company, since warehouse filtering is possible via PRODUCT
MULTI PRODUITS
Another possibility is to create several products, i.e. one per issuing company.
Example: the companies "Papeterie de Paris" and "Papeterie de Lyon" share the same Simple CRM because they are part of the same group.
They will, therefore, create in the PRODUCT category "Bic and Pen", the products
Ballpoint pen - Bic /Paris
Ballpoint pen - Bic /Lyon
Ballpoint pen - Parker /Paris
Ball style - Parker /Lyon
So, to see the stock status of Paris products, just go to PRODUCT and enter /Paris in the Product name and apply the filter.
This solution is to be chosen if companies pool their stocks.
Customer case study: alarm installation and maintenance company and anti-intrusion systems
In this case of Simple CRM configuration study, data security is paramount.
Indeed, both commercial and technical information is confidential.
Therefore, each employee cannot have access:
only the customer records to which they can have access
that at their personal appointment
only a limited amount of information concerning customers
To illustrate our configuration, we will, therefore, imagine that there will be 3 users :
A Director General
A salesman
A technician
The Executive Director shall be an ADMINISTRATOR.
The commercial and the technician, because of the confidential nature of the data, will, of course, be users Projects.
As a reminder, the full explanation of user rights is available at http://www.simple-crm-support.com/2014/09/comment-limiter-lacces-dun-utilisateur.html
For each client there will be 4 families of information:
the customer's contact details
commercial information
technical information
the alarm unlock codes
The contact details of the customer can be found in the Company and/or Contact form. These record(s) can be created either by the general manager, or not by the sales representative, or by the technician.
Once the Company/Contact(s) form has been created, the general manager will create 3 non-public projects that he will appoint for example :
Company ID ID CONTACT / Company Name / Contact Name / Business File
Company ID ID CONTACT / Company Name / Contact Name / Technical File
Company ID ID CONTACT / Company Name / Contact Name / Alarm Codes
In the commercial file, the general manager will bind the commercial.
The general manager will bind the technician to the technical file.
To the project containing the alarm codes, it will not bind anyone because nobody can read the codes except the general manager.
In the commercial file, the commercial will create an Interaction, in which he will store quotes and order forms. It will not link this Interaction to the company/contact. Indeed, if it links this interaction to the company/contact, the documents will be visible from the company/contact file.
This poses no problem from a practical point of view, since in the list of its Interactions, the interaction is linked to the project. So to consult the customer's details, all the salesperson has to do is click on the name of the project to access the customer's details from the project:
The same technique is to be applied to the technical project, where an interaction not directly related to the company/contact will contain the technical documents.
Finally, the "Alarm Codes" project will simply contain the alarm codes written in the Project's memo field, this project being only accessible to the General Manager.
Indeed, both commercial and technical information is confidential.
Therefore, each employee cannot have access:
only the customer records to which they can have access
that at their personal appointment
only a limited amount of information concerning customers
To illustrate our configuration, we will, therefore, imagine that there will be 3 users :
A Director General
A salesman
A technician
The Executive Director shall be an ADMINISTRATOR.
The commercial and the technician, because of the confidential nature of the data, will, of course, be users Projects.
As a reminder, the full explanation of user rights is available at http://www.simple-crm-support.com/2014/09/comment-limiter-lacces-dun-utilisateur.html
For each client there will be 4 families of information:
the customer's contact details
commercial information
technical information
the alarm unlock codes
The contact details of the customer can be found in the Company and/or Contact form. These record(s) can be created either by the general manager, or not by the sales representative, or by the technician.
Once the Company/Contact(s) form has been created, the general manager will create 3 non-public projects that he will appoint for example :
Company ID ID CONTACT / Company Name / Contact Name / Business File
Company ID ID CONTACT / Company Name / Contact Name / Technical File
Company ID ID CONTACT / Company Name / Contact Name / Alarm Codes
In the commercial file, the general manager will bind the commercial.
The general manager will bind the technician to the technical file.
To the project containing the alarm codes, it will not bind anyone because nobody can read the codes except the general manager.
In the commercial file, the commercial will create an Interaction, in which he will store quotes and order forms. It will not link this Interaction to the company/contact. Indeed, if it links this interaction to the company/contact, the documents will be visible from the company/contact file.
This poses no problem from a practical point of view, since in the list of its Interactions, the interaction is linked to the project. So to consult the customer's details, all the salesperson has to do is click on the name of the project to access the customer's details from the project:
The same technique is to be applied to the technical project, where an interaction not directly related to the company/contact will contain the technical documents.
Finally, the "Alarm Codes" project will simply contain the alarm codes written in the Project's memo field, this project being only accessible to the General Manager.
Case study: call script management and prospect responses in a call center
This case study describes the implementation and management of a call campaign carried out by a call center, with Simple CRM.
Call scripts are set up using interaction models.
Once the call campaign is generated, the operators open each interaction, read the script and enter the prospects' answers.
1) Creation of interaction models
First, you must create an interaction model.
The subject of the interaction model describes in a few words the purpose of the prospecting.
In the "Note" field of the interaction, paste the call script.
Save the interaction pattern.
2) Creation of the prospecting campaign
Now create your prospecting campaign, using the interaction model you created in 1)
To create a prospecting campaign, please consult the prospecting campaign creation.
3) Read the call script and enter the prospect's answers
Once the campaign is generated by the manager, the remote operator connects to Simple CRM. It arrives directly on the Simple CRM Desktop, presenting the list of prospecting operations to perform.
For each prospecting interaction, the teleoperator :
opens the interaction
call the prospect on the phone (Simple CRM can dial the prospect's phone number for you)
reads the prospecting script
captures the prospect's response
modifies the state of the interaction according to the prospect's response: planning a prospect visit, brochure to send, quote to make,...
modifies the state of the interaction: "In progress" if a follow-up is to be given, "Completed" if the prospect is not interested.
records interaction
Call scripts are set up using interaction models.
Once the call campaign is generated, the operators open each interaction, read the script and enter the prospects' answers.
1) Creation of interaction models
First, you must create an interaction model.
The subject of the interaction model describes in a few words the purpose of the prospecting.
In the "Note" field of the interaction, paste the call script.
Save the interaction pattern.
2) Creation of the prospecting campaign
Now create your prospecting campaign, using the interaction model you created in 1)
To create a prospecting campaign, please consult the prospecting campaign creation.
3) Read the call script and enter the prospect's answers
Once the campaign is generated by the manager, the remote operator connects to Simple CRM. It arrives directly on the Simple CRM Desktop, presenting the list of prospecting operations to perform.
For each prospecting interaction, the teleoperator :
opens the interaction
call the prospect on the phone (Simple CRM can dial the prospect's phone number for you)
reads the prospecting script
captures the prospect's response
modifies the state of the interaction according to the prospect's response: planning a prospect visit, brochure to send, quote to make,...
modifies the state of the interaction: "In progress" if a follow-up is to be given, "Completed" if the prospect is not interested.
records interaction
Subscribe to:
Posts (Atom)









