Stulipan Tudástár - User contributions [en]

Order

2022-03-26T13:28:25Z

Tulipanf: /* Funkciók és logika */

= Gondolatok =

Tudnivalók az Order-ről...

== Funkciók és logika ==

{| class="wikitable"
|-
! Funkció !! Leírás !! Egyéb
|-
| '''getTotalAfterSale()''' || A termékek eladási árával kalkulál. Tehát, ha egy termék akciós áron forgalmazzuk, akkor az eladási ár = akciós ár. ||
|-
| '''getTotalAmountToPay()''' || Ez a fizetendő összeg. <pre>totalAmountToPay = totalAfterSale + shippingFeeToPay + paymentFeeToPay + schedulingPrice</pre> ||
|-
| '''getAmountPaidByCustomer()''' || Az összeg, amit a vásárló kifizetett. Jelenleg, ez a rendelés teljes összege (nincs részleges fizetés.) ||
|-
| ''' ''' || ||
|-
| ''' ''' || ||
|-
| ''' ''' || ||
|}

Order

2022-03-26T13:27:53Z

Tulipanf: /* Funkciók és logika */

= Gondolatok =

Tudnivalók az Order-ről...

== Funkciók és logika ==

{| class="wikitable"
|-
! Funkció !! Leírás !! Egyéb
|-
| '''getTotalAfterSale()''' || A termékek eladási árával kalkulál. Tehát, ha egy termék akciós áron forgalmazzuk, akkor az eladási ár = akciós ár. ||
|-
| '''getTotalAmountToPay()''' || Ez a fizetendő összeg. <pre>totalAmountToPay = totalAfterSale + shippingFeeToPay + paymentFeeToPay + schedulingPrice</pre> ||
|-
| '''getAmountPaidByCustomer()''' || Az összeg, amit a vásárló kifizetett. Jelenleg, ez a rendelés teljes összege (nincs részleges fizetés.) ||
|-
| '''Example''' || Example ||
|-
| '''Example''' || Example ||
|-
| '''Example''' || Example ||
|}

Order

2022-03-26T13:27:05Z

Tulipanf: /* Funkciók és logika */

= Gondolatok =

Tudnivalók az Order-ről...

== Funkciók és logika ==

{| class="wikitable"
|-
! Funkció !! Leírás !! Egyéb
|-
| '''getTotalAfterSale()''' || A termékek eladási árával kalkulál. Tehát, ha egy termék akciós áron forgalmazzuk, akkor az eladási ár = akciós ár. ||
|-
| '''getTotalAmountToPay()''' || Ez a fizetendő összeg. totalAmountToPay = totalAfterSale + shippingFeeToPay + paymentFeeToPay + schedulingPrice ||
|-
| '''getAmountPaidByCustomer()''' || Az összeg, amit a vásárló kifizetett. Jelenleg, ez a rendelés teljes összege (nincs részleges fizetés.) ||
|-
| '''Example''' || Example ||
|-
| '''Example''' || Example ||
|-
| '''Example''' || Example ||
|}

Order

2022-03-26T13:26:38Z

Tulipanf: /* getTotalAmountToPay() */

= Gondolatok =

Tudnivalók az Order-ről...

== Funkciók és logika ==

=== getTotalAfterSale() ===

A termékek eladási árával kalkulál. Tehát, ha egy termék akciós áron forgalmazzuk, akkor az eladási ár = akciós ár.

=== getTotalAmountToPay() ===

Ez a fizetendő összeg. totalAmountToPay = totalAfterSale + shippingFeeToPay + paymentFeeToPay + schedulingPrice

{| class="wikitable"
|-
! Funkció !! Leírás !! Egyéb
|-
| '''getTotalAfterSale()''' || A termékek eladási árával kalkulál. Tehát, ha egy termék akciós áron forgalmazzuk, akkor az eladási ár = akciós ár. ||
|-
| '''getTotalAmountToPay()''' || Ez a fizetendő összeg. totalAmountToPay = totalAfterSale + shippingFeeToPay + paymentFeeToPay + schedulingPrice ||
|-
| '''getAmountPaidByCustomer()''' || Az összeg, amit a vásárló kifizetett. Jelenleg, ez a rendelés teljes összege (nincs részleges fizetés.) ||
|-
| '''Example''' || Example ||
|-
| '''Example''' || Example ||
|-
| '''Example''' || Example ||
|}

Order

2022-03-26T13:21:52Z

Tulipanf: /* Funkciók és logika */

Order

2022-03-26T13:17:38Z

Tulipanf: Created page with "= Gondolatok = Tudnivalók az Order-ről... == Funkciók és logika == === getTotalAfterSale() === A termékek eladási árával kalkulál. Tehát, ha egy termék akciós áron forgalmazzuk, akkor az eladási ár = akciós ár. === getTotalAmountToPay() === Ez a fizetendő összeg. totalAmountToPay = totalAfterSale + shippingFeeToPay + paymentFeeToPay + schedulingPrice"

Main Page

2022-03-26T13:11:02Z

Tulipanf:

[[Stulipan| Stulipan tudástár]]

[[Checkout]]

[[Order]]

* [[Same as shipping logic]]

== Getting started ==
Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]

Checkout

2022-03-26T07:34:14Z

Tulipanf: /* Step1 - Delivery Address */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

Submitting the CustomerBasic form this happens:
<pre>CheckoutSnippets::setCustomer() >> CheckoutBuilder::setCustomerBasic() >> StoreEvent::CUSTOMER_CREATE & StoreEvent::CUSTOMER_UPDATE
</pre>

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''ABANDONED CARTS vs. ABANDONED CHECKOUTS'''

https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''

Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

'''Complete the checkout'''

After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

'''Checkout - Order viszony'''

Checkout -> submit -> order kreala >> lesz ilyen: checkout.order

* csak az Ordernek van Transactionje. Miert? Azert mert, CC fizetes eseten tobb tranzakcio is varhato (authorization, void/capture, partial/refund). Ez mind az Orderhez kell kotni.
* ez esetben, ha COD a fizetes, akkor egy Transaction letezik.
* ha CC fizetes, es nem sikeres, akkor lesz egy Checkout, es egy Order -> mindketto Abandoned
** egy honap utan torlom az Ordert. A Checkout megmarad statisztika miatt.
** ha sikeres, akkor torlom a Checkoutot (es Cartot)

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

= Egyeb =

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-03-26T07:33:10Z

Tulipanf: /* Step1 - Delivery Address */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet

:: Submitting the CustomerBasic form this happens:
::<pre>CheckoutSnippets::setCustomer() >> CheckoutBuilder::setCustomerBasic() >> StoreEvent::CUSTOMER_CREATE & StoreEvent::CUSTOMER_UPDATE
</pre>

* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''ABANDONED CARTS vs. ABANDONED CHECKOUTS'''

https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''

Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

'''Complete the checkout'''

After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

'''Checkout - Order viszony'''

Checkout -> submit -> order kreala >> lesz ilyen: checkout.order

* csak az Ordernek van Transactionje. Miert? Azert mert, CC fizetes eseten tobb tranzakcio is varhato (authorization, void/capture, partial/refund). Ez mind az Orderhez kell kotni.
* ez esetben, ha COD a fizetes, akkor egy Transaction letezik.
* ha CC fizetes, es nem sikeres, akkor lesz egy Checkout, es egy Order -> mindketto Abandoned
** egy honap utan torlom az Ordert. A Checkout megmarad statisztika miatt.
** ha sikeres, akkor torlom a Checkoutot (es Cartot)

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

= Egyeb =

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-03-26T07:32:23Z

Tulipanf: /* Step1 - Delivery Address */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
::<pre>CheckoutSnippets::setCustomer() >> CheckoutBuilder::setCustomerBasic() >> StoreEvent::CUSTOMER_CREATE & StoreEvent::CUSTOMER_UPDATE
</pre>

* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''ABANDONED CARTS vs. ABANDONED CHECKOUTS'''

https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''

Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

'''Complete the checkout'''

After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

'''Checkout - Order viszony'''

Checkout -> submit -> order kreala >> lesz ilyen: checkout.order

* csak az Ordernek van Transactionje. Miert? Azert mert, CC fizetes eseten tobb tranzakcio is varhato (authorization, void/capture, partial/refund). Ez mind az Orderhez kell kotni.
* ez esetben, ha COD a fizetes, akkor egy Transaction letezik.
* ha CC fizetes, es nem sikeres, akkor lesz egy Checkout, es egy Order -> mindketto Abandoned
** egy honap utan torlom az Ordert. A Checkout megmarad statisztika miatt.
** ha sikeres, akkor torlom a Checkoutot (es Cartot)

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

= Egyeb =

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-03-26T07:25:16Z

Tulipanf: /* Step1 - Delivery Address */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet >> CheckoutSnippets::setCustomer() > CheckoutBuilder::setCustomerBasic() > StoreEvent::CUSTOMER_CREATE & StoreEvent::CUSTOMER_UPDATE
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''ABANDONED CARTS vs. ABANDONED CHECKOUTS'''

https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''

Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

'''Complete the checkout'''

After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

'''Checkout - Order viszony'''

Checkout -> submit -> order kreala >> lesz ilyen: checkout.order

* csak az Ordernek van Transactionje. Miert? Azert mert, CC fizetes eseten tobb tranzakcio is varhato (authorization, void/capture, partial/refund). Ez mind az Orderhez kell kotni.
* ez esetben, ha COD a fizetes, akkor egy Transaction letezik.
* ha CC fizetes, es nem sikeres, akkor lesz egy Checkout, es egy Order -> mindketto Abandoned
** egy honap utan torlom az Ordert. A Checkout megmarad statisztika miatt.
** ha sikeres, akkor torlom a Checkoutot (es Cartot)

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

= Egyeb =

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-03-12T09:51:24Z

Tulipanf: /* Shopify CHECKOUT attributes */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''ABANDONED CARTS vs. ABANDONED CHECKOUTS'''

https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''

Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

'''Complete the checkout'''

After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

'''Checkout - Order viszony'''

Checkout -> submit -> order kreala >> lesz ilyen: checkout.order

* csak az Ordernek van Transactionje. Miert? Azert mert, CC fizetes eseten tobb tranzakcio is varhato (authorization, void/capture, partial/refund). Ez mind az Orderhez kell kotni.
* ez esetben, ha COD a fizetes, akkor egy Transaction letezik.
* ha CC fizetes, es nem sikeres, akkor lesz egy Checkout, es egy Order -> mindketto Abandoned
** egy honap utan torlom az Ordert. A Checkout megmarad statisztika miatt.
** ha sikeres, akkor torlom a Checkoutot (es Cartot)

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

= Egyeb =

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-03-12T09:47:07Z

Tulipanf: /* Shopify CHECKOUT attributes */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''ABANDONED CARTS vs. ABANDONED CHECKOUTS'''

https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''

Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

'''Complete the checkout'''

After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

'''Checkout - Order viszony'''

Checkout -> submit -> order kreala >> lesz ilyen: checkout.order

* csak az Ordernek van Transactionje. Miert? Azert mert, CC fizetes eseten tobb tranzakcio is varhato (authorization, void/capture, partial/refund). Ez mind az Orderhez kell kotni.
* ez esetben, ha COD a fizetes, akkor egy Transaction letezik.
* ha CC fizetes, es nem sikeres, akkor lesz egy Checkout, es egy Order -> mindketto Abandoned
** egy honap utan torlom az Order. A checkout megmarad statisztika miatt.

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

= Egyeb =

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-03-12T09:46:50Z

Tulipanf: /* Shopify CHECKOUT attributes */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''ABANDONED CARTS vs. ABANDONED CHECKOUTS'''

https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''

Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

'''Complete the checkout'''

After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

'''Checkout - Order viszony'''

Checkout -> submit -> order kreala >> lesz ilyen: checkout.order

* csak az Ordernek van Transactionje. Miert? Azert mert, CC fizetes eseten tobb tranzakcio is varhato (authorization, void/capture, partial/refund). Ez mind az Orderhez kell kotni.
* ez esetben, ha COD a fizetes, akkor egy Transaction letezik.
* ha CC fizetes, es nem sikeres, akkor lesz egy Checkout, es egy Order -> mindketto Abandoned
** egy honap utan torlom az Order. A checkout megmarad statisztika miatt.

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

= Egyeb =

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-03-12T09:46:35Z

Tulipanf: /* Shopify CHECKOUT attributes */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''ABANDONED CARTS vs. ABANDONED CHECKOUTS'''

https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''

Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

'''Complete the checkout'''

After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

'''Checkout - Order viszony'''

Checkout -> submit -> order kreala >> lesz ilyen: checkout.order

# csak az Ordernek van Transactionje. Miert? Azert mert, CC fizetes eseten tobb tranzakcio is varhato (authorization, void/capture, partial/refund). Ez mind az Orderhez kell kotni.
# ez esetben, ha COD a fizetes, akkor egy Transaction letezik.
# ha CC fizetes, es nem sikeres, akkor lesz egy Checkout, es egy Order -> mindketto Abandoned
## egy honap utan torlom az Order. A checkout megmarad statisztika miatt.

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

= Egyeb =

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-03-12T09:46:11Z

Tulipanf: /* Shopify CHECKOUT attributes */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''ABANDONED CARTS vs. ABANDONED CHECKOUTS'''

https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''

Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

'''Complete the checkout'''

After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

'''Checkout - Order viszony'''

Checkout -> submit -> order kreala >> lesz ilyen: checkout.order

# csak az Ordernek van Transactionje. Miert? Azert mert, CC fizetes eseten tobb tranzakcio is varhato (authorization, void/capture, partial/refund). Ez mind az Orderhez kell kotni.
# ez esetben, ha COD a fizetes, akkor egy Transaction letezik.
# ha CC fizetes, es nem sikeres, akkor lesz egy Checkout, es egy Order -> mindketto Abandoned
## egy honap utan torlom az Order. A checkout megmarad statisztika miatt.

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

= Egyeb =

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-03-12T09:45:41Z

Tulipanf: /* Shopify CHECKOUT attributes */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''ABANDONED CARTS vs. ABANDONED CHECKOUTS'''

https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''

Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

'''Complete the checkout'''

After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

'''Checkout - Order viszony'''

Checkout -> submit -> order kreala >> lesz ilyen: checkout.order
- csak az Ordernek van Transactionje. Miert? Azert mert, CC fizetes eseten tobb tranzakcio is varhato (authorization, void/capture, partial/refund). Ez mind az Orderhez kell kotni.
- ez esetben, ha COD a fizetes, akkor egy Transaction letezik.
- ha CC fizetes, es nem sikeres, akkor lesz egy Checkout, es egy Order -> mindketto Abandoned
- egy honap utan torlom az Order. A checkout megmarad statisztika miatt.

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

= Egyeb =

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T10:16:42Z

Tulipanf: /* Egyeb */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''ABANDONED CARTS vs. ABANDONED CHECKOUTS'''

https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''

Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

'''Complete the checkout'''

After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

= Egyeb =

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T10:16:27Z

Tulipanf: /* Shopify CHECKOUT attributes */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''ABANDONED CARTS vs. ABANDONED CHECKOUTS'''

https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''

Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

'''Complete the checkout'''

After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T10:16:10Z

Tulipanf: /* CART >> CHECKOUT >> ORDER relationship */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''ABANDONED CARTS vs. ABANDONED CHECKOUTS'''

https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''

Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

'''Complete the checkout'''

After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T10:15:53Z

Tulipanf: /* CART >> CHECKOUT >> ORDER relationship */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''ABANDONED CARTS vs. ABANDONED CHECKOUTS'''

https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''

Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

'''Complete the checkout'''

After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T10:15:14Z

Tulipanf: /* CART >> CHECKOUT >> ORDER relationship */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''Abandoned Carts vs. Abandoned Checkouts'''

https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''

Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

'''Complete the checkout'''

After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T10:14:52Z

Tulipanf: /* CART >> CHECKOUT >> ORDER relationship */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''FROM SHOPIFY'''

'''Abandoned Carts vs. Abandoned Checkouts'''

https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''

Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

'''Complete the checkout'''

After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T10:14:38Z

Tulipanf: /* CART >> CHECKOUT >> ORDER relationship */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''FROM SHOPIFY'''

'''Abandoned Carts vs. Abandoned Checkouts'''
https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''

Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

'''Complete the checkout'''

After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T10:14:07Z

Tulipanf: /* Abandoned Carts vs. Abandoned Checkouts */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''

Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

'''Complete the checkout'''

After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T10:13:40Z

Tulipanf: /* Shopify CART attributes */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''

Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

'''Complete the checkout'''

After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Abandoned Carts vs. Abandoned Checkouts ==
https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T10:13:06Z

Tulipanf: /* Shopify CART attributes */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

=== Shopify CART attributes ===
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''

Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

'''Complete the checkout'''

After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Abandoned Carts vs. Abandoned Checkouts ==
https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T10:12:38Z

Tulipanf: /* Shopify CHECKOUT attributes */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''

Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

'''Complete the checkout'''

After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Abandoned Carts vs. Abandoned Checkouts ==
https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T10:12:26Z

Tulipanf: /* Complete the checkout */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''
Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

'''Complete the checkout'''
After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Abandoned Carts vs. Abandoned Checkouts ==
https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T10:12:12Z

Tulipanf: /* checkout.order */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

'''checkout.order'''
Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

==== Complete the checkout ====
After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Abandoned Carts vs. Abandoned Checkouts ==
https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T10:11:55Z

Tulipanf: /* Considerations */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

'''Considerations'''
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

==== checkout.order ====
Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

==== Complete the checkout ====
After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Abandoned Carts vs. Abandoned Checkouts ==
https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T10:11:33Z

Tulipanf: /* FROM SHOPIFY */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

'''FROM SHOPIFY'''

When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

'''COUPON'''

* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

==== Considerations ====
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

==== checkout.order ====
Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

==== Complete the checkout ====
After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Abandoned Carts vs. Abandoned Checkouts ==
https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T10:10:29Z

Tulipanf: /* CART >> CHECKOUT >> ORDER relationship */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

= CART >> CHECKOUT >> ORDER relationship =
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

=== FROM SHOPIFY ===
When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

==== COUPON ====
* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

==== Considerations ====
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

==== checkout.order ====
Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

==== Complete the checkout ====
After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Abandoned Carts vs. Abandoned Checkouts ==
https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T10:10:13Z

Tulipanf: /* Gondolatok */

= Gondolatok =

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

== CART >> CHECKOUT >> ORDER relationship ==
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

=== FROM SHOPIFY ===
When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

==== COUPON ====
* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

==== Considerations ====
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

==== checkout.order ====
Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

==== Complete the checkout ====
After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Abandoned Carts vs. Abandoned Checkouts ==
https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T10:09:49Z

Tulipanf:

== Gondolatok ==

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

== CART >> CHECKOUT >> ORDER relationship ==
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

=== FROM SHOPIFY ===
When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

==== COUPON ====
* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

==== Considerations ====
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

==== checkout.order ====
Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

==== Complete the checkout ====
After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Abandoned Carts vs. Abandoned Checkouts ==
https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T10:09:24Z

Tulipanf: /* Gondolatok */

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

== Gondolatok ==

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

== CART >> CHECKOUT >> ORDER relationship ==
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

=== FROM SHOPIFY ===
When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

==== COUPON ====
* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

==== Considerations ====
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

==== checkout.order ====
Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

==== Complete the checkout ====
After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Abandoned Carts vs. Abandoned Checkouts ==
https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T10:08:55Z

Tulipanf: /* InitiliazeCheckout */

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

== Gondolatok ==
* AddToCart --> termek a Kosar (Order)-ba kerul --> Ar nelkul!!

* Kosar - oldalon, lekerjuk az OrderItemeket, es a kapcsolodo termekek arat !!

* Majd a Continue to Checkout-kor, minden egyes alkalommal OrderItembe elmentjuk a termekarat

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items (quantity and prices)

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

== CART >> CHECKOUT >> ORDER relationship ==
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

=== FROM SHOPIFY ===
When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

==== COUPON ====
* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

==== Considerations ====
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

==== checkout.order ====
Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

==== Complete the checkout ====
After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Abandoned Carts vs. Abandoned Checkouts ==
https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T10:08:42Z

Tulipanf: /* InitiliazeCheckout */

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

== Gondolatok ==
* AddToCart --> termek a Kosar (Order)-ba kerul --> Ar nelkul!!

* Kosar - oldalon, lekerjuk az OrderItemeket, es a kapcsolodo termekek arat !!

* Majd a Continue to Checkout-kor, minden egyes alkalommal OrderItembe elmentjuk a termekarat

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems
* each time we update items with quantity and prices

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

== CART >> CHECKOUT >> ORDER relationship ==
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

=== FROM SHOPIFY ===
When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

==== COUPON ====
* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

==== Considerations ====
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

==== checkout.order ====
Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

==== Complete the checkout ====
After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Abandoned Carts vs. Abandoned Checkouts ==
https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T10:06:36Z

Tulipanf: /* Gondolatok */

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

== Gondolatok ==
* AddToCart --> termek a Kosar (Order)-ba kerul --> Ar nelkul!!

* Kosar - oldalon, lekerjuk az OrderItemeket, es a kapcsolodo termekek arat !!

* Majd a Continue to Checkout-kor, minden egyes alkalommal OrderItembe elmentjuk a termekarat

=== AddToCart ===

* we add a product to the cart
* the Cart is created
* we have CartItems

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items >> CartItems

=== InitiliazeCheckout ===
* we have the Cart
* we import items from Cart >> we have CheckoutItems

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

== CART >> CHECKOUT >> ORDER relationship ==
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

=== FROM SHOPIFY ===
When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

==== COUPON ====
* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

==== Considerations ====
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

==== checkout.order ====
Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

==== Complete the checkout ====
After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Abandoned Carts vs. Abandoned Checkouts ==
https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T09:57:28Z

Tulipanf: /* Gondolatok */

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

== Gondolatok ==
* AddToCart --> termek a Kosar (Order)-ba kerul --> Ar nelkul!!

* Kosar - oldalon, lekerjuk az OrderItemeket, es a kapcsolodo termekek arat !!

* Majd a Continue to Checkout-kor, minden egyes alkalommal OrderItembe elmentjuk a termekarat

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items

=== InitiliazeCheckout ===
* we have the Cart
* do: import items from Cart

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

== CART >> CHECKOUT >> ORDER relationship ==
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

=== FROM SHOPIFY ===
When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

==== COUPON ====
* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

==== Considerations ====
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

==== checkout.order ====
Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

==== Complete the checkout ====
After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Abandoned Carts vs. Abandoned Checkouts ==
https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T09:56:45Z

Tulipanf: /* Gondolatok */

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

== Gondolatok ==
* AddToCart --> termek a Kosar (Order)-ba kerul --> Ar nelkul!!

* Kosar - oldalon, lekerjuk az OrderItemeket, es a kapcsolodo termekek arat !!

* Majd a Continue to Checkout-kor, minden egyes alkalommal OrderItembe elmentjuk a termekarat

=== Step0 - Cart ===
* If items are present:
* we have the Cart
* we have items

=== InitiliazeCheckout ===
* we have the Cart
* do: import items from Cart

=== Step1 - Delivery Address ===
* we have Checkout entity
* we have items in Checkout
* no email address in Checkout yet
* no Customer entity yet
* no Recipient

=== Step 2 - Shipping method ===
* we have Customer entity
* we have Recipient
* no Shipping method

=== Step3 - Payment method & Billing ===
* we have Shipping method
* no Payment
* no Sender yet

== CART >> CHECKOUT >> ORDER relationship ==
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

=== FROM SHOPIFY ===
When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

==== COUPON ====
* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

==== Considerations ====
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

==== checkout.order ====
Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

==== Complete the checkout ====
After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Abandoned Carts vs. Abandoned Checkouts ==
https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Checkout

2022-02-21T09:54:33Z

Tulipanf: /* Gondolatok */

In my own logic, the '''Cart''' is temporary and it should expire. It can only exist until the cookie expires. Otherwise, it can't be linked to a user/buyer.

When the buyer enters an email address the Cart becomes a '''Checkout'''. Thus the Checkout will exist until the order is placed and the Checkout becomes an Order. As a result, as soon as it is created a Checkout is in fact an Abandoned Checkout.

The '''Order''' is the final destination. If the Order is created from a Checkout, then the Checkout will be deleted from database. Another way to create an Order is to create it in the admin.

In theory, the '''Transaction''' can be considered the true final destination, meaning that an Order becomes a Transaction. Ezt még át kell gondolni...

== Gondolatok ==
* AddToCart --> termek a Kosar (Order)-ba kerul --> Ar nelkul!!

* Kosar - oldalon, lekerjuk az OrderItemeket, es a kapcsolodo termekek arat !!

* Majd a Continue to Checkout-kor, minden egyes alkalommal OrderItembe elmentjuk a termekarat

== CART >> CHECKOUT >> ORDER relationship ==
https://community.shopify.com/c/shopify-apis-and-sdks/difference-between-webhook-quot-checkout-create-quot-quot-orders/td-p/484679

* A '''checkout/create''' event is fired when a checkout is initiated. That means that a user proceeds from their cart to checkout and the cart line items are "transferred" to the checkout line items. As the user enters data throughout the stages of checkout, personal details, shipping, shipping address, payment method, billing address etc. the checkout/update fires.

* The '''orders/create''' event is fired once the checkout is completed i.e. the user successfully completes all checkout steps and is presented with the checkout order summary screen. However, this event is also fired when you manually create an order in Admin UI or if you mark a draft order as paid i.e. the draft order progresses to become an actual order.

* A '''checkout/update''' event is fired when a customer with an active checkout makes updates to their cart during checkout.

=== FROM SHOPIFY ===
When a customer reaches the payment method page of the checkout, their cart is checked against your store's inventory levels. If the inventory is available, then it is held for the customer while they complete the payment. If the inventory has become unavailable, then an error message appears. If a payment fails, then the hold is released until the customer reaches the payment method page again.

==== COUPON ====
* Apply coupon at Checkout (not at Cart!!)
* at Cart level, you know only the Savings (from sale prices)
* therefore Savings and Coupon discounts are 2 different things

== Shopify CART attributes ==
https://shopify.dev/api/liquid/objects/cart
+API: https://shopify.dev/api/admin-rest/2022-01/resources/checkout#resource_object
+ https://shopify.dev/custom-storefronts/cart:

==== Considerations ====
* The cart is subject to the same throttling restrictions as the Storefront API.
* The cart supports a maximum of 500 line items.
* A shop or customer can create an unlimited number of carts.
* Unused and abandoned carts are auto-expired 10 days after creation by Shopify.
* Shopify automatically deletes the cart when the customer completes their checkout.

When a cart is created an id is assigned to it and it has an expiration which is set in cookie with name "cart" this token is also delivered in webhook post callbacks as id and cart_token in carts_update and checkout event.

== Shopify CHECKOUT attributes ==
Attributes: https://shopify.dev/api/liquid/objects/checkout

API: https://shopify.dev/api/admin-rest/2022-01/resources/order#top

==== checkout.order ====
Returns the order created by the checkout. Depending on the payment provider, the order might not have been created yet on the checkout order status page and this property could be nil.

==== Complete the checkout ====
After you've finished creating and performing any updates to the checkout, you can complete the checkout. There are several ways to complete a checkout:

# Use the webUrl field to redirect the customer to Shopify's web checkout form.
# Complete the checkout using one of the following methods:
## Shopify card vault
## Stripe
## Spreedly

== Shopify ORDER attributes ==
https://shopify.dev/api/liquid/objects/order

== Abandoned Carts vs. Abandoned Checkouts ==
https://keepshoppers.com/blog/the-difference-between-abandoned-carts-and-abandoned-checkouts

== Egyeb ==

This may be a simple question but I find the documentation quite confusing.

The REST API document shows the following entities: Abandoned checkouts, Order, Transaction

The webhook API document shows the following entities: Cart, Checkout, Order, OrderTransaction

What is the relationship between all these entities? And what is the overall flow.

Is like this: Cart => Checkout => Order => Transaction?

Why is the terminology different for both APIs?

For example:

Is a checkout always abandoned?

Is a transaction the same as an order transaction?

Why can't I retrieve Carts with the REST api?

Can I expect the same fields in both the REST and the webhook API?

For a given webhook entity, can I expect the same fields for the various topics (e.g checkouts/create and checkouts/delete)

What causes a checkout to be deleted?

Do carts ever get deleted?

This is all very confusing...

Same as shipping logic

2022-02-21T09:16:32Z

Tulipanf: /* B. Logged-in checkout */

= Prerequisites =

The Recipient and Sender are linked to a User, if any. A user may have more than one Recipient / Sender. Why this is important? In the checkout process there are two scenarios:

# Guest checkout
# Logged-in checkout
# Abandoned checkout URL process

== 1. Guest checkout ==

In this scenario when editing the Recipient / Sender details they are always overwritten. In other words, a Guest checkout will have one Recipient and one Sender object. These Recipient and Sender are not linked to a User.

== 2. Logged-in checkout ==

In this scenario the customer has two options: '''Add a new address''' and '''List previously saved addresses'''.

* With '''Add a new address''' a new Recipient / Sender is created in db and linked to the Checkout.
* When picking a '''previously saved address''' a different Recipient / Sender is linked to the Checkout.

== 3. Abandoned checkout URL ==

This is affected by whether the Checkout was previously done with scenario (1) or (2).

When resuming an ''Abandoned checkout'', you can edit only data linked to the current Checkout. Therefore, if the checkout was done by a ''logged-in user'' you no longer have access to the previous Recipient / Sender lists.

So, when editing a Recipient / Sender the entity linked to the Checkout is therefore overwritten.

= The "Same As Shipping" workflow =
When choosing the Billing Address (Sender) the Customer has 2 options:

* Same as shipping address
* Add new billing address

== Same as shipping address ==

Guest and logged-in checkout scenarios do not affect the ''Same as shipping'' logic. With this logic no Sender is created in db, but a flag is marked. As a result, upon checkout completion a Sender will be created and attached to the Order.

NOTE: Recipient fields must match Sender's. Results that Recipient must have Company and Company VAT fields.

==== A. Guest checkout ====

Previously a new Sender was added to the Checkout, then ''Same as shipping'' is selected.

* no Sender in db >> create new Sender with Recipient details
* already a Sender in db >> overwrite Sender with Recipient details

==== B. Logged-in checkout ====

Previously a new Sender was added to the Checkout, then ''Same as shipping'' is selected.

* no Sender in db >> create new Sender with Recipient details
* the Sender entity remains in the Checkout, but will be removed upon Order creation.
** we don't remove it because the flag tells us to ignore it.

==== C. Abandoned checkout URL ====

If previously a new Sender was added to the Checkout, then when choosing ''Same as shipping'':

* the flag becomes true and
* then apply either A. or B. from above

== Add new billing address ==

In this case the ''same_as_shipping'' flag is set to false (0) and a new Sender is created and added to the Checkout.

==== A. Guest checkout ====

* a Sender is in db >> replace it.
* no Sender >> create a new one.

==== B. Logged-in checkout ====

* no Sender in db >> create new one
* Sender already in db >> create new one

Note: there is a verification if the new sender already exists in previously saved list.

==== C. Abandoned checkout URL ====

* no Sender in db >> create new one
* Sender already in db >> apply either A. or B. from above

Same as shipping logic

2022-02-20T11:37:57Z

Tulipanf: /* Same as shipping address */

= Prerequisites =

The Recipient and Sender are linked to a User, if any. A user may have more than one Recipient / Sender. Why this is important? In the checkout process there are two scenarios:

# Guest checkout
# Logged-in checkout
# Abandoned checkout URL process

== 1. Guest checkout ==

In this scenario when editing the Recipient / Sender details they are always overwritten. In other words, a Guest checkout will have one Recipient and one Sender object. These Recipient and Sender are not linked to a User.

== 2. Logged-in checkout ==

In this scenario the customer has two options: '''Add a new address''' and '''List previously saved addresses'''.

* With '''Add a new address''' a new Recipient / Sender is created in db and linked to the Checkout.
* When picking a '''previously saved address''' a different Recipient / Sender is linked to the Checkout.

== 3. Abandoned checkout URL ==

This is affected by whether the Checkout was previously done with scenario (1) or (2).

When resuming an ''Abandoned checkout'', you can edit only data linked to the current Checkout. Therefore, if the checkout was done by a ''logged-in user'' you no longer have access to the previous Recipient / Sender lists.

So, when editing a Recipient / Sender the entity linked to the Checkout is therefore overwritten.

= The "Same As Shipping" workflow =
When choosing the Billing Address (Sender) the Customer has 2 options:

* Same as shipping address
* Add new billing address

== Same as shipping address ==

Guest and logged-in checkout scenarios do not affect the ''Same as shipping'' logic. With this logic no Sender is created in db, but a flag is marked. As a result, upon checkout completion a Sender will be created and attached to the Order.

NOTE: Recipient fields must match Sender's. Results that Recipient must have Company and Company VAT fields.

==== A. Guest checkout ====

Previously a new Sender was added to the Checkout, then ''Same as shipping'' is selected.

* no Sender in db >> create new Sender with Recipient details
* already a Sender in db >> overwrite Sender with Recipient details

==== B. Logged-in checkout ====

Previously a new Sender was added to the Checkout, then ''Same as shipping'' is selected.

* no * no Sender in db >> create new Sender with Recipient details
* the Sender entity remains in the Checkout, but will be removed upon Order creation.
** we don't remove it because the flag tells us to ignore it.

==== C. Abandoned checkout URL ====

If previously a new Sender was added to the Checkout, then when choosing ''Same as shipping'':

* the flag becomes true and
* then apply either A. or B. from above

== Add new billing address ==

In this case the ''same_as_shipping'' flag is set to false (0) and a new Sender is created and added to the Checkout.

==== A. Guest checkout ====

* a Sender is in db >> replace it.
* no Sender >> create a new one.

==== B. Logged-in checkout ====

* no Sender in db >> create new one
* Sender already in db >> create new one

Note: there is a verification if the new sender already exists in previously saved list.

==== C. Abandoned checkout URL ====

* no Sender in db >> create new one
* Sender already in db >> apply either A. or B. from above

Same as shipping logic

2022-02-20T11:27:30Z

Tulipanf: /* Add new billing address */

= Prerequisites =

The Recipient and Sender are linked to a User, if any. A user may have more than one Recipient / Sender. Why this is important? In the checkout process there are two scenarios:

# Guest checkout
# Logged-in checkout
# Abandoned checkout URL process

== 1. Guest checkout ==

In this scenario when editing the Recipient / Sender details they are always overwritten. In other words, a Guest checkout will have one Recipient and one Sender object. These Recipient and Sender are not linked to a User.

== 2. Logged-in checkout ==

In this scenario the customer has two options: '''Add a new address''' and '''List previously saved addresses'''.

* With '''Add a new address''' a new Recipient / Sender is created in db and linked to the Checkout.
* When picking a '''previously saved address''' a different Recipient / Sender is linked to the Checkout.

== 3. Abandoned checkout URL ==

This is affected by whether the Checkout was previously done with scenario (1) or (2).

When resuming an ''Abandoned checkout'', you can edit only data linked to the current Checkout. Therefore, if the checkout was done by a ''logged-in user'' you no longer have access to the previous Recipient / Sender lists.

So, when editing a Recipient / Sender the entity linked to the Checkout is therefore overwritten.

= The "Same As Shipping" workflow =
When choosing the Billing Address (Sender) the Customer has 2 options:

* Same as shipping address
* Add new billing address

== Same as shipping address ==

Guest and logged-in checkout scenarios do not affect the ''Same as shipping'' logic. With this logic no Sender is created in db, but a flag is marked. As a result, upon checkout completion a Sender will be created and attached to the Order.

NOTE: Recipient fields must match Sender's. Results that Recipient must have Company and Company VAT fields.

==== A. Guest checkout ====

Previously a new Sender was added to the Checkout, then with ''Same as shipping'':

* the flag becomes true and
* the Sender entity is updated with Recipient details ONLY upon Order creation.

==== B. Logged-in checkout ====

If previously a new Sender was added to the Checkout, then when choosing ''Same as shipping'':

* the flag becomes true and
* the Sender entity remains in the Checkout, but will be removed upon Order creation.
** we don't remove it because the flag tells us to ignore it.

==== C. Abandoned checkout URL ====

If previously a new Sender was added to the Checkout, then when choosing ''Same as shipping'':

* the flag becomes true and
* then apply either A. or B. from above

== Add new billing address ==

In this case the ''same_as_shipping'' flag is set to false (0) and a new Sender is created and added to the Checkout.

==== A. Guest checkout ====

* a Sender is in db >> replace it.
* no Sender >> create a new one.

==== B. Logged-in checkout ====

* no Sender in db >> create new one
* Sender already in db >> create new one

Note: there is a verification if the new sender already exists in previously saved list.

==== C. Abandoned checkout URL ====

* no Sender in db >> create new one
* Sender already in db >> apply either A. or B. from above

Same as shipping logic

2022-02-20T11:26:41Z

Tulipanf: /* Add new billing address */

= Prerequisites =

The Recipient and Sender are linked to a User, if any. A user may have more than one Recipient / Sender. Why this is important? In the checkout process there are two scenarios:

# Guest checkout
# Logged-in checkout
# Abandoned checkout URL process

== 1. Guest checkout ==

In this scenario when editing the Recipient / Sender details they are always overwritten. In other words, a Guest checkout will have one Recipient and one Sender object. These Recipient and Sender are not linked to a User.

== 2. Logged-in checkout ==

In this scenario the customer has two options: '''Add a new address''' and '''List previously saved addresses'''.

* With '''Add a new address''' a new Recipient / Sender is created in db and linked to the Checkout.
* When picking a '''previously saved address''' a different Recipient / Sender is linked to the Checkout.

== 3. Abandoned checkout URL ==

This is affected by whether the Checkout was previously done with scenario (1) or (2).

When resuming an ''Abandoned checkout'', you can edit only data linked to the current Checkout. Therefore, if the checkout was done by a ''logged-in user'' you no longer have access to the previous Recipient / Sender lists.

So, when editing a Recipient / Sender the entity linked to the Checkout is therefore overwritten.

= The "Same As Shipping" workflow =
When choosing the Billing Address (Sender) the Customer has 2 options:

* Same as shipping address
* Add new billing address

== Same as shipping address ==

Guest and logged-in checkout scenarios do not affect the ''Same as shipping'' logic. With this logic no Sender is created in db, but a flag is marked. As a result, upon checkout completion a Sender will be created and attached to the Order.

NOTE: Recipient fields must match Sender's. Results that Recipient must have Company and Company VAT fields.

==== A. Guest checkout ====

Previously a new Sender was added to the Checkout, then with ''Same as shipping'':

* the flag becomes true and
* the Sender entity is updated with Recipient details ONLY upon Order creation.

==== B. Logged-in checkout ====

If previously a new Sender was added to the Checkout, then when choosing ''Same as shipping'':

* the flag becomes true and
* the Sender entity remains in the Checkout, but will be removed upon Order creation.
** we don't remove it because the flag tells us to ignore it.

==== C. Abandoned checkout URL ====

If previously a new Sender was added to the Checkout, then when choosing ''Same as shipping'':

* the flag becomes true and
* then apply either A. or B. from above

== Add new billing address ==

In this case the ''same_as_shipping'' flag is set to false (0) and a new Sender is created and added to the Checkout.

==== A. Guest checkout ====

If a Sender is in db >> replace it.

If no Sender >> create a new one.

==== B. Logged-in checkout ====

If no Sender in db >> create new one

If Sender already in db >> create new one

Note: there is a verification if the new sender already exists in previously saved list.

==== C. Abandoned checkout URL ====

If no Sender in db >> create new one

If Sender already in db >> apply either A. or B. from above

Same as shipping logic

2022-02-20T11:26:23Z

Tulipanf:

= Prerequisites =

The Recipient and Sender are linked to a User, if any. A user may have more than one Recipient / Sender. Why this is important? In the checkout process there are two scenarios:

# Guest checkout
# Logged-in checkout
# Abandoned checkout URL process

== 1. Guest checkout ==

In this scenario when editing the Recipient / Sender details they are always overwritten. In other words, a Guest checkout will have one Recipient and one Sender object. These Recipient and Sender are not linked to a User.

== 2. Logged-in checkout ==

In this scenario the customer has two options: '''Add a new address''' and '''List previously saved addresses'''.

* With '''Add a new address''' a new Recipient / Sender is created in db and linked to the Checkout.
* When picking a '''previously saved address''' a different Recipient / Sender is linked to the Checkout.

== 3. Abandoned checkout URL ==

This is affected by whether the Checkout was previously done with scenario (1) or (2).

When resuming an ''Abandoned checkout'', you can edit only data linked to the current Checkout. Therefore, if the checkout was done by a ''logged-in user'' you no longer have access to the previous Recipient / Sender lists.

So, when editing a Recipient / Sender the entity linked to the Checkout is therefore overwritten.

= The "Same As Shipping" workflow =
When choosing the Billing Address (Sender) the Customer has 2 options:

* Same as shipping address
* Add new billing address

== Same as shipping address ==

Guest and logged-in checkout scenarios do not affect the ''Same as shipping'' logic. With this logic no Sender is created in db, but a flag is marked. As a result, upon checkout completion a Sender will be created and attached to the Order.

NOTE: Recipient fields must match Sender's. Results that Recipient must have Company and Company VAT fields.

==== A. Guest checkout ====

Previously a new Sender was added to the Checkout, then with ''Same as shipping'':

* the flag becomes true and
* the Sender entity is updated with Recipient details ONLY upon Order creation.

==== B. Logged-in checkout ====

If previously a new Sender was added to the Checkout, then when choosing ''Same as shipping'':

* the flag becomes true and
* the Sender entity remains in the Checkout, but will be removed upon Order creation.
** we don't remove it because the flag tells us to ignore it.

==== C. Abandoned checkout URL ====

If previously a new Sender was added to the Checkout, then when choosing ''Same as shipping'':

* the flag becomes true and
* then apply either A. or B. from above

== Add new billing address ==

In this case the ''same_as_shipping'' flag is set to false (0) and a new Sender is created and added to the Checkout.

==== A. Guest checkout ====

If a Sender is in db >> replace it.
If no Sender >> create a new one.

==== B. Logged-in checkout ====

If no Sender in db >> create new one
If Sender already in db >> create new one

Note: there is a verification if the new sender already exists in previously saved list.

==== C. Abandoned checkout URL ====

If no Sender in db >> create new one
If Sender already in db >> apply either A. or B. from above

Same as shipping logic

2022-02-20T11:15:53Z

Tulipanf: /* Same as shipping address */

= Prerequisites =

The Recipient and Sender are linked to a User, if any. A user may have more than one Recipient / Sender. Why this is important? In the checkout process there are two scenarios:

# Guest checkout
# Logged-in checkout
# Abandoned checkout URL process

== 1. Guest checkout ==

In this scenario when editing the Recipient / Sender details they are always overwritten. In other words, a Guest checkout will have one Recipient and one Sender object. These Recipient and Sender are not linked to a User.

== 2. Logged-in checkout ==

In this scenario the customer has two options: '''Add a new address''' and '''List previously saved addresses'''.

* With '''Add a new address''' a new Recipient / Sender is created in db and linked to the Checkout.
* When picking a '''previously saved address''' a different Recipient / Sender is linked to the Checkout.

== 3. Abandoned checkout URL ==

This is affected by whether the Checkout was previously done with scenario (1) or (2).

When resuming an ''Abandoned checkout'', you can edit only data linked to the current Checkout. Therefore, if the checkout was done by a ''logged-in user'' you no longer have access to the previous Recipient / Sender lists.

So, when editing a Recipient / Sender the entity linked to the Checkout is therefore overwritten.

= The "Same As Shipping" workflow =
When choosing the Billing Address (Sender) the Customer has 2 options:

* Same as shipping address
* Add new billing address

== Same as shipping address ==

Guest and logged-in checkout scenarios do not affect the ''Same as shipping'' logic. With this logic no Sender is created in db, but a flag is marked. As a result, upon checkout completion a Sender will be created and attached to the Order.

NOTE: Recipient fields must match Sender's. Results that Recipient must have Company and Company VAT fields.

==== A. Guest checkout ====

Previously a new Sender was added to the Checkout, then with ''Same as shipping'':

* the flag becomes true and
* the Sender entity is updated with Recipient details ONLY upon Order creation.

==== B. Logged-in checkout ====

If previously a new Sender was added to the Checkout, then when choosing ''Same as shipping'':

* the flag becomes true and
* the Sender entity remains in the Checkout, but will be removed upon Order creation.
** we don't remove it because the flag tells us to ignore it.

==== C. Abandoned checkout URL ====

If previously a new Sender was added to the Checkout, then when choosing ''Same as shipping'':

* the flag becomes true and
* then apply either A. or B. from above

== Add new billing address ==

In this case the ''same_as_shipping'' flag is set to false (0) and a new Sender is created and added to the Checkout.

==== Dealing with ====

Same as shipping logic

2022-02-20T11:09:37Z

Tulipanf: /* Same as shipping address */

= Prerequisites =

The Recipient and Sender are linked to a User, if any. A user may have more than one Recipient / Sender. Why this is important? In the checkout process there are two scenarios:

# Guest checkout
# Logged-in checkout
# Abandoned checkout URL process

== 1. Guest checkout ==

In this scenario when editing the Recipient / Sender details they are always overwritten. In other words, a Guest checkout will have one Recipient and one Sender object. These Recipient and Sender are not linked to a User.

== 2. Logged-in checkout ==

In this scenario the customer has two options: '''Add a new address''' and '''List previously saved addresses'''.

* With '''Add a new address''' a new Recipient / Sender is created in db and linked to the Checkout.
* When picking a '''previously saved address''' a different Recipient / Sender is linked to the Checkout.

== 3. Abandoned checkout URL ==

This is affected by whether the Checkout was previously done with scenario (1) or (2).

When resuming an ''Abandoned checkout'', you can edit only data linked to the current Checkout. Therefore, if the checkout was done by a ''logged-in user'' you no longer have access to the previous Recipient / Sender lists.

So, when editing a Recipient / Sender the entity linked to the Checkout is therefore overwritten.

= The "Same As Shipping" workflow =
When choosing the Billing Address (Sender) the Customer has 2 options:

* Same as shipping address
* Add new billing address

== Same as shipping address ==

Guest and logged-in checkout scenarios do not affect the ''Same as shipping'' logic. With this logic no Sender is created in db, but a flag is marked. As a result, upon checkout completion a Sender will be created and attached to the Order.

NOTE: Recipient fields must match Sender's. Results that Recipient must have Company and Company VAT fields.

==== Guest checkout ====

Previously a new Sender was added to the Checkout, then with ''Same as shipping'':

* the flag becomes true and
* the Sender entity is updated with Recipient details

upon Order creation.

==== Logged-in checkout ====

If previously a new Sender was added to the Checkout, then when choosing ''Same as shipping'':

* the flag becomes true and
* the Sender entity remains in the Checkout, but will be removed upon Order creation.
** we don't remove it because the flag tells us to ignore it.

== Add new billing address ==

In this case the ''same_as_shipping'' flag is set to false (0) and a new Sender is created and added to the Checkout.

==== Dealing with ====

Same as shipping logic

2022-02-20T11:02:27Z

Tulipanf: /* Guest checkout */

= Prerequisites =

The Recipient and Sender are linked to a User, if any. A user may have more than one Recipient / Sender. Why this is important? In the checkout process there are two scenarios:

# Guest checkout
# Logged-in checkout
# Abandoned checkout URL process

== 1. Guest checkout ==

In this scenario when editing the Recipient / Sender details they are always overwritten. In other words, a Guest checkout will have one Recipient and one Sender object. These Recipient and Sender are not linked to a User.

== 2. Logged-in checkout ==

In this scenario the customer has two options: '''Add a new address''' and '''List previously saved addresses'''.

* With '''Add a new address''' a new Recipient / Sender is created in db and linked to the Checkout.
* When picking a '''previously saved address''' a different Recipient / Sender is linked to the Checkout.

== 3. Abandoned checkout URL ==

This is affected by whether the Checkout was previously done with scenario (1) or (2).

When resuming an ''Abandoned checkout'', you can edit only data linked to the current Checkout. Therefore, if the checkout was done by a ''logged-in user'' you no longer have access to the previous Recipient / Sender lists.

So, when editing a Recipient / Sender the entity linked to the Checkout is therefore overwritten.

= The "Same As Shipping" workflow =
When choosing the Billing Address (Sender) the Customer has 2 options:

* Same as shipping address
* Add new billing address

== Same as shipping address ==

Guest and logged-in checkout scenarios do not affect the ''Same as shipping'' logic. With this logic no Sender is created in db, but a flag is marked. As a result, upon checkout completion a Sender will be created and attached to the Order.

NOTE: Recipient fields must match Sender's. Results that Recipient must have Company and Company VAT fields.

==== Guest checkout ====

Previously a new Sender was added to the Checkout, then with ''Same as shipping'':

* the flag becomes true and
* the Sender details will be updated with Recipient details

upon Order creation.

==== Logged-in checkout ====

If previously a new Sender was added to the Checkout, then when choosing ''Same as shipping'' the flag becomes true and the Sender is removed (from the Checkout) upon Order creation.

== Add new billing address ==

In this case the ''same_as_shipping'' flag is set to false (0) and a new Sender is created and added to the Checkout.

==== Dealing with ====