phoenix
phoenixPhoenix - Your AI Assistant
Inactive session will be ended in 24 hours
End Session

Customer Portal, Mobile App

  • Posted:
  • Proposals: 71
  • Remote
  • #4520835
  • OPPORTUNITY
  • Open for Proposals
Aadil S.Hamza M.Azharul I.Danyil V.Shahid I. + 66 others have already sent a proposal.
  • 4

Description

Experience Level: Expert
# Tender Brief – Customer Portal, Mobile App & EPOS Integration

## Project Overview

We are a multi-site second-hand retail business operating a buy, sell and buyback model.

We are looking for an experienced software development partner to create a digital customer platform that integrates with our existing .NET EPOS system.

The project should include:

* Customer website portal
* Digital customer agreements
* Buyback and renewal functionality
* Online payments
* EPOS integration
* iOS and Android mobile app
* Customer reminders and notifications

## Customer Portal

Customers should be able to:

* Register and log in securely
* View current and previous buyback agreements
* View agreement expiry and renewal dates
* Renew eligible agreements online
* Make required payments
* View and download agreements
* View relevant transaction history
* Receive account notifications and reminders

The website should be mobile-first and simple to use.

## Digital Agreements

The platform should create customer agreements using transaction data held within our EPOS.

It should support:

* Digital presentation of agreements
* Customer acceptance or electronic signature
* Date/time recording
* Secure document storage
* Downloadable copies for customers
* Full audit trail
* Linking agreements to the relevant customer and EPOS transaction

## Buyback Renewals

Customers should be able to renew eligible buyback agreements online.

The platform should:

* Display current agreement status
* Show renewal eligibility and cost
* Take online payment
* Confirm the renewal
* Update our EPOS
* Produce updated documentation where required
* Maintain a full audit history

Automated reminders should be available before expiry and renewal dates.

## EPOS Integration

Our existing EPOS is built in .NET.

The new platform must integrate securely with the EPOS, preferably using a central API layer.

Our preferred architecture is:

**.NET EPOS → Secure API → Customer Website / Mobile App**

The EPOS should remain the main source of customer, agreement and transaction information where appropriate.

## Mobile App

We require an iOS and Android app that broadly mirrors the customer website.

The app should use the same backend and APIs rather than being developed as a completely separate system.

Core functions should include:

* Customer login
* Agreement viewing
* Buyback renewals
* Payments
* Agreement documents
* Transaction history
* Push notifications
* Account management

We are open to native or cross-platform development.

## Payments and Notifications

The platform should integrate with an appropriate payment provider and support:

* Secure payments
* Payment confirmation
* Failed-payment handling
* Transaction references
* Reconciliation with our systems

Notifications may include:

* Agreement expiry reminders
* Renewal reminders
* Payment confirmation
* Renewal confirmation
* Important account updates

These may be delivered by push notification, email and/or SMS.

## Security

The solution must include appropriate:

* GDPR compliance
* Secure authentication
* Data encryption
* API security
* Audit logging
* Customer consent controls
* Payment security
* Backup and recovery

## Supplier Response

Please provide:

* Proposed technical solution
* Recommended architecture
* Relevant experience
* Experience with .NET integrations
* Website and mobile technologies proposed
* Approach to digital agreements
* Payment integration approach
* Security/GDPR approach
* Development stages
* Estimated costs
* Ongoing hosting/support costs
* Examples of similar projects

We are looking for a partner capable of delivering a single connected platform linking our .NET EPOS, customer website and mobile app, with scope for further development in future.

New Proposal

Login to your account and send a proposal now to get this project.

Log in

Clarification Board Ask a Question

  • App Mechanic

    I have few questions related to the project below:

    1) Does your .NET EPOS currently expose APIs, web services, or database access for customer and transaction data?
    2) Which payment provider and electronic signature method do you currently prefer?

  • App Mechanic

    1) Does your .NET EPOS currently expose APIs, web services, or database access for customer and transaction data?
    2) Which payment provider and electronic signature method do you currently prefer?

  • Tafsol Technologies

    A few things I’d like to clarify:

    1. How many retail locations and active customers should the platform support initially?

    2. What data should sync from EPOS (customers, agreements, payments, products, transactions, etc.)?

    3. Are digital signatures required to be legally compliant (DocuSign/Adobe Sign style), or would a simple acceptance record work?

    4. Which payment providers are preferred or currently used?

    5. Should renewals be fully automatic after payment, or require staff approval?

  • CYTNHIA W.

    The most important question I would resolve before architecture sign-off is: does your existing .NET EPOS already expose a documented API/service layer for customers, transactions, agreements and renewals, or is its functionality currently available only through the .NET application/database? If the latter, I would first need to establish whether we can introduce a controlled API within the existing EPOS codebase or whether an integration service must safely mediate access to the existing database.

    A second critical question is that when an online renewal payment succeeds but the EPOS is temporarily unavailable or rejects the corresponding renewal, what is the required business rule—should the payment remain captured and enter a reconciliation queue, be automatically refunded/voided, or require staff approval before the customer's agreement is considered renewed? That decision affects the transaction state machine, reconciliation architecture and audit requirements from day one.

  • Asad C.

    - Could you provide more details about the existing .NET EPOS and how it currently exposes customer, transaction, and buyback agreement data? Does the EPOS already have APIs or integration endpoints available, and which operations will the new platform be allowed to perform back into the EPOS, such as creating renewals, recording payments, updating agreement status, or generating transaction references?

    - Could you clarify the exact business rules that determine whether a buyback agreement is eligible for renewal? For example, are there different renewal periods, fees, grace periods, limits, or product/customer conditions, and should these rules be calculated by the new platform or remain controlled by the EPOS?

    - How should the complete digital agreement process work from the customer's perspective, from receiving the agreement through acceptance/signature to final storage and confirmation?

    - For online renewals, what should happen at each stage of the payment process, particularly when a payment succeeds, fails, is cancelled, or is completed but the EPOS update fails?