Difference between revisions of "Customer Order"

From ZUGSEIL Wiki
Jump to navigation Jump to search
Line 17: Line 17:


== Lifecycle of a Customer Order ==
== Lifecycle of a Customer Order ==
Customer orders can be created by manual creation in the suppliers identity or through digital interaction on the b-op network.
[[File:Customer Order Lifecycle.png|1084x1084px]]


=== 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 [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.
* the supplier recieves 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.


<nowiki>*</nowiki>Order creation
=== Order acceptance processes ===
**Either manually (does not require acceptance)
 
**Or over b-op network (requires acceptance)
Customer order acceptance process enabled (set per customer?)
*Customer order acceptance process enabled (set per customer?)
*waiting for acceptance
**waiting for acceptance
*accepted --> Active
**accepted --> Active
Change request of <u>''already accepted''</u> customer order**Change requested accepted
*Change request of <u>''already accepted''</u> customer order**Change requested accepted
*Change request rejected
**Change request rejected
*Change accepted order positions (one position 0 qtty == cancel positions, all positions 0 qtty --> entire order cancelled)
**Change accepted order positions (one position 0 qtty == cancel positions, all positions 0 qtty --> entire order cancelled)
 
*Delivery status
=== Order fulfillment processes ===
**partially delivered positions
 
** fully delivered positions
*partially delivered positions
*Billed status**partially billed position
* fully delivered positions
**fully billed positions
 
=== Order billing processes ===
 
<nowiki>**</nowiki>partially billed position
*fully billed positions





Revision as of 11:03, 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.

Lifecycle of a Customer Order

Customer Order Lifecycle.png

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 recieves 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

Customer order acceptance process enabled (set per customer?)

  • waiting for acceptance
  • accepted --> Active

Change request of already accepted customer order**Change requested accepted

  • Change request rejected
  • Change accepted order positions (one position 0 qtty == cancel positions, all positions 0 qtty --> entire order cancelled)

Order fulfillment processes

  • partially delivered positions
  • fully delivered positions

Order billing processes

**partially billed position

  • fully billed positions


Related articles