(✦) — General Trading & Wholesale Distribution (B2B)
We build catalogue and quotation websites for trading companies, wholesalers and distributors in Dubai and across the UAE. Help buyers find products, check specifications and send a useful enquiry. See our SFGT build, then define the languages, product structure and sales handoff your business needs.
Find the model. Check the details. Send a useful enquiry.
A website where a business buyer can identify a product, review the available information and send the details your team needs for a quotation.
See the work(01) — Selected work
(✦) — The B2B buying problem
A buyer may know a model code, a specification or only the application. If the website cannot connect that starting point to a product and an enquiry, your sales team has to reconstruct the request in email or chat. The design needs to support that decision before asking someone to contact you.
Supplier folders and PDF names can hide the product families a buyer expects to browse.
A model name without units, pack details or a relevant data sheet leaves the buyer with more questions.
A generic message does not tell the team which code, quantity or destination the buyer had in mind.
New ranges, revised files and translations need a clear owner and an agreed publishing workflow.
206
Products in SFGT’s source catalogue
Model codes, supplied details and enquiry context.
63
Categories in the same catalogue
Batteries, lighting and commodities.
English + Arabic
SFGT navigation and enquiry interfaces
Original supplier technical content remains English.
(✦) — What we can build
Organise brands, divisions, families and identifiers so buyers can browse a range or look for a known model.
Present supplied measurements, units, pack formats, documents and images together. Missing product information is identified before publication.
Carry product details into the enquiry and collect relevant quantities, destinations and requirements. Confirm the receiving team and next step.
Plan navigation, search and forms for smaller screens and both reading directions. Agree which supplier data needs translation.
Choose between managed content updates, a CMS or custom administration based on who edits products and how often. Editing tools are scoped explicitly.
Build useful product pages, clear internal links and language alternatives. Inventory old URLs and map replacements when moving an established site.
Choosing the right website
A catalogue and request-for-quotation website suits products whose price or supply terms depend on quantity, destination or specification. A wholesale checkout needs more decisions: customer approval, minimum quantities, account prices, tax, payment and fulfilment. Those requirements shape the system. We scope wholesale website development after understanding how an order is actually accepted; SFGT demonstrates the catalogue and enquiry route.
A battery pack and a lighting model need different attributes. We define shared fields such as brand and model code, then the specifications each range needs. Search filters must reflect reliable data. For SEO, a useful category page answers a distinct buying question; filter combinations should not generate repetitive pages. When replacing a site, existing product links need a checked destination alongside the new structure.
A small range updated occasionally can use managed content changes. Frequent additions or multiple editors may justify a CMS or custom administration. An ERP or CRM connection needs separate discovery: the source of product data, fields to synchronise, lead ownership, permissions and failed-update handling. Agree responsibilities before choosing the editing or integration tools. These options receive their own scope and quotation alongside the public website.
(03) — How we approach it
We start with a sample of your catalogue and a real enquiry your team receives. Together, we map the categories, model codes, specifications and questions that help a buyer identify the right product. Then we define the handoff: what the website collects, where the enquiry goes and who follows it up. Content, translation ownership and maintenance are agreed alongside the design.
(04) — What's included
(05) — How we deliver
A representative sample exposes catalogue and enquiry questions while they are still straightforward to resolve.
Review sample records, source files, existing URLs, languages and the details your sales team asks buyers to supply.
What you review
Decision: Confirm data gaps and who owns each source.
Prototype a category, a product and the quotation flow on mobile and desktop before extending the design.
What you review
Decision: Approve how a buyer identifies a product and contacts you.
Implement the agreed catalogue, language scope and enquiry handling. Treat CMS and integration work as explicitly scoped additions.
What you review
Decision: Check representative records and enquiry states.
Review links, redirects, responsive layouts and delivery configuration, then document the content-maintenance workflow.
What you review
Decision: Agree launch readiness and ownership after handover.
(✦) — Why NxFold
SFGT is our documented general trading example: a website for Sulemane Faruk General Trading LLC in Dubai. Explore its product pages and journey from catalogue to enquiry. The case study explains the delivered structure and technical content, with pricing and supply terms handled by the business.
Review the SFGT case study and the actual interface before discussing which parts fit your company.
We use representative product records to test the structure before repeating it across the catalogue.
Enquiry fields, recipients, delivery configuration and failure messages are part of the brief.
CMS tools, account pricing and external integrations receive their own requirements and quotation.
(✦) — Who this is for
Ranges with model codes, pack formats and technical specifications that buyers need to identify accurately.
Product families, data sheets and application information that support procurement enquiries.
Distinct divisions with different requirements for quantity, destination and supply discussions.
Businesses deciding between a public catalogue, quotation requests and a transactional wholesale portal.
(✦) — Explore next
Industries
(06) — FAQ
Everything you need to know before we start.
Catalogue size and data quality, page types, languages, search filters, enquiry requirements and migration work affect the scope. CMS tools and ERP or CRM connections add separate work. Share sample products and your current site so we can prepare an itemised quotation and milestone plan.
Yes, when editing tools are included in the agreed scope. We assess who maintains the catalogue and how often it changes before proposing managed updates, a CMS or custom administration. The quotation defines the editing functions and handover your team receives.
We can scope a connection after reviewing the system, available API, data ownership and enquiry workflow. The quotation identifies what is read or written and how failures are handled. The integration has its own requirements, quotation and validation plan.
Translation scope is agreed field by field. Arabic navigation, forms and RTL layouts can coexist with original English model names and technical documents. SFGT uses that approach. Full technical translation requires accurate source material and review by someone who understands the products.
We agree the receiving team, required buyer details, sending configuration and the messages shown if delivery fails. Before launch, we test the agreed delivery route and fallback so visitors have a clear next step.
We map categories to buyer intent, write distinct page metadata and plan internal links, canonicals, language alternatives and a sitemap. Existing URLs are inventoried for redirects. After launch, Search Console and enquiry data help identify which pages need better content or clearer next steps.
(✦) — Planning a catalogue or quotation website?
Tell us your product count, required languages, who maintains the catalogue and how enquiries reach sales today. We will use that to define the website and any separately scoped editing or integration work.
Dubai · Abu Dhabi · Sharjah · GCC · International
(✦) — Contact
Tell us about your project and we'll get back to you within 24 hours.
Senior designers and engineers are your project team, from brief to launch. You'll always talk to the people actually building it.
Your project brief
Talk to us directly
