OHRES: The Only Indigenous African EDI Company That Operates Globally

Published on October 22, 2026

Every EDI vendor serving African businesses today falls into one of two categories.

The first is **global platforms retrofitted to Africa** - SAP, OpenText, IBM Sterling, Cleo, SPS Commerce, Orderful. They are excellent at what they do (US and EU B2B integration) but have no African customs integration, no PAPSS settlement, and no NRS e-invoicing built in. When you deploy them in Nigeria, Ghana, Kenya, or South Africa, you end up building the African half yourself.

The second is **narrow point solutions** - customs-clearing software used by licensed agents, freight forwarder booking portals, payment gateways. Each solves one slice of the puzzle. To run a full African trade operation, you buy four or five of them and stitch them together.

Neither category was built for how African trade actually works. That is the gap OHRES was created to close.

What "Indigenous" Actually Means

The word gets thrown around loosely. Here is what it means at OHRES:

**1. Built in Africa, for African trade.** The team is Lagos-based. The compliance layer understands NCS B'Odogwu, ICUMS in Ghana, KenTrade in Kenya, and SARS in South Africa - because it was written by people who have sat in those customs offices, not by a team in Munich or Chicago reading WCO documentation.

**2. African-owned.** OHRES INC. is a Canadian parent company (Oluwafemi Hughes Resources Inc.) with THE OHRES LTD (RC 9626254) as the Nigerian operating subsidiary. The founder, Albert Oluwafemi Hughes, is African. Decisions are made in WAT business hours, not in an 8-hour-offset support queue.

**3. Full-stack, not point solutions.** Five products, all built and run by the same team: - **Canary EDI** - EDI and VAN services (X12, EDIFACT, AS2, AS4, SFTP, API) - **e-Customs** - customs integration for NCS, ICUMS, KenTrade, SARS - **5PL** - fifth-party logistics: freight, carriers, tracking - **OHRES ERP** - EDI-native ERP with full procure-to-pay - **Portal** - one login and one dashboard across all five

No competitor in Africa offers this combination. Every other provider is either one of these pieces or a foreign version of one.

**4. African-first rails.** - **PAPSS-native.** Payment rails built for the Pan-African Payment and Settlement System, so intra-African trade settles in local currencies instead of USD round-trips. - **NRS e-invoicing.** Built for the Nigeria Revenue Service e-invoicing mandate. - **AfCFTA-aware.** Rules of origin, tariff schedules, and certificate-of-origin workflows are part of the product, not add-ons.

**5. Global reach, African foundation.** This is where the "operates globally" part matters. Being indigenous does not mean being isolated.

• **Peppol-approved.** Final membership payment in progress; the Access Point activates as soon as the yearly subscription completes. Once live, OHRES connects to the Peppol network - 40+ countries exchanging e-invoices and e-orders on one standard.
• **AS2, AS4, SFTP, and API.** OHRES talks to the global B2B infrastructure used by Walmart, Target, Amazon, Costco, Maersk, Hapag-Lloyd, CMA CGM, and every major retailer and carrier.
• **X12 and EDIFACT both native.** American, European, Asian, and African partner formats all parse and generate natively.
• **Multi-carrier track and trace.** Maersk, Hapag-Lloyd, and CMA CGM integrations go live as each carrier activates their API keys. When they do, OHRES provides DCSA-compliant container tracking across the same corridors that global forwarders use.

A Nigerian exporter shipping to Walmart Canada uses OHRES to: - Generate the 856 ASN in X12 - Transmit over AS2 to Walmart - Submit the export declaration to NCS B'Odogwu - Track the container on Maersk - Settle payment via PAPSS - Reconcile against the Walmart 810 invoice

Every one of those steps is an OHRES product. Every one speaks the global standard. Every one is African-built.

Why Global Vendors Cannot Just "Add Africa"

The global vendors are not lazy. It is that African trade is structurally different, and retrofitting it into a system designed for US domestic EDI would break the US product.

Consider what "adding Africa" actually requires:

• **Customs protocol integration per country.** NCS in Nigeria, ICUMS in Ghana, KenTrade in Kenya, SARS in South Africa - each with its own API, credentials, and error handling. NICIS 2 is a different system from ICUMS is a different system from SARS. There is no pan-African customs API.
• **PAPSS settlement.** Not a payment gateway in the traditional sense. Requires Afreximbank membership, local-currency correspondent relationships across 20+ countries, and real-time FX handling.
• **AfCFTA compliance.** Rules of origin logic that runs before shipment, not after. Tariff schedule updates quarterly. Certificate of origin generation.
• **Local language and support.** WAT hours. Local phone numbers. Engineers who can debug a customs rejection in a live call.
• **Pricing for SMEs.** Most African traders are small. The enterprise price point of a global EDI provider is out of reach.

None of that fits in a global platform designed for a US company shipping between American states. Building it as a bolt-on always produces a worse product than building it first.

That is why OHRES exists: because you cannot bolt Africa onto a global platform.

How to Vet Any "African EDI" Claim

If a vendor claims to be African EDI, ask:

1. **Who owns the company?** - Global subsidiary or genuinely African-owned? Subsidiaries route decisions offshore. 2. **Where are the engineers?** - Lagos-based or is support routed through a regional partner? 3. **Where is the customs logic?** - Native in the platform, or a partner integration you have to manage separately? 4. **What's your PAPSS story?** - Native rail or "we support local payment methods" (which is not PAPSS)? 5. **What's your Peppol status?** - Approved Access Point, or "Peppol-ready" (which often means "not connected")? 6. **How many EDI message types do you support natively?** - Under 20 is a point solution. Over 50 is a platform. Over 80 is what OHRES runs. 7. **How many backends power the platform?** - The answer reveals whether you are buying one product or a full stack.

The Bottom Line

Africa does not need another foreign EDI vendor with an African reseller agreement. It needs infrastructure built for how African trade actually works - and that infrastructure needs to connect to the global standards that African businesses trade against.

OHRES INC. is the only company that does both. Indigenous in origin, African-owned, five integrated products, 11 backends, 80+ EDI message types, AS2 / AS4 / SFTP / API, Peppol-approved (final activation in progress), PAPSS-native, customs-aware, multi-carrier track and trace, ERP included, and Lagos-based.

If your business trades across African borders and into the global market, this is the platform your competitors will wish they had chosen first.

**Want to see it live?** Book a demo at /demo or reach us at [email protected].