Headless multi-store loyalty reward shop platform
Netbase delivered a headless multi-store reward shop platform for a Dubai-based loyalty and rewards technology company. Each of that company's client programmes gets its own branded reward shop, shoppers pay with a mix of points and cash, and orders route to the right supplier. This anonymised record reports delivered scope only. An agreement of confidentiality covers the engagement, no client is named, and no result is claimed.
Submit a project See the other records
Record at a glance
- Evidence level
- Portfolio record: delivered scope from the project documents, no measured result
- Client
- A Dubai-based loyalty and rewards technology company; not named
- 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 the client's points middleware, its ordering service and its product catalogue, using webhooks where an event must arrive immediately and scheduled synchronisation where a full set has to be reconciled. 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, and they are worth planning for on any comparable project. 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.
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. No client name, brand, programme or partner is published, and no interface detail of the integrations is described beyond 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.
- No result, adoption or revenue figure is published, because the source records none.
- 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.
Were the performance numbers in the specification achieved? Unknown, and not claimed. They are requirements in the documents, and no measurement is recorded, so this record does not report them as outcomes.
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.
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.