How does HublerX handle Arabic product descriptions that don't exactly match the ERP product master?

HublerX maintains a GCC product alias table — Arabic and English names, common abbreviations, and local trade names for each SKU — built from historical order data. Where an Arabic description closely matches one SKU, it is mapped automatically. Where it is ambiguous (two possible matches), the coordinator is alerted to confirm. The alias table is updated as new product names are seen in distributor messages.

Can HublerX handle orders from multiple GCC countries with different currencies and pricing schemes?

Yes. Each GCC distributor in HublerX is configured with their country, billing currency (USD, AED, SAR, KWD, QAR, BHD, OMR), applicable export price list, incoterm, and documentation requirements. Orders from different countries are processed with the correct country-specific configuration applied automatically.

What export documentation does HublerX trigger for GCC shipments?

HublerX triggers the documentation checklist based on the destination country's requirements — typically: commercial invoice, packing list, certificate of origin (Indian Chamber of Commerce), halal certificate (for food products), health certificate (from FSSAI or state authority), and any country-specific import permit. The documentation team receives the checklist the moment the sales order is created.

Is this workflow the same as the domestic WhatsApp-orders-to-ERP workflow, or is it separate?

The GCC variant handles additional requirements not present in the domestic workflow — Arabic language parsing, export pricing in foreign currencies, GCC-specific credit limits (often in USD), export documentation triggers, and destination-country compliance checks. The underlying order capture logic is similar, but the configuration and validation layer is specific to export operations.

WhatsApp Orders to ERP — GCC

The Problem

The Dubai distributor places orders on WhatsApp in Arabic. By the time it's in the ERP, it's been misread, repriced, and the ETA is wrong.

GCC distributors — in the UAE, Saudi Arabia, Kuwait, Qatar, Bahrain, and Oman — place B2B orders predominantly over WhatsApp. The orders arrive in a mix of Arabic and English, reference product codes that may differ from the ERP SKU master, and are priced in USD or AED at export rates that are different from domestic pricing. The export sales coordinator receives these messages, translates where needed, looks up the correct SKU code, applies the export price list, checks the distributor's credit limit, and manually keys the order into the ERP.

At each step, errors can enter: wrong SKU if the product description doesn't match exactly, wrong price if the export scheme is applied incorrectly, wrong credit check if the coordinator works off a stale balance, and wrong incoterm if the default ERP setting isn't overridden for this customer. The errors surface at invoice time or at port — when a shipment is held for a documentation discrepancy, or when the distributor disputes the invoice price.

Current Workaround

What most operations do today: Most export operations today: a dedicated export sales coordinator manages the GCC WhatsApp groups, manually translates orders, looks up SKU codes in the ERP, applies the export price list from a shared rate card spreadsheet, keys the order into the ERP, and emails the order confirmation. The rate card is updated monthly but can be out of date by week 3. Credit checks are done by asking the finance team. Documentation requirements — certificate of origin, halal certificate, health certificate — are tracked on a checklist spreadsheet. The process is manual, error-prone, and bottlenecked on one or two coordinators who manage multiple GCC markets simultaneously.

The HublerX Approach

A WhatsApp order from a GCC distributor contains all the information needed to create a validated ERP sales order — product, quantity, required delivery date, and customer. HublerX reads the WhatsApp message, maps the product description to the correct ERP SKU (handling Arabic product names and GCC-specific pack codes), applies the correct export price in the right currency, checks the distributor's credit position, and creates a draft sales order for coordinator review. The coordinator confirms or adjusts; the order reaches the ERP without manual keying, without pricing errors, and with the correct export documentation triggers.

How It Looks in HublerX

Live workflow view

GCC Order Capture Board

14 GCC orders this week

RECEIVED · PARSING2

Al Rawabi Trading — Dubai, UAEWhatsApp · 9:14 AM · Arabic message · 6 SKUsParsingSKU mapping in progress · Pricing being applied

Tamimi Markets — Riyadh, KSAWhatsApp · 10:02 AM · English · 4 SKUsParsingSKU mapped · Credit check running

COORDINATOR REVIEW3

Sultan Center — Kuwait City5 SKUs · KWD 820 · 28 casesReady to confirmAll SKUs mapped · Price validated · Credit OK · Awaiting confirm

Carrefour — Doha, Qatar3 SKUs · USD 1,680 · 18 casesReady to confirmAll validated · Halal cert current · Credit OK

ERP ORDER CREATED4

Al Safi Danone — BahrainSO-9011 · USD 2,840 · 32 cases · Created 8:45 AMERP confirmedDocs triggered: COO, Halal cert, Health cert · Shipping next Monday

Spinneys — DubaiSO-9009 · USD 3,120 · 36 cases · Created yesterdayERP confirmedDocs ready · Container booking Thursday

Nesto Hypermarket — SharjahSO-9007 · USD 1,560 · 18 cases · Created yesterdayERP confirmedProduction confirmed · Dispatch Friday

City Max — Muscat, OmanSO-9005 · USD 980 · 12 cases · Created MondayERP confirmedDispatched Tuesday · ETA Muscat port Sunday

EXCEPTION1

Mega Mart — Jeddah · Credit holdWhatsApp order · USD 3,800 · Credit limit exceededCredit holdAction neededOutstanding USD 28,400 vs limit USD 25,000 · Finance to review

How HublerX Coordinates It

The step-by-step sequence

1
WhatsApp order received and parsed
HublerX monitors the connected WhatsApp business account for incoming orders from registered GCC distributors. When an order message is received, HublerX parses the product names (in Arabic or English), quantities, and any delivery date or special instructions. Product descriptions are mapped to ERP SKU codes using a configured product alias table.
On message receipt · real time
2
Export pricing applied
HublerX applies the correct export price for each line — in the distributor's billing currency (USD or AED), at the applicable export scheme rate for their country and tier. Where a promotional export price is active, it is applied automatically. The pricing is drawn from the ERP export condition records, not from a separate spreadsheet.
On product mapping completion
3
Credit and compliance check
HublerX checks the GCC distributor's credit position — outstanding balance in the relevant currency, overdue invoices, and approved credit limit. It also checks any country-specific compliance requirements for the order: halal certification status, shelf life requirements for the destination market, and any export restriction on the SKU.
Simultaneously with pricing
4
Draft sales order reviewed by coordinator
HublerX presents the parsed and validated order to the export sales coordinator — with the mapped SKUs, quantities, export prices, delivery date, incoterm, and credit status. The coordinator reviews the draft, makes any corrections, and confirms. The order is not created in the ERP until the coordinator confirms.
On draft assembly · coordinator action
5
ERP sales order created with export configuration
On confirmation, HublerX creates the sales order in the ERP with the correct export configuration: shipping point, incoterm, currency, export pricing condition, and the distributor's country-specific plant. The order confirmation is sent back to the distributor on WhatsApp automatically — in English or Arabic based on their communication preference.
On coordinator confirmation
6
Export documentation triggered
The ERP sales order creation triggers the export documentation checklist in HublerX — certificate of origin, halal certificate, health certificate, packing list, and commercial invoice — based on the destination country's requirements. The export documentation team receives the task list the moment the order is confirmed, not the day before the container is sealed.
On ERP order creation