Fuel Delivery Web Portals

App primary functional features requirement document
Customer Master Management:-
- Customer can self-sign in / register with required fields and documents including GST / PAN/ Aadhaar / COI etc. which can come to us for approval. Attachment of document should be activated, so that customer documents should be attached.
- We can also create customer account on behalf of customer and register their details including required documents.
- It should check duplication of customer based on GST no or PAN. After approval, it should auto create customer account in Tally.
- We should be able to maintain the credit limit of customer in terms of amount and no of days which will also be integrated with Tally while customer creation.
- Customer wallet should get auto activated at the time of customer activation, which can negative upto the credit limit amount.
- Customer can be assigned to one or multiple OMC (IOCL, BPCL, HPCL and JioBP) cards by the admin which can be utilised at any point in time by customer at the respective petrol pump after placing the order.
- Rates of diesel can be assigned at every customer location level which can come from respective OMC API. Rates can be different for every petrol pump also if the customer is going to pick up the diesel directly from the pump.
- Customer can request to modify any customer master details through app which can be updated automatically in tally as and when approved by the admin.
- There should be a stock field in customer master which can be maintained against a site or asset wherein customers stock along with timestamp can be uploaded / updated at any time to monitor their stock on day to day basis. Keeping in mind that this can be integrated with customer IOT system data in future.
Order Management:-
- Customer can place the order by selecting any of their sites (and optionally assets if required) with requested date and tentative time.
- There can be site wise / asset wise SPOC of customers which can be maintained in the portal along with their contact details.
- System should check the credit limit at the time of ordering and if it gets exhausted, order should not be allowed to be created. In this case only admin can place the order on customer behalf.
- Credit limit will get reduced with the order amount at the time of ordering but it should show separately for actual customer balance and order to be delivered.
- Actual customer balance should always be synched with tally so that there is no difference between tally and app.
OMC Card Management:-
- If the customer is assigned to any OMC (IOCL, BPCL, HPCL or JioBP) card, it should be linked to respective OMC portal through APIs.
- After approval of customer order by admin, portal should automatically set the card limit in the respective OMC card with the calculated order amount.
- Once the order is picked up / delivered, this limit should be automatically reduced.
- Admin can check card wise limit balance in app.
Delivery Management:
- Once the order is placed, it should go to admin for approval.
- Admin will assign the driver / vehicle as well as assign delivery timeline.
- Once the driver is assigned, order should be visible to driver along with SPOC / address details in their login till the time delivery happens.
- App should integrate with vehicle GPS system and fetch the live location of the vehicle.
- This live location can be shown to customer if the customer master is authorised to do so.
- Driver should be able to capture the POD (proof of delivery) by attaching images at the time of delivery as well as taking the customer signature.
- Order should be marked as delivered once POD is attached by the driver and auto email should be triggered to customer along with POD / delivery challan.

Invoice Management:
- Auto invoice should be generated in Tally system after getting the POD and same invoice should be emailed to customer as per the tally format along with latest customer statement. (based on the selection in customer master for invoices, statements, POD)
- Customer should be able to view / download invoices as well as statements from the app itself.
- Auto reminder for payment should be triggered from system as and when the payment due.
Wallet Management:
- Payment gateway integration for collecting payment from customer should be integrated to new platform. (Customer should be displayed with a message if they make payment through app, stating “wallet balance will be updated only after confirmation by accounts team”)
- Wallet balance of customer should get updated from tally automatically every 2-3 minute so there is no lag between the two.
- Wallet transaction history can be seen by customer as well as admin at any point in time to reconcile or check if there is any anomaly.
Reward Management:
- Customer master should have the provision of activating reward points.
- If reward points are activated in customer master, reward points should be credited in customer master based on the payment received from customer.
- Every 100 rs received in the customer account through payment voucher should earn 1 reward point in customer master.
- Admin can assign the value to 1 reward point for every customer separately. It can vary from customer to customer.
- Reward points can be redeemed by the customer in multiples of 5,000 and request for redemption has to be approved by the admin only.
- Admin can do any modification in reward points but it should get recorded as an audit trail.
Dashboard Management:
- No of customers added on day to day basis.
- List of assets / locations by customer.
- Credit limit dashboard with changes and how much amount and %age is exhausted.
- Customer outstanding with due dates at summarised and invoice level.
- Order received / pending / fulfilled / invoiced / paid
- Wallet balance by customer
- Reward point by customers / locations
- Customer statements
- Customer order / consumption trends by assets / locations.
- Summarised / invoice level receipt register for customers for admin.
- Balance confirmation has to be done by every customer by 5th of the following month for previous month. If not done, customer ordering should get blocked.
Authorisation Management:
- Every user will be authorised to do only those things which are assigned to him, s/he should not be able to view/change others data.
- There should be multiple accounts for Admin based on the customers assigned to the admin. Authorisation to admin should be based on assigned customers.