General
Company information, a general commercial question or a request that does not fit a specialist route.
trade@example.comFor product enquiries, supplier submissions, RFQs or partnerships, share the request type and essential context so it can follow the right route.
Each route maps to a dedicated configurable email so the template can be adapted without rewriting the page.
Company information, a general commercial question or a request that does not fit a specialist route.
trade@example.comProduct, quantity, destination, target timing or a structured request for quotation.
rfq@example.comManufacturer or supplier introductions, product information and readiness documents.
suppliers@example.comDistribution territories, route-to-market capability and potential commercial collaboration.
partners@example.comReplace the Demo values in config.js; the page and global footer inherit the configured contact data.
Doha, Qatar — illustrative
This visual intentionally avoids map coordinates, embedded providers or directions because the default ORIGEX address is Demo content. Replace the address and connect a map only when the business location is verified.
Move directly into the structured RFQ or supplier-submission flow instead of repeating the same information in a general message.