The PROCUX ecosystem

Four parts,
one network.

Hubcux isn't an app on its own. The engine that pools spot demand, the cooperative that binds routine supply to framework contracts and the payment layer that protects the money all run on the same network — the user sees one interface.

hubcuxInterface

merkezisatinalmaDemand engine

satinalmamerkeziCooperative

PayCuxPayments

The parts

Each does one job, all of them are connected

The ecosystem has four layers. The user only sees Hubcux; the other three work behind it.

hubcuxSuper-app · the layer the user sees

Interface

The single app where orders are placed, quotes are seen, payments are made and deliveries are tracked. Everything the other three layers can do is used from here. Hubcux doesn't open a separate membership; you connect with the account you already have in the ecosystem.

ChatQuotes & RFQOrder trackingOrder AssistantMini apps

merkezisatinalmaDaily demand pool

Spot demand

Takes requests outside the framework, groups them by meaning and places them in the day's pool. The pool closes at 17:00, quote requests go to approved suppliers at 17:15, and the price comes for approval within 24 hours.

Free-text requestsSemantic groupingSupplier scoring24-hour approvalQuote confidentiality

satinalmamerkeziPurchasing cooperative

Routine supply

Signs framework contracts with wholesalers on behalf of members; for routine items the negotiation happens once per period. The member price appears without waiting and the order opens immediately.

Order CentreFinance CentreOrder AssistantSales AssistantMarketing HubInvoice Centre

PayCuxOur own payment infrastructure

Money

Holds the amount collected from the buyer and releases it to the supplier on delivery confirmation. Wallet balances, reconciliation and refunds all run in this layer.

Held accountWalletRelease on confirmationReconciliationRefunds

How they work together

One order passing through the layers

The user does one thing on one screen; behind it, the type of need decides which engine runs.

merkezisatinalmaThe need is classifiedIf what you type into Hubcux is a framework-contracted item it goes to the cooperative; if not, into the day's pool.

cooperative / poolThe price is setFor a framework item the member price appears instantly. For a pooled item quotes are collected and scoring surfaces the best match.

PayCuxThe payment is heldThe buyer approves and the amount moves to a held account. The supplier sees the payment and starts supplying.

hubcuxThe process is tracked on one screenShipping, delivery confirmation, release of the hold and the e-invoice — all of it flows in the single app the user sees.

Why one network

Apart, each part would carry the others' gaps

01A cooperative alone isn't enoughFramework contracts solve routine items. When something unlisted, infrequent or non-standard comes up, there is no ready price.

02A pool alone isn't enoughPools solve spot demand, but waiting until 17:00 every day for the coffee you buy weekly makes no sense. Routine supply can't absorb waiting.

03A payment layer alone isn't enoughYou can protect the money, but if the two sides never find each other there is no trade to protect.

Corporate structure

Four brands, one company

Hubcux, merkezisatinalma, satinalmamerkezi and PayCux are products developed at Balıkesir Teknokent under PROCUX TEKNOLOJİ A.Ş. They share the same data model, the same verification layer and the same security standards.

You enter Hubcux with your account from either platform
Verification happens once and is recognised everywhere
Supplier scores are shared across the ecosystem
Invoices and contracts gather in one archive

PROCUX Teknoloji A.Ş.Parent company

hubcuxSuper-app

merkezisatinalmaDemand pool