Many brands already have a dealer or retailer app for ordering, catalogue, ledger and service. The Unotag SDK adds a scheme and incentive module inside that app. We manage schemes, calculation, progress and payouts for your channel ecosystem; your app carries on with everything else, and your partners install nothing new.
A dealer who already orders on your app will not open another one to check a scheme. Building the scheme logic into your own app is the other option, and it turns every new scheme into a development request. The SDK avoids both.
The scheme screens sit where the partner already places orders, so scheme visibility reaches every active user of your app from the first day.
Scheme rules, eligibility and calculation live on the Unotag platform. A new or revised scheme appears in the module as soon as it is published.
Slabs, growth tiers, clubbed codes, approvals and payouts are our problem. Your team integrates once and returns to ordering, catalogue and service. If you have no app yet, the scheme engine also ships with our own app, WhatsApp and web portal.
The boundary is simple: identity and commerce stay with you, schemes and incentives sit with us.
| Area | Your existing app | Unotag SDK and platform |
|---|---|---|
| Login and identity | Authenticates the partner as it does today | Receives the signed-in partner's identity from your app; no second login |
| Ordering, catalogue, ledger, service | Unchanged | Not involved; can hand a suggested order to your order API |
| Scheme rules and eligibility | None | Configured and managed on the Unotag platform |
| Incentive calculation | None | Calculated by the scheme engine from your invoice feed |
| Scheme screens | Provides the entry point and branding | Schemes that apply, progress, next target, calculator, invoices counted, earnings |
| Payouts and rewards | None | Credit-note file, UPI, gift catalogue or cards, with approvals and tax aggregation |
| Launching a new scheme | No release needed | Published from the admin panel |
Platform and framework specifics are confirmed with your app team during technical scoping.
The same screens that run in Unotag's own app, in your branding, with each function switchable centrally or per sales office.
Every scheme the partner is eligible for, grouped as earning now and not yet qualified.
Where the partner stands today and the next purchase figures at which something opens.
What a planned purchase would earn across all schemes, before the order is placed.
The invoices behind each scheme result, so the number can be checked.
What has been earned, approved and paid, kept behind a tap if you prefer.
Each scheme explained in plain words in 8 Indian languages, in text or voice.
Redemption to UPI, gift catalogue or cards where the program pays in rewards rather than credit notes.
A suggested quantity passed to your own order flow, so the order stays in your system.
One integration serves whichever partners your app reaches.
Volume, growth, collection and cash-discount schemes beside the ordering screens.
Retailer incentive programs with slab progress, invoice proof and rewards.
Incentives for feet-on-street teams and franchise outlets inside the app they already report on.
It is a software module embedded in a brand's existing dealer, retailer or field app that shows the schemes a partner is eligible for, their calculated progress, earnings and rewards. The scheme rules, calculation and payouts are managed by the incentive platform behind the module, not by the host app.
No. The module sits inside your existing app. Partners sign in as they do today and find a schemes section alongside ordering. Unotag manages the schemes and incentives; your app does the other work.
No. Scheme rules, eligibility and calculation live on the Unotag platform, so a new or revised scheme appears in the module when it is published. An app release is needed only for the initial integration and for later SDK upgrades you choose to take.
Your app authenticates the partner and passes the signed-in identity to the module. There is no separate registration or login. The identity is matched to the dealer master used by the scheme engine.
Yes. When a partner acts on a suggested quantity, the module hands the order to your own order flow or order API, so ordering, credit checks and fulfilment stay in your system.
Platform and framework details depend on how your app is built and are confirmed with your app team during technical scoping. If an embedded module is not suitable, the same engine is available through Unotag's app, WhatsApp and a web portal.
Then you do not need the SDK. The same scheme engine is delivered through Unotag's own app, WhatsApp and a web portal, and you can move to an embedded module later without changing the schemes.
How embedding works, who is responsible for what, and the questions to ask.
A decision guide to the four ways of delivering channel incentives.
What a partner-facing incentive app must show, and what it should hide.