Purchase order - Revision history

Tijanabezbradica: /* Related Articles */

2025-04-10T12:39:23Z

← Older revision		Revision as of 12:39, 10 April 2025
Line 29:		Line 29:
	* [[Procure-To-Pay]]		* [[Procure-To-Pay]]
	* [[Purchasing contract]]		* [[Purchasing contract]]
			*[[App:Orders overview]]

	== Related development articles ==		== Related development articles ==

Stefanseiler at 11:40, 6 July 2024

2024-07-06T11:40:03Z

← Older revision		Revision as of 11:40, 6 July 2024
Line 22:		Line 22:

	== Structure ==		== Structure ==
	Each purchase order has the same structure containing a header and one or multiple positions. The '''header''' holds information, which regulates general information like target supplier and holds status information. On '''position''' and '''subposition''' level the information on the products to purchase and the [[~~Dev:~~Delivery ~~plan~~\|delivery ~~requirements~~]] are defined.		Each purchase order has the same structure containing a header and one or multiple positions. The '''header''' holds information, which regulates general information like target supplier and holds status information. On '''position''' and '''subposition''' level the information on the products to purchase and the requried [[Delivery option\|delivery options]] are defined.

	For more information please read up the [[Dev:Purchase order processing\|purchase order processing]] article.		For more information please read up the [[Dev:Purchase order processing\|purchase order processing]] article.

Stefanseiler: /* Interaction with suppliers / Contracting */

2023-11-06T17:38:25Z

Interaction with suppliers / Contracting

← Older revision		Revision as of 17:38, 6 November 2023
Line 4:		Line 4:
	Before a purchase order is created by the customer, the contracting phase is started, which means that customer and suppliers exchange offers until a mutual agreement is found ([[Purchasing contract\|purchase contract]]).		Before a purchase order is created by the customer, the contracting phase is started, which means that customer and suppliers exchange offers until a mutual agreement is found ([[Purchasing contract\|purchase contract]]).

	<u>Purchase order with contract reference (master contract based purchase order)</u>		<u>Purchase order, created with contract reference (master contract based purchase order)</u>

	Once this [[Purchasing contract\|purchase contract]] exists, a purchase order can be filed from the customer to the supplier with a reference to this contract. In this case, the supplier's digital only checks if the [[Customer Order\|customer order]] positions and conditions adhere to the contract and can auto-approve it.		Once this [[Purchasing contract\|purchase contract]] exists, a purchase order can be filed from the customer to the supplier with a reference to this contract. In this case, the supplier's digital only checks if the [[Customer Order\|customer order]] positions and conditions adhere to the contract and can auto-approve it.


	<u>Purchase order without contract reference (Individual purchase order)</u>
			<u>Purchase order, created without contract reference (Individual purchase order)</u>

	Purchase orders can also be filed to the supplier without a contract reference. In this case the positions and conditions of the purchase contract are considered to bear a purchasing contract proposal. The purchase order is showing a [[Customer Order\|customer order]] on the supplier side, which is subject to approval on the customer side. Once approved by the supplier, the system automatically forms a purchasing contract and links the purchase order and the customer order to this contract.		Purchase orders can also be filed to the supplier without a contract reference. In this case the positions and conditions of the purchase contract are considered to bear a purchasing contract proposal. The purchase order is showing a [[Customer Order\|customer order]] on the supplier side, which is subject to approval on the customer side. Once approved by the supplier, the system automatically forms a purchasing contract and links the purchase order and the customer order to this contract.

Stefanseiler at 17:04, 4 November 2023

2023-11-04T17:04:03Z

← Older revision		Revision as of 17:04, 4 November 2023
Line 1:		Line 1:
	[[File:Purchasing Process.png\|thumb\|Purchasing order contracting process]]A purchase order is a '''one sided declaration''' of a customer towards a supplier, which requires a contract to exist to be legally binding for the customer and the supplier side.		[[File:Purchasing Process.png\|thumb\|Purchasing order contracting process]]A purchase order is a '''one sided declaration''' of a customer towards a supplier, which requires a contract to exist to be legally binding for the customer and the supplier side.

	~~== Purchase orders in the b-op network ==~~
	When transmitted to a supplier by the [[Dev:B-Op supply chain network connector\|B-Op supply chain network connector]], a purchase order is transformed within the b-op network to a [[Customer Order\|customer order]].

	== Interaction with suppliers / Contracting ==		== Interaction with suppliers / Contracting ==
Line 17:		Line 14:

	For more information please read up the [[Dev:Purchase order processing\|purchase order processing]] article.		For more information please read up the [[Dev:Purchase order processing\|purchase order processing]] article.

			== Purchase orders in the b-op network ==
			When transmitted to a supplier by the [[Dev:B-Op supply chain network connector\|B-Op supply chain network connector]], a purchase order is transformed within the b-op network to a [[Customer Order\|customer order]].

			ZUGSEIL software also supports non b-op based supplier relationships. In this case, the [[Dev:B-Op supply chain network connector\|B-Op supply chain network connector]] always assumes that the supplier accepts the order and creates a contract and the expected deliveries and shipments as proposed by the customer.

	== Structure ==		== Structure ==
Line 29:		Line 31:
	== Related development articles ==		== Related development articles ==
	* [[Dev:Purchase order processing]] - Developer information page on purchase order		* [[Dev:Purchase order processing]] - Developer information page on purchase order
	*[[Dev:Purchasing contract negotiation process]] - b-op supports a fully digitalized RFP and negotiation process


	[[Category:Glossary]]		[[Category:Glossary]]

Stefanseiler at 17:00, 4 November 2023

2023-11-04T17:00:43Z

← Older revision		Revision as of 17:00, 4 November 2023
Line 1:		Line 1:
	A purchase order is a '''one sided declaration''' of a customer towards a supplier.		[[File:Purchasing Process.png\|thumb\|Purchasing order contracting process]]A purchase order is a '''one sided declaration''' of a customer towards a supplier, which requires a contract to exist to be legally binding for the customer and the supplier side.

	== ~~Structure~~ ==		== Purchase orders in the b-op network ==
	~~Each purchase order has the same structure containing~~ a ~~header and one or multiple positions. The '''header''' holds information, which regulates general information like target~~ supplier ~~and holds status information. On '''position''' and '''subposition''' level the information on the products to purchase and the delivery requirements are defined. For more information please read up~~ the [[Dev:~~Purchase~~ order ~~processing~~\|~~purchase~~ order ~~processing~~]] ~~article~~.		When transmitted to a supplier by the [[Dev:B-Op supply chain network connector\|B-Op supply chain network connector]], a purchase order is transformed within the b-op network to a [[Customer Order\|customer order]].

			== Interaction with suppliers / Contracting ==
			Before a purchase order is created by the customer, the contracting phase is started, which means that customer and suppliers exchange offers until a mutual agreement is found ([[Purchasing contract\|purchase contract]]).

			<u>Purchase order with contract reference (master contract based purchase order)</u>

			Once this [[Purchasing contract\|purchase contract]] exists, a purchase order can be filed from the customer to the supplier with a reference to this contract. In this case, the supplier's digital only checks if the [[Customer Order\|customer order]] positions and conditions adhere to the contract and can auto-approve it.

	~~The processing of a purchase order typically has these phases:~~

	* Contracting / ~~Negotiation phase~~		<u>Purchase order without contract reference (Individual purchase order)</u>
	* Creation
	* Fulfillment phase

	~~Detailed information on~~ purchase order ~~processing can be found in~~ [[~~Dev:Purchasing contract negotiation process~~\|~~this article~~]].		Purchase orders can also be filed to the supplier without a contract reference. In this case the positions and conditions of the purchase contract are considered to bear a purchasing contract proposal. The purchase order is showing a [[Customer Order\|customer order]] on the supplier side, which is subject to approval on the customer side. Once approved by the supplier, the system automatically forms a purchasing contract and links the purchase order and the customer order to this contract.

	~~== Creation ==~~		For more information please read up the [[Dev:Purchase order processing\|purchase order processing]] article.
	~~There are two ways of~~ purchase order ~~creation:~~

	* '''~~Individual purchase order~~''' ~~- once a buyer~~ and a seller have finalized their negotiations through the [[Dev:Purchasing contract negotiation process\|purchasing contract negotiation process]] an agreement has been reached, a [[purchasing contract]] is created.		== Structure ==
	* '''~~master contract based purchase order~~''' ~~- the contract has been prenegotiated~~ and the ~~purchase order is directly created based on it, so no [[Dev:Purchasing contract negotiation process\|negotiation phase]] is required.~~		Each purchase order has the same structure containing a header and one or multiple positions. The '''header''' holds information, which regulates general information like target supplier and holds status information. On '''position''' and '''subposition''' level the information on the products to purchase and the [[Dev:Delivery plan\|delivery requirements]] are defined.

	~~The purchase order is the business object~~ on the ~~customer side, the [[Customer Order\|customer order]] is the business object on the supplier side. They are bound together through~~ the [[Dev:~~B-Op supply chain network connector~~\|~~B-Op supply chain network connector~~]] ~~in the b-op network, if both parties have their [[Digital\|b-op digitals]] and they share enough trust~~.

	~~== Processing ==~~

			For more information please read up the [[Dev:Purchase order processing\|purchase order processing]] article.
	== Related Articles ==		== Related Articles ==

Stefanseiler at 16:43, 4 November 2023

2023-11-04T16:43:52Z

← Older revision		Revision as of 16:43, 4 November 2023
Line 1:		Line 1:
	A purchase order is a one sided declaration of a customer towards a supplier. ~~It contains~~ a header and one or multiple positions and		A purchase order is a '''one sided declaration''' of a customer towards a supplier.

			== Structure ==
			Each purchase order has the same structure containing a header and one or multiple positions. The '''header''' holds information, which regulates general information like target supplier and holds status information. On '''position''' and '''subposition''' level the information on the products to purchase and the delivery requirements are defined. For more information please read up the [[Dev:Purchase order processing\|purchase order processing]] article.

	~~which contains general purchasing positions.~~

Stefanseiler at 16:40, 3 November 2023

2023-11-03T16:40:16Z

← Older revision		Revision as of 16:40, 3 November 2023
Line 1:		Line 1:
	A purchase order is a one sided declaration of a customer towards a supplier, which ~~defines~~		A purchase order is a one sided declaration of a customer towards a supplier. It contains a header and one or multiple positions and

			which contains general purchasing positions.

Stefanseiler at 16:36, 3 November 2023

2023-11-03T16:36:46Z

← Older revision		Revision as of 16:36, 3 November 2023
Line 1:		Line 1:
	~~Once~~ a ~~buyer and~~ a ~~seller have finalized their negotiations through the [[Dev:Purchasing contract negotiation process\|purchasing contract negotiation process]] an agreement has been reached~~, ~~a [[purchasing contract]] is created.~~		A purchase order is a one sided declaration of a customer towards a supplier, which defines

	Depending on the [[Purchasing contract\|purchasing contract type]] one or multiple pairs of '''procurement orders''' and [[Customer Order\|customer orders]] can be created. The purchase order is the business object on the customer side, the customer order is the business object on the vendor side. They are bound together through [https://www.b-op.com the b-op network], if both parties have their [[Digital\|b-op digitals]] and they share enough trust.

	~~If there is not an existing~~ contract ~~that governs the relationship between~~ buyer and seller, the purchase order ~~can be used in place of a~~ contract. ~~Each~~ purchase order is ~~assigned it’s own unique number~~, ~~known as~~ the ~~purchase~~ order ~~number~~.		The processing of a purchase order typically has these phases:

			* Contracting / Negotiation phase
			* Creation
			* Fulfillment phase

			Detailed information on purchase order processing can be found in [[Dev:Purchasing contract negotiation process\|this article]].

			== Creation ==
			There are two ways of purchase order creation:

			* '''Individual purchase order''' - once a buyer and a seller have finalized their negotiations through the [[Dev:Purchasing contract negotiation process\|purchasing contract negotiation process]] an agreement has been reached, a [[purchasing contract]] is created.
			* '''master contract based purchase order''' - the contract has been prenegotiated and the purchase order is directly created based on it, so no [[Dev:Purchasing contract negotiation process\|negotiation phase]] is required.

			The purchase order is the business object on the customer side, the [[Customer Order\|customer order]] is the business object on the supplier side. They are bound together through the [[Dev:B-Op supply chain network connector\|B-Op supply chain network connector]] in the b-op network, if both parties have their [[Digital\|b-op digitals]] and they share enough trust.

			== Processing ==

	== Related Articles ==		== Related Articles ==

	* [[Procure-To-Pay]]		* [[Procure-To-Pay]]
	*[[Proposal Phase\|Proposal phase]]
	*[[Request for Proposal (RFP)]]
	* [[Purchasing contract]]		* [[Purchasing contract]]

	== Related development articles ==		== Related development articles ==
	* [[Dev:Purchase order]] - Developer information page on ~~purchaseorder~~		* [[Dev:Purchase order processing]] - Developer information page on purchase order
			*[[Dev:Purchasing contract negotiation process]] - b-op supports a fully digitalized RFP and negotiation process


	[[Category:Glossary]]		[[Category:Glossary]]

Stefanseiler at 16:24, 3 November 2023

2023-11-03T16:24:36Z

← Older revision		Revision as of 16:24, 3 November 2023
Line 1:		Line 1:
	Once a buyer and a seller have finalized their negotiations through the [[~~Request for Proposal (RFP)~~\|~~RFP phase~~]] ~~and/or [[Proposal Phase\|proposal phase]], and~~ an agreement has been reached ~~between them~~, a [[purchasing contract]] is created.		Once a buyer and a seller have finalized their negotiations through the [[Dev:Purchasing contract negotiation process\|purchasing contract negotiation process]] an agreement has been reached, a [[purchasing contract]] is created.

	Depending on the [[Purchasing contract\|purchasing contract type]] one or multiple pairs of '''procurement orders''' and [[Customer Order\|customer orders]] can be created. The purchase order is the business object on the customer side, the customer order is the business object on the vendor side. They are bound together through [https://www.b-op.com the b-op network], if both parties have their [[Digital\|b-op digitals]] and they share enough trust.		Depending on the [[Purchasing contract\|purchasing contract type]] one or multiple pairs of '''procurement orders''' and [[Customer Order\|customer orders]] can be created. The purchase order is the business object on the customer side, the customer order is the business object on the vendor side. They are bound together through [https://www.b-op.com the b-op network], if both parties have their [[Digital\|b-op digitals]] and they share enough trust.

Stefanseiler: /* Related Articles */

2023-11-03T00:01:28Z

← Older revision		Revision as of 00:01, 3 November 2023
Line 7:		Line 7:
	== Related Articles ==		== Related Articles ==

	* [[Proposal Phase\|Proposal phase]]		* [[Procure-To-Pay]]
			*[[Proposal Phase\|Proposal phase]]
	*[[Request for Proposal (RFP)]]		*[[Request for Proposal (RFP)]]
	* [[Purchasing contract]]		* [[Purchasing contract]]
	*[[Procure-To-Pay]]

	== Related development articles ==		== Related development articles ==