This guide has been created to teach the fundamentals of a sale/purchase order.
Note: in this session "Sale Orders", we will use another company Hongzhao as an example to explain how to create products, trade conditions and sale orders in ERP5. Hongzhao is also configured when we installed another ERP5 instance, the same way as presented in the tutorial "Configure your instance using ERP5 Configurator". So when you are practicing, please replace Hongzhao with the company you created when you configured your ERP5 instance.
Companies are always selling either or both a service or a products. The global process of selling a product or a service is the same and can be divided in three important phases:
The first is the order from the client to our company
The second is the delivering of the goods, or the performing of the service
The last is invoicing what has been performed or delivered.
This presentation will focus on the first part of the trade process which is the order.
In order to have clients, we already have seen that the companies have to prospect for new clients. This is why they use the CRM module of an ERP. The sale agent of the company contact the potential client and present what the company has to sell. If the client is interested, a sale opportunity is created, then the client will say “ok, I am interested, but please give me an offer”.
So an offer will be made, but what is exactly an offer? Is it a special document or not? Should we have a special module named “offer”?
In fact the offer is what will link a sale opportunity to the sale order. The offer is a pre-sale order, it is an order which is given to the customer, and if the customer accept the offer, it will then become a confirmed order. This is why an offer is not at all different from an order, it is just an order which haven't yet being done by the customer.
But every sale opportunity is not always linked to an offer, so sometimes there is no pre-trade process.
We will now see what is an order made of.
An order represents a movement of resource (goods, services) from a company to another. So in every order we will have a source (the supplier) and a destination (the buyer). But the destination can be more than one person or even organisation.
About the destination, We must distinguish three things:
The person or organisation which receives the goods, the person or organisation which is invoiced, and the person which is taking the decision to buy. This is why on an order we must have three fields to let us represent correctly the reality.
To illustrate those, we can take a look at how is organised the supermarket in France. The companies have buying centres in which they negotiate the prices for all of their brands. It allows them to have more power in the negotiation. But once they have bought one hundred thousand yoghurt, they ask for them to be delivered in small quantities in each of their distribution centre. So we already have a different destination point from the person which takes the decision to buy. Then we might have to invoice the buying centre, and not the distribution centre
We have also those kinds of distinction with the source of the movement.
With the source of the movement, we will have a person who is responsible for the offer which has been made. This person is responsible for the client, or at least for the conditions of the transaction. But it doesn't mean that this person is in the same organisation which will deliver the goods or this person is not the one which will deliver the service.
This is why we have a specific field about the organisation which is delivering. For example, companies as Nike don't produce their goods, they only work on design, marketing and on selling them. The entire production is handled by other companies. So those companies are the origin of the movement of goods which is done when an order is created.
But in such a case, the company which is invoicing is Nike.
Once we have correctly set up the origin and the destination of the resource, we must choose the products or the services we are talking about. But we need to see in detail what is a product or a service made of.
A product is any kind of goods sold by the company. It can be either the global package of a product, for example the product laptop will be composed of the laptop, the battery and the adaptor, but it can also be each part of a global package, for example a battery is a product, a power line is a product etc...
Services are the same but without goods. They represent a service which is provided by a company. For example a phone subscription is a service. An audit company will only sell services.
For both it is important to choose the right quantity unit. Quantity unit is how you measure a quantity of a specific good, or of a specific service. A service can be quantified in time, whereas a product can be counted in volume or in unit.
Products and services can have what is called a “variant”. For example we can ask for a financial service on 6, 12 or 18 months. Those can be considered has a variation of the service.
Products can also have variations. For example a shirt can be bought in many different sizes. In such a case we will have a single variant. But it is not the only variation of a shirt, we can have many different colours of the same shirt, so we will have two variations on the same product. But we can also have the logo on it which might change...
So many products might in fact be the same at the origin and must be represented with a unique document within the IT system. Otherwise it is not possible to manage your products or services correctly.
How are products differentiated from one to another is up to the company. One company will think that a shirt in a different colour is a different product, one will think that it is not different. There is no universal way to categorise the products and it will always be made according to the point of view of the company.
Conditions of a sale order are here to let you record the conditions on which you agreed with the other part.
For example you discuss with a buying centre, then they say “OK, we are referencing you as a supplier”. It is the time for you to create a specific trade condition for this organisation. Then each time you agree on a product, you will add a supply line.
The goods which are sold must be linked with a selling price. As we just have seen that a single product can have many different variations, the final price may not be the same. For example with clothes, if they are bigger, we might want to sell them a little bit more. So each variation can change the global price.
The other source of price variations is the quantity which is bought. The more we buy, the less they cost. So we must be able to create matrices with price and quantity for each of our products.
Once we have chosen the right price we will sell the product for, we might want to give a global discount on the total price of the order. But we might also want to apply a global discount only on a part of the products sold. This is why we have what we call base contribution and base application. Base contribution are a way of creating a group on which we will be able to apply a discount. For example we can create a base contribution category which can be named “de-stock” and on every product sold with the de-stock price, we will apply a global discount of 50% on the usual price.
On the other hand we might want to apply surcharge prices on order. For example an order which have to be delivered in top priority will cost more than an order which is made six months before the delivery date.
Taxes are handled the same way than Discount are. They are a percentage of the global price. Using Base contribution and Base application allow us to set up multiple taxes as Quebecois taxes. In Quebec there are two taxes, and the second one applied to the global price, and on the first tax. So finally you pay taxes on taxes :-) .
How will be done the payment is a very important condition of the order. You will have to choose the means of payment, but also the time when the payment is due. You can decide that the entire amount is due on a particular date, but you can also decide that a part of the global payment is due on a specific date, and that the other is due on another date.
This is very important to be able to handle it correctly, because it is often a reason why companies which have commands cannot continue and go in bankruptcy.
It is possible to have a different business process with each of your client. This is why you should be able to modify the entire order of when the documents are generated.
So finally we have this global work-flow. As we already said about the pre-trade phase, the Sale Order module of an ERP system is capable of generating two documents which look the same: an Offer and an Order. After you create and "Make" an Order document, it will be in the state "Offered", which means an Offer is made, but presented as an Order
If the clients "Accept" the Offer, it becomes a “Planned” Order, which allows you to mark the Order that you think will be done
. It is like an extension of the offered state with the idea that there is a high possibility that this order will be done. You can then create the planned order on the entire year to manage your working capital, FR or BFR.
"Placed" state means the client has made the Order, and your company has received it. But it doesn't mean that you accepted it
"Confirmed" order means that you will handle the order, that you accepted it
It is important to differentiate "Placed" orders from "Confirmed" orders since you might want to check if everything is in order with the client, or if you are capable of assuming the order etc.
Once you confirm the Sale Order, a related Sale Packing List will be created automatically for the next step of the trade process. We will talk about this in the next session.
As we have already seen, the trade process can be managed through work-lists, which you can access by opening "My Favourites" menu. These work-lists are here to summarize the information that you can find in the Sale Orders module itself.
Powered by Python, Zope and ERP5
(c) 2001-2011 Nexedi & ERP5 Community. All Rights Reserved.