Skip to content

Commit

Permalink
Update Integration-Processes.md
Browse files Browse the repository at this point in the history
Final edits
  • Loading branch information
MaciekVoucherify authored Dec 12, 2023
1 parent 6fd1e59 commit 45f192b
Showing 1 changed file with 14 additions and 14 deletions.
28 changes: 14 additions & 14 deletions docs/guides/implementation_blueprint/Integration-Processes.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ We will guide you through the most commonly used scenarios that involve the API

### Redeeming voucher codes

In this scenario a customer will be reedeming voucher codes.
In this scenario, a customer will be redeeming voucher codes.

The customer is given voucher codes using different methods. You can use [Voucherify's Distributions](doc:distributions) or a standalone voucher that the customer received in many different ways.

Expand All @@ -47,31 +47,31 @@ The process of applying the codes can be different depending on the customer exp

Step 1: A typical scenario is presented where the customer browses products, adds them to their cart, and proceeds to checkout.

>During the shopping process there is no need to send any API requests to Voucherify when a customer adds or removes any products from their cart. API requests are only needed if you want to verify whether a customer qualifies for the discount or to calculate the discount itself.
>During the shopping process, there is no need to send any API requests to Voucherify when a customer adds or removes any products from their cart. API requests are only needed if you want to verify whether a customer qualifies for the discount or to calculate the discount itself.
Step 2: Qualifications (optional) - you can choose to get a list of applicable discounts for the customer from Voucherify. If you don't choose this option, the customer has to input the codes by themselves.

>The Qualifications request can return just the promotions or a combination of discount codes, campaigns, and promotion tiers according to the "options" from the Qualifications request.
Step 3: Apply the coupon codes. If you use the qualification request you can show the discounts for the customer to choose from, or apply some discounts automatically. You can also allow the customer to input code acquired from a different source.
Step 3: Apply the coupon codes. If you use the qualification request, you can show the discounts for the customer to choose from or apply some discounts automatically. You can also allow the customer to input code acquired from a different source.

Step 4: Validations - a validation request is sent to Voucherify to check whether codes are applicable and appropriate results are returned.

Step 5: Exposing the calculated discount based on the combination of coupon codes validated on the order. Expecting the customer to pay for the order.

Step 6: Redemptions - when the customer pays for the order, Voucherify receives a redemption request and consumes the discount coupons.

>The Validations and Redemptions requests can validate and redeem a combination of different discount types and redeemables. With one request you can verify how promotion tiers and voucher codes affect the customer's cart.
>The Validations and Redemptions requests can validate and redeem a combination of different discount types and redeemables. With one request, you can verify how promotion tiers and voucher codes affect the customer's cart.
### Checking promotion (discount without a code) eligibility during checkout

In this scenario promotion eligibility is going to be verified during the checkout step. A customer did not receive any voucher codes beforehand, instead all discounts and promotions will be displayed at the checkout screen.
In this scenario, promotion eligibility is going to be verified during the checkout step. A customer did not receive any voucher codes beforehand. Instead, all discounts and promotions will be displayed on the checkout screen.

![Customer experience in Voucherify case 2](https://raw.githubusercontent.com/voucherifyio/voucherify-openapi/mk/integration-processes/docs/assets/img/guides_implementation_blueprint_integration_processes_customer_experience_case_2.png "Customer experience in Voucherify case 2")

Step 1: A typical scenario is presented where the customer browses products, adds them to their cart, and proceeds to checkout.

>During the shopping process there is no need to send any API requests to Voucherify when a customer adds or removes any products from their cart. API requests are only needed if you want to verify whether a customer qualifies for the discount or to calculate the discount itself.
>During the shopping process, there is no need to send any API requests to Voucherify when a customer adds or removes any products from their cart. API requests are only needed if you want to verify whether a customer qualifies for the discount or to calculate the discount itself.
Step 2: Qualifications (mandatory) - List applicable discounts for the customer from Voucherify.

Expand All @@ -85,17 +85,17 @@ Step 5: Exposing the calculated discount based on the combination of promotions

Step 6: Redemptions - when the customer pays for the order, Voucherify receives a redemption request and consumes the discount coupons.

>The Validations and Redemptions requests can validate and redeem a combination of different discount types and redeemables. With one request you can verify how promotion tiers and voucher codes affect the customer's cart.
>The Validations and Redemptions requests can validate and redeem a combination of different discount types and redeemables. With one request, you can verify how promotion tiers and voucher codes affect the customer's cart.
### Publishing a voucher code in a wandering customer scenario

In this scenario a customer is going to receive a voucher code during their visit in the store. The distribution will trigger after the specific action takes place.
In this scenario, a customer is going to receive a voucher code during their visit to the store. The distribution will trigger after the specific action takes place.

![Customer experience in Voucherify case 3](https://raw.githubusercontent.com/voucherifyio/voucherify-openapi/mk/integration-processes/docs/assets/img/guides_implementation_blueprint_integration_processes_customer_experience_case_3.png "Customer experience in Voucherify case 3")

Step 1: The customer visits your store, adds products to the cart but does not go to checkout for a while.
Step 1: The customer visits your store and adds products to the cart but does not go to checkout for a while.

>During the shopping process there is no need to send any API requests to Voucherify when a customer adds or removes any products from their cart. API requests are only needed if you want to verify whether a customer qualifies for the discount or to calculate the discount itself.
>During the shopping process, there is no need to send any API requests to Voucherify when a customer adds or removes any products from their cart. API requests are only needed if you want to verify whether a customer qualifies for the discount or to calculate the discount itself.
Step 2: Publications - The publication is triggered to give a customer the coupon code to encourage them to finish the purchase.

Expand All @@ -109,17 +109,17 @@ Step 5: Exposing the effect of the coupon code to the customer. Expecting the cu

Step 6: Redemptions - when the customer pays for the order, Voucherify receives a redemption request and consumes the discount coupon.

>The Validations and Redemptions requests can validate and redeem a combination of different discount types and redeemables. With one request you can verify how promotion tiers and voucher codes affect the customer's cart.
>The Validations and Redemptions requests can validate and redeem a combination of different discount types and redeemables. With one request, you can verify how promotion tiers and voucher codes affect the customer's cart.
### Rewarding customers with points for purchases.

In this scenario a customer is going to receive points for their purchase. The customer may or may not use discounts during the purchase. The redemption request will create an order in Voucherify, but if the customer does not have any eligible discounts, you have to send an API request to synchronize the new order so that Voucherify can reward the customer with points. Voucherify can inform the customer how many points the customer earned.
In this scenario, a customer is going to receive points for their purchase. The customer may or may not use discounts during the purchase. The redemption request will create an order in Voucherify, but if the customer does not have any eligible discounts, you have to send an API request to synchronize the new order so that Voucherify can reward the customer with points. Voucherify can inform the customer how many points the customer earned.

![Customer experience in Voucherify case 4](https://raw.githubusercontent.com/voucherifyio/voucherify-openapi/mk/integration-processes/docs/assets/img/guides_implementation_blueprint_integration_processes_customer_experience_case_4.png "Customer experience in Voucherify case 4")

Step 1: A typical scenario is presented where the customer browses products, adds them to their cart, and proceeds to checkout.

>During the shopping process there is no need to send any API requests to Voucherify when a customer adds or removes any products from their cart. API requests are only needed if you want to verify whether a customer qualifies for the discount or to calculate the discount itself.
>During the shopping process, there is no need to send any API requests to Voucherify when a customer adds or removes any products from their cart. API requests are only needed if you want to verify whether a customer qualifies for the discount or to calculate the discount itself.
Step 2: The customer can be eligible for a discount.

Expand All @@ -131,6 +131,6 @@ Step 3: This step has two possible outcomes depending on your previous choice:

Step 4: The customer is rewarded with points. The points are calculated by Voucherify according to the Earning Rules.

Step 5: Optional - The marketing team can decide whether the customer should be informed about the earned points and how. The list of possible distribution options is available here <!-- Link -->
Step 5: Optional - The marketing team can decide whether the customer should be informed about the earned points and which [distribution channel](https://support.voucherify.io/article/19-how-does-the-distribution-manager-work#channels) will be used.

Step 6: The customer received a notification.

0 comments on commit 45f192b

Please sign in to comment.