Record at a glance
- Evidence level
- Portfolio record: delivered scope from the project documents
- Client
- A Dubai-based loyalty and rewards technology company; not named
- Sector
- Loyalty and rewards
- Client location
- Dubai
- Netbase role
- Delivered the platform in four phases over 3.5 to 4.5 months
- Architecture
- Magento 2 Open Source with a Next.js front end, deployed on AWS or on-premise
- Languages
- Arabic and English
- Service
- Custom Product Engineering
- Published metrics
- None
What the platform contains
One platform serves many reward shops, each branded for a different client programme. A shopper browses merchandise, gift cards and travel bookings and checks out with a hybrid of points and cash, so a single order can draw on a points balance and a card in the same transaction. A multi-vendor module routes each line to the supplier that fulfils it and raises an alert when a service level is breached. The interface is available in Arabic and English. A centralised super-administrator dashboard sits above all the shops, and mobile software development kit interface components let the company embed reward shopping inside its clients' own applications.
The integration surface
This is the part of the record a buyer should study, because it is where the work actually was. The platform connects to three systems, each over the mechanism the record states:
| System | How it connects | Best for |
|---|---|---|
| Points middleware | Webhooks, so a balance change arrives immediately | Checkout flows that must not oversell a points balance |
| Ordering service | Webhooks, so an order event arrives immediately | Keeping order status in step across branded shops |
| Product catalogue | Scheduled synchronisation, reconciled as a full set | Catalogues too large to keep in real time |
Single sign-on carries identity in from the programme side, and payment gateways handle the cash half of a hybrid checkout.
Three consequences follow from that shape. A points balance is authoritative somewhere else, so the checkout has to reserve and release rather than assume. A catalogue that arrives by scheduled synchronisation is always slightly behind the source, so the order path needs a rule for what happens when it is wrong. And a fulfilment service level that can be breached needs an owner for the alert, not only a definition of the breach. Teams scoping a similar programme can compare how a points balance interacts with a card terminal on the point of sale glossary entry, the sector context on retail, commerce and marketplaces, and the wider platform pattern on the loyalty and rewards platform guide. Programmes that combine rewards with an ongoing membership community can also see membership and community platforms.
Technology and delivery
The commerce core is Magento 2 Open Source, the storefront is Next.js, and the two are separated so the same core can serve differently branded shops. Deployment targets were AWS or on-premise. Delivery ran in four phases over 3.5 to 4.5 months.
Evidence level and limitations
- This is a portfolio record. It reports scope from the project documents and nothing those documents do not state.
- An agreement of confidentiality covers the engagement, so the client name, brand, programme and partner stay unnamed, and the integrations are described only by the synchronisation pattern above.
- The per-shop user numbers and load-time figures in the documents are requirements written into the specification, not measured results. They are not published.
- Other bids held in the same source folder are not Netbase work and are not drawn on here.
- The source records no result, adoption or revenue figure for this engagement.
- The image on this page is illustrative. It shows no client system and no interface.
Questions a buyer asks
What does hybrid points-and-cash checkout mean in practice? A single order can be settled partly from a points balance held in the programme's own system and partly through a payment gateway.
Which languages and deployment options does the platform support? Arabic and English, with AWS or on-premise deployment.
Can this record name the client or the loyalty programmes it serves? No. Confidentiality covers the engagement, and the client is described only as a Dubai-based loyalty and rewards technology company.
Can Netbase work with a client in my country? Yes. Every service on this site is delivered remotely from Hanoi, and Netbase has worked with clients in 80 countries. Delivery communication is in English, with weekly reviews and a named project manager.
Does Netbase work in my industry? Netbase takes on projects in any industry where the work can be delivered remotely and accepted by milestones. The industry pages describe the approach sector by sector, and the Work records show delivered projects.
How do I pay for a project? Payment is by bank transfer to the company account of Netbase JSC or through PayPal Business. The payee is always Netbase JSC, the company that operates OutsourcingVN.
Who do I talk to, and how do I start a project? Talk to Huy Nguyen (David), Founder and CEO of Netbase JSC: message him on WhatsApp at +84 937 869 689 or email project@netbasejsc.com. You can also send your brief through the project request form. Say which workflow or system the project concerns and what has to stay unchanged; the first step is a discovery conversation, and scope and milestones are agreed after it.
Planning an integration-heavy build?
Order, payment and fulfilment patterns are set out under order and payment operations, comparable platforms are scoped through Custom Product Engineering, and the methodology page explains the evidence grading used across the work records. When you are ready, submit a project brief. OutsourcingVN is operated by Netbase JSC and is Netbase's own outsourcing-services platform.