MONTRA Lifts
B2B elevator spare-parts marketplace — smart order routing, RFQ workflows, tamper-proof ledgers.

// By the numbers
- 100%
- Money traceability
- Automatic
- Order dispatch
- 4
- Client apps
- 98%
- Scope delivered
tamper-proof ledgers — every payout and commission auditable end to end
smart routing splits each order to the right suppliers, no manual dispatch
customers, installers, traders and admins each get their own surface
of the contracted platform shipped to production
// From the client
The order routing and the financial ledger are what sold us. Every payout and commission is traceable end to end, and an order automatically splits to the right suppliers. For a B2B platform handling other people's money, that trust is everything.
Operations lead
B2B elevator spare-parts marketplace · Egypt
What the business was up against
Elevator spare parts are bought by installers and maintenance companies who need a specific component for a specific lift, often urgently, and rarely from a single supplier. The trade ran on phone calls and spreadsheets: quotations negotiated privately, orders forwarded to suppliers by hand, and commissions and payouts reconciled from memory at month end. Nobody could prove who was owed what, and every large project order was a separate manual operation.
A production-grade B2B marketplace for the elevator spare-parts industry. It connects customers, installers, suppliers and operators through smart order routing, project (RFQ) workflows, tamper-proof financial ledgers and a built-in content system — fully bilingual Arabic/English with right-to-left support.
How it's put together
Customer Marketplace
Catalog · cart · RFQ · returns
Supplier Dashboard
Listings · fulfillment · payouts
Admin Console
Operations · finance · CMS
Marketing Site
CMS-driven · bilingual · SEO
Backend API
Auth · orders · pricing engine · commissions · payments · returns
Relational Database
50+ models · append-only ledgers
Payments
Card · wallet · cash on delivery
Media Pipeline
Image storage & delivery
One backend API powering four independent client applications.
The calls that shaped it
The handful of decisions that determined how this system behaves — and what each one bought.
- 01
Order routing modelled as a first-class step
A basket spanning several suppliers splits automatically into per-supplier sub-orders, each with its own fulfilment state, while the customer keeps one order. Dispatch stopped being a person's job.
- 02
Append-only financial ledger instead of balance columns
Payouts, commissions, refunds and adjustments are entries; balances are derived. It is slower to write and it is the only version that survives a dispute — which for a platform handling other people's money is the whole product.
- 03
Projects (RFQ) separated from direct orders
Large jobs are negotiated, not carted. Giving RFQ its own lifecycle — request, offers, negotiation, award — kept high-value trade inside the platform instead of leaking back to private chats.
- 04
Four role surfaces on one API
Customers, installers, traders and admins each got a purpose-built surface against a single backend, so business rules could not diverge between who saw what.
- 05
Content managed in-platform, bilingually
A built-in CMS drives the marketing site in Arabic and English, so the commercial team can publish without a developer and without a second stack to maintain.
Signature capabilities
Smart order routing
A multi-strategy engine splits each order across suppliers by price, availability and reliability — and re-assigns recursively when an offer is declined.
Project (RFQ) workflows
Installers configure full elevator projects from reusable templates; suppliers bid with multi-item offers, and the winning bid becomes a tracked project order.
Tamper-proof ledgers
Every money movement is an append-only entry with cryptographic checksums, making the financial trail verifiable end to end.
Risk-based deposits
Large orders are gated behind deposit rules that adapt to order value and customer trust before fulfillment begins.
Automated commissions
Platform fees accrue on delivery confirmation, are invoiced on a schedule, and reconcile against each supplier's ledger.
Bilingual & RTL
Every surface and the catalog itself ships in Arabic and English with full right-to-left support.
Business feature set
The functional scope delivered across every part of the product.
Customer marketplace
- Catalog browsing with search & filters
- Multi-supplier pricing per item
- Wishlist & favorites
- Cart, checkout & saved addresses
- Card, wallet & cash-on-delivery
- Deposit gating on large orders
- Order & sub-order tracking with invoices
- Returns & exchanges workflow
- Project (RFQ) requests & supplier offers
Suppliers
- Listings management (price, stock, lead time)
- Bulk import / export
- Order assignment queue (accept / reject)
- Fulfilment lifecycle
- Returns review & approval
- Balance & commission ledger
- Per-supplier analytics
Operations & admin
- Master catalog & categories
- Trader verification & user management
- Order overrides & status control
- Reusable BOM patterns
- Stock overview across suppliers
- Shipping zones & distance matrix
- Commissions, payouts & invoicing
- Platform analytics & promo banners
Content & platform
- Built-in CMS (services, blog, portfolio, clients)
- Bilingual Arabic / English with full RTL
- Activity logs & in-app notifications
- Support ticketing
What changed operationally
Documented outcomes from the delivered system. Where exact figures are confidential, the operational change is stated instead.
- Automatic multi-supplier order dispatch replacing manual forwarding
- Every payout and commission traceable end to end through the ledger
- Four distinct role surfaces live in production on one backend
- RFQ negotiation captured in-platform with a full award trail
- Bilingual Arabic/English storefront and back office with full RTL
- Marketing content editable by the client without a deploy
What we had to work within
- Money handling had to be defensible under dispute, not merely correct on the happy path
- Industrial catalogue with technical part identity, not consumer-style products
- Buyers are trade professionals — speed of reorder matters more than browsing
- Bilingual Arabic/English required across storefront, back office and content
- Suppliers vary widely in digital maturity; the vendor surface had to be usable without training
What I owned
End-to-end on this project — from architecture and data modelling through to a shipped, production product.
- Product & system architecture
- Database design & data modeling
- Backend services: auth, orders, pricing engine, commissions, payments, returns
- Four front-end applications: marketplace, supplier, admin, marketing
- Payment gateway & media integrations
- Bilingual Arabic/English with full RTL
- Containerized deployment & CI/CD
Built with
Backend
Frontend
Infrastructure
Integrations
Want something like MONTRA Lifts?
Boutique software studio — agency-quality systems, shipped by one senior engineer.
// Related work


