Products and Configuration
Fee and commission plans, feature flags and country config - all versioned and effective-dated
Grace Umutoni - Config Administrator
1 change pending checker
Configuration governance: every change here is versioned, effective-dated, requires a checker distinct from the maker, and can be rolled back or simulated before it goes live. Pricing, fee and commission plans are owned by the Rules and Config Engine (BRCE) and audited to the WORM store.
Country config:
Rwanda active
What this screen is answerable for. One configuration surface covers fee and commission plans, wallet limits and tiers, lending products and charges, marketplace listing controls, notification templates and catalogues, care SLA targets, report definitions and country config. Each is versioned, effective dated and maker-checked.
Marketplace commission plan
Draft v14 pending checkerCurrently effective: v13 since 01 Jul 2026 - editing draft v14, effective 01 Aug 2026
| Category | Commission | Min fee | Applies to |
|---|---|---|---|
| Electronics | % |
RWF 500 | All sellers |
| Fashion | % |
RWF 300 | All sellers |
| Groceries | % |
RWF 200 | All sellers |
| Home and Living | % |
RWF 300 | All sellers |
Maker-checker: you are the maker on v14. It will not take effect on 01 Aug until a distinct checker approves it.
Version history
effective-dated - rollback-able| Version | Effective from | Maker | Checker | Change reason | Status | Action |
|---|---|---|---|---|---|---|
| v14 | 01 Aug 2026 | Grace Umutoni | awaiting | Q3 seller incentive | Pending checker | Review |
| v13 | 01 Jul 2026 | Grace Umutoni | Patrick Habimana | Mid-year repricing | Live | Roll back to this |
| v12 | 01 Apr 2026 | Patrick Habimana | Grace Umutoni | Fashion commission +1% | Superseded | Roll back to this |
| v11 | 01 Jan 2026 | Grace Umutoni | Patrick Habimana | New year base plan | Superseded | Roll back to this |
Rollback: rolling back does not delete history. It creates a new approved, audited version that restores the chosen plan, still under maker-checker.
Feature flags
Rwanda (RWF)Instant settlement
Merchants can settle to wallet in minutes for a fee
Checkout BNPL
A wallet loan taken at checkout, split settlement to the merchant
USSD delivery confirmation *182#
Confirm marketplace delivery from any feature phone
Merchant financing offers
Show settlement-backed working capital offers
Note: toggling a flag is a maker-checker, effective-dated change like any other config item. Flags gated to a later phase are shown but locked in Rwanda.
Dry run result
Nothing has been published. This is what the change would do.
A dry run evaluates the proposed value against sample
inputs and returns the outcome difference. It is the Phase 1 way of seeing a config change before
it goes live, and it touches nothing.
| Sample input | Current value | Proposed value | Difference |
|---|---|---|---|
| Electronics order, RWF 189,000 | Commission RWF 15,120 at 8.0% | Commission RWF 16,065 at 8.5% | + RWF 945 |
| Groceries order, RWF 32,500 | Commission RWF 1,625 at 5.0% | Commission RWF 1,625 at 5.0% | No change |
| Fashion order, RWF 65,000 with a flash sale fee | Commission RWF 6,500, fee RWF 0 | Commission RWF 6,500, fee RWF 0 | No change, stacking rule unchanged |
| Order with a corporate voucher | Commission on gross | Commission on gross | No change |
Merchants affected
148
Electronics only
Monthly revenue effect
+ RWF 1.9M
On last month's volume
Merchants worse off by 5%+
0
No plan floor is breached
A dry run is not an approval. Publishing still needs a change reason,
an effective date and a second operator.
Products and Configuration
Commission plan v14 draft against v13 in force
Both versions are shown together, never one replacing the other on screen. A checker deciding a config change needs to see what is live and what is proposed side by side, because the diff is the decision.
| Setting | v13, in force | v14, draft | Change |
|---|---|---|---|
| Electronics commission | 8.0% | 8.5% | +0.5 points |
| Groceries commission | 5.0% | 5.0% | No change |
| Fashion commission | 10.0% | 10.0% | No change |
| Minimum commission per order | RWF 200 | RWF 250 | +RWF 50 |
| Instant settlement fee | 1.0% | 1.0% | No change |
| Stacking order | Commission, then processing, then withholding | Commission, then processing, then withholding | No change |
| Draft created by | g.nyirahabimana, today 09:14 |
| Change reason | Board approved electronics repricing, minute 2026-07-12 |
| Effective from | 1 August 2026, 00:00 |
| Merchants affected | 148, electronics only |
| Waiting on | A config approver who is not the maker |
| Booked orders | Unaffected. A plan version applies from its effective date forward. |
Nothing is retrospective. An order placed on 31 July settles on v13 even if it is confirmed in August, because the version is pinned at order time rather than at settlement time.
Products and Configuration
A change reason is required before this can be submitted
Submit is blocked because the change reason is empty. This is not a form nicety. A config change with no recorded reason is unauditable, and in a year nobody will remember why the electronics rate moved.
Required. Name the decision or the authority behind the change.
| Error the platform returns | 422 CHANGE_REASON_REQUIRED |
| Applies to | Every config version, every rule version, every product version |
| Who can waive it | Nobody. There is no override flag. |
| Where it ends up | The version record, the approvals inbox and the audit chain |
Good reasons are specific. "Board approved electronics repricing, minute 2026-07-12" is useful. "Update" is not, and a checker is entitled to refuse it.
Products and Configuration
Approved and scheduled, not yet in force
Approved by a checker, and it activates by itself on 1 August at 00:00. Nobody has to be at a keyboard for it to take effect, and nobody can bring it forward without a new version.
| Version | Commission plan v14 |
| State | Scheduled |
| Maker | g.nyirahabimana, 19 July 09:14 |
| Checker | t.nkusi, 19 July 11:20 |
| Effective from | 1 August 2026, 00:00 CAT |
| In force until then | v13 |
| Can it be brought forward | No. That would be a new version with its own approval. |
| Can it be cancelled | Yes, until the effective moment, by a checker |
| Version | Effective from | State | Approved by |
|---|---|---|---|
| v14 | 1 Aug 2026 | Scheduled | t.nkusi |
| v13 | 1 Apr 2026 | In force | m.habimana |
| v12 | 1 Jan 2026 | Superseded | t.nkusi |
| v11 | 1 Oct 2025 | Superseded | m.habimana |
The history is append only. A superseded version is never deleted, so a dispute about what a merchant was charged in February can be answered from the record rather than from memory.