Hi Akshay,
You could consider that a prepaid 'Topup' is also a product(offer) which an end-user/customer can order and which is managed in your catalog/order management system.
It allows for a few scenario's:
- You can model each topup amount as a different offers (eg. 20/40/50 euro's), or even use a captured topup amount from the user.
- It allows you to track topup's as 'orders', and therefor also visible in your CRM systems and selfcare environment
- depending on your order management capabilities, add promotions: topup for 20 euro and get 25 euro credit (or maybe some other kind of gift/promotion).
- your order management system can coordinate the fulfillment activities for the topup, like integration with external charging system/backing system, execute topup on your prepaid system, audit logging etc...
hope this helps.
------------------------------
Eric Janssen
VodafoneZiggo
------------------------------
Original Message:
Sent: Nov 20, 2020 16:19
From: Akshay Hiremath
Subject: BSS: Top Up amount in the Self Serve Buy flow for Prepaid
Hi,
We are building a self serve buy flow that will be used by the customer for new activations.
We have one scenario where the business wants to allow a customer to choose an extra top-up amount in the new activation flow where a customer is choosing the main plan and addons.
So this extra amount is going to be a top-up in the main pre-paid balance on the top of the main plan.
Business wants to charge the customer only once for a total of the top-up amount and the plan amount.
Now we have the plans, addons in the Catalog but the Top Up amount is a random value entity so naturally outside the catalog. We are looking for ways how this could be implemented,
Which system should do what?
Option 1: Keep the item for top-up amount outside the main order
UI/UX layer calls
the order management to Calculate prices and taxes for all Catalog items in the Shopping Cart
then the taxation engine for taxes on the top-up amount
aggregates both amounts and then calls the Payment service directly to make one payment.
Problem: After the order is processed if we have to show the details of the main order we don't have the top-up in the order so which system should maintain the top-up item, payments? doesn't sound logical but then how will I show the details of the order to customer in the account management.
Option 2: Create a placeholder offer in the Catalog and add the top-up item as another item in the catalog
UI/UX layer calls
the order management to Calculate prices and taxes for all Catalog items in the Shopping Cart (now even the top-up amount is represented by another offer)
the order management calculates the prices and taxes for all items and returns the response with aggregate amount and tax to the UI/UX layer
Problem: Is it possible (and good practice) to create such a kind of placeholder offers/products in the Catalog?
What kind of product specification will be associated with this offer?
Because this offer doesn't really belong to any actual product.
looking for suggestions. I feel we are missing some elements/systems here.
#CustomerExperience
------------------------------
Akshay Hiremath
Rogers Communications Inc.
------------------------------