


How we built verified supplier onboarding, a searchable catalogue and an auditable deal workflow for Hyves — a Dubai client trading luxury goods between vetted dealers worldwide.
Hyves is a B2B trading platform for verified dealers in watches, bags, art and sneakers. Strip away the product category and what remains is a procurement system: qualify your suppliers, publish a catalogue, let buyers search live availability, negotiate with a record, and control the point between inspection and payment.
It goes further than most trade platforms do. Shipped and running are supplier performance scoring — counterparties rate each other after every trade, so approval is re-earned rather than granted once — plus competitive bidding, time-boxed quote validity holds, requisitions broadcast to the approved network, multi-currency purchasing and a formal dispute escalation path. And we do the ERP integration ourselves — Oracle, Workday, Bullhorn and UKG are shipped in production — so a portal build does not need a second vendor bolted onto it.
Digital Innovation built it end to end — data model, backend, web application, iOS and Android apps, and the AWS infrastructure underneath. It is live at hyves.co, so every capability described on this page can be checked in a click.
This will be familiar to anyone running distribution or procurement in a relationship-driven trade. The market worked — it simply worked in scattered chat threads, and everything that a business needs from a transaction was lost the moment the conversation scrolled past.
Dealers were sourcing and selling across dozens of unconnected messaging groups. The same stock was posted repeatedly by hand, and a buyer looking for one specific item had no way to search supply — only to ask everyone and wait.
In a trade where a single item moves for five or six figures, counterparty risk is the whole business. There was no shared record of who was verified, who had traded before, or who could be trusted with goods in transit.
Negotiations happened in personal chats, so terms, photos and agreements were scattered across devices. Nothing was recoverable, reportable or transferable to a colleague.
Even once two dealers agreed, moving high-value goods and money between strangers in different countries needed an intermediary — and arranging one ad hoc slowed every cross-border deal to a crawl.
Each piece below is visible on the live platform or in its published app listing. Together they take a deal from “who can supply this?” to “goods received, payment released” without leaving the system.
A vetting workflow where dealers submit business documents and certifications, and are admitted only after the client's team has checked them — so every counterparty is a known, approved trading entity rather than an anonymous account.
A structured inventory model covering four distinct categories — watches, bags, art and sneakers — each with its own attributes, condition states and imagery. Publish an item once, and it is visible to the entire verified network.
Advanced search and filtering across live supply, so a buyer with a specific requirement finds it directly instead of broadcasting a request and waiting for replies.
Integrated secure messaging built into each deal — photos, voice notes and location sharing in one thread — so negotiation, evidence and agreement live in the same auditable place rather than in someone's personal chat history.
The platform surfaces the client's own global office network for authentication, escrow and secure handling, turning cross-border settlement from an ad-hoc arrangement into a standard step in the deal flow.
One platform delivered across web, iOS and Android, because dealers close deals from a phone on a shop floor as often as from a desk.
Dealers rate and review each other after trading, so performance accumulates into a visible track record instead of living in one person's memory. In procurement terms this is a supplier scorecard, and it is the capability most trade platforms leave out.
Buyers bid on listings, reserve an item for a fixed 15-minute window while they decide, and post open "looking for" requests that notify them when matching supply appears — demand signals running in the opposite direction to the catalogue.
Trading in the counterparty's preferred currency with worldwide currency support, and a formal escalation path where the client's team resolves disputes — so a disagreement has a defined process rather than ending the relationship.
Everything here is checkable without asking us. The platform is live at hyves.co, and the shipped feature set is described in the client’s own App Store listing. We would rather point you at the client’s own words than ask you to take ours.
A luxury-goods platform sounds unrelated to distribution or procurement until you line the two up. The left column is what we shipped for Hyves. The right column is the same capability under the name a sourcing, wholesale or procurement team would give it.
| What we built for Hyves | The same thing in procurement terms |
|---|---|
| Verified dealer onboarding | Supplier qualification and vendor onboarding — approving, recording and maintaining an approved-supplier list. |
| Multi-category catalogue with attributes and condition states | Product and SKU catalogue management across categories, with the attributes each category actually needs. |
| Search and filtering over live supply | Sourcing and supplier discovery — finding who can supply a given specification right now. |
| Deal thread with photos, notes and agreement in one place | RFQ and quotation workflow with a complete, auditable negotiation record per line item. |
| Authentication, escrow and secure handling | Goods inspection, acceptance and payment release — the control point between order and settlement. |
| Native apps for dealers in the field | Mobile approvals and field ordering for buyers, reps and warehouse staff. |
| Document submission and checking at onboarding | Vendor document compliance — trade licences, certifications and credentials collected and verified before a supplier is approved. |
| Dealer rating and review after each trade | Supplier performance scoring and vendor scorecards — a track record that accumulates instead of being re-litigated every renewal. |
| Bidding and a 15-minute reservation hold | Competitive tendering, and a quote validity window inside which a price is committed. |
| "Looking for" requests broadcast to the network | Requisitions raised against the approved-supplier list, with notification when supply appears. |
| Trading in the counterparty's preferred currency | Multi-currency purchasing across markets, without a separate process per country. |
| Formal dispute escalation handled by the operator | Contract dispute and claims handling — a defined path when goods, terms or payment are contested. |
We are not claiming to have built an ERP procurement module. We are saying the hard parts of one — supplier verification, catalogue structure, searchable availability, an auditable negotiation record and a control point before payment — are already running in production in a business where getting them wrong costs six figures a deal.
The fair objection to this case study is that a platform trading single high-value items is not a platform trading pallets. That is correct. Hyves models the condition of one watch; a distributor models pack sizes, price bands and credit. So here is the honest split — what we would genuinely reuse, and what we would build new for you.
Already designed, built and running in production.
The commercial layer wholesale needs and luxury resale does not.
We would rather show you this split now than discover it in month two. The left column is why this engagement starts ahead of a blank page; the right column is what the discovery sprint scopes and prices.
A trade portal is only half the job. The other half is making it talk to the system that already holds your stock, your customers and your ledger — and that is usually where these projects fail. It is not a gap in our record; it is one of the strongest parts of it.
On Asurint, a US background-screening platform used by Manpower, CRST and Employbridge, we shipped production integrations into the HR and staffing systems its customers already ran. On that engagement the integration was the product, not an add-on.
Shipped in production, not a capability list. We have not delivered a Coupa or Ariba implementation, and we will say so rather than stretch a case study to fit. For the AI layer on top of these systems, see AI Enterprise Integration.
PostgreSQL with a Sequelize/Node service layer, modelled around dealers, listings, categories and deal threads — so a new trading category can be added without reshaping the schema.
A server-rendered web application, chosen so listings load fast and remain crawlable, with a shared component layer across the marketing and application surfaces.
Deployed on AWS behind a continuous integration and delivery pipeline, so releases ship frequently and safely instead of in risky batches.
Verification state, deal history and messaging permissions were treated as core domain logic rather than bolted-on features — in a high-value trade, trust is the product.
The platform is live, in production, and serving a verified dealer network internationally. Trading that previously ran across disconnected messaging groups now runs through a single system with verified counterparties, searchable supply and a record of every deal.
Hyves states on its own website that the platform will “10X your dealflow” and save dealers thousands of hours. That is their published positioning, and we reproduce it as theirs. We did not measure it, and we will not present it as a result we produced.
There are no other numbers on this page, because we do not hold client-approved figures for this engagement. We would rather publish a case study with no metrics than one with metrics we cannot stand behind. Where we can quantify an outcome — as with Harry, our AI co-worker platform — we do.
The same building blocks — approved suppliers, a real catalogue, searchable availability and an ordering thread with a record — are what replaces WhatsApp-and-spreadsheet ordering in a distribution business.
Supplier qualification, sourcing, RFQ, and an inspection-to-payment control point are the same four stages we built here, under different names.
Two-sided liquidity, counterparty verification and a settlement layer are the three problems every trade platform has to solve. We have solved them once, in production.
If your buyers and suppliers do not already know each other, the verification and custody design matters more than the catalogue. That is the part most builds underestimate.
Not by name — it is a B2B trading platform for verified luxury dealers. But the stages it automates are the procurement stages: qualifying and approving suppliers, publishing and searching a catalogue, running a negotiation with an auditable record, and controlling the point between goods inspection and payment. That is why we describe it in procurement terms rather than retail ones.
End-to-end product engineering: the data model, the backend services, the web application, the iOS and Android apps, and the AWS infrastructure and CI/CD pipeline underneath them. The platform is live at hyves.co.
The client is based in Dubai, United Arab Emirates. The platform itself serves verified dealers internationally, so it is a Dubai client with a global product rather than a UAE-only system.
It is the client's own published claim on hyves.co, not a figure we measured or independently verified. We reproduce it as their statement and label it as theirs. Every other statement on this page describes work we delivered, and can be checked against the live platform.
Because we do not have client-approved figures for this engagement, and we would rather publish a case study with no numbers than one with numbers we cannot stand behind. If you want financial outcomes, ask us about Harry, where we can quantify the saving.
Yes, and it is the closest match in our portfolio to that brief. The reusable parts are supplier verification, the catalogue model, searchable availability, the deal or order thread, and the control point before payment. What changes is the category model, the pricing and credit rules, and the integrations into whatever ERP or accounting system you already run.
Both. Onboarding verifies a supplier once, using submitted documents and certifications; the rating and review system then records how each counterparty actually performs on every trade afterwards. That second half is a supplier scorecard, and it is the part most trade platforms skip — approval is treated as permanent rather than as something a supplier keeps earning.
The trade mechanics carry over: supplier approval, catalogue structure, searchable availability, an auditable order thread, and the control point before payment. What does not carry over is the commercial layer a distributor needs — bulk and case quantities, MOQs, tiered and customer-specific price lists, credit terms, live stock synchronisation and tax or duty rules. Hyves models condition states for a watch; your business models pack sizes and price bands. We would reuse the first list and build the second.
We do the integration ourselves — it is one of the strongest parts of our record rather than a gap. On Asurint, a US background-screening platform used by Manpower, CRST and Employbridge, we shipped production integrations with Oracle, Workday, Bullhorn and UKG, where the integration was the product rather than an add-on. We have not delivered a Coupa or Ariba implementation and will say so rather than stretch a case study to fit.
A build of this shape is a multi-month engagement, and the honest answer depends on how much of the trust and settlement layer you need on day one. We scope it in a paid discovery sprint and give a fixed price and a fixed date after that — not before.
No. We are an engineering company based in Lahore, Pakistan, working as an offshore delivery partner. Our working day overlaps the UAE business day by all but one hour. We say this on the first screen rather than the last.
Tell us how sourcing works in your business today. We will tell you which parts of this are reusable, which need building, and roughly what that costs — and if we are not the right fit, we will say so.