- 01
Market
Saudi Arabia
- 02
Written for
Commercial Director, CIO, COO
- 03
Decision
Give distributors, suppliers and business customers a working channel into our systems
- 04
Languages
EN · AR
Information security for software delivery

ISO/IEC 27001
ISO/IEC 27001 certified
The order path
From a branch buyer's basket to a confirmed line in your ERP
The point of a B2B portal is that this path runs without a phone call — including the checks a phone call used to perform.
A flow from order placement through the customer's own approval, a live ERP check and fulfilment reporting back — with a branch routing unusual orders to the sales desk with context.
- 01
The order is placed
A buyer at one branch orders against their organisation's catalogue and contract prices — the ones negotiated for them, not a public list.
- 02
Authority is checked
The portal knows this buyer's limit and their company's rules: an order above threshold routes to the customer's own approver before it ever reaches you.
- 03
The ERP answers
Availability, credit standing and delivery dates come from the ERP live, so the confirmation the buyer sees is the one your warehouse will honour.
- 04
Fulfilment reports back
Despatch, delivery and the invoice flow back into the portal against the same order, so "where is it" stops being a call to your account manager.
The order that needs a person
A blocked credit line, a special price, an unusual quantity — these route to your sales desk with the full context attached, instead of failing silently or going through unchecked.
The organisation model
What a B2B portal must model that no consumer login ever needs
Each of these is a structural requirement. Skipping one does not make the portal simpler; it makes the customer keep phoning.
The company as the account
The organisation, its branches and its people are modelled as a hierarchy, with terms, catalogues and credit held at the right level of it.
What the customer can then do: A head office view across branches, and branch views of their own.
Delegated administration
Each customer organisation appoints its own administrators, who add, remove and permission their users — within boundaries your side defines and can audit.
What the customer can then do: A joiner or leaver at the customer handled the same day, by them.
Approval chains that mirror theirs
Order thresholds, spend limits and multi-step approvals are configurable per organisation, because your customers do not share one org chart.
What the customer can then do: Orders arriving already authorised by the customer's own rules.
Contracts and prices as data
Negotiated prices, volume terms and validity periods live in the system of record and surface in the portal — every basket priced from the contract, not from a stale export.
What the customer can then do: A price the buyer, the invoice and the contract all agree on.
The distinction
Why a consumer portal cannot be promoted into a B2B one
The tempting shortcut is to take a working consumer portal and add company accounts to it. It fails on structure, not effort: a consumer portal's deepest assumption is that one login equals one person equals one account, and everything above it — carts, payments, history, notifications — inherits that assumption. A business relationship breaks it in every direction: many people act for one company, one person acts for several branches, the entity that orders is not the entity that pays, and authority depends on amount, category and the customer's own delegation rules.
The same distinction runs through the workflows. A consumer completes a purchase in one sitting; a business order may wait for an approver, draw on a credit line, reference a contract and arrive in five deliveries against one invoice. So we build B2B portals on an organisation model from the first line, and where a company runs both channels, the two portals share integrations and a design language — but not an account model, because the account model is precisely what differs.
Our role
Wiring the B2B portal to the ERP without duplicating the ERP
- 01
One system of record
Prices, stock, credit and orders stay owned by the ERP; the portal reads them live and writes orders back through defined interfaces. A portal that keeps its own copies becomes a second ERP that argues with the first.
- 02
Designed for the ERP's pace
ERPs answer at their own speed and sometimes not at all, so the portal is built for that reality — cached reads where staleness is safe, live checks where it is not, and clear behaviour when the back end is briefly away.
- 03
Rollout customer by customer
We onboard pilot organisations first — real distributors with real orders — and let their friction reshape the portal before the long tail joins. Adoption is won at the first organisations, not announced at launch.
Credit policy, pricing authority and who may override what are commercial rules that stay with your team; the portal enforces them consistently instead of asking your account managers to remember them.
Common questions
What buyers ask
How does a B2B portal handle one company with many branches and buyers?+
By making the organisation, not the person, the unit the portal is built around. The company is modelled as a hierarchy — head office, branches, and the people within each — and every commercial fact attaches at its correct level: contract prices at the company, delivery addresses and stock views at the branch, spend limits at the individual buyer. A head-office finance user then sees consolidated orders and invoices across all branches, while a branch buyer sees their own, and an order placed anywhere carries its full context — which branch, which buyer, under whose approval — into your ERP. That structure is also what makes onboarding a fifty-branch customer tractable: you set up the organisation once and they populate it themselves.
Can our customers administer their own users in the B2B portal?+
Yes — delegated administration is one of the strongest reasons to build the portal at all. Each customer organisation appoints administrators who add and remove their own users, assign roles and set buyer limits, all within boundaries your side defines: which roles exist, what each may ever do, and a full audit trail of who granted what. Without it, every joiner, leaver and permission change across hundreds of customer organisations lands on your service desk, and the dangerous workaround appears — shared logins, which destroy accountability. With it, access hygiene at the customer improves because the person managing it actually knows who joined and who left.
Does a B2B portal replace our ERP's order entry or sit in front of it?+
In front of it, always. The ERP remains the system of record for prices, stock, credit and orders; the portal is the channel through which your customers reach it, with the organisation model and approval workflows the ERP was never built to expose externally. Practically, the portal reads availability and pricing through defined interfaces and writes orders back as first-class ERP orders, so your fulfilment, invoicing and reporting continue unchanged — the portal's orders are not a parallel stream someone re-keys. The alternative, letting the portal keep its own product and order data, creates the reconciliation problem that makes teams distrust both systems within a quarter.
In this cluster
Walk us through your systems
A working session that maps one real customer organisation — branches, buyers, approvals — into a portal model your commercial team recognises.
Start the conversation