STEP 01
Price from the buyer's tier
Each buyer resolves to one price list with volume tiers. A buyer with no assigned list gets no price and cannot order — failing closed rather than falling back to a default nobody chose.
Approved dealers only · Funds held before any code moves
We route
the world's codes.
We supply digital voucher codes to approved trade dealers. Every order reserves funds against the dealer's wallet before a code leaves the vault, every code is issued to exactly one order line, and every line is billed for the quantity actually delivered.
Scroll to explore
One hub. Every supplier.
Suppliers quote independently and their prices move independently. Routing every order to one of them leaves margin on the table — and leaves you with no second option when they fail.
36
Currencies, incl. 3-decimal KWD
4
Sub-distributor tiers
0
Floating-point values in the ledger
318
Tests gating every release
How routing works
Cheapest is not always
the right answer.
A price older than the freshness window, or stock that cannot cover the quantity, disqualifies a supplier before price is compared at all. Every rejection is recorded with its reason, so any decision can be explained months later without re-running anything.
| Supplier | Unit cost | Price age | Outcome |
|---|---|---|---|
| supplier-d | AED 89.95 | 12s | Rejected — no stock |
| supplier-c | AED 90.80 | 61m | Rejected — price stale |
| supplier-a | AED 91.40 | 18s | Selected |
| supplier-b | AED 92.15 | 24s | Held as fallback |
STEP 02
Reserve the funds
Money moves from the spendable wallet into a hold, under a per-buyer lock. Two simultaneous orders queue rather than both passing the same balance check. That is what stops a double-spend.
STEP 03
Buy from the cheapest live supplier
Stale prices, empty stock, quantity caps and contract restrictions eliminate suppliers first. What remains converts to one currency and ranks. If the winner fails, the next is tried automatically.
STEP 04
Settle, or return every fils
On delivery the hold splits into supplier cost and your margin. If nothing could be sourced, the hold is released in full. Either way the double-entry ledger balances to zero.
Where the money sits
Every movement is
a journal line.
A customer's wallet is a liability — their money held by you, never booked as your own. Amounts are integer minor units; the system holds no floating-point value anywhere.
| Event | Debit | Credit | Amount | Spendable |
|---|---|---|---|---|
| Customer tops up | CASH | CUSTOMER_WALLET | 10,000.00 | 10,000.00 |
| Order placed — funds reserved | CUSTOMER_WALLET | CUSTOMER_HOLD | 367.25 | 9,632.75 |
| Codes delivered — hold settled | CUSTOMER_HOLD | SUPPLIER_FLOAT 350.00 REVENUE_SALES 17.25 | 367.25 | 9,632.75 |
| or supplier failed — hold released | CUSTOMER_HOLD | CUSTOMER_WALLET | 367.25 | 10,000.00 |
Stocking the shelves behind the brands you know
Platform
Built for distributors,
not for end consumers.
Wholesale distribution needs things a retail storefront does not: prepaid float, credit terms, per-buyer pricing, and the ability to hand a dealer their own API.
01
Supplier routing
Cheapest in-stock per SKU, with reliability and deterministic tie-breaks. Automatic failover excludes the supplier that just failed.
02
Wallets and terms
Prepaid balance plus an optional credit line and net terms. Every limit change is audited by database trigger, not by convention.
03
Sub-distributor API
Their own key, their own price list derived from yours with a markup, their own wallet. Up to four tiers deep.
04
Code vault
Encrypted per record and bound to it. Issued exactly once, enforced by the database. Every read logged with who, when and why.
05
Idempotent throughout
Every mutating call is keyed by the caller, so a network retry after a timeout reaches the same order and never charges twice.
06
Marketplace rules
Suppliers whose contracts bar onward resale are excluded from marketplace channels automatically, rather than by an operator remembering.
Security
Your supply chain never
leaves the building.
Which suppliers you use, and what you pay them, is the commercial value of a distribution business. The architecture treats that as a secret to be structurally protected, not a field someone must remember to strip.
ISOLATION
Identity cannot leak upward
The types returned to buyers carry no supplier, cost or margin field at all. Leaking one is not an oversight you can make — the data is not in the shape.
CREDENTIALS
Sealed and bound to their row
Supplier credentials are encrypted with a key derived per record. A ciphertext moved to another supplier's row fails to decrypt rather than quietly working.
KEYS
Only hashes are stored
An API key is never recoverable after issue, not even by us. A stolen database yields nothing usable, and every authentication attempt is logged.
ERRORS
Nothing informative reaches an attacker
Another buyer's order returns "not found", never "forbidden" — a distinction that would confirm it exists. Internal errors return a bare 500.
Questions
What distributors ask first.
Direct answers, for people who already run a distribution business.
What is multi-supplier routing?
Holding contracts with several suppliers at once and, for each individual product, buying from whichever is cheapest and actually in stock at that moment. Prices for the same product move independently between suppliers, so routing everything to one supplier leaves margin on the table. Routing also gives you failover: if the cheapest rejects an order, the next is tried automatically.
Can I connect my own supplier accounts?
Yes — that is the point. This is software that runs over the contracts you already hold, not a network reselling its own catalogue to you. Your terms with each supplier stay yours, and the routing margin stays with you rather than an intermediary.
How does API resale to sub-distributors work?
Each sub-distributor gets their own API key, their own price list derived from yours with a markup, and their own prepaid wallet. They call the same API you do but see only their prices and their orders, and can have sub-distributors of their own up to four tiers deep. None of them can see your supplier costs or which supplier filled an order.
How are codes protected?
A code is a bearer instrument: whoever reads it can spend it. Codes are encrypted at rest with AES-256-GCM using a key derived per record and bound to that record, so a ciphertext copied elsewhere will not decrypt. Each code can be issued to exactly one order line — enforced by the database, not by application logic — and every decryption is recorded with who, when and why.
What happens if a supplier fails after a customer has paid?
Funds are reserved before any supplier is contacted and settled only once codes are delivered. If every supplier fails, the reservation is released and the full amount returns to the wallet. The ledger is append-only, so that refund is a recorded movement rather than an edit, and the books balance at every point in between.
Which regions and currencies are supported?
Thirty-six currencies, including the three-decimal Gulf currencies KWD, BHD and OMR and zero-decimal currencies such as JPY and KRW. Products carry a region code, and suppliers whose contracts restrict onward marketplace resale are excluded from marketplace channels automatically rather than by an operator remembering.
How is VAT handled?
Every line on the platform is a voucher code, invoiced VAT-exempt / out of scope. Optrenex International General Trading LLC is the invoicing party on every order.