Difference between revisions of "Customer Order"
Stefanseiler (talk | contribs) |
Stefanseiler (talk | contribs) |
||
| Line 16: | Line 16: | ||
A customer-order is an immutable object on which each change has to create a new customer-order which eventually references to the old customer order. If the order at the moment of change has been partially fulfilled or billed, all corresponding objects have to become re-associated with the new customer-order. | A customer-order is an immutable object on which each change has to create a new customer-order which eventually references to the old customer order. If the order at the moment of change has been partially fulfilled or billed, all corresponding objects have to become re-associated with the new customer-order. | ||
== | == Basic flow of a Customer Order == | ||
[[File:Customer Order Lifecycle.png|1084x1084px]] | [[File:Customer Order Lifecycle.png|1084x1084px]] | ||
| Line 23: | Line 23: | ||
* as all status updates can be automatically synced to the customer, this reduces the status request phone-calls or irritations when the delivery of the ordered goods is not progressing as expected. | * as all status updates can be automatically synced to the customer, this reduces the status request phone-calls or irritations when the delivery of the ordered goods is not progressing as expected. | ||
* the supplier | * the supplier receives his money quicker as the bills can be sent over digitally to the customer where the bill checking process is no longer required at all. | ||
=== Order acceptance processes === | === Order acceptance processes === | ||
Once the order is created the supplier has to accept it. For trustworthy customers (not with a track record of unpaid bills) and orders under a certain threshold, this is typically set to automatic acceptance. Still you should define per customer certain thresholds above which you will be asked. Once the order is accepted, the regular fulfillment process starts. | |||
=== Order fulfillment processes === | === Order fulfillment processes === | ||
| Line 44: | Line 38: | ||
*fully billed positions | *fully billed positions | ||
== Structure of a customer order == | |||
== Status types of a customer order == | |||
=== Business process status === | |||
== Status of customer order positions == | |||
=== Fulfillment status === | |||
=== Billiing status === | |||
==Related articles== | ==Related articles== | ||
Revision as of 16:20, 3 June 2022
A customer order is a formal order from the customer which provides details of the amount and due date for a customer’s requirement of products. It is a legal document specifying the orders made by the customer. In addition, it states the amount of money to be paid, the due date on which the funds can be expected, and the quantity of the product delivered.
Related b-op data entities
Once a purchasing contract between a customer and a supplier has been signed, one or multiple purchases can be done by the customer based on this contract. A purchase order is created on the customer side, which documents to the supplier that he is ordered to deliver goods based on the contract conditions. This purchase order by the customer creates the customer order object on the suppliers side. Based on this order the suppliers takes all actions, like fulfillment, production or procurement with sub-suppliers to fulfill the customer order.
Related data entities:
- Purchasing Contracts
- Purchase Orders
- Deliveries
- Production Orders
- Bills
A customer-order is an immutable object on which each change has to create a new customer-order which eventually references to the old customer order. If the order at the moment of change has been partially fulfilled or billed, all corresponding objects have to become re-associated with the new customer-order.
Basic flow of a Customer Order
Order creation process
From a suppliers perspective customer orders can be created by manual creation in the suppliers identity or through digital interaction on the b-op network. Obviously the way over the b-op network reduces the work on the suppliers side dramatically as no manual work has to be invested any more. And even more the supplier benefits from having a b-op digital to place orders:
- as all status updates can be automatically synced to the customer, this reduces the status request phone-calls or irritations when the delivery of the ordered goods is not progressing as expected.
- the supplier receives his money quicker as the bills can be sent over digitally to the customer where the bill checking process is no longer required at all.
Order acceptance processes
Once the order is created the supplier has to accept it. For trustworthy customers (not with a track record of unpaid bills) and orders under a certain threshold, this is typically set to automatic acceptance. Still you should define per customer certain thresholds above which you will be asked. Once the order is accepted, the regular fulfillment process starts.
Order fulfillment processes
- partially delivered positions
- fully delivered positions
Order billing processes
**partially billed position
- fully billed positions