Difference between revisions of "Customer Order"
Stefanseiler (talk | contribs) |
Stefanseiler (talk | contribs) |
||
| (47 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[ | A customer order is a formal order from the customer in a vendors digital, which provides '''a list of ordered items.''' | ||
[[ | |||
For each of these items, these information are provided mandatorily | |||
* '''price information''' | |||
* [[Dev:Fulfillment plan|delivery plan]] - due dates, target location, risk handover agreement, ... ([[wikipedia:Incoterms|INCOTERMS]]) | |||
* '''payment plan''' - due dates for payments | |||
By default a customer order is a one-sided request declaration by the customer without legal binding to the supplier. By acceptance of the supplier side, it becomes a legal document (contract) with obligations for both sides of the business. This legal document has two "perspectives" in the b-op world. On the customer side, it is a [[purchase order]], on the supplier side it is a '''customer order.''' b-op keeps them in sync through the [[Dev:B-Op e-Business collaboration model|b-op 0e-Business collaboration model]] | |||
== Process == | |||
[[File:Customer_Order_Lifecycle.png|1124x1124px]] | |||
== Business Contexts == | |||
=== Regular purchase === | |||
== | === Purchase as part of a master purchasing contract === | ||
Once a purchasing contract between a customer and a supplier has been signed, one or multiple | Once a [[purchasing contract]] between a customer and a supplier has been signed, the customer can file one or multiple [[Purchase order|requests]] based on this contract. An isolated single request based on the contract is implemented by a [[purchase order]], which is created on the customer side. It documents to the vendor that he is ordered to deliver goods based on the contract conditions. When the customer`s digital is integrated over [https://www.b-op.com the b-op network] with the vendor`s digital, the customer`s procurement order automatically creates a ''Customer Order'' on the vendors side, bearing all the data the vendor requires. Based on this order the vendor takes all actions, like shipment, production or procurement with sub-suppliers to fulfill the customer order. | ||
Related data entities: | Related data entities: | ||
* Purchasing Contracts | * [[Purchasing contract|Purchasing Contracts]] | ||
* Purchase | *[[Purchase order|Purchase orders]] | ||
* | * [[Dev:Fulfillment Supply Chain|Fulfillment Supply Chains]] | ||
* Production Orders | * Production Orders | ||
* Bills | * 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. | 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. Also, if created over [https://www.b-op.com the b-op network] the customer has to give his consent to changes in the order as the customer order is linked to the procurement order on his side. | ||
== Basic flow of a Customer Order == | |||
== | === Order intake phase === | ||
[[ | The order intake phase bears all process steps until the order is fully accepted by the vendor organization and the [[fulfillment]] of the order starts. | ||
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 [https://www.b-op.com 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: | 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 [https://www.b-op.com 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. | * 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. | ||
Once the order is created the vendor has to accept it before the order is forwarded to [[fulfillment]]. 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. | |||
=== Order fulfillment phase === | |||
[[Fulfillment]] processes can range from simple [[Shipment order|shipment orders]] to very complex fulfillment collaboration scenarios using [[ZUGSEIL Lifecycle Management|product instance lifecycle tracking]]. Billing also is an important part of fulfillment, which can take place as soon as products have been shipped to the customer. | |||
== | ==Related articles== | ||
* [[Fulfillment]] | |||
*[[Purchasing & Procurement]] | |||
* [[Purchase order]] | |||
== Developer articles == | |||
* | * [[Dev:Customer Order]] - Developer insights on a customer order | ||
[[Category:Order Types and related objects]] | |||
[[Category:Glossary]] | |||
Latest revision as of 21:11, 9 November 2024
A customer order is a formal order from the customer in a vendors digital, which provides a list of ordered items.
For each of these items, these information are provided mandatorily
- price information
- delivery plan - due dates, target location, risk handover agreement, ... (INCOTERMS)
- payment plan - due dates for payments
By default a customer order is a one-sided request declaration by the customer without legal binding to the supplier. By acceptance of the supplier side, it becomes a legal document (contract) with obligations for both sides of the business. This legal document has two "perspectives" in the b-op world. On the customer side, it is a purchase order, on the supplier side it is a customer order. b-op keeps them in sync through the b-op 0e-Business collaboration model
Process
Business Contexts
Regular purchase
Purchase as part of a master purchasing contract
Once a purchasing contract between a customer and a supplier has been signed, the customer can file one or multiple requests based on this contract. An isolated single request based on the contract is implemented by a purchase order, which is created on the customer side. It documents to the vendor that he is ordered to deliver goods based on the contract conditions. When the customer`s digital is integrated over the b-op network with the vendor`s digital, the customer`s procurement order automatically creates a Customer Order on the vendors side, bearing all the data the vendor requires. Based on this order the vendor takes all actions, like shipment, production or procurement with sub-suppliers to fulfill the customer order.
Related data entities:
- Purchasing Contracts
- Purchase orders
- Fulfillment Supply Chains
- 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. Also, if created over the b-op network the customer has to give his consent to changes in the order as the customer order is linked to the procurement order on his side.
Basic flow of a Customer Order
Order intake phase
The order intake phase bears all process steps until the order is fully accepted by the vendor organization and the fulfillment of the order starts.
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.
Once the order is created the vendor has to accept it before the order is forwarded to fulfillment. 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.
Order fulfillment phase
Fulfillment processes can range from simple shipment orders to very complex fulfillment collaboration scenarios using product instance lifecycle tracking. Billing also is an important part of fulfillment, which can take place as soon as products have been shipped to the customer.
Related articles
Developer articles
- Dev:Customer Order - Developer insights on a customer order